Pipe timeout problem with 0.14.3-1
David Relson
relson at osagesoftware.com
Sun Sep 14 22:30:52 CEST 2003
On Sun, 14 Sep 2003 19:27:57 +0100
"Laurence" <ljng at hbbs.org> wrote:
> Hi, I just installed 0.14.3-1 using Debian's dselect. I'm using exim
> as my MTA so my .procmailrc is configured with the default:
>
> :0fw
> | bogofilter -u -e -p
>
> # if bogofilter failed, return the mail to the queue, the MTA will
> # retry to deliver it later
> # 75 is the value for EX_TEMPFAIL in /usr/include/sysexits.h
>
> :0e
> { EXITCODE=75 HOST }
>
> Now all messages get stuck in the queue - they eventually get returned
> with"pipe delivery process timed out".
>
> I've looked in all the relevant logs and nothing helpful is logged.
>
> Any suggestions what to try?
>
> Thanks,
> Laurence
Greetings Laurence,
I can't say exactly what problem you're encountering, but ther _are_
several things to try. First, procmail is willing to reveal much about
what is going on, if you set the proper symbols. I have the following:
VERBOSE=yes
LOGABSTRACT=yes
LOGFILE=/var/log/procmail
Also, relevant are:
MAILDIR=/var/spool/mail
BOGOFILTER_DIR=/var/lib/bogofilter
though bogofilter is perfectly happy ing ~/.bogofilter/ as private (per
user) storage for each user.
Looking at the flags you're using with bogofilter, '-u' turns on
auto-update mode which requires write access to the database. Have you
checked to see where wordlist.db is stored and if its permissions are
good? My procmailrc includes the '-l' flag for logging info on what
bogofilter does, i.e.
:0fw
| bogofilter -p -u -l -e -v
#### begin error catcher ####
# if bogofilter failed, return the mail to the queue, the MTA will
# retry to deliver it later
# 75 is the value for EX_TEMPFAIL in /usr/include/sysexits.h
:0e
{
EXITCODE=75
HOST
}
Hope this helps!
David
More information about the Bogofilter
mailing list