Random/Sporadic email domains failing Exchange TLS Communication after Microsoft Exchange 2003 to 2010 Upgrade

Hi,

We recently upgraded one of our clients from Exchange 2003 to Exchange 2010.

Exchange Server Info:
Exchange version: 2010
Exchange Serice pack: SP3
Certificate: GoDaddy
Default Send Connector: TLS optional'
Email routing: Via DNS (smart host not used)


The majority of email sends without issue, but email to sporadic domains just sits in the queue retrying.

Troubleshooting Steps:
I found the out where the issue was occurring when I turned off optional TLS on the send connector. After restarting the Exchange Transport service, the mail queues emptied, but this is only a work around.

In the SMTPSend logs I can see TLS communication running successfully for the majority of domains, but for the trouble domains, I can see a successful initial connection to the remote SMTP host, and the exchange of certificates showing the correct host DNS entries, but then the data payload is empty and the connection retries.

I can also successfully connect to the remote SMTP servers via telnet on port 25, and send a test email to a recipient via EHLO.

Has anyone had TLS issues before after upgrading an Exchange 2003 server to Exchange 2010?

Thanks,
Fin
LVL 1
cpadmAsked:
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.

Jon BrelieSystem ArchitectCommented:
Are your send connectors set to use only TLS connections?

Set them to use both.  Exchange will use TLS when available, but will fall back when it's not.
0
cpadmAuthor Commented:
The send connector is configured as per the default setting of "TLS Optional".
0
Simon Butler (Sembee)ConsultantCommented:
When the messages are in the queues, what does the queue viewer actually say?

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

cpadmAuthor Commented:
The error on the emails in the queue are:

Delivery is delayed to these recipients or groups: Diagnostic-Code: smtp; 400 4.4.7 (TLS)
0
Simon Butler (Sembee)ConsultantCommented:
TLS is down to the receiver. Your SSL certificate doesn't come in to it.
That error means the TLS communication wasn't successful, and is usually down to a misconfiguration on the receiving side.

Do check to begin with though that nothing you have is scanning the SMTP traffic. Firewalls for example often do this.

Can you confirm exactly what setting you are changing for this:

"Default Send Connector: TLS optional"

Simon.
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
cpadmAuthor Commented:
We're using Trend Micro DeepSecurity 8.0 that has a number of bugs - After switching the Exchange server to unmanaged, the problem mysteriously vanished... I'm off to study Exchange 2010 antivirus folder/file exclusions....
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
Windows Server 2008

From novice to tech pro — start learning today.