this shouldn't be happening at all if you've got the QMT installed correctly with CHKUSER (and it is on). These types of messages should be rejected BEFORE the queue--e.g. at the initial SMTP communication. Years ago, qmail USED TO reject messages post-queue with bounces, but that behavior was effectively and correctly modified by patch add-ons years ago. In this day and age, no mail server should ever reject messages post-queue with additional bounce messages. It's just improper and effectively turns your mail server into a spam server itself as you will be sending messages to what are invariably going to be forged return headers.
Additionally, if you've got the Spamdyke add-on installed, you will also have additional options on before-the-queue rejections. Tim On Fri, October 9, 2015 4:45 am, Rajesh M wrote: > dan > > sorry to contradict but in my personal opinion this is not a good idea > .... if a the sender makes a mistake then my customer will not receive the > email and nobody will know. > > rajesh > > ----- Original Message ----- > From: Dan McAllister [mailto:[email protected]] > To: [email protected] > Sent: Thu, 8 Oct 2015 15:01:57 -0400 > Subject: Re: [qmailtoaster] queue is flooding user > > I suspect the queue messages that are stacking up are for the delivery > of the bounce -- which is also likely going to a non-existent user or > domain. > > My STRONGEST suggestion is to NOT BOUNCE messages that are directed to > non-existent users!!! > To do this, cd to the top of the domain in vpopmail (e.g.: > /home/vpopmail/domains/<domain.com>) > Then examine the file .qmail-default. > You want the last word to be "delete" not "bounce-no-mailbox" > > Dan > > > On 10/8/2015 2:51 PM, Eric Broch wrote: >> No one should be able to get a message in your queue to a non-existent >> user unless they're using an account that they've hacked. >> Someone correct me if I'm wrong. >> >> On 10/8/2015 12:37 PM, Eric Broch wrote: >>> Has someone hacked a password? >>> >>> On 10/8/2015 11:59 AM, Rajesh M wrote: >>>> spammer is emailing a non existent user on my server. >>>> >>>> qmailtoaster is accepting the email and then trying to respond back >>>> >>>> my queue is flooding because ot this >>>> >>>> should'nt chkuser be directly bouncing the email during smtp >>>> transaction time when email id is not present on the server ? >>>> >>>> pl see below the message trapped in my queue. kindly let me know how i >>>> could prevent these >>>> >>>> thanks for your help >>>> >>>> rajesh >>>> >>>> log files >>>> >>>> @400000005616a19e352eb154 info msg 1840641: bytes 60095 >>>> from<[email protected]> qp 40028 uid 89 >>>> @400000005616a19e36a305bc starting delivery 1066: msg 1840641 to >>>> [email protected] >>>> @400000005616a19e36a328e4 status: local 1/200 remote 60/60 >>>> @400000005616a19e374ed234 delivery 1066: failure: >>>> Sorry,_no_mailbox_here_by_that_name._(#5.1.1)/ >>>> >>>> >>>> sample bounce message >>>> >>>> Received: (qmail 5240 invoked for bounce); 8 Oct 2015 17:23:48 -0000 >>>> Date: 8 Oct 2015 17:23:48 -0000 >>>> From:[email protected] >>>> To:[email protected] >>>> Subject: failure notice >>>> >>>> Hi. This is the qmail-send program at ns1.bizmailserver.net. >>>> I'm afraid I wasn't able to deliver your message to the following >>>> addresses. >>>> This is a permanent error; I've given up. Sorry it didn't work out. >>>> >>>> <[email protected]>: >>>> Sorry, no mailbox here by that name. (#5.1.1) >>>> >>>> --- Below this line is a copy of the message. >>>> >>>> Return-Path:<[email protected]> >>>> Received: (qmail 3803 invoked by uid 89); 8 Oct 2015 17:19:29 -0000 >>>> Received: by simscan 1.4.0 ppid: 3636, pid: 3743, t: 2.9901s >>>> scanners: attach: 1.4.0 clamav: 0.98.6/m: spam: 3.3.2 >>>> X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on >>>> ns1.bizmailserver.net >>>> X-Spam-Level: >>>> X-Spam-Status: No, score=0.0 required=5.0 tests=T_FROM_12LTRDOM >>>> autolearn=disabled version=3.3.2 >>>> Received: from unknown (HELO redbrokerage.com.inbound10.mxlogicmx.net) >>>> (187.234.134.4) >>>> by ns1.bizmailserver.net with SMTP; 8 Oct 2015 17:19:26 -0000 >>>> Received-SPF: unknown (ns1.bizmailserver.net: domain at listrak does >>>> not designate permitted sender hosts) >>>> Received: from redbrokerage.com.inbound10.mxlogicmx.net >>>> (redbrokerage.com.inbound10.mxlogicmx.net [208.65.144.3]) >>>> by redbrokerage.com (Outbound Mail Relay) with ESMTP id >>>> yZSt49AdKNeARht0 >>>> for<[email protected]>; Thu, 08 Oct 2015 13:19:29 >>>> -0400 (EDT) >>>> MIME-Version: 1.0 >>>> Message-ID:<[email protected]> >>>> Date: Thu, 08 Oct 2015 13:15:29 -0400 >>>> From: "Noemie Considine"<[email protected]> >>>> To:[email protected] >>>> Subject: contract >>>> Content-Type: multipart/mixed; >>>> boundary="------------070709070301020805080405" >>>> --------------070709070301020805080405 >>>> Content-Type: text/plain; charset=utf-8; format=flowed >>>> Content-Transfer-Encoding: 7bit >>>> >>>> Dear customer, >>>> >>>> I'm sending you a new contract of the project (Private collateral >>>> statement of account) >>>> >>>> --------------070709070301020805080405 >>>> Content-Type: application/zip; name="Private collateral statement of >>>> account.zip" >>>> Content-Description: "Private collateral statement of account.doc" >>>> Content-Disposition: attachment; filename="Private collateral >>>> statement of account.zip"; size=43024; >>>> creation-date="Thu, 08 Oct 2015 13:16:29 -0400"; >>>> modification-date="Thu, 08 Oct 2015 13:17:29 -0400" >>>> Content-Transfer-Encoding: base64 >>>> >>>> >>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail:[email protected] >>>> For additional commands, >>>> e-mail:[email protected] >>> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] -- Tim Pleiman http://support.bravosystemstech.net Bravo Systems Technologies "Advanced Open Source Solutions for Business" Chicago, IL USA **No trees were killed in the sending of this message, but a large number of electrons were terribly inconvenienced. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
