1
Strange Delivery Issue to ymail.com (Delivered or Bounced?)
Question asked by Leo Novelli - January 20, 2015 at 11:33 AM
Unanswered
I'm trying to send an email to a @ymail.com subscriber.  It bouncing back by SM stating:

Failed Recipient: (someemail@ymail.com)
Reason: Failed to connect to the recipients mail server.  No DNS
information was found for the 'ymail.com)' domain.
Status: 544 5.4.4 Host not found (not in DNS).
 
This is what I find in the Delivery logs:
 
[2015.01.19] 13:49:05 [35658] Delivery started for someemail@SMdomain.com at 1:49:05 PM
[2015.01.19] 13:49:08 [35658] Skipping spam checks: No local recipients
[2015.01.19] 13:49:11 [35658] Sending remote mail for someemail@SMdomain.com
[2015.01.19] 13:49:12 [35658] Initiating connection to 63.250.192.46
[2015.01.19] 13:49:12 [35658] Connecting to 63.250.192.46:25 (Id: 1)
[2015.01.19] 13:49:12 [35658] Binding to local IP 206.135.15.100:0 (Id: 1)
[2015.01.19] 13:49:12 [35658] Connection to 63.250.192.46:25 from 206.135.15.100:54747 succeeded (Id: 1)
[2015.01.19] 13:49:12 [35658] RSP: 220 mta1661.mail.gq1.yahoo.com ESMTP ready
[2015.01.19] 13:49:12 [35658] CMD: EHLO mail.atlantisnet.com
[2015.01.19] 13:49:12 [35658] RSP: 250-mta1661.mail.gq1.yahoo.com
[2015.01.19] 13:49:12 [35658] RSP: 250-PIPELINING
[2015.01.19] 13:49:12 [35658] RSP: 250-SIZE 41943040
[2015.01.19] 13:49:12 [35658] RSP: 250-8BITMIME
[2015.01.19] 13:49:12 [35658] RSP: 250 STARTTLS
[2015.01.19] 13:49:12 [35658] CMD: STARTTLS
[2015.01.19] 13:49:12 [35658] RSP: 220 Start TLS
[2015.01.19] 13:49:12 [35658] CMD: EHLO mail.atlantisnet.com
[2015.01.19] 13:49:12 [35658] RSP: 250-mta1661.mail.gq1.yahoo.com
[2015.01.19] 13:49:12 [35658] RSP: 250-PIPELINING
[2015.01.19] 13:49:12 [35658] RSP: 250-SIZE 41943040
[2015.01.19] 13:49:12 [35658] RSP: 250 8BITMIME
[2015.01.19] 13:49:12 [35658] CMD: MAIL FROM:<someemail@SMdomain.com> SIZE=7340
[2015.01.19] 13:49:12 [35658] RSP: 250 sender <someemail@SMdomain.com> ok
[2015.01.19] 13:49:12 [35658] CMD: RCPT TO:<someemail@ymail.com>
[2015.01.19] 13:49:12 [35658] RSP: 250 recipient <someemail@ymail.com> ok
[2015.01.19] 13:49:12 [35658] CMD: DATA
[2015.01.19] 13:49:12 [35658] RSP: 354 go ahead
[2015.01.19] 13:49:15 [35658] RSP: 250 ok dirdel
[2015.01.19] 13:49:15 [35658] CMD: QUIT
[2015.01.19] 13:49:15 [35658] RSP: 221 mta1661.mail.gq1.yahoo.com
[2015.01.19] 13:49:17 [35658] Delivery for someemail@SMdomain.com to someemail@ymail.com has completed (Delivered)
[2015.01.19] 14:04:19 [35658] Sending remote mail for someemail@SMdomain.com
[2015.01.19] 14:04:22 [35658] Bounce email written to 204587535749.eml
[2015.01.19] 14:04:22 [35658] Delivery for someemail@SMdomain.com to (someemail@ymail.com) has completed (Bounced)
[2015.01.19] 14:04:22 [35658] Delivery finished for someemail@SMdomain.com at 2:04:22 PM    [id:204587535658]
 
One log entry shows it was delivered while another shows it bounced.  Which is correct?  I can't remember ever running across something like this before.  As for the DNS error displayed in the bounced email...  I checked the DNS server and it is performing a MX lookup on ymail.com just fine.

6 Replies

Reply to Thread
0
Bruce Barnes Replied
January 20, 2015 at 12:54 PM
We need a bit more information to assist you with this:
 
  • Sending e-mail address
     
  • Receiving e-mail address
 
Then we can run external tests and give you better information as to the cause of the issue.
Bruce Barnes
ChicagoNetTech Inc

Phone: (224) 444-0169

E-Mail and DNS Security Specialist
Network Security Specialist

Customer Service Portal: https://portal.chicagonettech.com
Website: https://www.ChicagoNetTech.com
Security Blog: http://networkbastion.blogspot.com/

Web and E-Mail Hosting, E-Mail Security and Consulting
0
Leo Novelli Replied
January 20, 2015 at 1:15 PM
Thanks for the help!
 
The sender was myself, lnovelli[at]atlantisnet.com, and the recipient was cspinc[at]ymail.com.
0
Bruce Barnes Replied
January 20, 2015 at 1:44 PM
Here's a link to the test results for MYMAIL.COM: http://bit.ly/1EniVHO
 
MYMAIL.COM has issues with the DNS SERVERS:
 
 - there are TWO DNS servers listed at your domain name registrar:
 
 
 - but they refer to a 3rd DNS server, and that can cause lookup errors and non-delivery - IE: N3.MYMAIL.COM is a ROUGH DNS SERVER - it's listed in the other two DNS servers, but has no IP address, and does not respond when queried.
 
 
 - and they don't accept TCP
 
 
Here's a link to the test results for ATLANTISNET.COM: http://bit.ly/181s0Mb | atlantisnet.com is an OPEN RELAY:
 
 
both links are good for only two days.
 
 
Bruce Barnes
ChicagoNetTech Inc

Phone: (224) 444-0169

E-Mail and DNS Security Specialist
Network Security Specialist

Customer Service Portal: https://portal.chicagonettech.com
Website: https://www.ChicagoNetTech.com
Security Blog: http://networkbastion.blogspot.com/

Web and E-Mail Hosting, E-Mail Security and Consulting
0
Leo Novelli Replied
January 21, 2015 at 4:53 PM
Who is MYMAIL.COM?  Is that the mail servers used by Yahoo (ymail.com)?
 
The test for ATLANTISNET.COM is not quote accurate as it is actually testing against the MX servers (MX Logic by McAfee) and not our SM server.  We use the MX Logic service to filter all inbound email form SPAM.  We do not run an OPEN RELAY.
 
0
Bruce Barnes Replied
January 21, 2015 at 9:07 PM
My error on the MYMAIL.COM tests, disregard. 
 
EDITED: YMAIL.COM has issues with three of their MX servers having invalid rDNS information, this could be contributing to the delivery problems:
 
.
 
I would also concentrate on the ATLANTISNET.COM issue(s) from the original post.
Bruce Barnes
ChicagoNetTech Inc

Phone: (224) 444-0169

E-Mail and DNS Security Specialist
Network Security Specialist

Customer Service Portal: https://portal.chicagonettech.com
Website: https://www.ChicagoNetTech.com
Security Blog: http://networkbastion.blogspot.com/

Web and E-Mail Hosting, E-Mail Security and Consulting
0
Leo Novelli Replied
January 22, 2015 at 10:31 AM
I removed the name server software version information from our DNS servers and also upgraded them at the same time.
 
The SOA serial number will be modified to use the YYYYMMDDnn syntax in our next software update.
 
A postmaster@ account has been added.
 
WWW has always been enabled.  I'm not sure why the report shows that they were unable to connect.
 
The SMTP greeting, and Open Relay test were from the McAfee MX Logic anti-spam servers which unfortunately I have no control over.
 
Thanks for you help.

Reply to Thread