Re: base64 to text

On 25 Sep 2017, at 20:49, Kees Theunissen wrote:

> On Mon, 25 Sep 2017, Dianne Skoll wrote:
>
>> On Mon, 25 Sep 2017 10:46:01 -0700
>> "Michael Fox" <[email protected]> wrote:
>>
>>> I'd like to be able to deliver HTML and Base64 messages to those
>>> clients.
>>
>> You can do it by throwing away non-text/plain parts where a 
>> text/plain part
>> exists.
>
> Be careful with that. In an ideal world "multipart/alternative" MIME
> parts would supply differently formatted versions of the same message.
> But I have seen way too much messages where the plain text version
> is only used to inform me that my mail client doesn't support 
> html-mail.
>
> A particular sender "Nederlandse Spoorwegen" (Dutch Railways) comes
> in my mind, but there might be other brain death senders.

There certainly are. Apropos to Mr. Fox's specific mention of Sprint, 
here's what I get as the Base64-encoded text/plain part of a 
multipart/alternative  message every month:


    Sprint(R)

    Sprint sent you a plain text email because your settings do not
    allow for images.

    This is an account related email.

    You are receiving this email because your bill is ready to view
    online. Visit sprint.com/mysprint to make payments, view your bill
    and more.

    If you have questions about your bill, please visit
    sprint.com/contactus.

    To contact Sprint, write to:
    Office of Privacy - Legal Department, Sprint,
    P.O. Box 4600, Reston, Virginia, 20195.



The text/html alternative part contains the full text of my bill.

_______________________________________________
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID.  You may ignore it.

Visit http://www.mimedefang.org and http://www.roaringpenguin.com
MIMEDefang mailing list [email protected]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang