This is indicative of the Mimesweeper machine not being able to handle the
volume being passed it from the qmail machine. We've had the same issues and
the group responsible for Mimesweeper (and in our case Mailsweeper) had to add
additional load balanced machines to keep up with qmail.
I reject their suggestion of reducing my concurrency since that only pushes the
problem back to sender.
Jeff Sweeten
Sr. Internet Engineer
Aon
200 E Randolph
Chicago, Il 60601
Darren Kukulka <[EMAIL PROTECTED]> on 07/24/2001 02:33:49 AM
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc: (bcc: Jeff D Sweeten/ASC/US/AON)
Subject: Qmail resending multiple times...
Hi,
Just wanting to know if anyone has solved this behaviour...
We are running SMTP redirects via Qmail 1.03 through to a Mimesweeper mail
host.
Most messages make it through quite happily but every now and then we get
ones that hang around and get retransmitted, usually with the following
appearing in the log ;
delivery xxxxx: deferral:
Connected_to_xx.xx.xx.xx_but_connection_died._Possible_duplicate!_(#4.4.2)
Have been around the web to find someone else with a solution but to no
avail - closest I came to was some guy suggesting to check if the source
mail contained "Bare CR's" (think he was referring to bare carriage returns
but not sure).
Any ideas ?
Cheers,
Darren Kukulka
[EMAIL PROTECTED]
