August's CompTIA IT Fundamentals course includes 19 hours of basic computer principle modules and prepares you for the certification exam. It's free for Premium Members, Team Accounts, and Qualified Experts!
COURSE of the MONTH
12 days, 15 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Send connector FQDN setting for Exchange 2010
Posted on 2013-01-02
I recently upgraded to exchange 2010. In front of exchange is a websense email server (WES) filtering spam. The Exchange connector is configured to relay mail to the WES server before it leaves the building. On the exchange server there is an error logged every few minutes:
ID 12014 - Microsoft Exchange could not find a certificate that contains the domain name wes.domain.local in the personal store on the local computer. Therefore, it is unable to support the STARTTLS SMTP verb for the connector WES with a FQDN parameter of wes.cunj.local. If the connector's FQDN is not specified, the computer's FQDN is used. Verify the connector configuration and the installed certificates to make sure that there is a certificate with a domain name for that FQDN. If this certificate exists, run Enable-ExchangeCertificate
What should be listed under Exchange's send connector properties where it says "Specify the FQDN this connector will provide in response to HELO or EHLO:"?
Right now I have wes.domain.local which I'm thinking maybe should be the name of my mail record. Or perhaps I have that entirely wrong and the error indicates something else. Please let me know what you think, thanks!
ID 12014 - Microsoft Exchange could not find a certificate that contains the domain name wes.domain.local in the personal store on the local computer. Therefore, it is unable to support the STARTTLS SMTP verb for the connector WES with a FQDN parameter of wes.cunj.local. If the connector's FQDN is not specified, the computer's FQDN is used. Verify the connector configuration and the installed certificates to make sure that there is a certificate with a domain name for that FQDN. If this certificate exists, run Enable-ExchangeCertificate
What should be listed under Exchange's send connector properties where it says "Specify the FQDN this connector will provide in response to HELO or EHLO:"?
Right now I have wes.domain.local which I'm thinking maybe should be the name of my mail record. Or perhaps I have that entirely wrong and the error indicates something else. Please let me know what you think, thanks!
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
2
4 Comments
this error simply means that the name in your EHLO command is not present in the ssl certificate installed on your server, you can ignore this error but it is easy to fix
@Akhater - Ok, I'm 99% sure that all I'd need to do is change the entry to the same address as my public mail record. Sound right?
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Let's recap what we learned from yesterday's Skyport Systems webinar.
- Ransomware
- Experts Exchange
- Skyport Systems
- Active Directory
- Security
- *privileged credentials
Active Directory can easily get cluttered with unused service, user and computer accounts. In this article, I will show you the way I like to implement ADCleanup..
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource.
Use Google, Bing, or other preferred search engine to locate trusted NTP …
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online.
The email signature template has been downloaded from:
www.mail-signatures…
Suggested Courses
Course of the Month12 days, 15 hours left to enroll
777 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.