Re: Spam sent from compromised (web)hosts vs botnet spam

>If we wanted to get serious about this type of implementation, an SMTP 
>extension could do the trick.
>
>Perhaps a new ABUSEID command could be used by the sending machine, 
>after the EHLO and before the MAIL FROM, to provide a unique ID for the 
>transaction on all outbound messages sent, in the form of ID@domain, 
>where ID@domain must be unique.
>
>A complaint could be generated by attempting to send mail to ID@domain 
>as an email address, but at the RCPT TO stage, using RCPT ABUSETO: 
><ID@domain> listed above. DATA could be entirely optional, could be a 
>ARF or regular bounce message, or it could be just comments for 
>user-initiated complaints.
>
>This would give a fair amount of flexibility, senders could use 
>@abuse.example.com if they want abuse reports to a specific server, or 
>just @example.com if all of their MXes can accept abuse reports, or even 
>@mx2.example.com if each MX handles it's own abuse reports.

Write it up as a draft, please.

-
This is the asrg mailing list.  To change your subscription settings, see
http://lists.services.net/cgi-bin/mj_wwwusr/domain=lists.gurus.org