A while back i posted about how mis-setting the HOST variable
wasn't causing procmail 3.22 to abort processing as expected.
As the issue came up again today in another new recipe, i
took a closer look, and found that rcfile processing does
indeed seem to be stopping immediately, but the message
is also getting delivered to $DEFAULT. I'm pretty sure
that's not the documented behavior. Is there something i'm
missing?
:0
* ^Subject: blahtest
{
LOG="*** Got test message (${LOGNAME}, ${DEFAULT}) ${NEWLINE}"
VERBOSE=yes
HOST=
}
LOG="*** Still here! (${LOGNAME}, ${DEFAULT}) ${NEWLINE}"
VERBOSE=no
--- begin log ---
*** Got test message (matt, /var/spool/mail/matt)
procmail: [2970] Tue Feb 19 16:01:33 2002
procmail: Assigning "HOST="
procmail: HOST mismatched "myhost"
procmail: Assigning "PATH=/home/matt/bin:/bin:/usr/ucb:/usr/local/bin"
procmail: Locking "/var/spool/mail/matt.lock"
procmail: Assigning "LASTFOLDER=/var/spool/mail/matt"
procmail: Opening "/var/spool/mail/matt"
procmail: Acquiring kernel-lock
procmail: Unlocking "/var/spool/mail/matt.lock"
From matt(_at_)myhost Tue Feb 19 16:01:33 2002
Subject: blahtest 1
Folder: /var/spool/mail/matt 850
--- end log ---
So it looks like rcfile processing does cease as expected,
but the message still goes to the default maildrop. Is
there a build or runtime option i'm missing that might be
causing this? There are no other rcfiles beside the system-
wide /etc/procmalrc. Here's how procmail gets run by sendmail:
Mlocal, P=/usr/local/bin/procmail, F=lsDFMAw5:/|@qSPfhn9,
S=EnvFromL/HdrFromL, R=EnvToL/HdrToL,
T=DNS/RFC822/X-Unix,
A=procmail -Y -a $h -d $u
Thanks in advance for any clues...
-Matt
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail