I think I figured this out. .mailfilter had a check just before the call
to SpamProbe to catch messages with blank or missing Subject headers and
empty bodies. The RegExp that searched for the empty body must have been
written poorly causing Maildrop to spend a lot of time searching through
messages with large attachments. I changed the RegExp for the empty body
to !/.+/:b, and everything seems to work.
Does this make sense and can anyone explain why?
Thanks,
Al
P.S. Thanks for Maildrop!
I'm using Maildrop 1.7.0 (Debian package) to filter mail through
SpamProbe. Almost all messages get delivered properly except those with
large attachments (known to be a problem at >137KB). Messages with large
attachments cause an exit code of 75. Attempts at redelivery fail with
the same error message. The relevant lines from .mailfilter are:
# score the mail with SpamProbe and tag it
SCORE=`spamprobe train`
xfilter "reformail -I \"X-SpamProbe: $SCORE\""
log "Completed SpamProbe - Score: $SCORE"
...and the output is:
maildrop: Filtering through `spamprobe train`
Unable to execute /bin/bash
maildrop: Filtering through xfilter reformail -I "X-SpamProbe: "
Unable to execute /bin/bash
maildrop: error writing to filter.
maildrop: Unable to filter message.
The "Completed SpamProbe..." line does not show up in the log file.
$SCORE is usually a string of the form "SPAM 0.9998434
5542938c7224d326c28ca89f69a56969" The same message goes through
SpamProbe without problems when called from an interactive bash shell.
Any suggestions for troubleshooting would be greatly appreciated.
Thanks,
2 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Unable to execute /bi...
