[Asrg] MTA registration means Path registration

[Dave Crocker <dhc at dcrocker.net>]

Alan,

AD>   Maybe I'm missing something.
AD> http://www.ietf.org/internet-drafts/draft-mengwong-spf-01.txt
 AD>   Doesn't even mention RCPT TO.  Therefore, SPF cannot bind anything to
AD> an email sender/recipient pair (referring to people/accounts, not
AD> domains).


A message follows a path.  A path is from an originator to a recipient.

That is, a message goes from the originator, through a sequence of
MTAs, and gets delivered to the recipient.  The sequence from the
originator to one recipient can and will be different than to another
recipient.

Any receiving SMTP server may attempt to validate an incoming message.

(If there are restrictions on which SMTP servers are expected to do
validation, please show me where that is in the specification and
explain to me how the expectation will be satisfied in real life.)

Absent restriction on which MTA may perform validation, any receiving
MTA may do it on any incoming message.

With SPF, they do that validation by check the sending client MTA
against a registration made by the domain cited in RFC2821.MailFrom.

Since RFC2821.MailFrom derives from the author of the message, this
means that the author needs to have a registration that authorizes each
sending SMTP client along the path.

Hence the originator will need to register every path of MTAs to every
recipient.


>> That is quite different form what you said.
AD>   My statement was true, even in your re-definition of SPF.

I did not redefine SPF.  Since you think I did, please tell me what
statement I made that deviated from SPF semantics.

d/
--
 Dave Crocker <mailto:dcrocker at brandenburg.com>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>


_______________________________________________
Asrg mailing list
Asrg at ietf.org
https://www1.ietf.org/mailman/listinfo/asrg