Karsten Bräckelmann-2 wrote: > > On Wed, 2010-07-21 at 01:12 -0700, Ted Mittelstaedt wrote: >> On 7/20/2010 11:55 PM, Daniel Lemke wrote: > >> > To hijack the thread: Does anyone know an optimum for message size >> limit? >> > Ours is set to 2MB at the moment, but we have problems when receiving >> large >> > text mails (e.g. more than 1MB) as the message check will become REALLY >> time >> > consuming. This leads to a curious situation where our Exchange (or >> maybe >> > it's the external mail server, not sure of that) sends the message >> again >> > after ~55 seconds, so the next child begins checking the mail... And >> there >> > we've got a loop (until the server runs out of memory)... > > So *why* does Exchange re-try after less than a minute? > >> > I set the --timeout-child of spamd to 45 secs now, what's working as a >> > workaround for now, but there may exist a more solid solution, is that >> > correct? > > That's a rather low timeout-child value. And it isn't clear if that 45 > secs is a raised or lowered timeout, compared to what you had before. > > If it was even lower before, then that seems to be the issue. And might > even explain the impatient Exchange. If, however, it was higher before, > and you lowered it to timeout faster than Exchange forcefully re-trying > a mail that's still being processed -- you should look after Exchange. >
It was higher before, so yes, it's just a dirty workaround to prevent this curious loop situation. However, I guess it's not an issue with our Exchange, but with our glue (which implements the SpamAssassin protocol and some other extensions) between Exchange and SpamAssassin. But with the lowered message size limit, I hope to avoid this situation anyway. However, I like that concept of amavisd-new, only passing only a specific amount of bytes to SpamAssassin. Shouldn't be a big deal to implement something similiar on our glue. Daniel -- View this message in context: http://old.nabble.com/Does-SpamAssassin-perform-tests-scans-on-attachments--tp29222058p29234031.html Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
