> So really it somes down to , on failure: > > Either > 1) the sender gets an email from [EMAIL PROTECTED] that the email > sent to [EMAIL PROTECTED] did not work out, which confuses the hell out of > the sender, cause he/shee sent it to [EMAIL PROTECTED] > 2) the sender gets an email from [EMAIL PROTECTED] that the email > sent to [EMAIL PROTECTED] did not work out, which confuses the hell > out of the sender cause the person exists.
Assuming the SPF flags are set in a manner that those responses are appropriate for the AOL server, yes. > Does this not mean that exchange will need to do this by default when > setting a CR (assuming MS will provide this SRS functionality in a > patch) It would need to do it for messages which originated from a domain other than one listed in the default recipient policies, when the CR has a primary address which is not in the default recipient policy. And then everyone needs to apply the patch or upgrade to a version of the software which has the patch available (Odds on a 5.5 version of the patch are probably nil.) And Microsoft is working on Sender-ID, so the odds they would release an SPF specific patch in lieu of a patch which includes a superset of the functionality is also pretty low IMO. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
