RE: [courier-users] Courier TOO good

[Josh Remus]

I apologize, as I'm certainly no courier guru since we've brought it online - what I was changing was the MAXDAEMONS in the esmtp config file.  I see that in the modules information on the web site, there are MAXHOST and MAXDELS config options.  I'm a little confused which one I want to tune, however.  Is the correct thing to change MAXDELS, since I want only, say, 10 attempted SMTP deliveries at a time?  And (correct me if I'm wrong) this wouldn't affect inbound SMTP or its deliver to local recipients?   As far as traffic shaping, I'm reading up on that as quick as I can, but am nowhere close to being ready to do that.   Thanks!   Josh -----Original Message----- From: Saxon Jones [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 28, 2003 12:19 PM To: 'Josh Remus'; '[EMAIL PROTECTED]' Subject: RE: [courier-users] Courier TOO good Are you changing the max inbound SMTP (MAXPERC MAXPERIP, etc..) or are you changing the MAXHOST in module.esmtp?  I do believe the last is the one you'd want...  You could also potentially traffic shape if your OS/kernel supports it.  FreeBSD's ipfw supports it, and I'm quite sure Linux would in some form.   ________________________ Saxon Jones   Network Infrastructure Admin Interbaun Communications Suite 200 18404 Stony Plain Road Edmonton, AB T5S 2M8   mailto:[EMAIL PROTECTED] http://www.interbaun.com/ (780) 447-8276   -----Original Message----- From: Josh Remus [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 28, 2003 9:49 AM To: [EMAIL PROTECTED] Subject: [courier-users] Courier TOO good   I've got a problem that I encountered this morning.  We have a 384 pipe in and out of here, and one of our marketing people sent out a mass-emailing (1.31 MB a piece) that completely clobbered our bandwidth.  But of course, courier handled itself just as I had hoped it would, it had no problem with the number.   When I got in, people were screaming about the bandwidth.  Turning down the maximum number of ESMTP connections (which doesn't seem to like less than 40 for that setting) doesn't cut it.  So - here's what I had to do: I moved the folders under /var/spool/courier/msgs to someplace temporary, since there were 800 in the queue.  This stopped the flood for the moment & let the normal email go in and out again.   I don't know if this is kosher at all, but courier seemed to handle those folders disappearing okay.  But I need two things:     1. I need to reintroduce those messages a little at a time, because while I could cancel the marketing email, some legit email probably got moved along with all the marketing junk.     2. I need to throttle the outgoing connections or something like that so that the mail server can not normally consume all that bandwidth, or all that bandwidth for all that time.   Ideally (which never usually happens) - I could make some changes to the configs on the mail server and somehow move all the messages back in - then they would slowly deliver themselves while keeping some of the bandwidth available for other things.   Can anyone help me out with this?  Thanks a lot, I'm up a certain creek without a paddle.  This would never have happened with the old mail server software, as it would have just crashed under that kind of load!   Thanks! --- Josh Remus Network Manager