-----Original Message-----
From: owner-spf-discuss(_at_)v2(_dot_)listbox(_dot_)com
[mailto:owner-spf-discuss(_at_)v2(_dot_)listbox(_dot_)com] On Behalf Of David
MacQuigg
Sent: dinsdag 24 mei 2005 20:03
To: spf-discuss(_at_)v2(_dot_)listbox(_dot_)com
Subject: RE: [spf-discuss] Email ID Declaration - Summary of
Objections
Your ID, otoh, is no more
than a glorified extra HELO; and who needs that?
!!! Where did you get this? The new ID *can* be the same as the HELO
identity, but probably only the CSV folks will insist on that.
If the CSV folks would insist on ID being the same as HELO, then they
would insist on the uselessness of ID. :) And, in fact, CSV bases
everything, including reputation, on the EHLO string (or a
derivative thereof;) like so:
mailhost IN A 199.201.159.9
IN PTR _vouch._smtp.csv_vouch
_client._smtp.mailhost SRV 1 2 0 mailhost
Exit ID.
As I understand it, the HELO identity is supposed to be the
hostname of the sending MTA.
Exactly.
That is not the best place to accumulate
reputation,
What better place to check the reputation of the sending MTA than at the
identity which is supposed to be the hostname of the sending MTA? Your ID,
otoh, can be anything (presumably a domain name); and because it can be
anything, it is nothing. Unless you do SPF checks on it -- in which case
you can already gather everything you need at HELO or MAIL FROM.
- Mark
System Administrator Asarian-host.org
---
"If you were supposed to understand it,
we wouldn't call it code." - FedEx