Re: [vchkpw] maildrop with bounce-no-mailbox
more thoughts.. the reason why maildrop exits 75 is the sigpipe it receives, because vdelivermail exits 100 without reading the pipe. so a hack would be to always read the input, even if the user does not exist. i might prepare a patch for this on the weekend. you could test this right now by changing your to maildropfilter line to something like: VPOP=| /var/vpopmail/bin/vdelivermail '' bounce-no-mailbox to | /usr/bin/tee /dev/null 2/dev/null $VPOP hm.. i'm going to test this over the weekend instead of a patch.. -- Mit internetten Grüßen / Best Regards --- Justin Heesemannionium Technologies [EMAIL PROTECTED]www.ionium.org
[vchkpw] maildrop with bounce-no-mailbox
Hi.. although this is a highly maildrop regarded question, I have to ask here, since maildrop folks seem to be unresponsive.. some of you are using maildrop together with vpopmail, usually somewhere in the maildirfilter file there's some line like VPOP=| /var/vpopmail/bin/vdelivermail '' bounce-no-mailbox to $VPOP this works totally fine, when the user exists. however if he doesn't, vpopmail exits 100, which seems to be a great problem for maildrop: any process not exiting 0 makes maildrop exit with code 75. this is especially bad, because 75 means for qmail to defer this message and try it again and again until the queuelifetime is reached. and we all know about those little spammers trying invalid usernames... so, how do you do it? use the chkuser patch for qmail, so no illegal users get into the queue? write a wrapper for vpopmail so that it exits 0 even when the user doesn't exist? use some hack for maildrop?? each way seems to have it's own disadvantage :/ -- Mit internetten Grüßen / Best Regards --- Justin Heesemannionium Technologies [EMAIL PROTECTED]www.ionium.org
Re: [vchkpw] maildrop with bounce-no-mailbox
so, how do you do it? use the chkuser patch for qmail, so no illegal users get into the queue? write a wrapper for vpopmail so that it exits 0 even when the user doesn't exist? use some hack for maildrop?? I am also having the same problems. I hadn't noticed it until my queue was over 30,000 messages. I haven't had the time to work out a real solution yet. I didn't know if it was better to hack maildrop or hack vdelivermail since I haven't even looked into either one of them yet. What I had found was that one of my domains was receiving thousands of messages per hour for non-existent users and bouncing back. So as a quick fix, I set the default to delete, I shortened the queuelifetime to 3 days, and increased the concurrency settings because they were constantly maxed out. I'd also like to hear what real solutions people have come up with to deal with this.
Re: [vchkpw] maildrop with bounce-no-mailbox
In maildrop Make test for the user dir before process anything else. If the directory of that user doesn't exist than call a little perl prg. In the perl prg grep the domain .qmail file and check that there is a delivery to somewhere. (so catch all is exists or not) In my system if a user doesn't exists than it is bounced back to the sending server, so if I can't find a user Maildir than catch-all is enabled. (I don't remember the name of that qmail patch witch do this for me...) If there it is, then find out this new users dir, and send back this info to maildrop. Than process evrything as usual. Use vuserinfo and vdominfo. CoyoteTM - Original Message - From: Jay Tortorelli [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, July 15, 2004 11:14 PM Subject: Re: [vchkpw] maildrop with bounce-no-mailbox so, how do you do it? use the chkuser patch for qmail, so no illegal users get into the queue? write a wrapper for vpopmail so that it exits 0 even when the user doesn't exist? use some hack for maildrop?? I am also having the same problems. I hadn't noticed it until my queue was over 30,000 messages. I haven't had the time to work out a real solution yet. I didn't know if it was better to hack maildrop or hack vdelivermail since I haven't even looked into either one of them yet. What I had found was that one of my domains was receiving thousands of messages per hour for non-existent users and bouncing back. So as a quick fix, I set the default to delete, I shortened the queuelifetime to 3 days, and increased the concurrency settings because they were constantly maxed out. I'd also like to hear what real solutions people have come up with to deal with this.
