I had this thing all setup and working fine until I changed the IP addresses due to moving it to a different network. It receives email ok, but when I try to send out it hangs in the queue. After running the Exchange Mail Flow Troubleshooter, it give me the following error:
Error submitting mail: Mail submission failed: Error message: Server does not support secure connections..
All other tests pass fine. I can telnet out to the mail server I'm trying to send to. I'm guessing it has to do with the certificate, but I only set this up a few months back so it shouldn't be expired. In fact it is a trial version that appears to have expired and says it's not genuine but still works fine otherwise.
I verified the send connector exists, and is of type 'Internet' SMTP * 1.
My server is setup on a dynamic IP, but I have verified the host and MX records are setup properly and are current. I can't setup a reverse DNS record since it's dynamic, but doubt that is the problem, especially since I've tried sending to another outside Exchange mail server that has no spam filtering setup. It is a different domain altogether.
I also received event ID 12023. Type: TransportService
Microsoft Exchange could not load the certificate with thumbprint of FD6C18FE7C47E51795D84E8A4441F3B045146F01 from the personal store on the local computer. This certificate was configured for authentication with other Exchange servers. Mail flow to other Exchange servers could be affected by this error. If the certificate with this thumbprint still exists in the personal store, run Enable-ExchangeCertificate FD6C18FE7C47E51795D84E8A4441F3B045146F01 -Services SMTP to resolve the issue. If the certificate does not exist in the personal store, restore it from backup by using the Import-ExchangeCertificate cmdlet, or create a new certificate for the FQDN or the server enabled for SMTP by running the following command: New-ExchangeCertificate -DomainName serverfqdn -Services SMTP. Meanwhile, the certificate with thumbprint DF4FA71547E302A3CA916207C6969A526DEDB463 is being used.
When I try to run the cmdlet as instructed above, I get:
The term 'Enable-ExchangeCertificate' is not recognized as a cmdlet, function, operable program, or script file. Verify
the term and try again.
At line:1 char:27
+ Enable-ExchangeCertificate <<<< FD6C18FE7C47E51795D84E8A4441F3B045146F01 -Services SMTPEnable-ExchangeCertificate FD
6C18FE7C47E51795D84E8A4441F3B045146F01 -Services SMTPEnable-ExchangeCertificate FD6C18FE7C47E51795D84E8A4441F3B045146F0
1 -Services SMTP
Also, the other cmdlet fails. Does SBS2008 not have all the cmdlets that the full blown Exchange 2007 have? Not sure what's going on here.
I reran the Connect to the Internet wizard, the Fix My Network wizard, and they all turn up ok.
Originally, I setup a certificate that I had purchased with the internet host name and OWA worked fine. I can still connect fine via OWA with no cert errors, but it just won't send.
Sure it's a trial and I could wipe it and start over, but what fun would that be?