%% You should probably cite draft-ietf-appsawg-malformed-mail instead of this I-D.
@techreport{kucherawy-mta-malformed-03,
    number =    {draft-kucherawy-mta-malformed-03},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-kucherawy-mta-malformed/03/},
    author =    {Murray Kucherawy},
    title =     {{Best Current Practices for Handling of Malformed Messages}},
    pagetotal = 9,
    year =      2011,
    month =     jul,
    day =       11,
    abstract =  {The email ecosystem has long had a very permissive set of common processing rules in place, despite increasingly rigid standards governing its components, ostensibly to improve the user experience. The handling of these come at some cost, and various components are faced with decisions about whether or not to permit non-conforming messages to continue toward their destinations unaltered, adjust them to conform (possibly at the cost of losing some of the original message), or outright rejecting them. This memo includes a collection of the best current practices in a variety of such situations, to be used as implementation guidance. It must be emphasized, however, that the intent of this memo is not to standardize malformations or otherwise encourage their proliferation. The messages that are the subject of this memo are manifestly malformed, and the code and culture that generates them needs to be fixed. Nevertheless, many malformed messages from otherwise legitimate senders are in circulation and will be for some time and, unfortunately, commercial reality shows that we cannot simply reject or discard them. Accordingly, this memo presents recommendations for dealing with them in ways that seem to do the least additional harm until the infrastructure is tightened up to match the standards.},
}