Solved

Slow email from bellsouth.net

Posted on 2008-06-18
7
976 Views
Last Modified: 2013-11-30
When ever someone from the bellsouth.net domain sends an email to the nth-works.com domain it take from 5 to 48 hours to receive the email. From what I can see there is not an issue with our MX records, and I do not have a problem receiving emails from any other domain. Before I try to call bellsouth what troubleshooting steps should I take to confirm that the problem is not on my side.
0
Comment
Question by:JimNadeau
  • 4
  • 3
7 Comments
 
LVL 9

Expert Comment

by:Press2Esc
Comment Utility
Unless the recipients specifically notify you that your emails are delayed (or they never received your emails), how would you know other domains are not having any problem?

 Firstly, nth-works.com (209.12.89.227) doesn't appear to be blacklisted...  Ok, lets try to ping their domain....
- click Start > Run > Enter "cmd" > @ blinkg cursor enter "ping -n 50 mail02.nth-works.com" & post the statistics summary...

Q: What is your domain name (FQDN)?  
Q: Are you running a local mail server?
Q: Does the emails you are sending use your domain name?
Q: Are these emails being sent non-typical (e.g., large attachments, multiple recepients, etc)?
Q: Who is your ISP?

P2E  
0
 

Author Comment

by:JimNadeau
Comment Utility
A: FQDN: nth-works.com
A: Local mail server is Exchange 2003
A: The emails we are having a problem with comes just from bellsouth.net, but yes the emails we send has our domain name.
A: the problem happens even with pain text and under 25 char

The delay seams to happen at Received-SPF step.
Here is a header from one of the delayed emails from bellsouth.net to our domain:
Microsoft Mail Internet Headers Version 2.0
Received: from mail02.nth-works.com ([192.168.1.75]) by MAIL02.precision.local with Microsoft SMTPSVC(6.0.3790.3959);
  Mon, 16 Jun 2008 19:21:34 -0400
X-ASG-Debug-ID: 1213658489-202700000002-uM3LXM
X-Barracuda-URL: http://192.168.1.75:8000/cgi-bin/mark.cgi
Received: from fmailhost05.isp.att.net (localhost [127.0.0.1])
 by mail02.nth-works.com (Spam Firewall) with ESMTP
 id 72E298A963; Mon, 16 Jun 2008 19:21:31 -0400 (EDT)
Received: from fmailhost05.isp.att.net (fmailhost05.isp.att.net [204.127.217.105]) by mail02.nth-works.com with ESMTP id joWS5blWi4sRCdtE; Mon, 16 Jun 2008 19:21:31 -0400 (EDT)
Received-SPF: pass (mail02.nth-works.com: domain of xxxxxxxx@bellsouth.net designates xxx.xxx.xxx.xxx as permitted sender) receiver=mail02.nth-works.com; client_ip=xxx.xxx.xxx.xxx; envelope-from=xxxxxxxx@bellsouth.net;
Received: from leebb1823b20b2
 (adsl-80-33-111.sdf.bellsouth.net[65.80.33.111])         by isp.att.net
 (frfwmhc05) with SMTP         id <20080616164503H0500e77o0e>; Mon, 16 Jun
 2008 16:45:03 +0000
X-Originating-IP: [65.80.33.111]
From: "xxx xxxxxxx" <xxxxxxxx@bellsouth.net>
To: "'xxxx xxxxxx'" <xxxx.xxxxxx@nth-works.com>,
 "'xxxxxx xxxxxx'" <xxxxxx.xxxxxx@nth-works.com>
Cc: "'xxxx xxxxxx'" <xxxxxxx@bellsouth.net>
X-ASG-Orig-Subj: RE:
Subject: RE: FW: Emailing: Q20080433-4 WP Handle and Cooktop
Date: Mon, 16 Jun 2008 12:44:38 -0400
0
 
LVL 9

Expert Comment

by:Press2Esc
Comment Utility
once again...
Q: Are these emails being sent non-typical (e.g., large attachments, multiple recepients, etc)?
Q: Who is your ISP?

Your (?) nth-works.com domain & mx show 209.12.89.228.  Since you did not provide your ISP info, I offer you any specific advise re: your PTR record (rDNS)

Your Received-SPF is OK (pass).  You passsed the basic smell-test...

If your mail server is 65.80.33.111, you have SPAM issues.  Out of 124 RBLs (block lists), you are being listed on 11 of 'em (see below)...  If Bellsouth subscribes to any of these lists, I suspect it will become increasingly more difficult to get bellsouth.net emails through their servers..

In short, locate the source of your mail SPAM, remedy the issue and contact the RBLs to get your IP delisted....

FIVETENFREE  
FIVETENIGNORE
FIVETENKLEZ  
FIVETENMULTI  
FIVETENOPTIN  
FIVETENOTHER
FIVETENSINGLE  
FIVETENSRC  
FIVETENTCPA  
FIVETENWEBFORM  
Spamhaus-ZEN

P2E
0
How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

 

Author Comment

by:JimNadeau
Comment Utility
We are using Time Warner for your T1 and our domain is nth-works.com and we are having problems receiving emails from bellsouth.net residental customers only. We do receive the emails but it takes up to 48 hours. One of our customers is using bellsouth.net for his business email and complaining about how long it takes for us to respond. I do not believe that the problem is on our networks, but before I call bellsouth.net to try and get a solution to this problem I wanted to make sure that I have all my bases covered on my side of things.
And if you look at the time stamp before the Received-SPF and after the Received-SPF you will see it took almost 5 hours. I have some emails from bellsouth.net that have take 48 hours to pass that step.
0
 
LVL 9

Accepted Solution

by:
Press2Esc earned 500 total points
Comment Utility
For starters, to avoid increasingly more frequent problems, I would suggest you contact TW and seek info to config rDNS for your domain (listed w/NWSolutions) and you mail server's public IP (TW) address..

Secondly, get off the Blacklists...

Thirdly, yes I did see the delayed time from send to receive.    Concerning long bellsouth mail delivery times, well Jimbo... I'm afraid you might have hit the  proverbial brick wall.  Bellsouth's routing tables are the worst imaginable... (don't believe me, trying PING'g a public bellsouth IP addr)..  

In closing, once Bellsouth's network comes in to the 21st century, I suspect the bellsouth emails will get delivered in seconds to 1-2 minutes (vs hours to days).  

Gotta run...  good luck!
0
 

Author Comment

by:JimNadeau
Comment Utility
rDNS is configured on the web and mail
I could not find my mail server on any of the black lists.
and Bellsouth.net does have a old network.

Thanks for your time...
0
 
LVL 9

Expert Comment

by:Press2Esc
Comment Utility
Ah, I see the rDNS at your domain (nth-works.com, 209.12.89.228, 227) - my bad.

The Blocked IP I ran against the RBL was 65.80.33.111, a Bellsouth IP. This was BEFORE you mentioned your ISP was TW.

Per your email header .... "X-Originating-IP: [65.80.33.111]", your sender (not you) seems to have RBL issues.

Good Luck, Jim.
0

Featured Post

Threat Intelligence Starter Resources

Integrating threat intelligence can be challenging, and not all companies are ready. These resources can help you build awareness and prepare for defense.

Join & Write a Comment

This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
Learn to move / copy / export exchange contacts to iPhone without using any software. Also see the issues in configuration of exchange with iPhone to migrate contacts.
In this video we show how to create a Distribution Group in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >>…
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…

763 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

7 Experts available now in Live!

Get 1:1 Help Now