Cristian Seres wrote:
From:
Gordon Messmer <yiny...@eburg.com>
Cristian Seres wrote:
* BYE Clock skew detected. Check the clock on the file server
The clock on your file server is more than 30 seconds different from
your IMAP server. Check the operation of NTP on both.
There is no file server. All filesystems are local. It is a single
server running Courier IMAP.
Well, that's real odd.
What happens if you log in as the user whose IMAP session you tried to
open, and do:
$ date && touch test && stat test
I get the following output:
Mon Oct 29 15:38:06 PDT 2007
File: `test'
Size: 0 Blocks: 8 IO Block: 4096 regular
empty file
Device: fd01h/64769d Inode: 15990870 Links: 1
Access: (0664/-rw-rw-r--) Uid: ( 500/ gordon) Gid: ( 500/ gordon)
Access: 2007-10-29 15:38:06.000000000 -0700
Modify: 2007-10-29 15:38:06.000000000 -0700
Change: 2007-10-29 15:38:06.000000000 -0700
Note that the "Modify" date near the end is pretty much the same as the
output from "date", since those commands take less than one second to run.
Courier's IMAP server is doing something very much like those commands.
It gets the current time (unix time; DST won't affect it), then
creates a file in Maildir/tmp, and then stats the file to get the
modification time. If the mtime is more than 30 seconds off from the
current time, it'll give you the error message that you saw.
6 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Bye Clock skew de...
