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:
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: QUOTED-PRINTABLE
Aparently there's a problem with the charset.
--
21:50:04 up 2 days, 9:07, 0 users, load average: 0.92, 0.37, 0.18
---------------------------------------------------------
Lic. Martín Marqués | SELECT 'mmarques' ||
Centro de Telemática | '@' || 'unl.edu.ar';
Universidad Nacional | DBA, Programador,
del Litoral | Administrador
---------------------------------------------------------
