Thank you.  I will try turning on the Session Logging and looking there.

Hi,
I have Mercury/32 v.4.74.  It mostly works well.

But, when I send an email from one particular server, the emails don't arrive.

In the past, this was caused by the "Content Control".  So, the "Content Control" is disabled.

"Spam Control" is also diabled.

There is one MX record, and reverse DNS is set up and working.

Please help.

Sincerely,

Victor Reinhart

One possible explanation is that the sending server uses some anti-spam service that is blocking your server. You can check common blacklists here: http://mxtoolbox.com/blacklists.aspx.

Other than that, check that the MX record contains an A record (hostname), not an IP address. 

Thank you for the suggestions.  I tried the URL for the blacklist and my domain is not listed.  The MX record is OK.

After many tests, here is what solved my problem:

Configuration, MercuryS SMTP Server, SSL tab, then uncheck all 3 checkboxes:

- Enable SSL/TLS Support on Primary Ports

- Enable SSL/TLS Support on Alternate Ports

- Diable Weak Authenticators

Once I did this, and restarted the Mercury Service, all my emails from the last 5 days appeared within a half hour, all at once. 

Subsequent emails arrive within 5 minutes of sending them.

So, it seems the SSL doesn't always work in v4.74.

My old email server is v 4.01a.  It has the single "SSL" checkbox checked, and it did not have a problem. 

Sincerely,

Victor Reinhart 

When my problem was happening, I checked the logs in the MERCURYS folder.  There was nothing in the log from the source email account.

This led me to believe the problem was in the sending email server, not mine. 

After unchecking the SSL checkboxes, the source email account now appears in the logs.  

Very strange.  I was depending on the Mercury log files to tell me if there was any attempt to send the mail to me.

I had a self-signed certificate on the new server, just like it was on the old server.

As discussed in another thread (http://community.pmail.com/forums/thread/39782.aspx) the current SSL library in Mercury will be replaced with OpenSSL in version 4.80, which should eliminate incompatibilities with some other servers. If the connecting server didn't manage to establish a connection to Mercury it presumably never got to the point of sending MAIL FROM. If you know the IP address of the server you may be able to find traces of that the in the logs.