Remote host said: 601 Attempted to send the message to the following IP

Problem reported by Simon Boo - 5/22/2014 at 12:05 AM

Submitted

Could not deliver message to the following recipient(s):

Failed Recipient: ericyeung@wmg-group.com.hk

Reason: Remote host said: 601 Attempted to send the message to the following ip's:

116.251.204.147

Could not deliver message to the following recipient(s):

19 Replies

Reply to Thread

Employee Replied

5/27/2014 at 3:42 PM

Employee Post

601 is a generic error message. An item to check is login to the server that SmarterMail is installed on and try to telnet to the IP address 116.251.204.147 and see if you get a 220 response. If you do not this could be network related or the IP address your telneting from may be blocked on the receiving end. If you can telnet verify if the IP address that SmarterMail is sending from is the same IP address you used when doing the test.

Aleyant Replied

9/11/2014 at 9:00 AM

I get this periodically, but on investigating the logs it is always mx.google.com (or one of its aliases) on the other end. I have been recommending that my domain users make sure our outgoing Smartermail server is in their SPF record.

Today I got it for our primary domain, which most definitely does have our outgoing server in its SPF record. See this lengthy log extract:

http://pastebin.com/knNHa27L

I cannot find our outgoing IP on any blacklists; our rDNS and EHLO banner match the dns, mail7.aleyant.net. What else could cause google to reject this? And in such an unfriendly manner -- saying "Go ahead" and then disconnecting when we do?

Souhil Benammour Replied

1/12/2015 at 3:19 PM

I''m having the same problem and I can't find any solution. Help ?

Chinmay Khandekar Replied

2/11/2015 at 11:25 AM

I am unable to Telnet . But I am getting it for all companies E-Mail Account

rishikesh Somshetti Replied

3/13/2015 at 8:14 AM

Chinmay, Your IP is blacklisted with one of the hundreds of Blacklist. The reason why you are not able to send email to specific IP is the recipient is using a specific blacklist which may not be common. Check on mxtoolbox. regards, Rishikesh Somshetti NetGains Technologies Pvt Ltd., www.netgainstechnologies.com Making iT Simple CIOReview - Company of the Month!

regards, Rishikesh Somshetti NetGains Technologies Pvt Ltd., Making iT Simple Website: www.netgainstechnologies.com CIOReview - Company of the Month!

Dzung Huynh Replied

2/25/2016 at 8:48 AM

I'm having the same problem too and no solution.

Mostafa Arabameri Replied

6/7/2016 at 10:13 PM

Hello
call to your ISP and ask them to active PTR record on your ip and domain name
then after 24 hr it will be fixed

sameer.khanna Replied

9/22/2018 at 6:10 AM

Having Similar problem, not able to send mail to other than self domain.

Please help.

Nima Gholizadeh Replied

4/12/2019 at 9:14 PM

Follow and check below item and your prob is solved 100%

1- check your domain or IP to be unblocked by spam checking website, the powerful website in this range is Barracuda'

2- Try to test SMTP OUT by Telnet command by type: telnet IP port ( mostly 25 or 2525)

3- Get details about your PTR on the main domain you defined on Smartermail or etc mail server software

4- Contact to your ISP to check to open the specific port 25) -------> this may be done at first step and all solve by doing this

details: may your ISP get changes on Microtic config upon your router

PERSIAN GULF

Larry Rampenthal Replied

8/19/2019 at 12:03 PM

having the same issue with this domain getting 601 to technijian.com from transducertechniques.com
from my mail server on idcmailserver2.com
Can SOA refresh or SOA Number format cause issues?
The reverse is fine but using mail.idcmailserver in SMTP setting... will that cause issues with the reverse?

Kyle Kerst Replied

8/19/2019 at 4:52 PM

Employee Post

When you attempt to send an email through Smartermail, we first perform an MX lookup on the domain to determine what server to hand the email off to. If this lookup fails we may not be able to deliver successfully, and so I recommend checking your DNS server settings under Settings>General. You can test temporarily by adding these to your configuration:

Google DNS 1: 8.8.8.8

Google DNS 2: 8.8.4.4

Kyle Kerst IT Coordinator SmarterTools Inc. www.smartertools.com

Larry Rampenthal Replied

8/19/2019 at 5:43 PM

Most mail is working. But did check.... there are no DNS settings for Primary or secondary only hostname and Postmaster Mailbox. It has always been like that and working. Is there a default it is using?
I did read the help file on this and it says its recommended to be left blank. Would it be better to add a DNS server for primary and secondary?

Jason Blanchard Replied

8/26/2019 at 10:08 AM

I'm getting similar errors but only sending to comcast.net email addresses. I'm using the recommended google dns settings. In the logs I'm seeing errors similar to the following:

[2019.08.23] 13:01:49 [64249] System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond [2001:558:fe21:2a::6]:25

I feel like it's on comcast's end. My server isn't on any blacklists and the domains attempting to send all have spf records. I am able to successfully telnet to the comcast mx servers from my host as well.

Kyle Kerst Replied

8/26/2019 at 2:41 PM

Employee Post

Larry, by default SmarterMail will leverage the DNS servers configured in Windows, or the first available DNS server on the network. When getting 601 errors I typically start by assuming a DNS lookup failure has occurred and I adjust those settings. Setting them manually can prevent it using a DNS server on the internal network that isn't set up to handle external requests.

Jason, these errors may be related to blacklisting as Comcast can be notoriously difficult to deliver mail to depending on your IP reputation. I recommend checking out your server's blacklist status here:

https://mxtoolbox.com/blacklists.aspx

Kyle Kerst IT Coordinator SmarterTools Inc. www.smartertools.com

Larry Rampenthal Replied

8/26/2019 at 3:56 PM

My server isn't blacklisted. I think the receiving end has issues.

Kyle Kerst Replied

8/28/2019 at 11:44 AM

Employee Post

Thats definitely possible Larry. Did you try setting your DNS server addresses under Settings>General to see if this helps? You can temporarily use the Google public DNS servers:

Google DNS 1: 8.8.8.8

Google DNS 2: 8.8.4.4

If that does the trick, the DNS server available to your internal network isn't able to find a valid record associated with the domain and is failing to deliver because of it.

Kyle Kerst IT Coordinator SmarterTools Inc. www.smartertools.com

Michael Muller Replied

11/5/2019 at 11:52 AM

I'm now having this issue, too. Here's our logs, below. Note that the smtp connection timed out twice. We're using 1.1.1.1 and 8.8.8.8 as primary and secondary DNS within SM

Here's the DNS for townofcharlton.net

11:30:35.447 [22097] Delivery started for xxxxx@xxxx.org at 11:30:35 AM
11:30:41.562 [22097] Added to SpamCheckQueue (0 queued; 1/30 processing)
11:30:41.562 [22097] [SpamCheckQueue] Begin Processing.
11:30:41.718 [22097] Starting Spam Checks.
11:30:41.718 [22097] Skipping spam checks: User authenticated
11:30:41.718 [22097] Spam Checks completed.
11:30:41.718 [22097] Removed from SpamCheckQueue (0 queued or processing)
11:30:44.573 [22097] Added to RemoteDeliveryQueue (1 queued; 1/50 processing)
11:30:44.573 [22097] [RemoteDeliveryQueue] Begin Processing.
11:30:44.573 [22097] Sending remote mail for xxxx@xxxx.org
11:30:44.713 [22097] MxRecord count: '1' for domain 'townofcharlton.net'
11:30:44.807 [22097] Attempting MxRecord Host Name: 'mail.townofcharlton.net', preference '10', Ip Count: '1'
11:30:44.807 [22097] Attempting to send to MxRecord 'mail.townofcharlton.net' ip: '68.112.39.99'
11:30:44.807 [22097] Sending remote mail to: xxxx@townofcharlton.net
11:30:44.807 [22097] Initiating connection to 68.112.39.99
11:30:44.807 [22097] Connecting to 68.112.39.99:25 (Id: 1)
11:30:44.838 [22097] Connection to 68.112.39.99:25 from 216.144.202.99:61987 succeeded (Id: 1)
11:31:44.851 [22097] The smtp session has timed out.
11:31:44.851 [22097] Attempt to ip, '68.112.39.99' success: 'False'
11:31:44.851 [22097] Removed from RemoteDeliveryQueue (0 queued or processing)
11:46:47.251 [22097] Added to RemoteDeliveryQueue (1 queued; 0/50 processing)
11:46:47.251 [22097] [RemoteDeliveryQueue] Begin Processing.
11:46:47.251 [22097] Sending remote mail for xxxx@xxxx.org
11:46:47.360 [22097] MxRecord count: '1' for domain 'townofcharlton.net'
11:46:47.422 [22097] Attempting MxRecord Host Name: 'mail.townofcharlton.net', preference '10', Ip Count: '1'
11:46:47.422 [22097] Attempting to send to MxRecord 'mail.townofcharlton.net' ip: '68.112.39.99'
11:46:47.422 [22097] Sending remote mail to: xxxx@townofcharlton.net
11:46:47.422 [22097] Initiating connection to 68.112.39.99
11:46:47.422 [22097] Connecting to 68.112.39.99:25 (Id: 1)
11:46:47.453 [22097] Connection to 68.112.39.99:25 from 216.144.202.99:62381 succeeded (Id: 1)
11:47:21.524 [22097] RSP: 220 mail.townofcharlton.net
11:47:21.524 [22097] CMD: EHLO mail.MontagueWebWorks.com
11:47:22.959 [22097] RSP: 250-TOCBATSF.townofcharlton.net Hello mail.montaguewebworks.com [216.144.202.99], pleased to meet you
11:47:22.959 [22097] RSP: 250-SIZE 100000000
11:47:22.959 [22097] RSP: 250-PIPELINING
11:47:22.959 [22097] RSP: 250-8BITMIME
11:47:22.959 [22097] RSP: 250 HELP
11:47:22.959 [22097] CMD: MAIL FROM:<xxxx@xxxx.org> SIZE=5125
11:47:23.022 [22097] RSP: 250 Sender <xxxx@xxxx.org> OK
11:47:23.022 [22097] CMD: RCPT TO:<xxxx@townofcharlton.net>
11:47:36.828 [22097] RSP: 250 Recipient <xxxx@townofcharlton.net> OK
11:47:36.828 [22097] CMD: DATA
11:47:37.826 [22097] RSP: 354 Start mail input; end with <CRLF>.<CRLF>
11:48:37.855 [22097] The smtp session has timed out.
11:48:37.855 [22097] Attempt to ip, '68.112.39.99' success: 'False'
11:48:37.855 [22097] Delivery for xxxx@xxxx.org to lynn.dyer@townofcharlton.net has bounced. Reason: Remote host said: 601 Attempted to send the message to the following IPs: 
	68.112.39.99
11:48:37.855 [22097] DSN email written to 428722319 with status failed to xxxx@townofcharlton.net
11:48:37.855 [22097] Delivery for xxxx@xxxx.org to xxxx@townofcharlton.net has completed (Bounced)
11:48:37.855 [22097] Removed from RemoteDeliveryQueue (0 queued or processing)
11:48:38.900 [22097] Removing Spool message: Killed: False, Failed: False, Finished: True
11:48:38.900 [22097] Delivery finished for xxxx@xxxx.org at 11:48:38 AM	[id:x428722097]

--- Montague WebWorks Powered by RocketFusion

Michael Muller Replied

11/7/2019 at 8:40 AM

Any ideas? My customer, which was having trouble last week because of the SSL problem, is now having trouble this week with the issue, shown above. Same customer. Not good.

--- Montague WebWorks Powered by RocketFusion

Employee Replied

11/7/2019 at 8:46 AM

Employee Post

Michael,

Since you have active Maintenance and Support on your SmarterMail license key, your best bet would be to open a ticket with support for this issue so that one of our technicians can take a closer look.

Back to Community Threads

Please leave this box unchecked

19 Replies

Reply to Thread

Tags

Related Knowledge Base Articles