Not a complete misunderstanding.
The SPF initiative is to have something on DNS that verifies the IP a
message can come from. So, even if your domain was identified as
allowed, they don't want to accept Email unless they can verify that
Email with that domain should initiate from the specific IP that's
connecting to dump mail off.
I'm surprised that AOL is blocking this way. I knew that a lot of major
ISPs were jumping on the bandwagon, but I didn't realize SPF had the
kind of penetration that would allow you to only accept Email based on
The good news is that the SPF record is easy enough to create.
PS: Vote "yes" on interesting to me, also (although agree it is
unrelated to this list).
[mailto:owner-mhonarc-users(_at_)mhonarc(_dot_)org] On Behalf Of Gunnar
Sent: Tuesday, October 19, 2004 2:13 PM
Subject: Re: OT: AOL filters
Quoting Tom Patterson (pattersontom(_at_)earthlink(_dot_)net):
I have been experiencing delivery problems with a mailing list
digest for those on the list using AOL. Below is the information
which I received concerning the problem. Has anyone else found a
solution to the difficulty?
Use SPF on your outgoing mail server, and sign up to be whitelisted
at AOL. This will include setting up a 'feedback loop' so that
complaints from AOL members can be routed to you for removal.
I have done this and have experienced no difficulties in delivering
mail to AOL since.
Hmm.. Off topic or not, I for one find this interesting, and I hope
that others do as well.
A first observation is that nothing about SPF or AOL's whitelist was
mentioned in the information that Tom posted.
Then I can't help making a reflection: If I run a mailing list, and one
or more with AOL addresses subscribe, I feel it's not right that *I* am
the one who need to do stuff in order for the list messages to be
delivered. Wouldn't it be much more reasonable that the AOL address
holders were required do whichever "whitelisting" measures are needed?
Something must be wrong. Or have I misunderstood it all?