On Sep 11, 2004, at 8:56 PM, Matt Kettler wrote:
At 12:18 PM 9/11/2004 -0700, p dont think wrote:BEWARE, however, that SPF is a hotly contested technology that breaks forwarding in many cases
True, but if your domain is used for forwarding, you can simply not publish SPF records, or publish wide-open ones. However, this is really something for the administrator of the domain to decide based on how his/her domain works.
But even if *I* don't use forwarding, one of my customers may. For example, if I need to email a customer of mine who is using, say, ieee.org forwarding, and it is redirecting to AOL, my SPF records will cause AOL to reject my message to my customer. The email recipient really has no control over any of the SPF records, since he owns none of the domains in question. I publish SPF records because we're forged constantly.
smime.p7s
Description: S/MIME cryptographic signature
