Umm, i showed direct evidence that it wasn't anything to do with
evolution.
Date: is the only header evolution creates, and they are all correct.
On Wed, 2005-08-24 at 10:21 -0400, Jeremey Wise wrote:
So the question still stands. What is the resolution to fix Evolution.
As you saw in the
Your example messages are not the same in only 1 way - the path they
take to their destination. That is the cause. Not the client creating
the messages.
On Wed, 2005-08-24 at 22:52 +0800, Not Zed wrote:
Umm, i showed direct evidence that it wasn't anything to do with
evolution.
Date: is
Hmm. Maybe the issue is that the time zone is set to New_York but no
mention of Daylight savings time etc.
On Wed, 2005-08-24 at 22:52 +0800, Not Zed wrote:
Umm, i showed direct evidence that it wasn't anything to do with
evolution.
Date: is the only header evolution creates, and they are
that setting is calendar-only. the mailer uses the system time and the
system timezone
Jeremey Wise wrote:
Hmm. Maybe the issue is that the time zone is set to New_York but no
mention of Daylight savings time etc.
On Wed, 2005-08-24 at 22:52 +0800, Not Zed wrote:
Umm, i showed direct
Hmm, both of those messages are identical within a few minutes.
What time, exactly, are you talking about?
Also, FWIW, the mailer only uses your system timezone.
From the 'bad' message:
Received: from 172.27.16.164 ([172.27.16.164]) by dcex1.pios.com
([172.25.15.51]) with Microsoft
