SMTP client logging - Messagelabs

HCL Domino Domino Forum
1

Hi.We use Messagelabs as a relay service. On a daily basis we get the following messages in the log:

08/04/2005 08:18:45 [0948:0009-0A34] SMTPClient: Attempting to Connect: Host CLUSTER2.EU.MESSAGELABS.COM, Port 25, SSL Port 0, Connecting Domain myserver.mydomain.co.net

08/04/2005 08:18:50 [0948:0009-0A34] SMTPClient: Connection terminated with status: 2055

08/04/2005 08:18:50 Router: No messages transferred to CLUSTER2.EU.MESSAGELABS.COM (host CLUSTER2.EU.MESSAGELABS.COM) via SMTP: The server is not responding. The server may be down or you may be experiencing network problems. Contact your system administrator if this problem persists.

The server usually recovers in a minute or so and successfully transmits the message. We have set our SMTPClientDebug=3. Messagelabs indicates there are no connection problems with their towers. We have done everything on our end except replace the Domino server hardware.

Question: Do any other Messagelabs users see these messages on a regular basis? Ignoring the Messagelabs aspect, is it reasonable to see these messages during daily processing?

My feeling is that if the system recovers in a minute or so then this is not really a problem. Failed connections will happen during daily processing. However, I need to confirm (somehow) whether or not these messages are “normal” or if we have a serious problem.

TIA for any info.

Bel

2

Subject: SMTP client logging - Messagelabs

We have exactly the same issue with the same cluter cluster2.eu.messagelabs.com. Messagelabs also tell us that there are no connection problems with their towers. We have also done everything short of replacing the hardware.

I personally agree with you that as long as it recovers it is not really a problem and occasional failed connections are not unexpected. However we would also like to get a definitive confirmation that this is not a problem.

As part of our resolution efforts I found these additional parameters in a trawl of the forum and technotes and added them to the server config:

SMTPTimeoutMultiplier=10

RouterDomainCacheDisabled=1

RouterServerCacheDisabled=1

Some domino admins have had an issue with smtp timeout and have needed to raise the parameter to 1000+ to resolve it. I have not gone that far yet as I’m not yet convinced it’s relevant here.

Disabling the cache has not resolved the messagelabs not responding messages. There may be an issue with resolving higher-cost MX records after the primary becomes unavailable, but I have neither confirmed that it is an issue nor found a resolution.

Have you found a definition of the 2055 status by the way?

If you’d like to discuss further my email address is james.briscoe@clyde.co.uk. It may help if we compare notes.

James