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 <[email protected]> wrote: > 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 sender isn't aware of the successful delivery. > > I've bumped up the idle-timeout to 180, which I expect will remedy the > situation. > > I wonder, though, if this setting could or should be suspended during > the time which spamdyke is waiting for delivery to happen. Perhaps there > should be 2 settings - one for the incoming side and one for the > delivery side? I like keeping this setting on the low side to keep > senders from tying up incoming processes, yet the setting doesn't seem > to make any sense when waiting for scanning/delivery, especially when > spamdyke can't cancel that part of things. > > Thanks Sam. > > -- > -Eric 'shubes' > > _______________________________________________ > spamdyke-users mailing list > [email protected] > http://www.spamdyke.org/mailman/listinfo/spamdyke-users
_______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
