Bookworm wrote:
I think I can say that even as a casual user of the list (I only take
care of about 10 smaller mail systems), I find the discussions more
useful than not. I would have little to no use for the direct SPF
mailing list - but in so far as it applies to anti-spam, I'm more than
interested in pros and cons. Marc's brought up some arguments that
are useful to me, so have others (both for and against)
To throw in my two bits (inflation), I have no published an SPF record
for any of my domains.
BW
This is all simple. SPF says that mail; from netflix.com can only come
from server A. So if someone forwards an email account to another server
that checks SPF and says, this email isn't from a valid netflix server
so it must be forged. This applies to front end spam filtering services
as well, mine in particular.
So people email me and say, "Why am I not getting any of my Netflix
email anymore?" Reason - their email server is bouncing the netflix
email as forged because of SPF.
So - I could do SRS bu then all the email they receive will be from
[EMAIL PROTECTED] and I'm sure my customers do not want
their email modified to come from my domain. What they want is for email
to pass my servers as transparently as possible.
So - in short - SPF breaks email forwarding UNLESS everyone change their
email systems to support SRS. That is NOT going to happen, therefore
email forwarding is broken.
So - which is more important to be compatible with. A useless SPF
standard that has NO UPSIDE at all, or email forwarding?
