Yes, it's out there date wise. That's not the point, of course, however. People do sometimes send email messages with such wonky, weird dates, and Zimbra needs to be able to handle it.

Any ideas on how to allow the imap server to accept such dates?

(note, my only other problem during IMAP import, about file sizes being > 10MB, was resolved with another post. As a suggestion for Zimbra, an offical "howto" with these "gotchas" might be a great idea for IMAP).

The "date" there is meant to be the received date, not the date listed in the "Sent" header in the message. If your IMAP server is marking messages as received in 1965, I think it may have some issues...

In the meanwhile, please file a bug against Zimbra to add a flag indicating that it should use the current date when a message is APPENDed with an invalid (too-early) date.

The "date" there is meant to be the received date, not the date listed in the "Sent" header in the message. If your IMAP server is marking messages as received in 1965, I think it may have some issues....

The IMAP server is entirely correct... and IMAP servers do not typically mark messages as received at any date or time. That's usually done by the SMTP server.

However, your point is valid, in that... wtf is going on?! Well, the problem as I see it, is that these email folders were transfered from outlook, to Mozilla Mail on Windows, to Thunderbird under Linux, and finally to IMAP via a conversion script (moz mail format -> imap mbox) under Linux.

Since then, these email messages have sat on our mail server.. for about three years without anything of note happening to them. However, here's a snippet from the header of one of those messages:

so yes, one of the conversion points over the last 7 years or so has indeed screwed the From initial header up. As a FYI, I ran a simple perl search and replace on the entire IMAP directory structure of each user affected, and simply changed the date line to sometime in 1985. This allowed the import without trouble.

In the meanwhile, please file a bug against Zimbra to add a flag indicating that it should use the current date when a message is APPENDed with an invalid (too-early) date.

I'd like to, but neither my forum or support login information seem valid in the bug system. [sarcasm]I tried to file a bug report against this, but.....[/sarcasm]

Anyhow, I have about five or six other bugs to report, so could someone fix my bug reporting issue?

Have the same problem.
Description:
Zimbra Open Source Edition 6.0.8.
We migrate at the moment to Zimbra from unstructured mail system, there users keeps their mail DBs localy in different mail clients. To migrate from Thunderbird Local Folders we use chain UnixMailBox -->IMAP--(imapsync)--> Zimbra.
For one user we have same problem. I check Thunderbird Mail DB -- some of mails really starts from Field "From ..... 00:00 1 Jan 1965". A lot of mails with tha same line. I think it can appear from previous importing/exporting procedures from another mail client to Thunderbird. Only one way I find to solve it -- change in this line 1965 to 2007 year.

Have the same problem.
Description:
Zimbra Open Source Edition 6.0.8.
We migrate at the moment to Zimbra from unstructured mail system, there users keeps their mail DBs localy in different mail clients. To migrate from Thunderbird Local Folders we use chain UnixMailBox -->IMAP--(imapsync)--> Zimbra.
For one user we have same problem. I check Thunderbird Mail DB -- some of mails really starts from Field "From ..... 00:00 1 Jan 1965". A lot of mails with tha same line. I think it can appear from previous importing/exporting procedures from another mail client to Thunderbird. Only one way I find to solve it -- change in this line 1965 to 2007 year.

You need to provide details of the exact IMAPSYNC command you're using. Which version of Thunderbird are you using?