Pat,
Are you using the qmail-scanner-queue to submit directly into the maildrop
filter like this post, or via the .qmail file for the domain?
I'm not running verbose_spamassassin but I'm trying to think of any
disadvantages of doing it this way rather than altering the .qmail-default file
like I've done to submit it through.
Also, I've seen recommendations of adding the exit tag but this is the first
one I've seen suggesting a firm EXITCODE=100.
As for my original error, it actually was a file limit
exceeded...my /var/spool/mail/vpopmail file had reached 2GB. Seems the
messages that couldn't bounce stayed there and piled up over time. I'd still
like to fix this so that maildrop isn't preventing messages from bouncing or
staying in my queue, and so I shouldn't have that spool file fill up anymore.
...ken
Quoting Pat <cour...@coteobscure.ca>:
Hi Ken,
I ran into the same problem few weeks ago... Here's something that help me
alot.
http://www.geocrawler.com/archives/3/513/2003/5/0/10503826/
Happy reading :)
On Fri, 29 Aug 2003, Ken Winke wrote:
I just started seeing this pop up in my qmail send log, after noticing my
queue had been skyrocketing in size the past day.
delivery 3111:
deferral: Sorry,_no_mailbox_here_by_that_name._vpopmail_(#5.1.1)/
maildrop:_signal_0x19/
I run maildrop in my .qmail file for the individual domains to sort spam
into a separate maildir, like this...
| preline maildrop /path/to/my/filter
which has been working great for about a month. I've see the no_mailbox
error but I haven't seen the signal_0x19 before.
No bounced or error messages are replying back to the sender who attempts
to send to a non-existent address. Also, these failed messages never
leave
the queue, so my server is getting somewhat bogged down with retry
attempts
as qmail keeps trying to resend these messages. Much higher load times
that usual.
Anyone seen the signal_0x19 error and know how to get rid of it?
...ken
3 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Error 0x19 for unknow...
