Pegasus Mail & Mercury

Welcome to the Community for Pegasus Mail and
The Mercury Mail Transport System, the Internet's longest-serving PC e-mail system!
Welcome to Pegasus Mail & Mercury Sign in | Join | Help
in
Home Blogs Forums Downloads Pegasus Mail Overview Mercury Overview Wiki

Connection Error in MercuryE client when sending non-local email.

Last post 09-30-2016, 20:04 by Anaglypta. 2 replies.
Sort Posts: Previous Next
  •  09-30-2016, 16:35

    • Anaglypta is not online. Last active: 29 May 2019, 12:03 Anaglypta
    • Top 500 Contributor
    • Joined on 09-30-2016
    • Luton, England
    • Member
    • Points 345

    Connection Error in MercuryE client when sending non-local email.

    Hello all,

    I've been testing Mercury 4.80 because I need to replace an ageing Infinite Interchange server.

    During my initial testing, everything seemed to work without problem. The testing was done on a Windows 10 laptop.

    I have now installed Mercury on my ageing Windows 2000 server, and disabled Infinite Interchange. I've recreated the settings I had on the laptop and started testing again.

    Now everything works except for sending non local email which gives a connection error.

     

    MercuryE Session LOG

    15:19:56.113: --- 30 Sep 2016, 15:19:56.113 ---

    15:19:56.143: Connect to '74.125.23.27', timeout 60 seconds.

    15:19:56.173: 5: Connect failed, 10053 (ECONNABORTED)

    15:19:56.203: --- 30 Sep 2016, 15:19:56.203 ---

    15:19:56.213: Connect to '173.194.72.26', timeout 60 seconds.

    15:19:56.243: 5: Connect failed, 10053 (ECONNABORTED)

    15:19:56.273: --- 30 Sep 2016, 15:19:56.273 ---

    15:19:56.313: Connect to '66.102.1.26', timeout 60 seconds.

    15:19:56.343: 5: Connect failed, 10053 (ECONNABORTED)

    15:19:56.373: --- 30 Sep 2016, 15:19:56.373 ---

    15:19:56.383: Connect to '173.194.220.26', timeout 60 seconds.

    15:19:56.433: 5: Connect failed, 10053 (ECONNABORTED)

     MercuryE LOG

    T 20160930 151540 57ee68b8 Job MO000D98 processing complete.

    T 20160930 151956 57ee68b9 Begin processing job MO000007 from redacted@redacted

    W 20160930 151956 57ee68b9 Error connecting to primary server '74.125.23.27'.

    W 20160930 151956 57ee68b9 Error connecting to alternate server '173.194.72.26'.

    W 20160930 151956 57ee68b9 Error connecting to alternate server '66.102.1.26'.

    W 20160930 151956 57ee68b9 Error connecting to alternate server '173.194.220.26'.

    E 20160930 151956 57ee68b9 Processing of job MO000007 incomplete or failed.

    T 20160930 151956 57ee68b9 Job MO000007 processing complete.

     

     If I quit Mercury and start Infinite Interchange and resend my message it works as it always did. Help!

     (Infinite Interchange and Mercury are installed on the same machine, but obviously not running at the same time)

    John 

  •  09-30-2016, 17:30

    • Rolf Lindby is not online. Last active: 2019-09-21, 18:34 Rolf Lindby
    • Top 10 Contributor
    • Joined on 05-08-2007
    • Stockholm, Sweden
    • SuperStar
    • Points 26,350
    • BetaTeam Moderator SystemAdministrator

    Re: Connection Error in MercuryE client when sending non-local email.

    So apparently there is something in the Windows 2000 Server environment that is causing networking issues. If there is any local anti-malware or firewall software running you could try disabling it. Doing a Telnet connection on port 25 to one of those destinations might give additional information. 

  •  09-30-2016, 20:04

    • Anaglypta is not online. Last active: 29 May 2019, 12:03 Anaglypta
    • Top 500 Contributor
    • Joined on 09-30-2016
    • Luton, England
    • Member
    • Points 345

    Re: Connection Error in MercuryE client when sending non-local email.

    Rolf Lindby:

    So apparently there is something in the Windows 2000 Server environment that is causing networking issues. If there is any local anti-malware or firewall software running you could try disabling it. Doing a Telnet connection on port 25 to one of those destinations might give additional information. 

     

    Hello Rolf,

    Sometimes it's the simplest things that throw you!

    I spent several hours going through the server's Policy, and Active Directory settings to no avail. Firing up a command prompt and Telnetting to one of the IP's as you suggested, came back with an almost instant failure. (Unusual as Telnet normally takes several seconds to time out if there's a problem). Checking the router's NAT Sessions table showed no port 25 sessions from the server,  which is a sure sign that something was blocking the connection.

    Running on my ageing server is an equally ageing copy of McAfee VirusScan Enterprise which has an Access Protection definition for preventing mass mailing viruses from using port 25.

    Adding Mercury.exe to the exception list solved the problem and Mercury proceeded to disgorge the contents of its queue to the wider internet, rather like a drunken British teenager empties his stomach after a Friday night binge! :D

    Thanks again for your help Rolf

     

    John. 

     

View as RSS news feed in XML

Contact | Advertise | Host provider: PraktIT | Terms of Use | Privacy Statement
Copyright © 2007-2011 David Harris / Peter Strömblad. | Pegasus Mail Home Page