The Smartermail 601 error, mostly, is a generic error message which can appear when there is DNS issues.
Here at Ibmi Media, as part of our Server Management Services, we regularly help our Customers to perform related DNS queries.
In this context, we shall look into the causes and fixes to this error.
Nature of Smartermail 601 error ?
Recently, one of our customers came across a bounce-back message starting with, "Remote host said: 601 Attempted to send the message to the following ip's:"
Though a generic error message, the exact reason for this error can be found from the lines that follow it.
For instance, a typical error message looks like this:
Could not deliver message to the following recipient(s):
Failed Recipient: email@example.com
Reason: Remote host said: 601 Attempted to send the message to the following
xxx.xx.xx.xx (recipient ip address)
Causes and fixes of of Smartermail 601 error ?
1. IP blacklist
One of the common reasons can be our sending IP address blacklisted in any RBL. Generally, this happens in the case of shared hosting environments where multiple users share a common mailing IP address.
Thus the first step is to confirm if the IP address is on the blacklist or not. To do so, we can use online tools like mxtoolbox.
On the other hand, to fix the error immediately without waiting for the delisting, we need to set up a new Outgoing Gateway.
We can update this from, "Settings > Routing > Outgoing Gateways >New".
2. DNS records
At times this error occurs because of a lack of proper DNS records.
Usually, the mistake will be with the SPF record. We need to ensure to include that the Smartermail IP addresses with the SPF records.
In addition, we need to ensure that the PTR records are set up correctly.
For that, we can call our ISP and ask them to active PTR records on our IP and domain name. Once activated, we have to wait for 24 hours for the changes to propagate.
We can also try setting our DNS server addresses under Settings>General.
For temporary purposes, we can use the Google public DNS servers:
Google DNS 1: 220.127.116.11
Google DNS 2: 18.104.22.168
3. Network problems
The error is likely to occur due to network issues as well. The connection could have been interrupted in transit, or dropped, or timed out.
The best way to test this is to run a telnet command from the server to the IP addresses that are in the 601 error.
Once done, we enter an EHLO command and check the response. If we get something other than a 220 response when making the original connection or a similar reply to the EHLO command we need to further troubleshoot the issue.
A network package sniffer can help with this.
It can also happen when the sending IP address blocks at the receiver. So we may need to contact the receiver end and whitelist it.