On Wed, Feb 26, 2003 at 03:23:51PM -0700, Robert Stoeber wrote:
At 01:43 PM 2/26/2003, Devin Rubia wrote:
By the looks of these logs, that incoming e-mail is hitting another rule
in your filters before it hits the one we have been talking about.
What are the contents of the rule that delivers to:
| /home/vpopmail/bin/vdelivermail '' bounce-no-mailbox
That would be the one stopping that e-mail from being deleted.
I attached the whole filter below which ends up sending 'good' messages to
spamassassin (spamc) for processing before final delivery. That all works
great - my own mail gets filtered and every message has the X-Spam header,
so I know the filter is working.
But the rule that's failing sometimes (apparently) is the very first
thing. I wanted to trap that junk before wasting any further processor
cycles on it.
Here's something that might be a clue. I must have sent 100 test messages
to the 'bad' address now. Every single one gets trapped by the filter
rule. Messages that seem to fail/miss the test are true junk mail with
goofy headers. Is it possible that maildrop isn't seeing such headers
properly?
Here's the mailfilter file:
import HOME
import EXT
import HOST
VPOP="| /home/vpopmail/bin/vdelivermail '' bounce-no-mailbox"
VHOME=`/home/vpopmail/bin/vuserinfo -d $EXT@$HOST`
logfile "/tmp/junkmail/Maildir/maildrop.log"
if ( /jsmith/:h )
{
log "Rule 1: $MATCH"
EXITCODE=0
exit
}
[SNIP]
Now that is odd. If that is the first rule in your mailfilter, then
that mail should not be getting through. Do you have a copy of the
headers from the message that slipped through? Maybe there is something
in there that could be causing maildrop not to match "jsmith"?
If you still have a copy of the message, you could also try manually
feeding it to maildrop and see what happens.
14 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] filters only work som...
