You have to set up an SPF record for each of the domains anyway, since the SPF record resides in the DNS of the sending domain, so I don't see that it's a big deal.
Bottom line: It's a useful tool. Not as useful as originally intended, but still useful. Use it or don't at your discretion. Darin. ----- Original Message ----- From: "Tyran Ormond" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Thursday, September 08, 2005 11:09 AM Subject: Re: [Declude.JunkMail] SPFPass - good or bad? On 10:32 AM 9/8/2005 -0400, it would appear that Darin Cox wrote: >Regarding the situation you outlined, SPF can be easily configured to >specify the server that mail is forced through as the sending server. SPF >records can also be designed to inherit other SPF records, so if an ISP has >SPF defined, then customers who manage their own SPF records can specify to >inherit the ISPs SPF record, thus avoiding having to know and specify all of >the ISPs sending servers. That still means that I have to setup includes for each of the possible sending domains, still unacceptable and reason enough for me to discard SPF completely. Tyran Ormond Programmer/LAN Administrator Central Valley Water Reclamation Facility [EMAIL PROTECTED] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com. --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
