{"id":62,"date":"2007-10-04T11:36:33","date_gmt":"2007-10-04T16:36:33","guid":{"rendered":"http:\/\/c-command.com\/blog\/?p=62"},"modified":"2007-11-28T10:51:11","modified_gmt":"2007-11-28T15:51:11","slug":"catching-spams-from-your-address","status":"publish","type":"post","link":"https:\/\/c-command.com\/blog\/2007\/10\/04\/catching-spams-from-your-address\/","title":{"rendered":"Catching Spams From Your Address"},"content":{"rendered":"<p>If blatant spam messages keep getting through to your inbox, one possibility is that there\u2019s a <a href=\"http:\/\/c-command.com\/spamsieve\/manual-ah\/why-is-spamsieve-not-ca\">setup problem<\/a> such that SpamSieve was not asked to filter those messages. Another possibility is that the spammer forged one of your addresses, the sender address is in Address Book, and SpamSieve let the messages through because you had told it that the addresses in your address book never send spam. You can see whether this is the case by <a href=\"http:\/\/c-command.com\/spamsieve\/manual-ah\/open-log\">checking SpamSieve\u2019s log<\/a> to see if the message was <tt>Predicted: Good<\/tt> because <tt>Reason: sender <em>address<\/em> in address book<\/tt>. For safety reasons, the address book has <a href=\"http:\/\/c-command.com\/spamsieve\/manual-ah\/filters\">higher precedence<\/a> than the blocklist and Bayesian classifier, so training won\u2019t affect these messages.<\/p>\n<p>Even if the message got through because of the address book, you probably don\u2019t want to uncheck <a href=\"http:\/\/c-command.com\/spamsieve\/manual-ah\/use-mac-os-x-address-bo\">Use Mac OS X Address Book<\/a>. It\u2019s a useful safety feature that lets you be sure that messages from certain people will always get through. Instead, it\u2019s time to use a lesser known SpamSieve preference called <a href=\"http:\/\/c-command.com\/spamsieve\/manual-ah\/exclude-my-addresses\">Exclude my addresses<\/a>. What this means is that if you receive a message from one of your own addresses, SpamSieve will pretend that the address isn\u2019t in Address Book and it will look at the entire contents of the message in order to classify it. Messages from your contacts will continue to get through, but messages from your own address will get extra scrutiny, in case the address was forged. (This also works if you\u2019ve told SpamSieve to use the Entourage address book.)<\/p>\n<p>How does SpamSieve know whether the address is one of your addresses? It looks at the \u201cMe\u201d card in Address Book, which you can access by choosing <strong>Card \u2023 Go to My Card<\/strong>. Make sure that all of your e-mail addresses are listed on this card. You can use the <strong>SpamSieve \u2023 <a href=\"http:\/\/c-command.com\/spamsieve\/manual-ah\/update-address-book-me\">Update Address Book \u201cMe\u201d Card<\/a><\/strong> command to automatically add the addresses from the accounts in your mail program to the \u201cMe\u201d card.<\/p>","protected":false},"excerpt":{"rendered":"<p>If blatant spam messages keep getting through to your inbox, one possibility is that there\u2019s a setup problem such that SpamSieve was not asked to filter those messages. Another possibility is that the spammer forged one of your addresses, the sender address is in Address Book, and SpamSieve let the messages through because you had [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[2],"tags":[],"_links":{"self":[{"href":"https:\/\/c-command.com\/blog\/wp-json\/wp\/v2\/posts\/62"}],"collection":[{"href":"https:\/\/c-command.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/c-command.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/c-command.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/c-command.com\/blog\/wp-json\/wp\/v2\/comments?post=62"}],"version-history":[{"count":0,"href":"https:\/\/c-command.com\/blog\/wp-json\/wp\/v2\/posts\/62\/revisions"}],"wp:attachment":[{"href":"https:\/\/c-command.com\/blog\/wp-json\/wp\/v2\/media?parent=62"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/c-command.com\/blog\/wp-json\/wp\/v2\/categories?post=62"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/c-command.com\/blog\/wp-json\/wp\/v2\/tags?post=62"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}