I think I understand. You're using simscan to run ClamAV and SpamAssassin
during the delivery process, so the message will be rejected immediately if
either of those tests fails. If one of the tests takes too long, spamdyke
times out.
Unfortunately I still don't see how to do anything about t
On 02/08/2014 02:40 PM, Sam Clippinger wrote:
> I'm a little unclear here -- what scanning are you doing and when does
> it take place?
I'm not crystal clear either about exactly how everything's happening.
Simscan is invoking clamav and spamassassin. Simscan is implemented via
QMAILQUEUE="/var/
I'm a little unclear here -- what scanning are you doing and when does it take
place? How can spamdyke tell the difference between a delay caused by
something on your server versus a delay from the remote sender?
-- Sam Clippinger
On Feb 7, 2014, at 4:37 PM, Eric Shubert wrote:
> With spa
With spamdyke 4.3.1, I've come across an email which takes an inordinate
amount of time to scan, for whatever reason. I had idle-timeout=60, so
spamdyke would timeout the session, and a minute or so later the scan
completes, and the message is delivered. This causes duplicates though,
as the se