Pete wrote:
gunnar@xxxxxxxxxxxx wrote:
Yes, why not? The only case when SPF would stop them is if
- somebody registers say the address webring@xxxxxxxxxxx,
where would they register this address?
Via the form for submitting a new ring. I'm simply talking about the
ringmaster address they submitted.
- there is an SPF record for example.com (with '-all') that does
not state gunnar.cc as an allowed server, *and*
- the ring member's mail server rejects messages because of SPF
failures.
Okay, then give me examples of sending servers I would need to
identify?
Thought I did that.
Sending what?
??
v=spf1 a a:webringworld.org -all
'using @webring.cc addresses at webringworld.org'
Seems to me that I do not need to identify any sending servers,
because I am not using @webring.cc addresses on any other domains, or
am I?
Nobody but you can tell.
The reason why I included 'a:webringworld.org' in the suggested SPF
record for webring.cc is that I happen to know that you manage a few
webrings hosted at webringworld.org, and I assumed that you may have
used @webring.cc addresses as ringmaster addresses (or master admin
address) there.
Just curious why AOL uses '?all'?
Probably to not stop their users from sending from AOL addresses via
non-AOL mail servers.
--
Ringlink http://www.ringlink.org/
"created by ringmasters for ringmasters"