So by testing empirically and change my max-childrens to 5 and this is what
actually happens:
Jun 11 09:35:45 mgw1 spamd[30100]: prefork: child states: BBBBBJun 11 09:35:45
mgw1 spamd[3024]: spamd: connection from localhost [127.0.0.1]:8686 to port
783, fd 6
Jun 11 09:35:45 mgw1 spamd[30100]: prefork: server reached --max-children
setting, consider raising it
Jun 11 09:35:46 mgw1 spamd[663]: spamd: timeout: (300 second timeout while
trying to PROCESS)
This VM has 2 GB of RAM and 2 vCPUs and does only serve as a mail gateway,
nothing else really. Does SpamAssassin really need so much resources?
On Friday, June 10, 2016 11:46 PM, Devin Reade <g...@gno.org> wrote:
--On Friday, June 10, 2016 09:04:07 PM +0000 ML mail <mlnos...@yahoo.com>
wrote:
> Well right now I have max-children on 50, so you mean lowering this value
> to something like 10? But then if I receive 20 simultaneous incoming SMTP
> connection, what will happen to the 10 others?Will they fail/timeout or
> simply wait?
You're going to have to check the spamassassin docs because I don't
recall offhand. Or test empirically. The idea, if you've got too
many simultaneous scans going on, is to reduce the number of scans
to something your machine can handle without tuning it so low that
mail starts getting rejected.
I use MailScanner as part of the mix so during bursts messages get
accepted into a disk queue and then scanned at a reasonable rate. As long
as the average scan rate exceeds the average receive rate, everything
is fine. What you're going to have to check, though, is if spamassassin
will queue things when it gets busy or if just doesn't accept the
connection.
If you tune things down and can't find a workable midpoint between
rejecting too much and thrashing your machine, it argues that you either
need a beefier machine or less processing per message.
Either way, trying random delays in smtpd doesn't feel like the right
answer.
Devin
