If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.
Send connector FQDN setting for Exchange 2010
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!
Asked:
2
1 Solution
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?
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=8.0&EvtID=12014&EvtSrc=MSExchangeTransport
http://support.microsoft.com/kb/555855