On Thu, 14 Apr 2005, Hector Santos wrote:
Come on Tony. CSV's client FQDN requirement mandates change across the
board, including MUAs, MSAs, MTAs and MDAs, as well to satisfy the
chain of trust in order to effectively work.
No, it's only for use across the pulic Internet, so MDAs and MUAs are
irrelevant.
Specifically, CSV takes place between an immediate SMTP client and the SMTP
server it is talking to directly. No other part of the email service is
affected.
It uses a domain set by the administrator of that client. So no other part of
email administration is affected.
The domain reflects an operation identity, so no other participants in the
email service are involved.
Changes to the SMTP client might be zero; the only SMTP client requirement is
to use a HELO/EHLO domain name that is authorized by the administrator of the
client's operation.
Changes to the SMTP server would need to be more extensive, since it must
implement the rest of the CSV semantics.
I'm talking about implementations barriers.
How about ESMTP AUTH state machine conversation issues?
Irrelevant.
Correct. I cannot even guess how one would think smtp auth was involved.
How about 80% of all transactions being spoofed or NXDOMAIN at the
returned path?
How about 50-65% of all transactions being having invalid forwarding
paths?
Not within CSV's scope.
Correct. CSV has nothing to do with the RFC2821.MailFrom command or address.
In any event, this thread is about "DNS Loading". And this recent portion of
the thread has nothing to do with that.
But that portion has made up for the digression by accomplishing nothing very
productive, from what I can see.
d/
---
Dave Crocker
Brandenburg InternetWorking
+1.408.246.8253
dcrocker a t ...
WE'VE MOVED to: www.bbiw.net