I had suggested to Gerard to create a log file by setting
LOG=/path/file, and he responded:
| [...]
| LOG=path/log/file didn't work, but setting LOGFILE to that file did
| work. I assume you mixed LOG and LOGFILE up?
Yes, that's exactly what I did. That's what I get for responding to mail
at 1:00a after a long weekend when I should be in bed. It was a careless
mistake and I apologize.
| Either way, I got my verbose info:
| procmail: Match on "^X-list: lfs-discuss"
| procmail: Locking "lfsdiscuss.lock"
| procmail: Assigning "LASTFOLDER=lfsdiscuss"
| procmail: Opening "lfsdiscuss"
| procmail: Acquiring kernel-lock
| procmail: [3666] Sun Jul 22 22:22:55 2001
| procmail: Error while writing to "lfsdiscuss"
| procmail: Unlocking "lfsdiscuss.lock"
| <cut>
|
| >From there it goes on trying other recipies, which fail, then it'll use
| the spool file /var/mail/maillist
|
| The first thing that comes to mind: permission problems:
| -rw-r--r-- 1 maillist maillist 52011055 Jul 22 22:04 lfsdiscuss
| This is exactly like the other mailinglists which work fine. Keep in
| mind that when I remove a few emails from it to below some threshold, it
| won't fail. I just tested this without touching the permissions to
| confirm that.
|
| Also, manual procmail still works, so now it's going to be quite fun
| debugging postfix and see what it's up to.
|
| Is there a way to get more verbose information why procmail couldn't
| write to the file 'lfsdiscuss' (can it log permission problem, memory
| problem or something?). I don't see anything to that effect in the man
| pages for procmail.
|
| Perhaps it's time to subscribe to the postfix list and see what they
| know.
I still don't have any ideas for you, but the procmail man page offers
this description of the error message:
Nonexistent subdirectory, no write
permission, pipe died or disk full.
Because procmail can write to the file when run from the command-line,
your guess that postfix is the culprit seems reasonable. I know nothing
of postfix, but does it run as a non-priviledged user other than the
user "maillist"? Of course that would explain this only if the other
files procmail is successfully delivering to from similar recipes have
different ownership than this one. But it's all I can think of. Of
course, I haven't finished my first cup of coffee so am probably no
more clear headed than last night. :-(
--
/"\
Don Hammond \ / ASCII Ribbon Campaign
Raleigh, NC US X Against HTML Mail,
/ \ and News Too
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail