Thread: [maildropl] drop / delete messages
Brought to you by:
mrsam
From: Robert S. <Ro...@us...> - 2003-01-25 03:57:00
|
Help, Sorry about the lengthy message, but I thought it best to provide lots of info. Perhaps I'm just interpreting the logs below incorrectly. The word "deferral" has me confused since the message is clearly being processed and not deferred. What I've got is a bunch of users that don't exist anymore. They have been gone long enough that I'm not worried about real mail, but these guys get a ton of junk, maybe two tons every day. So all I want to do is drop or delete the messages with no further processing. I don't want them to bounce either. Unfortunately, I can't get it to work. It seems like I should be able to create a filter to recognize the To: address and then just send the message to never-never land. I'm sure that I can recognize the proper messages now, but I can't make them disappear - they always end up getting processed by the spam filters that these messages should not pass through. The maildrop man page refers to "deleting" messages, but I've not been able to find a description of how to do that. Once before I was told that the exit command would drop the message and not process it further, but that doesn't seem to work. My environment is RedHat Linux / qmail / vpopmail / maildrop / SpamAssassin I'm calling maildrop from .qmail-default like this: | maildrop -V 2 mailfilter A couple of examples of what I tried follow, along with some log output. Can anyone tell me what I'm doing wrong? Can't I just delete the message as soon as I see it? With the following filter the messages end up getting processed and put into the specified junk mailbox. But they are getting processed for spam on the way to the mailbox, which I don't want. And I have to purge them from the mailbox regularly. if ( /darenz@/ ) { to "/tmp/junkmail" } With this next filter, with and without setting EXITCODE manually, the messages end up going through the spam filter. Output from logs is shown below so you can see that the message is fully processed for spam, which is a waste of time I want to eliminate. if ( /darenz@/ ) { EXITCODE=0 exit } Here's the output from /var/log/qmail/current where you can see the message was not stopped at the filter, it was processed when I wanted it to disappear. But then what? Sorry, no mailbox message since the user doesn't exist. So I assume it's bouncing, which I also don't want. @400000003e32073f2cadd7e4 status: local 0/10 remote 0/20 @400000003e32088a2c1d6f24 starting delivery 972: msg 16230 to local usa...@us... @400000003e32088a2c1da9bc status: local 1/10 remote 0/20 @400000003e32088a3817cf54 delivery 972: deferral: Message_start_at_0_bytes,_envelope_sender=vpopmail/maildrop:_Attempting_mailfilter/maildrop:_Filtering_through_`/home/vpopmail/bin/vuserinfo_-d_$EXT@$HOST`/maildrop:_Filtering_through_xfilter_/usr/bin/spa...@us.../maildrop:_Delivering_to_/Maildir/.SPAM//maildrop:_Delivering_to_|_/home/vpopmail/bin/vdelivermail_''_bounce-no-mailbox/Sorry,_no_mailbox_here_by_that_name._vpopmail_(#5.1.1)/maildrop:_error_writing_to_mailbox./maildrop:_Delivering_to_/var/spool/mail/vpopmail/ @400000003e32088a3818968c status: local 0/10 remote 0/20 Here's the information from /var/log/maillog where you can see that the message was processed by SpamAssassin: Jan 24 20:46:08 durango spamd[27487]: processing message <00003cac5de7$00002582$000...@mx...> for da...@us...:89, expecting 4036 bytes. Jan 24 20:46:08 durango spamd[27487]: identified spam (32.4/5.0) for da...@us...:89 in 0.1 seconds, 4036 bytes. -- Robert Stoeber USA Business Networks, LLC Robert@USABusiness.net P.O. Box 682402 435.901.9931 UT Park City, UT 84068-2402 973.735.2102 NJ www.usabusiness.net |