Carlos E. R. wrote:
On 2014-05-07 15:35, Per Jessen wrote:
Carlos E. R. wrote:
Some way longer:
spamd: clean message (-2.7/5.0) for cer:1000 in 57.3 seconds, 5630 spamd: clean message (-2.6/5.0) for cer:1000 in 53.2 seconds, 7839 bytes.
(see the size)
or
spamd: identified spam (6.5/5.0) for cer:1000 in 213.1 seconds, 15976538 by
That's a very large spam-mail - quite unusual. 213 seconds to process it could be caused by lots of DNS timeouts.
But it is not spam :-)
According to spamassasin it was :-)
Yes, it could be DNS timeouts. I have the vague idea that cpu load was high, but I'm unsure. I would have to force filter it again with spamd - ah, I know how. Send to another local account.
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 13292 cer2 20 0 390280 296056 2112 R 99,87 3,613 0:20.82 spamd child
So, it is not DNS timeouts, it is really processing load.
Then it's simply due to the size of it. SA is generally speaking a large collection of regex'es, they're totally CPU-bound.
It went a bit faster than the other time, /just/ 173 seconds.
And this time it was thought clean. Go figure.
If you want to know, look at the rules that were hit. -- Per Jessen, Zürich (14.5°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org