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
Home Blogs Forums Downloads Pegasus Mail Overview Mercury Overview Wiki

Message delivers ok via Mercury C but not E

Last post 12-21-2018, 16:31 by Greenman. 2 replies.
Sort Posts: Previous Next
  •  12-20-2018, 19:09

    • Brian Fluet is not online. Last active: 05-31-2020, 5:06 Brian Fluet
    • Top 10 Contributor
    • Joined on 12-24-2014
    • North Carolina, USA
    • SuperStar
    • Points 31,040

    Message delivers ok via Mercury C but not E

    I need some help with an odd problem.  Messages sent to a address via MercuryC are getting delivered but ones sent via MercuryE are not.  I would appreciate some help understanding what is going on.  I confirmed this by sending a message from Mercury (Ctrl+N) by each method. 

    The entries in the MercuryE connection history window for the failure are:

    Connection error during handshake with

    Connection error during handshake with

    12:19:51: processing job MO0000A6
    Resolved MX for '' to
    Connecting to
    Connection error.
    Attempting connection to alternate,
    Connection error on alternate.

    The associated MercuryE log entries are:

    T 20181220 121951 5c1b6ad9 Begin processing job MO0000A6 from
    W 20181220 121952 5c1b6ad9 Error connecting to primary server ''.
    W 20181220 121953 5c1b6ad9 Error connecting to alternate server ''.
    E 20181220 121953 5c1b6ad9 Processing of job MO0000A6 incomplete or failed.
    T 20181220 121953 5c1b6ad9 Job MO0000A6 processing complete.

    Edit:  A subsequent test via MercuryE with session logging enabled logged this:

    15:37:14.941: --- 20 Dec 2018, 15:37:14.941 ---
    15:37:14.957: Connect to '', timeout 400 seconds.
    15:37:15.971: >> (mxgmx117) Nemesis ESMTP Service not available<cr><lf>
    15:37:15.971: >> 554-No SMTP service<cr><lf>
    15:37:15.971: >> 554-Bad DNS PTR resource record.<cr><lf>
    15:37:15.971: >> 554 For explanation visit<cr><lf>
    15:37:15.971: << EHLO<cr><lf>
    15:37:15.987: >>
    15:37:15.987: --- Connection closed normally at 20 Dec 2018, 15:37:15.987. ---

    I've looked at the explanation link buts it's beyond my level of expertise.  We have a dedicated IP address but it's from Spectrum Business so could very well be in a block of address recorded as dynamically allocated.   I see the EHLO as and wonder if that is considered a fully qualified domain name.  That's fixable if it needs to be; I just don't know.

    Thanks for any help.

  •  12-21-2018, 1:18

    • Rolf Lindby is not online. Last active: 2020-05-30, 19:35 Rolf Lindby
    • Top 10 Contributor
    • Joined on 05-08-2007
    • Stockholm, Sweden
    • SuperStar
    • Points 26,605
    • BetaTeam Moderator SystemAdministrator

    Re: Message delivers ok via Mercury C but not E

    Well, the error message says "". You can check the PTR record (rdns) for your IP address for instance here:

    A mail server is according to RFC required to have a reverse DNS record, but some sites have their own requirements. Many reject rdns names that suggest that the address is dynamically assigned, and others refuse all generic PTR addresses (such as

    If you have a fixed IP address you should be able to ask your Internet provider to set a different PTR record for that address. 


  •  12-21-2018, 16:31

    • Greenman is not online. Last active: 21 Nov 2019, 9:28 Greenman
    • Top 10 Contributor
    • Joined on 07-19-2007
    • UK
    • SuperStar
    • Points 14,300

    Re: Message delivers ok via Mercury C but not E

    15:37:15.971: >> 554-Bad DNS PTR resource record.<cr><lf>

    The arrows pointing to the right denote the remote server's response/query (arrows pointing to the left are your server's responses/queries).

    As Rolf says you need to ask your ISP to set a PTR (PoinTeR) record (a reverse lookup record which the opposite of an A Record).

    As you are probably aware a DNS query for a name requests the A record so that the name (e.g. can be resolved to an IP address. A reverse record, known as a PTR record allows you to resolve an IP address to a name. Mail servers use it as a way to ensure the name the server announces itself as matches the IP address the mail message originated from.  

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