Brian J. Murrell wrote: > On Wed, 2009-03-25 at 15:01 -0400, Michael Scheidell wrote: > > > > Match your MTA processes to the spamd children. Your MTA will send > > 4xx 'busy now, come back to play later' message. Let the sending > > MTA queue it back up (or zombies will just go away) > > I don't really see that as a socially responsible action. If my > mailserver was completely loaded to the point of not even being able > to queue a message, I'd buy pushing back on the sender with a 4xx, > but the reality is that while I may have maxed out my spamd children, > I can likely still receive and queue mail locally. > > The queueing up of mail to spamd really belongs on the local server, > and should not become a burden on sending MTAs.
This really depends on where you are running SA in the delivery process. If you are running it during the SMTP transaction, you would need to return a 4XX to avoid overloading SA. Alternately, you could limit the number of incoming connections, which would have a similar effect. On the other hand, if you are running SA during delivery, your MTA has already accepted and queued the mail, so the only thing you are limiting is the number of concurrent deliveries. I don't really see a downside at that point. > I'm kinda gathering that this is not possible within spamassassin > itself. Probably in fact it is for at least some MTAs but how to > achieve it becomes MTA specific and OT here. SA is not capable of any sort of queuing. If you need that, you will have to make your MTA do it one way or another. -- Bowie
