Spam Filter ISP Forums : Socket Error 10054 - Invalid MX record

Socket Error 10054 - Invalid MX record : Just incase anyone else runs into...

Sat, 10 Dec 2005 11:49:15 +0000

Author: Guests
Subject: 5381
Posted: 10 December 2005 at 11:49am

Just incase anyone else runs into this issue. It was resolved byupdating the DNS entry in SpamFilter to point to a valid DNS server.The socket closed error was because the DNS server I was pointing to nolonger existed.

Socket Error 10054 - Invalid MX record : Stuart, I believe that...

Tue, 06 Dec 2005 17:02:41 +0000

Author: LogSat
Subject: 5381
Posted: 06 December 2005 at 5:02pm

Stuart,

I believe that rather than trying to troubleshoot "why" the VMWare machine is causing the TCP Socket Error, we may solve this faster by modifying SpamFilter to behave differently if that error occurs and assume it is a DNS timeout. This will cause the MX test *not* to fail, as if there are DNS timeouts SpamFilter will not be able to tell if the test passes or fails, and thus is forced to pass it to avoid false positives. We'll need a day or two to make the changes and test them, after which we'll make the new build available on the website. If we have an alpha build sooner and you're willing to test it, we'll be happy to provide it to you.

Socket Error 10054 - Invalid MX record : Roberto, I apologize for the...

Tue, 06 Dec 2005 12:52:24 +0000

Author: Guests
Subject: 5381
Posted: 06 December 2005 at 12:52pm

Roberto,

I apologize for the delay in responding to your request for my logfiles. Last night I sent in a zip of my log files. Please let me knowif you need anything else. If for some reason you did not get it,please let me know.

Thanks,
Stuart

Socket Error 10054 - Invalid MX record : We have several users who deploy...

Tue, 22 Nov 2005 13:31:39 +0000

Author: LogSat
Subject: 5381
Posted: 22 November 2005 at 1:31pm

We have several users who deploy SpamFilter under VMWare, and we usethe product ourself for testing, and fully support the environment.

So far we the only issue we heard of with VMWare are ARP requests withinvalid MAC addresses being sent from a guest. This will cause howevernoticeable TCP errors warning of duplicate IPs onthe network, both onthe actual Windows screen and in the Windows system logs. If you're nothaving these symptoms, and the server is able to access the networkwithout problem, I would not think VMWare to be a problem.

If you can please zip us to support at logsat.com a copy of yourSpamFilter activity logfiles we'll try to debug them to see what theproblem is.

Socket Error 10054 - Invalid MX record : Thanks. I'll try that. Given...

Tue, 22 Nov 2005 13:19:23 +0000

Author: BigRedN
Subject: 5381
Posted: 22 November 2005 at 1:19pm

Thanks. I'll try that.

Given that you are not confident that it is really a DNS Timeout issue,and that this is running inside a VMWare guest, have you had anyexperience with their Network Card driver causing this type of issue?Since the log times between query and error are more on the order of 4milliseconds apart, my timeout theory maybe off the mark abit..

Socket Error 10054 - Invalid MX record : Stuart, The Socket Error #...

Sat, 19 Nov 2005 18:15:55 +0000

Author: LogSat
Subject: 5381
Posted: 19 November 2005 at 6:15pm

Stuart,

The Socket Error # 10054 is a Windows Socket error, and usuallyindicates that the remote host has focibly disconnected SpamFilter. Thereference page is at http://msdn.microsoft.com/library/default.asp?url=/library/e n-us/winsock/winsock/windows_sockets_error_codes_2.asp

In short, the error is described as:

WSAECONNRESET 10054

Connection reset by peer.
An existing connection was forcibly closed by theremote host. This normally results if the peer application on theremote host is suddenly stopped, the host is rebooted, the host orremote network interface is disabled, or the remote host uses a hardclose (see setsockopt for more information on the SO_LINGER option onthe remote socket). This error may also result if a connection wasbroken due to keep-alive activity detecting a failure while one or moreoperations are in progress. Operations that were in progress fail withWSAENETRESET. Subsequent operations fail with WSAECONNRESET.

While I do not believe the error you are receiving is a dns timeoutissue, the only way to be sure is... to increase the timeout and see ifthat helps. The bad news is that SpamFilter has a fixed timeout of 5000milliseconds that it uses for all DNS queries... The good news is thatwe just uploaded in the registered user area a new build (2.6.3.493)that will allow you to modify the DNS timeout by specifying thenew value in the SpamFilter.ini by using the DNSTimeout option.

The release note for this new build are:

// New to VersionNumber = '2.6.3.493';
{TODO -cNew : Added DNSTimeout option in SpamFilter.ini to customize the DNS timeout for all of SpamFilter's DNS queries}
{TODO -cNew : Added EnableDbgLogs SpamFilter.ini option to enable separate detailed logging for troubleshooting purposes}
{TODO -cNew : Added to SpamFilter.ini several of the optional entries with their default values for users to see}
{TODO -cFix : Clicking on "Check if IP in ORBS" button in GUI could result in Access Violations being logged}

Please let us know if this works for you.

Socket Error 10054 - Invalid MX record : Recently I moved my spam filter...

Sat, 19 Nov 2005 10:55:27 +0000

Author: BigRedN
Subject: 5381
Posted: 19 November 2005 at 10:55am

Recently I moved my spam filter server to a virtual host and ever sincethen approximately 70% of the incoming messages get spam tagged becauseof being unable to resolve the mx record.

To make matters more complicated this site is utilizing a satelliteconnection and even with a local dns server, name resolution takes muchlonger than other sites. for example in a nslookup, for a mx recordthat isn't cached I need to set the timeout to 8 seconds before it willresolve without timing out.

I have used a packet anaylzer and I can not see where spamfilter ismaking this resolution query, so I am unable to find out if the DNSserver is sending back a failure, or if the product is failing on itsown.

So all that said... my question is: How can I troubleshoot this issueand is there a way to increase the timeout for MX record resolution.

Below is an example of the error :

Connection from: 68.142.198.211 - Originating country : United States
11/17/05 13:41:44:557 -- (1948) Resolving 68.142.198.211 - Errorresolving IP address (Socket Error # 10054 Connection reset by peer.)
11/17/05 13:41:44:573 -- (1948) - Invalid MX record - Socket Error # 10054 Connection reset by peer.
11/17/05 13:41:44:573 -- (1948) 68.142.198.211 - Mail from: To: will bespam-tagged

Thanks,
Stuart