Re: [Exim] Date problem with Exim (FreeBSD Port) with Outloo…

Top Page
Delete this message
Reply to this message
Author: Oliver Eikemeier
Date:  
To: lannygodsey
CC: exim-users
Subject: Re: [Exim] Date problem with Exim (FreeBSD Port) with Outlook Express 5 (Windows, and Mac)
Lanny Godsey wrote:

> Outlook uses the Received line to display the Date in the user's mail
> list. I can only guess that it parses the last Received: line to
> gather date received. Once you double click the email, the date is
> displayed properly and again guessing that it now uses the Date:
> header.


Sounds reasonable, although I can't understand why Outlook uses two
different headers, which must result in different dates being displayed.

> I don't want to make an issue out of this, if you want to keep the ;
> and popular opinion says that it doesn't violate the RFC that is fine.


No, no problem. I've changed that into using what Debian does: nested
comments. The whole hassle about RFC vs. Outlook bug is that, in order
to work around an Outlook bug every other character than `;' will do,
while, in case it had been a violation of RFC 822, `:' would probably
have been illegal too.

> My gripe was simply that the ; was introduced in the port and caused a
> "mysterious" email display problem which in turn generated 1000s of
> support calls.


This line has been there since Sep 29 2003, how is it that it only turned
up recently?

> The simple fix was replacing the ; with a :. Should someone else have
> the same symptoms I only wanted there to be a record of our findings to
> save the next admin time.


I've chosen to follow Debin with nested comments, since problems with that
should have hitten them before me ;)

> As someone else pointed, you can simply specify a new
> received_header_text which is exactly what I did initially.


Yep, but if it is an easy workaround for an MUA bug which does not
introduce new problems, it's good to have it in the port.

I just committed the workaround, so if you CVSup and rebuild everything
should be fine. You have to force the rebuild, though: I didn't bump the
PORTREVISION since I believe most users will not be affectd, and we will
have an new exim version soon anyway ;)

Thanks for your patience

-Oliver