Strange problem I've just observed with Courier-imap, on a Maildir which I
use for a high-volume mailing list. The POP3 server doesn't "see" all the
messages in one go.
This morning, manually checking the maildir, I saw 90 messages:
bash-2.05a# ls /mail/1/8/1a/1d/blah%example.com/new | wc -l
90
When I ran 'fetchmail' at the client end, it said there were 64 messages,
and downloaded them all. 26 messages remained in /new. When I ran it again
immediately afterwards, it said there were 26 messages, and downloaded them
all.
So nothing was lost, but for some reason the full maildrop wasn't visible
first time.
This particular server isn't running the latest courier with its
courierpop3dsizelist file. In fact I can't tell you exactly which tarball it
was compiled from, but it was compiled on Dec 16th 2002, so it would be
whichever interim version was current around then.
The Maildir itself is stored on a Netapp NFS fileserver, and courier-imap is
running under FreeBSD-4.6.2
Looking at the code, scannew() should move everything from new/ to cur/, and
should stop only if readdir() returns NULL or malloc fails - both of which I
wouldn't expect to happen.
Next time that mailbox gets full I'll write a test program which just does
the scannew functionality and see what it returns - but I presume 'ls' is
doing pretty much the same thing, so it's hard to see how it could be an OS
problem.
Regards,
Brian.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
