Mike
Ironically, I was able to find this the other day and it probably related
certain network connections. For example, I was seeing it only with two
people on this list but not anyone else. It was related to a change made to
detect a faster shutdown. The above shows the problem
05:20:05 C: DATA
05:20:05 S: 354 Enter mail, end with "." on a line by itself
05:20:15 C: QUIT
The 10 secs and a QUIT was the bug. In the original code, it was a 10 mins
wait, enough time to see the 250 response. But a shutdown took longer. So
it was changed to a 10 sec loop wait for a total of 10 mins and at each 10
seconds it checks for shutdown (close) command.
But it didn't wait the total 10 mins. After the first 10 secs and not seeing
a 250 response, it prematurely stopped waiting the full 10 mins and sent the
QUIT and that means another retry.
Anyway, waiting to see of other reports, I will post a hot fix on the AUP
shortly.
-----------------------------------------------------------------
List archives located at: https://mail.dcsol.com/login
username "rebel" password "builder"
Unsubscribe: rebel-builders-unsubscribe@dcsol.com
List administrator: mike.davis@dcsol.com
-----------------------------------------------------------------
