Please bear with me, this is my first bug report and I'm not sure exactly what information you might need, but I'll explain the problem I'm having as best I can. Up front, though, I'm not sure if this is a problem with Claws Mail or with procmail, but the problem I'm experiencing is similar to bug #1434: http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=1434 and I'm unable to reproduce the problem at will, making the problem difficult to troubleshoot. We're using a local delivery method where procmail delivers mail to an NFS-mounted mailspool file (/var/mail/<username>) that claws picks up. Unlike the bug link above, our messages do not get out of sync. Occasionally, I run into a problem where Claws Mail won't pickup the mail from the spool file because, for some reason, the first character in the spool file is missing. For example, a normal spool file will begin with: From user@foo.com Wed Mar 5 16:30:41 2008 but we end up with this: rom user@foo.com Wed Mar 5 16:30:41 2008 and CM refuses to pull in the spool file because of the missing character. I'm not sure what causes the missing "F" or why CM refuses to import the mail with it missing, but my administrative staff claims it's because CM isn't doing file locking properly. As a result, they've just written the problem off as a client issue and I've been left to fend for myself. Any information you may need to help me track this down, I'll gladly provide. My configure command that I use to build CM is: ./configure --prefix=${HOME}/platform/${CPU} \ --enable-shared \ --disable-static \ --disable-valgrind \ --disable-libetpan \ --disable-clamav-plugin \ --disable-trayicon-plugin \ --disable-spamassassin-plugin \ --disable-jpilot \ --with-aspell-prefix=${HOME}/platform/${CPU} \ --with-aspell-libs=${HOME}/platform/${CPU}/lib \ --with-aspell-includes=${HOME}/platform/${CPU}/include and I build the pdf_viewer plugin using: ./configure --prefix=${HOME}/platform/${CPU} \ --enable-shared \ --disable-static Again, given my inability to reproduce this problem at will, I'm not sure where the problem lies, so any help in either fixing it or at least pointing to where the issue lies would be extremely helpful.
*** This bug has been marked as a duplicate of bug 1544 ***