Greg Cirelle Enterprises wrote: > > >>> You're close, but not quite there. >>> >>> Spamdyke (v4) can impose two different timeouts depending on the >>> configuration, one for the total session and one for inactivity. However, >>> spamdyke is only active on *incoming* smtp sessions, so spamdyke doesn't >>> come into play in this scenario. >>> >>> What's probably happening is that during the day your server or bandwidth >>> are overloaded to the point where a receiving server times out, qmail sees >>> that there was no acknowledgment of successful transmission, and >>> reschedules >>> delivery, resulting in the duplicate. I'd try throttling back the number >>> of >>> concurrent remote tasks. You should have a >>> /var/qmail/control/concurrencyremote file that specifies this value. >>> See "man qmail-send" for details. >>> >>> -- >>> -Eric 'shubes' >>> > Thank you Eric, the current value is 600 will try reducing this some, I > think > the original value was 400
Wow. A more appropriate value here should cure your problem. FWIW, the default for qmail is 20, and qmail-toaster's default is 60. You want this value to be somewhat less than what it would take to saturate your available bandwidth. How much less depends on how much bandwidth you need to reserve for other concurrent activity (incoming mail, dns, etc). -- -Eric 'shubes' _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
