On Sat, 18 Jul 2009, Michael Deutschmann wrote:
On Fri, 17 Jul 2009, Stuart D. Gathman wrote:
Since everyone is shooting down my v3 ideas with "here's how you could
do it in v1", let me shoot yours down. :-) All(!) you have to do is
have your MTAs encode the sender in the helo name it uses when
transmitting the email.
That won't work. The problem cases involve hops after the e-mail leaves the
sender's servers. The HELO the broken receiver will see, will be the name of
the backup MX, or the forwarder's mailserver -- not what the sender used.
Duh. I'm an idiot.
--
Stuart D. Gathman <stuart(_at_)bmsi(_dot_)com>
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
-------------------------------------------
Sender Policy Framework: http://www.openspf.org
Modify Your Subscription: http://www.listbox.com/member/
Archives: https://www.listbox.com/member/archive/735/=now
RSS Feed: https://www.listbox.com/member/archive/rss/735/
Powered by Listbox: http://www.listbox.com