I'm having some trouble seeing the contents of mail some mail, and I thought it had to do the encoding specified in the header of the mail. But today I tried the latest svn version on a server I have with an older RC running, and I can't see the contents of a message sent by cron. If I click on "view source" I see the contents of the message, which are these (I eliminated all the received and delivered-to headers):
Martin Marques wrote:
I'm having some trouble seeing the contents of mail some mail, and I thought it had to do the encoding specified in the header of the mail. But today I tried the latest svn version on a server I have with an older RC running, and I can't see the contents of a message sent by cron. If I click on "view source" I see the contents of the message, which are these (I eliminated all the received and delivered-to headers):
From: ... To: ... Subject: Cron <...> run-parts /etc/cron.daily Message-Id: 20060826071309.C60DB788080@newweb.matematica Date: Sat, 26 Aug 2006 04:13:09 -0300 (ART) Status: RO X-UID: 12012 Content-Length: 462 X-Keywords:
Looks like the missing Content-Type header causes the problem. I have another test mail that isn't displayed properly which doesn't have one too.
I'll check that and add a fallback to text/plain.
Thomas
Hi Thomas,
Thanks for fixing it so quickly, that was annoying me for about a week, I thought it was something to do with my how some of my unix cron jobs were running as i just upgraded postfix aswell.
Regards,
Carson.
On Sun, 27 Aug 2006 13:18:40 +0200, Thomas Bruederli roundcube@gmail.com wrote:
Martin Marques wrote:
I'm having some trouble seeing the contents of mail some mail, and I thought it had to do the encoding specified in the header of the mail. But today I tried the latest svn version on a server I have with an older RC running, and I can't see the contents of a message sent by cron. If I click on "view source" I see the contents of the message, which are these (I eliminated all the received and delivered-to
headers):
From: ... To: ... Subject: Cron <...> run-parts /etc/cron.daily Message-Id: 20060826071309.C60DB788080@newweb.matematica Date: Sat, 26 Aug 2006 04:13:09 -0300 (ART) Status: RO X-UID: 12012 Content-Length: 462 X-Keywords:
Looks like the missing Content-Type header causes the problem. I have another test mail that isn't displayed properly which doesn't have one too.
I'll check that and add a fallback to text/plain.
Thomas
On Sun, 27 Aug 2006 13:18:40 +0200, Thomas Bruederli roundcube@gmail.com wrote:
Looks like the missing Content-Type header causes the problem. I have another test mail that isn't displayed properly which doesn't have one too.
Just managed to see that was the problem be chacking another mail that comes from logwatch (which does have a content-type) and looks good.
I'll check that and add a fallback to text/plain.
Could the fallback be for badly written content-type headers too?
Lic. Martín Marqués | SELECT 'mmarques' || Centro de Telemática | '@' || 'unl.edu.ar'; Universidad Nacional | DBA, Programador, del Litoral | Administrador
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.
Bob
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: