Sorry about that, didn't realise that a plugin I had active was doing that
behind the scenes.

On 2 Jun 2017 1:22 a.m., "Eric Christopherson" <echristopherson / gmail.com>
wrote:

> On Thu, Jun 1, 2017 at 1:40 PM, Marvin Glker <m-guelker / phoenixmail.de>
> wrote:
>
>> On Thu, Jun 01, 2017 at 08:40:52AM -0700, Paul Kuruvilla wrote:
>> > This email has been sent in HTML mode. In order to view this email,
>> > please activate HTML message viewing.
>>
>> Please stop sending such nonsense mails! Either include a text/plain
>> part that has a meaning, or leave it off entirely. But do not send such
>> a nonsense notice in it. It's multipart/ALTERNATIVE, not
>> multipart/NOTHING_VALUABLE_HERE! If you do not offer an equal
>> *alternative*, then do not include the text/plain part. This prevents
>> autoformatters from detecting the HTML part and automatically dumping it
>> to plaintext (using e.g. Lynx).
>>
>> Sorry for the OT, but I couldn't let this go.
>>
>> Marvin
>>
>
> I agree. I have that same problem with a few automated emails I get (ones
> that I actually care somewhat about). Mutt and lynx/links/w3m work well
> enough for most HTML emails, if they just know enough about a message to
> convert the HTML automatically. This kind of placeholder defeats that
> feature.
>
> --
>         Eric Christopherson
>
>
> Unsubscribe: <mailto:ruby-talk-request / ruby-lang.org?subject=unsubscribe>
> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-talk>
>
>
(supressed text/html)
Unsubscribe: <mailto:ruby-talk-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-talk>