Stop incoming mail if message queue exceeds set value
gary at sgluk.com
Mon Apr 27 12:02:16 IST 2009
Well, there are many options... confMAX_DAEMON_CHILDREN, and confCONNECTION_RATE_THROTTLE will control how many open connections / concurrently accepted connections there are... Setting these low(ish)will help.
http://www.milter.info/sendmail/milter-limit/ is another option.
Depending on what you want to achieve, and how big your budget is, some proper network load balancing may be another answer.
mailscanner-bounces at lists.mailscanner.info wrote:
> Thanks, have implemented these already. The issue is not on
> the load, the load stays pretty under control. I just want
> to stop accepting mail on the
> 1 server so the mails are forced to go to the other servers,
> i.e. 1000 messages handled by 4 servers will be quicker than 1000
> mails handled by 1...
> -----Original Message-----
> From: mailscanner-bounces at lists.mailscanner.info
> [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf
> Of Gary Pentland
> Sent: 27 April 2009 12:47 PM
> To: 'MailScanner discussion'
> Subject: RE: Stop incoming mail if message queue exceeds set value
> Look here...
> Particularly these...
> confQUEUE_LA QueueLA [varies] Load average at which
> queue-only function kicks in. Default values is (8 * numproc)
> where numproc is the number of processors online (if that can
> be determined).
> confREFUSE_LA RefuseLA [varies] Load average at which
> incoming SMTP connections are refused. Default values is (12
> * numproc) where numproc is the number of processors online (if that
> can be determined).
> confDELAY_LA DelayLA  Load average at which sendmail will
> sleep for one second on most SMTP commands and before
> accepting connections. 0 means no limit.
> But a few others might be of use. Be sure you're rejecting
> invalid recipients during the SMTP dialouge and not at some
> stage later. It sounds obvious but can easily be missed and
> result in 1,000s of messages from a bot being queued and work
> being done on them, reject these before you queue them!
> mailscanner-bounces at lists.mailscanner.info wrote:
>> I am running a round robin dns mail solution with 4 mailscanner
>> servers accepting mail. The problem I am having is that on occasion
>> 1 of the servers gets hit with massive volumes over a very short
>> time so the queue can grow to 5000+ in a matter of minutes causing
>> mail delivery delays on that specific server. I would like to be
>> able to set a limit on the queue size so that the server stops
>> accepting mail until the queue drops below that set value.
>> I have tried with sendmail creating 2 cf files but can't get it
>> working. Does this have to be managed by mailscanner, r can it be
>> done in sendmail?
>> Currently using sendmail-8.14.1 and Mailscanner 4.63.8
>> Gordon Colyn
>> Office : 086 123 ITNT (4868)
>> Cell : 083 296 7534
>> Fax : 086 520 0885
>> InTheNet Technologies
>> MSN:gordoncolyn at hotmail.com
>> SKYPE:gordoncolyn <skype:gordoncolyn?call>
>> Confidentiality: This e-mail including any attachments is intended
>> for the above named addressee(s) only and contains confidential
>> information. If you have received this email in error you must take
>> no action based on its contents, nor must you reproduce or show the
>> e-mail or any attachments or any part thereof or communicate the
>> contents to anyone; please reply to the sender of this e-mail
>> informing them of the error.
>> Viruses: We recommend that in keeping with good computing practice
>> the recipient should ensure that e-mails received are virus free
>> before opening.
>> __________ Information from ESET NOD32 Antivirus, version of virus
>> signature database 4035 (20090425) __________
>> The message was checked by ESET NOD32 Antivirus.
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> Before posting, read http://wiki.mailscanner.info/posting
> Support MailScanner development - buy the book off the website!
> __________ Information from ESET NOD32 Antivirus, version of
> virus signature database 4036 (20090427) __________
> The message was checked by ESET NOD32 Antivirus.
More information about the MailScanner