Re: plain text only policy prohibits the use of android based mobile devices

[Eugene Sajine <euguess@gmail.com>]

On Wed, May 18, 2011 at 7:14 PM,  <david@lang.hm> wrote:
> On Wed, 18 May 2011, ellis@spinics.net wrote:
>
>>> The necessity to use the desktop in order to send a message to the
>>> list is annoying and not quite contemporary.
>>
>> So the list should change just because your mail client is broken?
>
> if the client is sending out multipart mail with both a HTML and a text
> portion, then having the list accept the text portion and strip the HTML
> portion off seems like a reasonable request.
>
> I am very much a text e-mail person (I use pine almost exclusivly), but this
> doesn't seem that bad.
>
> David Lang
>

That is exactly what I'm thinking about.
IMHO multipart message is completely valid format and list could
preserve its integrity by just pulling out the plain text part of the
message.
And it doesn't matter which client I'm using and if it is broken or not.
I think that the gmail client of android 2+ and 3.0+ is in fact broken
in that regard, but the one from 3.1+ is not. That's is why i was not
asking about "openning up the gates for broken clients" and allowing
HTML content. I'm talking specifically about 3.1+ android versions
that will inherit this gmail client behavior and they are coming soon.

Now I posted this to the list for few reasons:
1. If only one person contacts list admins about such matter - he will
get the answer i got up in the thread. Within a blink of an eye.
2. I wanted to run it by list to understand if there are others who
are annoyed by the way this policy works and to get their input. Do
they think the list could accommodate the multipart messages or they
just using some other clients or they just don't care.

As of now i see the majority doesn't care, so it is up to me to decide
how I'm going to work with this.

Many thanks for the feedback about this bikeshedding issue.

Eugene