Cannot send email to bellsouth.net accounts

Mail from our Exchange 2003 server to bellouth.net addreeses is returned with a 4.7.7 error. We host our own email but use Nuvox as our ISP. Have emailed AT&T for delisting twice. Each time, problem goes away for a week, and then returns. Have checked DSL reports and other sites and we are not blacklisted anywhere. Any guidance will be appreciated.
bhaadprAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

murgroupCommented:
How does your DNS record look on www.dnsreport.com ? Any problems with your reverse dns record?
0
bhaadprAuthor Commented:
No problems were detected at www.dnsreport.com.
0
murgroupCommented:
Are you using a static IP or routing mail through a smart host?
0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

bhaadprAuthor Commented:
Static IP
0
absremoteCommented:
I also have SEVERAL clients complaining about this issue. Most are on Nuvox or a similar T1 provider in town. Anyone make any traction getting this fixed?
0
scooter47Commented:
I have the exact same problem and I am using Nuvox also. I found this workaround for exchange 2003 that works for me. I just set it up today. The domains I could not send to were bellsouth.net, comcast.net and yahoo.com. I called Nuvox and they said these ISP's probably have a range of Nuvox IP addresses blacklisted.

http://www.amset.info/exchange/smtp-connector.asp

0
russellg1787Commented:
We use Nuvox.  We were able to sove this problem by sending an email to bellsouth.net requsting to be removed from their block/abuse list.
0
MAXIMUS-8Commented:
I was able to work around this adding a second SMTP connector in Exchange. On the first one, the namespace is a wildcard, and the second one for Bellsouth only. I found out the real server host name of our mail server by doing a reverse lookup, and used the server's real fqdn (hostname.isp.net). Also remember to check the option that tells you to allow relaying to that namespace.

I hope this works for you.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Email Protocols

From novice to tech pro — start learning today.