Emails Blocked by AT&T

Hello,

Are our Email server emails being blocked because we are using an IP address rather than our domain?

We've recently fired up our new Exchange server.  Our emails are being blocked, cannot be received, by email boxes supported by AT&T.  I have sent in an unblock request.

Thanks,
~AJ
ajthomas12Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

jmac44Commented:
Are you using AT&T Webmail?  Why are you using an ip address instead of domain name? That maybe why your being blocked. Go to mxtoolbox.com and run an mxlookup on your domain then click on find problems. Then reply back with the results.
0
Dr. KlahnPrincipal Software EngineerCommented:
Are our Email server emails being blocked because we are using an IP address rather than our domain?

Very possible.  Sender validation tools such as SPF, DKIM and DMARC can't be used to validate incoming email when only an IP address is provided.  The FQDN of the sender MTA should always appear in the HELO/EHLO exchange.

Many receiving MTAs will deny incoming mail from senders with only an IP address in the HELO/EHLO.  This is logical practice because (at least on my own system) any incoming email where the MTA did not identify itself properly always turns out to be spam.
3

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
timgreen7077Exchange EngineerCommented:
First question is was the emails going out successfully before and is ATT your ISP?
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

ajthomas12Author Commented:
Hello,  Sorry for the delay in responding to you all.

AT&T responded with this: "we have determined that reverse DNS is not setup correctly.  We advise you to set up a pointer (PTR) for reverse DNS so that it reflects your company's name, domain name, or another name that indicates the significance of your server."

I did some more research based on Dr. Klahn's response.  I ran Get-SendConnector | fl and saw that my fqdn was blank.  I set it by opening the Exchange Admin Center and going to mail flow -> send connectors -> clicked on edit pen -> scoping -> scroll to bottom -> FQDN:  here I entered our mail.domain.com and saved.  

This must of been overlooked somehow when we setup our exchange server.  Now I am wondering if this essentially satisfies what AT&T said our issues were or is there more that I need to do?  or is this another question for another thread?

Thanks,
~AJ
0
Dr. KlahnPrincipal Software EngineerCommented:
Now I am wondering if this essentially satisfies what AT&T said our issues were or is there more that I need to do?

Only way to find out is to wait a few days and see if the problem disappears.

AT&T responded with this: "we have determined that reverse DNS is not setup correctly.  We advise you to set up a pointer (PTR) for reverse DNS so that it reflects your company's name, domain name, or another name that indicates the significance of your server."

rDNS setup normally is done by the owner of the CIDR block.  In most cases that would be the ISP who provides your IP address, unless you do own your CIDR block.
0
jmac44Commented:
Who's your ISP. Their router should have a reverse lookup entry for your email server's FQDN. If they won't or can't then at the very least you need set one up in the DNS of whoever your using an Internet domain registrar (GoDaddy) and your internal dns must be up to standards.
0
ajthomas12Author Commented:
Hello,

As far as I can tell the problem has been resolved.

Not sure if the solution was putting in the FQDN or that AT&T unblocked us.  I will update if I receive any more information.

Thanks for your help.
~AJ
0
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
Exchange

From novice to tech pro — start learning today.