Bah I was wrong -- both installs are reporting the time incorrectly after 1:00 PM.
If anybody has any ideas, fire away? -a > -----Original Message----- > From: Aaron Freeman [mailto:aa...@sendthisfile.com] > Sent: Sunday, June 24, 2012 10:29 PM > To: server-user@james.apache.org > Subject: James 3.0 - beta 4 Date/Time Problem > > I just sent an email to myself. It was 21:22 (9:22 PM) when I sent it. I > received it immediately after sending it. > > The date in the Received header is incorrect, but the Date: header is correct. > So Outlook displays it incorrectly in its list of incoming email, but when you > view the email itself, it looks correct. > > I have noticed it doesn't EVER handle PM correctly -- so in the morning, the > emails work properly because it's AM, but in the evening all email still gets > listed as AM. > > I can think of two ways this might happen: > > 1) The Received: field is always missing the AM/PM. > > ... or ... > > 2) Whatever is created the Received header expects a 24 hour number and is > always getting a 12 hour number with AM/PM and it's ignoring the PM (pure > speculation on my part as to if that's what is happening, but that's a good > description of the problem). > > Here is an example of an email in error: > > Return-Path: <aa...@no-spam.com> > Message-ID: <01b201cd5279$69425e10$3bc71a30$@no-spam.com> > MIME-Version: 1.0 > X-MessageIsInfected: false > Delivered-To: aa...@no-spam.com > Received: from computer.net (EHLO AaronPC) ([199.74.33.131]) > by mail.no-spam.com (JAMES SMTP Server ) with ESMTP ID 1431131469 > for <aa...@no-spam.com>; > Sun, 24 Jun 2012 09:22:46 -0500 (CDT) > From: "Aaron Nospam" <aa...@no-spam.com> > To: <aa...@no-spam.com> > Subject: test > Date: Sun, 24 Jun 2012 21:22:47 -0500 > Content-Type: text/plain; > charset="us-ascii" > Content-Transfer-Encoding: 7bit > X-Mailer: Microsoft Outlook 14.0 > Thread-Index: Ac1SeWfYz5vg0a4NSv6oCpmsEtzKLA== > Content-Language: en-us > > Is there anywhere in the system or any options I could change to fix this? > What's weird is I believe we are running James 3.0 beta 4 on another box and > we don't have this problem on that one -- I'll need to verify it's beta 4 and not > beta 3 to be sure though. > > Thoughts? > > Thanks, > > Aaron > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org > For additional commands, e-mail: server-user-h...@james.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org