On Freitag, 17. März 2006 00:25 Mathias Homann wrote: > One day, i get a ticket in our ticket system, which sums up as "we > need to have spf records, and we need them now, because that guy at > $SOMEOTHERCOMPANY says so, so that our newsletter is less likely to > get flagged as spam." > > When you think about it, it even makes sense.
SPF is not intended to be a flag of whether or not a mail is SPAM. Any spammer can setup SPF records. SPF can only assure that the owner of the domain can control which SMTP are allowed to send mail for that domain. Nothing more. And if there is no SPF for a domain, that doesn't means it's likely SPAM - and if there are SPF records, it doesn't mean it's HAM. > One day, spamassassin seems to think that this newsletter, send to my > private email, is spam. This leads to me running it through > spamassassin in debug mode... and what do I see... > The guy at $SOMEOTHERCOMPANY has set up SPF records for their systems > as well... and has NOT included the server that gets fed the > newsletter... I had the same problem with a customer. Easy to solve, just another entry into the SPF record. SPF has its edges. Especially for e-mail forwarding it's a PITA. I have some accounts doing that, needing not just a redirect but a resend. But after all, SPF helps prevent forged senders - IF the recipient checks SPF records. There are still too many servers not doing that. mfg zmi -- // Michael Monnerie, Ing.BSc --- it-management Michael Monnerie // http://zmi.at Tel: 0660/4156531 Linux 2.6.11 // PGP Key: "lynx -source http://zmi.at/zmi2.asc | gpg --import" // Fingerprint: EB93 ED8A 1DCD BB6C F952 F7F4 3911 B933 7054 5879 // Keyserver: www.keyserver.net Key-ID: 0x70545879
pgpet5tvwEZlq.pgp
Description: PGP signature
