[apps-discuss] update to rfc5965

[Franck Martin <[e-mail]>]

http://tools.ietf.org/html/rfc5965 

Specifies the format of Abuse Reporting Format of emails. 

2.d indicates the report should contain either the headers of the reported email as a text/rfc822-headers MIME part or the complete message as an message/rfc822. However if the message reported contains spam, virus, bad links, or in general malware, the complete report is likely to be discarded by the receiver anti-spam filters, never reaching abuse desks for processing. 

It is common amongst security professionals to exchange such dangerous payloads as an encrypted zip file with the common password "infected". This format allows to bypass anti-spam filters as the MTA/MUA is not able to decrypt the attachment to analyze the content. 

It i difficult to request abuse desk to create a separate email infrastructure for [e-mail] and especially to disable anti-spam and anti-virus checks. Some of these addresses are part of email hosted in the cloud. 

I suggest we add the possibility to send the complete email as message/rcf822 email within either an encrypted zip file or within a GPG symmetrically encrypted file, both using the common password "infected". 

The MIME type should be 
message/rfc822-zip-crypt for an encrypted zip file 
message/rfc822-gpg-crypt for the gpg encrypted file 

gpg and zip are widely used on many systems. 

I'm gathering comments, and will tentatively write a draft if no major block is received.