>> 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
> I might add to Eric's suggestion that possibly you have "SpamAssassin"
> included in the mix, and you are potentially causing the messages being
> submitted to "Timeout" SpamAssassin, which I've seen cause duplicates on my
> server. (Usually inbound mail, during large spam bot attacks).
>
> Any easy way to determine this is to look at the message headers on the
> first of the duplicate e-mails (Not the last one they get) and see if the
> SpamAssassin scores are (?/?), indicating SpamAssassin "Timed out". If so,
> that's likely your issue. This issue causes what Eric refers to, but in
> reverse. You're web server sends the message to your mail server, it times
> out on accepting it, and the web server re-queues it for delivery, and sends
> it again...So, in fact, your web server may be sending it twice, and qmail
> is simply taking it twice and delivering it.
>
> If it turns out to be this, simply exempt your web server from SpamAssassin
> in your SpamAssassin config, or find a way to lower the load on your mail
> server during the 800 simultaneous message deliveries.
>
>
> Michael J. Colvin
>
>
Thank you Michael, but spamassassin is only active on incoming mail
so I don't think this would be the problem
Best
Greg Cirino
_______________________________________________
spamdyke-users mailing list
[email protected]
http://www.spamdyke.org/mailman/listinfo/spamdyke-users
