> There is also nothing stopping a static bulk mailer from > implementing SPF on their own system, and to my knowledge, > there is no way to stop that from happening.
That is correct. As somebody else has said passing the SPF does not mean the email isn't spam, and as SPF states it is aimed to work in line with existing black lists. In that scenario it would prevent the spammer from hijacking somebody else's domain. And as you said, if static bulk mailers implemented SPF on their own domains, they'd be somewhat easier to blacklist. > To each their own of course. I'm just trying to document > some of the issues that people should look out for when > implementing SPF for their domains, and scoring it on their systems. I'm sure your input is appreciated, the replies you have generated from other members of the list have helped me see more pros in SPF in the number of ways it is beneficial. You have certainly prompted more of a discussion which may have helped other people on the list understand, or made aware of SPF. Regards, Lyndon. ************************************************ Email checked by UKsubnet anti-virus service To prevent email abuse & block spam contact [EMAIL PROTECTED] Tel: +44(0)8712360301 Web: www.uksubnet.net Fax: +44(0)8712360300 Powered by UKsubnet Internet Service Provider Business to Business Internet (ISP) ************************************************ --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
