Matt,
I
think the point is, that there are TWO different decisions:
a) can you implement SPF for your own domain - you say
"No" - then don't.
b) can you follow the SPF policies that OTHER
administrators set for THEIR domains - apparently they want you
to.
IF
someone created an SPF policy (even if you can NOT for YOUR domains) and IS able
of using "-all" and your server gets an email that violates the stated policy,
then you are doing YOUR customers a favor in not delivering that
message.
Example, I host hundreds of domains that have no associated email
accounts and are not using for outbound messages. I would only HOPE that you
would NOT deliver spam or viruses generated as [EMAIL PROTECTED]!
Because then YOUR costumers will try to send me (as the hoster) SPAM by
complaining about viruses and/or advertisements that used a fake domain of
@Gameware.com. Best
Regards |
Title: Message
- RE: [Declude.JunkMail] SPF Lyndon Eaton
- RE: [Declude.JunkMail] SPF R. Scott Perry
- RE: [Declude.JunkMail] SPF Lyndon Eaton
- Re: [Declude.JunkMail] SPF Matt
- RE: [Declude.JunkMail] SPF Kevin Bilbee
- Re: [Declude.JunkMail] SPF Matt
- RE: [Declude.JunkMail] SPF Kevin Bilbee
- RE: [Declude.JunkMail] SPF Kami Razvan
- Re[2]: [Declude.JunkMail] SPF Sanford Whiteman
- Re: [Declude.JunkMail] SPF Matt
- Re[2]: [Declude.JunkMail] SPF Andy Schmidt
- Re[2]: [Declude.JunkMail] SPF Sanford Whiteman
- Re[2]: [Declude.JunkMail] SPF Sanford Whiteman
- RE: [Declude.JunkMail] SPF Lyndon Eaton
- RE: [Declude.JunkMail] SPF R. Scott Perry
- RE: [Declude.JunkMail] SPF Lyndon Eaton
- RE: [Declude.JunkMail] SPF Lyndon Eaton
- RE: [Declude.JunkMail] SPF Lyndon Eaton