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. > >
