Craig R Hughes wrote: > > spamd does not write to mailboxes. The -P option is for "spamassassin" which > works somewhat differently. spamc will take the message from procmail, and pass > it to spamd, which will process it, and return it back to spamc again, which > will pass it on back to procmail. Without further instructions in its recipe > list, procmail should then just deliver the message to the mail spool, and I > would have thought it was smart enough to do locking in that default case. But > what you're describing still sounds like a locking issue... > > C >
Right on the button Craig! I turned on verbose and logging and look what I found: procmail: Locking "/tmp/passthrough.lock" procmail: Assigning "LASTFOLDER=/tmp/passthrough" procmail: Opening "/tmp/passthrough" procmail: Acquiring kernel-lock procmail: Unlocking "/tmp/passthrough.lock" procmail: Executing "spamc" procmail: Bypassed locking "/var/spool/mail/klinebl.lock" <----- procmail: Assigning "LASTFOLDER=/var/spool/mail/klinebl" procmail: Opening "/var/spool/mail/klinebl" procmail: Acquiring kernel-lock procmail: Notified comsat: "klinebl@377431:/var/spool/mail/klinebl" Subject: Database backup Mon Apr 15 16:30:00 EDT 2002 Folder: /var/spool/mail/klinebl 346236 Now all I have to do is figure out why. Thanks very much for your help Craig. Barry _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
