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. Yes, about 1/3 of SMTP senders have misconfigured HELO names,
but their general incompetence means they're unlikely to implement any
anti-spam protocol. And in any case, that's not a technical problem that
can or should be addressed by a technical specification.
I'm talking about implementations barriers.
How about ESMTP AUTH state machine conversation issues?
Irrelevant.
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.
Tony.
--
f.a.n.finch <dot(_at_)dotat(_dot_)at> http://dotat.at/
BISCAY: WEST 5 OR 6 BECOMING VARIABLE 3 OR 4. SHOWERS AT FIRST. MODERATE OR
GOOD.