On Thu, Jul 20, 2017 at 02:46:02AM -0400, Rupert Gallagher wrote:
| Out of curiosity, I just checked what all the fuss is about. It turns out
that someone reads mail with a non-RFC compliant client, and thus fails to read
mime parts. Screw it, update your client.
| The other problem seemed to be with the list archive. It turns out that at
least one archive has no problem at all (*). If other archives have mime
problems, they can update themselves or just delete the mail.
All of this while large parts of the world consider those sending such
mails to be spam (after spammers abused trick this to evade anti-spam
solutions), never to deliver them.
Your base64-encoded mime parts are braindead, but nobody is really
worried: those e-mails will simply be ignored by those that might
otherwise have had useful replies. Just because something is a
standard, doesn't mean everybody should do it. There are (very many)
harmful standards (caused in large part by a lack of ax-murderers, I
hear).
Cheers,
Paul 'WEiRD' de Weerd
--
>++++++++[<++++++++++>-]<+++++++.>+++[<------>-]<.>+++[<+
+++++++++++>-]<.>++[<------------>-]<+.--------------.[-]
http://www.weirdnet.nl/
