michael scheidell gyutuumwjsecnapnet francesco abeni date tue 19 feb 2008 115559 0100 subject ot bogus mx opinions good morning everyone im charge reducing spam customer site already spamassassin saupdate weeklyexecuted id like implement bogus mx filtering spam dont know correct name bogus mx mean setting low priority mx record points nonsmtp server use bogus mx lowest priority 1 mis configured mta legit sources hit low mta stop 2 dont lot spam go highest mx 3 even fully rfc compliance mtas may see hit low mx delay checking higher one 30 mins 2 hours might well implement greylisting dont 4 dont use bogus mx record 127001 rfc1818 ip cname etc get blacklisted rfcignorantorg bogus mx list run hosted antispam service based spammertrap product client see 30 spam hitting highest mx record domains three mx records see 25 spam hitting mx 2 35 hitting mx3 dont ask dont understand looks like malwarespam sent mx2 smart enough look last mx record answer 1 use low priority lose email delay email answer 2 use higher priority mx reduce spam free also depending mta type using something like pblspamhausorg blacklist much better job _________________________________________________________________________ email scanned certified safe spammertraptm information please see httpwwwspammertrapcom _________________________________________________________________________ thu 07 aug 2008 001414 0500 ot bogus mx opinions