On Sat, 22 Apr 2006, Obantec Support wrote:
Hi
I am having problems with dovecot POP3 server on FC3. to try and track down
the problem i added logging to procmail for the user who cannot get his
mail.
from the procmail.log
procmail: [28464] Sat Apr 22 14:19:33 2006
procmail: No match on "^X-Spam-Status: Yes"
procmail: Locking "/var/mail/easukcom.lock"
procmail: Assigning "LASTFOLDER=/var/mail/easukcom"
procmail: Opening "/var/mail/easukcom"
procmail: Acquiring kernel-lock
procmail: [28464] Sat Apr 22 15:03:25 2006
procmail: Unlocking "/var/mail/easukcom.lock"
procmail: Couldn't unlock "/var/mail/easukcom.lock"
procmail: Notified comsat: "easukcom(_at_)123379:/var/mail/easukcom"
From
gbounce-250716971-244-40401863(_at_)bounce(_dot_)newsletter(_dot_)cottontraders(_dot_)co(_dot_)uk
Sat Apr 22 14:19:24 2006
Subject: Two fantastic half price offers
Folder: /var/mail/easukcom 16404
there is a file easukcom.lock which seems to be created by procmail but not
dropped and procmail cannot add the new message because of this. i suspect
the lock file exists before procmail sets the lock.
From my experience, POP3 users with very big folders have this
problem. Also when user try to access the inbox by two programs
in same time eg the user reads mail from office while his computer
at home check the mail every 10 minuts (and the folder so big).
--
Udi
the lock is owned by usersUID.usersGID mbox file is usersUID.mail
Mark
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail
+++++++++++++++++++++++++++++++++++++++++++
This Mail Was Scanned By Mail-seCure System
at the Tel-Aviv University CC.
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail