Package: procmail Version: 3.22-16 Severity: wishlist Tags: upstream Put this in ~/.procmailrc :0: /tmp/newdir/ then do $ echo|mail $USER looking in $LOGFILE, one sees procmail: Locking "/tmp/newdir/.lock" procmail: Error while writing to "/tmp/newdir/_km,xic1GB.jidanni2" procmail: [2468] Thu Aug 30 03:27:53 2007 procmail: Locking "/tmp/newdir/.lock" procmail: Error while writing to "/tmp/newdir/_km+xic1GB.jidanni2" procmail: [2468] Thu Aug 30 03:28:01 2007 ... procmail: [2468] Thu Aug 30 03:28:41 2007 procmail: Locking "/tmp/newdir/.lock" procmail: Error while writing to "/tmp/newdir/_km.pjc1GB.jidanni2" procmail: Lock failure on "/tmp/newdir/.lock" procmail: Assigning "LASTFOLDER=/tmp/newdir/new/1188415721.2468_1.jidanni2" procmail: Notified comsat: "[EMAIL PROTECTED]:/tmp/newdir/new/1188415721.2468_1.jidanni2" >From [EMAIL PROTECTED] Thu Aug 30 03:27:45 2007 Folder: /tmp/newdir/new/1188415721.2468_1.jidanni2 296
Which means procmail instead of detecting that directory doesn't exist yet, just thinks it is a filename special character problem instead, and retires over and over for a whole minute before wisening up. Yes, the user has no need to use :0: for Maildir/ directories, and procmailrc(5) should mention that he should just use :0, but still, procmail should realize the directory hasn't been created yet so of course there will be an error while writing to the lockfile. P.S., one cannot send mail to [EMAIL PROTECTED] if one has a SPF record. The destination checks a midway point thinking it is the origin. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
