On Thu, Jun 19, 2003 at 08:31:07AM +0200, Andreas Aardal Hanssen wrote:
> Hi, Cory! :-)

Hey Andy!

> The logs should have also reported which message had the faulty uid value
> (noted). This happens if you have one or more message(s) in your folder
> that has a future timestamp (time(NULL) part of the file name).

Ok, I think I have tracked down what was happening.   I noticed that this
was only happening on two folders:  ~/Maildir/ and ~/Maildir/.Corz/ .  These
two folders are delivered into using safecat, which I recently upgraded.  
The new version of safecat changed the naming convention of the files in the
maildir, and they now look like this:

[EMAIL PROTECTED]@[EMAIL PROTECTED]:2,S
[EMAIL PROTECTED]@[EMAIL PROTECTED]:2,S
[EMAIL PROTECTED]@[EMAIL PROTECTED]:2,S
[EMAIL PROTECTED]@[EMAIL PROTECTED]:2,S
[EMAIL PROTECTED]@[EMAIL PROTECTED]:2,S
[EMAIL PROTECTED]@[EMAIL PROTECTED]:2,RS
[EMAIL PROTECTED]@[EMAIL PROTECTED]:2,S

And here is an entry from the logs:

2003-06-20 12:00:47.239988500 11598 00000 [EMAIL PROTECTED]:] Client connected to Binc 
IMAP from 127.0.0.1
2003-06-20 12:00:47.255696500 11599 00000 [EMAIL PROTECTED]:] User <cwright> entered 
authenticated mode.
2003-06-20 12:00:47.283835500 11599 00001 [EMAIL PROTECTED]:] found a recent message 
with uid 59 _after_ one that had no uid
2003-06-20 12:00:47.305510500 11599 00002 [EMAIL PROTECTED]:] Error when processing 
SELECT: unable to open "INBOX", uidvalidity bounced
2003-06-20 12:00:47.371011500 11599 00003 [EMAIL PROTECTED]:] Error from client:  
undefined or disallowed in current state

Another strange thing is that it only happens *every other* time that I try
to access the folder.  It works, then it doesn't, then it does, then it 
doen't again.

> It often happens when sysadmins upgrade or move a depository to a machine
> whose clock is set wrong, a message gets delivered, and then the clock is
> adjusted back to normal. I did this myself (the clock was set to 7/3 when
> it should have been 3/7) and the result was that I had to shut down the 
> mail system and run a perl script on all users' mailboxes. :-/

Nothing has changed on the server, other than stopping Courier :)

Does that make any sense?

Cory

--
Cory Wright
Stand Blue Technology
http://www.standblue.net/

Reply via email to