Jeff, based on the thread in DKIM
http://mipassoc.org/pipermail/ietf-dkim/2011q2/016476.html
You might wish to consider adding a new X.8.27 extended status code
for ADSP related rejects:
554 5.8.27 Message refused by ADSP From.Domain=<IDENTITY>
If acceptable, I'm sure Murray can help provide the description as it
relates to DKIM-aware MLM using this 5.8.27 detection to avoid
creating erroneous automated unsubscribing notifications to members
with DKIM-ADSP ready mail host receivers.
--
Sincerely
Hector Santos
http://www.santronics.com
Jeff Macdonald wrote:
Hi Folks,
There is a slight update, where I added a code for greylisting. I've
also updated the contact information to reflect my current job.
Draft can be found here:
https://datatracker.ietf.org/doc/draft-macdonald-antispam-registry/
Suggested values for SMTP Enhanced Status Codes for Anti-Spam Policy
draft-macdonald-antispam-registry-02
Abstract
This document establishes a set of extended SMTP policy codes for
anti-spam. It seeks to provide additional codes for error texts that
currently use the extended SMTP error code 5.7.1. The anti-spam
codes were determined by looking at error texts produced by major
ISPs and finding commonalities. The result is a new set of error
texts with associated extended SMTP error codes.
There is an implementation at my former job:
$ telnet mail-router.e-dialog.com 25
Trying 208.94.20.16...
Connected to mail-router.e-dialog.com.
Escape character is '^]'.
550 5.8.3 Listed on RBL Zen: See http://www.spamhaus.org/query/bl?ip=1.1.1.1
Here I tried to connect to the inbound MX at e-Dialog, from my home
over Comcast cable. This is a residential connection so the listing
makes sense (it is actually a PBL listing).
I've changed the IP to keep spammers at bay.
If you've implemented this draft, please let me know.