[Top] [All Lists]

Re: slight update to draft-macdonald-antispam-registry

2011-05-11 10:28:55

On May 11, 2011, at 7:01 AM, Murray S. Kucherawy wrote:

I'm not following this thread closely, but I thought I'd say something
about extended status codes.  Part of the idea of extended status codes
is that you should be able to determine the likely source of the
problem by looking at the second facet of the status code.  Or to put
it another way, the second facet of the status code is supposed to
indicate _who_ probably needs to fix the problem (e.g. the sender, the
MSA, a relay, the delivery agent, etc.)

I haven't implemented this, but I have to say I really like this approach.  
Perhaps the proposal would benefit from making such distinctions in the new 
codes it's registering.

If you're going to make the second facet of the status code be who probably 
needs to fix the problem, you could also make the third facet point to where 
they need to go to fix it. 
It doesn't even need to be that detailed. 1 for this is internal (so you need 
to contact the recipient domain) and 2 for this is external (so you need to 
contact a third party). Then follow that with a URL pointing to the third party 
or the postmaster / internal troubleshooting pages. 


Laura Atkins
Word to the Wise                        "The Deliverability Experts!"
Direct: 650 678-3454            Fax: 650 249-1909
AIM: wttwlaura                  YIM: wttw_laura
Delivery blog: <>

<Prev in Thread] Current Thread [Next in Thread>