Do you run qmail-scanner-queue.pl SetUID or with the included Qmail-Scanner-Queue wrapper?
It has been my experience that running the perl script SetUID has weird results.. To change to the wrappered version: 1. change the top lines of qmail-scanner-queue.pl from /usr/bin/suidperl -T to /usr/bin/perl 2. chown qmailq.qmail /var/qmail/bin/qmail-scanner-queue.pl 3. chmod 755 /var/qmail/bin/qmail-scanner-queue.pl 4. issue 'make' in contrib/ directory to qmail-scanner source tree 5. install qmail-scanner-queue to /var/qmail/bin 6. chown qmailq.qmail /var/qmail/bin/qmail-scanner-queue 7. chmod 4755 /var/qmail/bin/qmail-scanner-queue Some things to take a look at.. Possible problems: mail is being seen for [EMAIL PROTECTED] or [EMAIL PROTECTED] or even [EMAIL PROTECTED] Maybe even [EMAIL PROTECTED] ----- Original Message ----- From: Rafi Khardalian <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, August 29, 2003 8:12 AM Subject: [vchkpw] qmail+qmail-scanner+vpopmail+maildrop > > Hi all, > > So I've managed to get the combination of software packages listed above, > with one glitch. The most confusing part of all of this was getting maildrop > to play nice with vpopmail. Fortunately, I happened to stumble on a script > by Howard Jones > (http://wotsit.thingy.com/haj/mailfilter-spamassassin-vpopmail.shtml) which > was pretty close to what I was trying to accomplish. > > Rather than calling spamassassin via maildrop, as done in Howard's script, > qmail-scanner provides that function for me -- being called via QMAILQUEUE. > So I've modified his script to accommodate for the change, as provided > below. All of this works as you'd expect, unless email is marked as spam > for a non-existent mailbox/user. > > SPAM flagged to [EMAIL PROTECTED] (deferral): > deferral: > Sorry,_no_mailbox_here_by_that_name._(#5.1.1)/maildrop:_error_writing_to_mai > lbox./maildrop:_Unable_to_deliver_to_mailbox./ > > Clean to [EMAIL PROTECTED] (failure): > delivery 3269: failure: Sorry,_no_mailbox_here_by_that_name._(#5.1.1)/ > > Why am I getting a deferral when the message is marked as SPAM, instead of > the correct response of a failure? The obvious annoyance here is that the > deferral ends up sitting in the queue for 'queuelifetime', repeatedly > failing to deliver before sending the bounce. At this point my mind is blank > and was hoping I could find some direction or opinions on how to get to the > bottom of this. > > I hope I've made some sense -- been a long day. > > Regards, > > Rafi > > --- > > VPOP="| /home/vpopmail/bin/vdelivermail '' bounce-no-mailbox" > VHOME=`/home/vpopmail/bin/vuserinfo -d [EMAIL PROTECTED] > BOUNCE="|/usr/bin/bouncesaying 'Sorry, no mailbox here by that name. > (#5.1.1)'" > > # Absense of this check resulted in deferred status in cases > # where spamassassin flagged email positive. > > if ($RETURNCODE > 0) > { > to "$BOUNCE" > exit > } > > if (/^X-Spam-Status: *Yes/) > { > # try filtering it using user-defined rules > exception { > include $VHOME/Maildir/.mailfilter > } > # then try delivering it to a Spam folder > exception { > # to "$VPOP" > to "$VHOME/Maildir/.Spam/" > } > # ah well, I guess they'll just have to live with disappointment > exception { > to "$VPOP" > } > } > else > { > exception { > include $VHOME/Maildir/.mailfilter > } > exception { > to "$VPOP" > exit > } > } > > exit > > > > >