> I do not get it. localdomains in external sender means mostly spam, > so why include them in IPWL?
If you can't use spf on your domain is because localdomains in external sender are NOT spam ! Consider this scenario: We all get a @asspspmt.org email address, and of course we use our local smtp server. More than one, because in the office I use a different smtp server than when at home, and a different when I use gprs connection. So when I write to you there is a mail from [EMAIL PROTECTED] to [EMAIL PROTECTED] In that example you can't use a dns spf record, because you don't know all originating servers, and it's all good mail. In any case I see no harm in excluding localdomains from that check, because *IF* I can have a SPF dns record for my domain all spoof will be detected and blocked with the assp-spf check, not locking the domain ! So, if you can use a DNS SPF record, that's the way to go. Use it. But when you can't (because you can't list all originating ip) you risk having your own "domain blocked" ! And after a few retry also a valid originating ip blocked. Don't forget all this started because in the last spam wave I observed yesterday the spammer was sending the mail from [EMAIL PROTECTED] to [EMAIL PROTECTED] That spam strategy can easily block my own domains per maxSMTPdomainIPExpiration seconds ! Sort of a DDOS in many scenarios. Am I wrong here ? ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
