On Thu, 6 Jan 2000 11:07:49 -0600, "Larry P . Schrof"
<schrof(_at_)cig(_dot_)mot(_dot_)com> wrote:
o Is procmail writing to /var/mail/<USERNAME> because it falls off the
end of /etc/procmailrc and still considers itself in a non-delivered
state?
If so, isn't this contradicotry to the man page exceprpt:
Delivering recipes are those that cause header and/or body
of the mail to be: ... absorbed by a pro-
gram ...
How so? The first delivery failed. Assigning EXITCODE a value is not a
delivering action.
o I really need to tell procmail to NEVER EVER write to /var/mail. I
don't want to use the '-t' command-line argument to do this because
bounces will never be generated. Can the DELIVERED variable be used to
somehow do this?
Probably, but it's probably also a bad idea. If you really really
badly want to prevent Procmail from delivering to /var/mail, perhaps
you should run it with procmail -m instead. (Haven't really looked
into this. Careful.)
o Could someone suggest a rewrite of the above RC file excerpt, so as
to keep mail from ever getting written into /var/mail , especially
upon an error of the delivery agent?
# ... same stuff as before, up to
:0e
{ EXITCODE=$? HOST }
The HOST (which is a shorthand assignment, really; HOST=empty) makes
Procmail drop everything there and then, and thus give up delivery.
/* era */
--
Too much to say to fit into this .signature anyway: <http://www.iki.fi/era/>
Fight spam in Europe: <http://www.euro.cauce.org/> * Sign the EU petition