spf-discuss
[Top] [All Lists]

Re: Re: DEPLOY: SPF/Sender ID support in Courier.

2004-08-29 19:03:23
In 
<Pine(_dot_)LNX(_dot_)4(_dot_)44(_dot_)0408290948120(_dot_)23504-100000(_at_)sokol(_dot_)elan(_dot_)net>
 "william(at)elan.net" <william(_at_)elan(_dot_)net> writes:

On Sun, 29 Aug 2004, wayne wrote:

In which case why is it being considered by (and developed in) the
"MTA Authorization Records in DNS" Working group? If it is aimed at
MUAs and is not relevant to MTAs then it should be rejected (or should
already have been rejected) as being off-charter.

The MTA being authorized is the sending MTA.  Whether the
authorization is done by the receiving MTA or the receiving MUA is
irrelevant.

You're way wrong on this one. It can ONLY be done by receving MTA as
MUAs are not participant in SMTP session and only pickup email from
mailbox after the fact. MUAs have no reliable way to know identity
of SMTP server(s) previously involved in email transmission [...]

The point remains that authorization is about the the sending MTA.

Spamassassin already does identifies the SMTP servers involved with
receiving the mail.  It does so by looking at the Received: headers.
Yes, it is not 100% accurate, but that is irrelevant.


[long list of advantages of doing checks during the SMTP session]

I agree with those, but again, they don't change what is being
authorized.


-wayne


<Prev in Thread] Current Thread [Next in Thread>