Those three are mainly there so that the amount of mail going through the fourth step is minimised.
Unfortunately, there's a flaw. *Some* spammers *do* fall back to secondary MXes so can get around the first filter. Then other spammers go straight to the secondary MXes and don't bother with the primary. And finally, spamassassin isn't perfect. There's not a lot I can do about the latter, but I can help it. So as of a few days ago, there's another little filter just before mail gets to spamassassin. It looks for messages that have been delivered by my secondary MX, then looks at the host that the secondary received the message from. If that host is in my blacklist, it adds a header like:
X-Dodgy-Received: blacklisted netblock (218.82.225.65 is in 218.64.0.0/11)
the presence of which means a positive spamassassin score. The number of spams getting through to my inbox is now noticeably lower. Source code available on request.
request! (Score:1)
Re:request! (Score:1)
Change your email address periodically.
Like... every minute! :-\
Re:request! (Score:2)
Any message which goes through your secondary MX will have a header inserted to tell you whether it came to the secondary from a blacklisted or whitelisted host, or whether the sending host is neither black- or white-listed.