> On 09/08/2009 01:50 PM, Jason Haar wrote: > > We're having problems with a particular class of email. >400K in size, > > text-only. spamd takes 40-80sec to process it, and spamc is set with a > > 30sec timeout. The long processing time isn't network-related: it's > > all those "body" searches that are causing the hang.
On 08.09.09 16:27, Jason Haar wrote: > Just to follow myself up, it looks like "spamc -t 30" means if spamd > doesn't return in 30sec, spamc will simply output the email to stdout > and exit. spamd carries on processing the email and I can see the final > spamd syslog report when it finishes in >30sec. Unfortunately we > re-invoke spamc and it just goes through the same problem again :-( It's > a pity spamd can't keep a small cache of checksum'ed previous messages > and their scores, so that if it sees the same message again within (say) > 10-30 min, it just throws up the cached score? That could cause other troubles. Note that at second scan of the same message the result can be much different mostlu because of network checks. It would also make spamd more complicated for no good reason. Simply use spamc -t 120 or 180, I think up to 240 is safe at SMTP level unless you are using other time-consuming test (data phase should end in 5 minutes otherwise client may assumt the connection hanged and close it). -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Silvester Stallone: Father of the RISC concept.
