exitcode=75 [was: Question about Mutt macro and output]
David Relson
relson at osagesoftware.com
Wed Mar 19 16:31:06 CET 2003
At 10:19 AM 3/19/03, Boris 'pi' Piwinger wrote:
>David Relson wrote:
>
> >> >> :0fw
> >> >> | bogofilter -u -e -p
> >> >>
> >> >> :0e
> >> >> { EXITCODE=75 HOST }
> >> >
> >> > Exitcode==75 tests for X_TEMPFAIL (see sysexits.h).
> >
> > I should have said "The test 'EXITCODE=75' is testing for a temporary
> > failure so that procmail will run bogofilter again at a later time. The
> > value '75' is return code EX_TEMPFAIL as defined in /usr/lib/sysexits.h".
>
>Actually it means that procmail creates this exitcode, so
>the mail appears to have failed temporarily. Whatever that
>might be good for. Right?
Yes. If it's bad code in bogofilter, unfortunately there's no number of
retries will fix the problem. I think we've had an error or two like that
in the early code for mime-decoding and killing html comments. A temporary
problem like a database locking failure, which we've also had, will be
handled by this. It has been many weeks since this code has been _needed_,
but it's still useful.
> >>What do you mean by test? The EXITCODE is set.
> >
> > If bogofilter fails (for whatever reason), it can be useful to have
> > procmail retry.
>
>Actually, that is the effect.
Yes.
More information about the Bogofilter
mailing list