----- Original Message -----
From: "David" <david(_at_)ols(_dot_)es>
Newsgroups: spf.-.sender.policy.framework.discussion
To: <spf-discuss(_at_)v2(_dot_)listbox(_dot_)com>
Sent: Sunday, September 11, 2005 4:58 AM
Subject: Re: [spf-discuss] solving the forwarding problem
David, do you think the MTA that is broken is going to add logic to
support
a new header? Do you think they will fix MAIL FROM modifiers at this
point?
Or do you think the administrator will update his POST SMTP software but
not
update his SMTP server?
those are totally diferent things, i propose that the header should be
added by the sender's mta which is publishing spf records, which is
trivial as most mailers can do that. All other do not need to add any
header. For smtp arguments to work ALL involved mta's MUST support them
for it to work, which requires is almost all cases to upgrade the mta
software. Two VERY different things.
No really. See below.
BTW, i left the idea of a new header.
Ok, but my point was if the sender's MTA would be given more intelligence
to do add a header and it reliability is purely based on a compliant
enhanced receiver to read this new special header, then it should also be
intelligent enough to fix its MAIL FROM modifier support which I believe you
claim to be widely broken.
Three things:
1) I assert that that is the not the case (MTA are widely broken to
correctly read the MAIL FROM);
2) more importantly, you can't design software purely based on the idea that
software is broken. It doesn't work very well that way; and
3) you might as well use a MODIFIER like the SUBMITTER proposal to
accomplish the same task of addressing transition points.
--
Hector Santos, Santronics Software, Inc.
http://www.santronics.com
-------
Sender Policy Framework: http://spf.pobox.com/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com