procmail
[Top] [All Lists]

Re: Procmail/formail question

2001-06-05 00:36:47
Marshal Benton <post_bote(_at_)post(_dot_)com> writes:
CONDITION:
I have procmail scanning all locally delevered
messages. I also use procmail to filter my private
messages.

I have a recipe that works. I added a formail statment
to add a header to the mail message (that also works).
the problem is that the log file shows additional
lines which I would like not to log when the formail
statment is added.

======
etcprocmail lines

SHELL=/bin/sh
PATH=/usr/local/SOLARIS/bin:/usr/bin:/usr/ucb:/bin:/usr/local/bin:
LINEBUF=4096

Don't set LINEBUF unless you need to (and I don't see anything needing
such a big buffer in what you sent to the list).


ORGMAIL=/var/spool/mail/$LOGNAME

Uh, isn't that the default on your system?  Why are you overridding it?



JUNKDIR =       /var/junkjunk
UMASK = 000

UMASK = 0 means that *anyone* can read and write files created by procmail
(except the mailspool, which is already created before this point).
Is that just for testing, or is there a real purpose to that setting?


...
=============
recipe in question

:0
* ^Resent-From:(_dot_)*(_at_)usa(_dot_)com(>)?
{
VERBOSE=NO
LOGABSTRACT=off
  :0 fhw
  | formail -b -f -A "$good_header resend OK"

  :0
  { VALUE=GOOD }

VERBOSE=yes

You're turning VERBOSE back on here.  That's why you're getting the extra
log messages.



...
# deliver to junkdir of BAD
:0:
* $VALUE ?? BAD
$JUNKDIR

That should be

        :0:
        * VALUE ?? BAD
        $JUNKDIR

You're not expanding the VALUE variable, but rather just telling procmail
to do the regexp matching against it.


Philip Guenther
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail

<Prev in Thread] Current Thread [Next in Thread>
  • Re: Procmail/formail question, Philip Guenther <=