SMTP Retry setting?

[bradley13]

Hi,

I have an occasional problem sending messages using the Wingate SMTP server. Looking in the log, I see that - in the latest case - the problem is:

10/27/05 18:03:39 127.0.0.2 <system> 0000373080 Debug: Delivery for domain att.net - MX lookup succeeded
10/27/05 18:03:39 127.0.0.2 <system> 0000373080 Debug: ==== Attempting connection to gateway2.att.net[12.102.240.23]
10/27/05 18:03:39 127.0.0.2 <system> 0000373080 Debug: gateway2.att.net <=S: busy - please try later
10/27/05 18:03:39 127.0.0.2 <system> 0000373080 Debug: ==== Server gateway2.att.net closed connection

Now, if the server is busy, it does no good to immediately try again - one ought to wait a while. But Wingate tries immediately, and after 4 failures all within 10 seconds, it gives up.

Is there somewhere that one can set the delay between retries?

Thanks,

Brad

[adrien]

Hi Brad

Normally there is a 3 digit response code sent back by the server, in this case I would have expected it to be 421 server busy.

WinGate looks for the response code to determine whether the server is telling us it is an error, or not or whether the error is permanent or not.

If this server isn't sending a code, it isn't compliant with the specifications, WinGate I guess is not able to tell what the problem is. In any case, it shouldn't retry like that.

Or had you edited the log file before you pasted it in here?

Adrien

[bradley13]

Nope - I didn't do anything but copy out the log entry. I only copied one - there are four essentially identical, immediately after each other, with timestamps just a few seconds apart. Here they all are - direct copy from the log file. This is WinGate 6.0.3, should that be important...

10/27/05 18:03:03 127.0.0.2 <system> 0000373075 Debug: Delivery for domain att.net - MX lookup succeeded
10/27/05 18:03:03 127.0.0.2 <system> 0000373075 Debug: ==== Attempting connection to gateway2.att.net[12.102.240.23]
10/27/05 18:03:03 127.0.0.2 <system> 0000373075 Debug: gateway2.att.net <=S: busy - please try later
10/27/05 18:03:03 127.0.0.2 <system> 0000373075 Debug: ==== Server gateway2.att.net closed connection
10/27/05 18:03:05 127.0.0.2 <system> 0000373075 Traffic 0 26 0 0 2s
10/27/05 18:03:05 127.0.0.2 <system> 0000373075 Terminated exit code 0
10/27/05 18:03:09 127.0.0.2 <system> 0000373077 Debug: Delivery for domain att.net - MX lookup succeeded
10/27/05 18:03:09 127.0.0.2 <system> 0000373077 Debug: ==== Attempting connection to gateway2.att.net[12.102.240.23]
10/27/05 18:03:09 127.0.0.2 <system> 0000373077 Debug: gateway2.att.net <=S: busy - please try later
10/27/05 18:03:09 127.0.0.2 <system> 0000373077 Debug: ==== Server gateway2.att.net closed connection
10/27/05 18:03:11 127.0.0.2 <system> 0000373077 Traffic 0 26 0 0 2s
10/27/05 18:03:11 127.0.0.2 <system> 0000373077 Terminated exit code 0
10/27/05 18:03:24 127.0.0.2 <system> 0000373078 Debug: Delivery for domain att.net - MX lookup succeeded
10/27/05 18:03:24 127.0.0.2 <system> 0000373078 Debug: ==== Attempting connection to gateway2.att.net[12.102.240.23]
10/27/05 18:03:24 127.0.0.2 <system> 0000373078 Debug: gateway2.att.net <=S: busy - please try later
10/27/05 18:03:24 127.0.0.2 <system> 0000373078 Debug: ==== Server gateway2.att.net closed connection
10/27/05 18:03:26 127.0.0.2 <system> 0000373078 Traffic 0 26 0 0 2s
10/27/05 18:03:26 127.0.0.2 <system> 0000373078 Terminated exit code 0
10/27/05 18:03:39 127.0.0.2 <system> 0000373080 Debug: Delivery for domain att.net - MX lookup succeeded
10/27/05 18:03:39 127.0.0.2 <system> 0000373080 Debug: ==== Attempting connection to gateway2.att.net[12.102.240.23]
10/27/05 18:03:39 127.0.0.2 <system> 0000373080 Debug: gateway2.att.net <=S: busy - please try later
10/27/05 18:03:39 127.0.0.2 <system> 0000373080 Debug: ==== Server gateway2.att.net closed connection
10/27/05 18:03:41 127.0.0.2 <system> 0000373080 Traffic 0 26 0 0 2s
10/27/05 18:03:41 127.0.0.2 <system> 0000373080 Terminated exit code 0

[reinikainen]

I have encountered quite similar problem: My company's mail server is configured to reply " 450 Try again after one minute " to all SMTP delivery attempts. Somehow my wingate (6.1.1) trys again after 10 minutes which is too late - and I have no idea if it's possible to change this interval.

[Nev]

I have encountered quite similar problem: My company's mail server is configured to reply " 450 Try again after one minute " to all SMTP delivery attempts. Somehow my wingate (6.1.1) trys again after 10 minutes which is too late - and I have no idea if it's possible to change this interval.

Hi, wonder if you open:

Email --> Delivery --> Process mail every nn seconds is yours on 600 to be ten minutes?

Maybe change this to a lower value.

Report back how it goes.