Home Forums OS X Server and Client Discussion Mail IMAP/Mail.app time display error, 12:00

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #368826
    Forrest
    Participant

    Hello folks

    I have a single 10.4 server which serves mail via IMAP to our 10.3 and 10.4 desktop clients. The desktop clients use mail.app primarily (and squirrelmail occasionally) to access the IMAP server.

    I have a weird problem where the 10.3 and 10.4 Mail.app clients won’t display the correct date & time for certain emails. Instead it shows 12:00 for the time. Because I see the same error in 10.3 and 10.4, I assume the cause is something to do with the IMAP server (since it is the only common component).

    However if I view an email in the preview pane or open the message, the correct time displays inside that view. It is only inside the mailbox view that the error is seen.

    Here is a screenshot from a 10.3 client to demonstrate what I’m talking about. Note that a number of the emails in the mailbox have 12:00 as the time, but the preview pane shows a different time.

    [url=http://vetyle.pair.com/gavinh/mail.app.jpg]screen shot[/url]

    This a major problem because it makes it really hard for my staff to find specific emails for a given day. It really impacts their workflow if they have to search through a whole set of emails from a given day just to find a particular email.

    Has anyone else seen this problem? Is there a known fix?

    FWIW if I create a new mailbox and copy the affected emails across to it, the incorrect time is still displayed in the new mailbox. The other thing top note is that I have not attempted the cyrus reconstruct command for the affected users.

    #368828
    Forrest
    Participant

    I forgot to add that the time & date are correctly set on the clients, and the server.

    #368847
    uptimejeff
    Participant

    Time zones correct on server & client ?

    Jeff

    http://mac007.com

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.

Comments are closed