Just to update as this was posted on the mailing list as well: The ISP is currently investigating why traffic on port 25 apparently is blocked.
Starting a few days ago, in the middle of the night, Mercury stopped being able to either send or receive email to or from outside our own system. The errors we are seeing are like this:
Connecting to 199.192.6.218
Connection error.
Attempting connection to alternate, 199.192.6.219
Connection error on alternate.
9:04:05: processing job MO001A34
Resolved MX for 'icsmerrill.com' to 64.235.150.252
Connecting to 64.235.150.252
Connection error.
etc etc. Just lots of connection errors. I enabled session logging on the Mercury E SMTP and here's an example of the results:
1:32:07.027: --- Tue Mar 08 11:32:07 2016 ---
11:32:07.027: Connect to '65.55.33.135', timeout 1500.
11:32:28.040: 15: Peer connect failure
11:32:28.040: --- Tue Mar 08 11:32:28 2016 ---
11:32:28.040: Connect to '65.55.37.104', timeout 1500.
11:32:49.069: 15: Peer connect failure
11:32:49.069: --- Tue Mar 08 11:32:49 2016 ---
11:32:49.069: Connect to '65.54.188.126', timeout 1500.
11:33:10.098: 15: Peer connect failure
11:33:10.098: --- Tue Mar 08 11:33:10 2016 ---
11:33:10.098: Connect to '65.55.92.168', timeout 1500.
11:33:31.127: 15: Peer connect failure
I am able to ping any of these addresses from the server, and our internet access is not affected. I've rebooted Mercury, as well as the Windows server itself. I've turned off the antivirus. I've turned off our PopFile spam filter. I've rebooted our system's domain controller. I've called our ISP (Comcast) and they did note that our modem went down early Saturday morning, which is about when the oldest mail messages in our mail queue currently date from. So I'm guessing that there was a power outage or something similar and some setting somewhere got corrupted in the process. But I'm at a loss as to what it might be. Any suggestions of where to look next?
We're running Mercury 4.5 on a Windows 2008 server.
