Hi,A primary server was migrated (R6.5 on a Win2003) to a R8.52 in a new box with Win2008-64bit. A few days lather we started having problems with the smtp routing to internet domains. In fact it works BUT the thing is that they start to stuck in queue for too long. The only thing that seems to help (but not in all cases) is to stop the router/smtp tasks… and reload them, as to have a “fresh” start… several times daily. With this it starts to deliver most of the messages, until the queue starts to grow again.
The parameters SMTPTimeoutMultiplier=2 and DNSServer=175.50.5.46,201.xxx.xxx.xxx (example) hasn’t improved the routing.
The queue always shows these type of delivery errors (mostly the first one):
-
Last error: The connection has timed out
-
Last error: Remote system no longer responding
-
Last error: The remote server is not a known TCP/IP host
-
Last error: SMTP Protocol Returned a Transient Error
-
Last error: Transient error received from remote server
-
Last error: 221 mx09.suantispam.com closing connection
-
Last error: 221 2.0.0 Bye
6 WaitingForDNS Waiting for DNS availability
By the way, using the on the console does resolve the IP correctly… example:
trace scania.com
Network: Determining path to server SCANIA.COM
Network: Available Ports: TCPIP
Network: Checking normal priority connection documents only…
Network: Allowing wild card connection documents…
Network: Enabling name service requests and probes…
Network: Checking for SCANIA.COM on TCPIP using address ‘SCANIA.COM’
Network: Requesting IP Address for SCANIA.COM from DNS
Network: DNS returned address 139.122.204.8 for SCANIA.COM
Network: Unable to connect to SCANIA.COM on TCPIP (The connection has timed out.)
The network, dns, etc is the same as before… also the configuration-document.
Any suggestion greatly appreciated (desperate client).