We have a mailserver that allows IMAP-only access to users. One or two
"special" users NFSmount their mail homedir and the mailspool to their
machines. Likewise, the mailhomes and spool are NFSmounted to a common
machine that isn't running a mailserver. This allows users to access
their homedir and modify their procmailrc.
One user recently was receiving no mail. He was one of the "special"
ones. Any mail to him was received by the machine but queued up and a
procmail process kicked off for each message. When I turned on logging
in his procmailrc, it was spinning on file locking. Removing file
locks wouldn't fix it.
Here's the amazing part. I completely removed his procmailrc and the
problem continued. Ultimately, I fixed it by whacking his machine.
I'm theorizing that there was a NFS-lock problem and smaking
his machine upside the head got it to understand things my way.
The machines involved happen to be Solaris but I'm wondering if
anyone has seen such behavior or knows of NFSlocking issues with
procmail.
TIA
=-=-=-=-=-=-=-=-=-=- generated by /dev/dave -=-=-=-=-=-=-=-=-=-=-=-=
David Stern University of Maryland
Institute for Advanced Computer Studies
____________________________________________________________
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