Example of CSV in action:
Received: from harry.mail-abuse.org (Harry.Mail-Abuse.ORG [168.61.5.27])
by sb7.songbird.com (8.12.11/8.12.11) with ESMTP id i96JqBJH026149
for <ietf-clear(_at_)mipassoc(_dot_)org>; Wed, 6 Oct 2004 12:52:12 -0700
dig _client._smtp.harry.mail-abuse.org SRV
(Catching my own error...)
reply includes:
_client._smtp.harry.mail-abuse.org. 86400 IN SRV 1 2 0 harry.mail-abuse.org.
harry.mail-abuse.org. 86400 IN A 168.61.5.27
And indeed, 168.61.5.27 is the IP that wished to send the message.
Prolly worth mentioning this as a guide. Showing a clip from a zone
file would be helpful too.
Given that CSV requires far fewer admins take action, we're likely to
see stupid^H^H^H^H^H inappropriate comparisons, like # of domains
publishing SPF vs # publishng CSV, given that most domain owners that
would benefit from CSV don't need to have CSV records.
On 10/8/2004 1:42 PM, Matthew Elvey sent forth electrons to convey:
Authors, has anyone published CSV records that you know of?
dig _client._smtp.harry.mail-abuse.org PTR