Benches Uncategorized

1

imap ERROR: invalid date/time: 0 (year = 70) + ...

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

I had some problems with Mail clients not being able to connect on port 143 to 10.5.6 server (in LAN). MailAccess.log showed no connection (but not a network problem). Telnetting on 127.0.0.1 got an initial response...

Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.

BUT did not produce the full IMAP response I expected, i.e...

Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
OK CAPABILITY IMAP4 IMAP4rev1 LITERAL+ ID STARTTLS AUTH=PLAIN AUTH=CRAM-MD5 server.example.com Cyrus IMAP4 v2.3.8-OS X Server 10.5: 9C31 server ready

The telnet connection was unresponsive after the initial "Connected to..." message.

A full restart of the server seemed to clear it and telnet got full response, then, after 20 mins, in system.log...

Jul 23 17:23:05 server imap[1211]: login: localhost [::1] alanb CRAM-MD5 User logged in+
Jul 23 17:23:08: --- last message repeated 1 time ---+
Jul 23 17:23:08 server imap[1211]: ERROR: invalid date/time: 0 (year = 70)+
Jul 23 17:23:09 server ReportCrash[1210]: Formulating crash report for process imapd[1211]+
Jul 23 17:23:09 server master[1073]: process 1211 exited, signaled to death by 6+
Jul 23 17:23:09 server ReportCrash[1210]: Saved crashreport to /Library/Logs/CrashReporter/imapd2009-07-23-172308theserver.crash using uid: 0 gid: 0, euid: 0 egid: 0+

This repeated each 7 seconds or so until the user quit the webmail. Other Mail.app users reported problems accessing mail at the same time.

I've never seen that "*ERROR: invalid date/time: 0 (year = 70)*" before. A google did not come up with much for it.

I've also never got around to understanding crash reports but just in case someone else has...

--------------------------------------------
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Crashed Thread: 0

Thread 0 Crashed:
0 libSystem.B.dylib 0x926daaf0 __kill + 12
1 libSystem.B.dylib 0x92775bac abort + 84
2 imapd 0x0003c114 cyrus_ctime + 100
3 imapd 0x0001ee88 index_fetchreply + 788
4 imapd 0x00025318 index_forsequence + 648
5 imapd 0x0001019c cmd_fetch + 5136
6 imapd 0x00016b60 cmdloop + 3284
7 imapd 0x00018cf0 service_main + 1088
8 imapd 0x00002e2c main + 2948
9 imapd 0x000021c0 start + 64
--------------------------------------------

Things seem to be back to normal now but this may just be due to users heading off at 17:30. Checks and tests all seem OK and I cannot reproduce the errors or crash. I'm just concerned that it will all return tomorrow morning and ruin the start to my day!

Anybody seen an error like this before?... *"imap[1211]: ERROR: invalid date/time: 0 (year = 70)"*

1 reply

Sign in or join Beachball Help to reply.

  1. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    UPDATE... error messages have not reappeared and everything running OK. To quote Toyah...

    +It's a mystery, it's a mystery+
    +I'm still searching for a clue+
    +It's a mystery to me+