[LINK] Fwd: Re: Eudora/Droid issue

[Rick Welykochy]

Jan Whitaker wrote:

> This problem may be of interest to linkers. To have a new email
> system not include all the components required seems a bit odd.
> Jan
>
>
>>> "Gibberish from Motorola Droid"
>>> http://eudorabb.qualcomm.com/showthread.php?t=14833
>>
>> I have been seeing the same problem in Eudora reading mail from aol
>> servers with message id's of the form: Message-ID:<x at email.android.com>
>>
>> The relevant header sub-block shows, eg:
>>
>>> Message-ID:<56ioyy3keu1538af9078kra6.1268751525026 at email.android.com>
>>> Content-Type: text/plain; charset=utf-8
>>> Content-Transfer-Encoding: base64
>>
>> The Mime header is missing.

Eudora is doing the Right Thing (tm), but not an intelligent thing.

If the MIME header is missing, the mail client should ignore all
MIME-related headers. But many email clients deduce that if there
are MIME headers like "Content-Transfer-Encoding: base64" that
MIME 1.0 should be used.

It might behoove Eudora to provide an option for this intelligent
behviour rather than being so obstinate, in the way the browsers
are forgiving with incorrect HTML and make provisions for mssing
tags.

Another option is manually decoding the Base-64 content, a PITA.

cheers
rickw


-- 
_________________________________
Rick Welykochy || Praxis Services

Simply stated, it is sagacious to eschew obfuscation
      -- Norman Augustine