That's always the first line of diagnosis of a problem - enable
comprehensive logging and examine the log for oddities. Better is taking
the messages which are causing problems (which are in your mailqueue,
though you might have to do some editing to tweak the copied mailq file to
reproduce a message to pipe into procmail, depending upon how your MTA
queues) and redirect them into the procmail script running in a sandbox
configuration (with VERBOSE=ON).
I'll try to find a way to grab messages from the queue as you've described,
until then here's a verbose log:
procmail: [13294] Sun Jun 8 22:57:05 2003
procmail: Executing "/usr/local/bin/dccproc,-ERw,whiteclnt,-ccmn,30"
procmail: [13294] Sun Jun 8 22:57:05 2003
procmail: Non-zero exitcode (67) from "/usr/local/bin/dccproc"
procmail: Rescue of unfiltered data succeeded
procmail: [13294] Sun Jun 8 22:57:05 2003
procmail: Assigning "EXITCODE=67"
procmail: Assigning "LASTFOLDER=/dev/null"
procmail: Opening "/dev/null"
From list4(_at_)casinospot(_dot_)net Mon Jun 09 02:57:05 2003
Subject: ADV:$50 F R E E At Bella Vegas Casino
Folder: /dev/null 7219
procmail: Unlocking
"/usr/home/mail/USER/lock"
qmail log:
2003-06-08 22:58:34.550321500 starting delivery 49725: msg 176402 to local
USER
2003-06-08 22:58:34.551072500 status: local 1/384 remote 0/384
2003-06-08 22:58:34.859118500 delivery 49725: deferral:
procmail:_Exceeded_LINEBUF/
2003-06-08 22:58:34.859923500 status: local 0/384 remote 0/384
It appears to have filtered this one properly, but procmail still complains
about Exceeding LINEBUF...
I wonder if it's something different about the way qmail interacts with
procmail. The preline script or something might not be working correctly, I
will do my best to check.
Thanks,
=Dave=
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail