Missing Content-Type: header element (Was: Problems seeing mail)

Martin Marques martin at bugs.unl.edu.ar
Mon Aug 28 14:58:07 CEST 2006


On Sun, 27 Aug 2006, B. Johannessen wrote:

> Martin Marques wrote:
>> Thomas Bruederli wrote:
>>> I'll check that and add a fallback to text/plain.
>> Could the fallback be for badly written content-type headers too?
>
> If you do, please make sure you only fall-back to text/plain if the "badly 
> written" Content-Type header element starts with "text/". That would be in 
> agreement with the MIME RFC, which mandates that an unknown subtype of "text" 
> should be treated as text/plain.

You are totally right. I should have said to fall-back all text/* 
contents.

As an example, mails with this type of content-type fail to be seen:


More information about the Dev mailing list