Problem with Mail Relay test Exchange 2016 on Windows Server

All questions related to installations, configurations and maintenance of Advanced Host Monitor (including additional tools such as RMA for Windows, RMA Manager, Web Servie, RCC).
Post Reply
rgoebel
Posts: 42
Joined: Tue Feb 21, 2012 4:39 am

Problem with Mail Relay test Exchange 2016 on Windows Server

Post by rgoebel »

Hi there,

we have the problem after a migration from our Microsoft Exchange server 2013 and Windows Server 2012R2 to MS Exchange 2016 and Windows Server 2019 that the mail relay test fires the following "unknown" status

Unknown 276: error during handshake[2]: 0x80090308

The KS Hostmon we use is: 11.97 on a windows server 2012R2

We use as incomming mail server in the mail relay test the following config:
Protocol: POP3
Port: 995
TLS: Implicit

On the old Exchange server is the mail relay test still working.

We use as well a "POP3 test" on the new exchange server which is working.
The config here is also Port 995 and TLS Implicit.

All OS (old and new server and KS host server) were configured with the default setting from IIS Crypto.

Is the KS Hostmonitor using a own TLS configuration or do you have any other idea about this issue?

Thank you in advance.

Bye, Robert
KS-Soft
Posts: 13012
Joined: Wed Apr 03, 2002 6:00 pm
Location: USA
Contact:

Post by KS-Soft »

All OS (old and new server and KS host server) were configured with the default setting from IIS Crypto.
This means only TLS 1.2 enabled?
AES128 and AES256 ciphers?
SHA, SHA256, SHA512 hashes?
What key exchange methods enabled? Diffie-Hellman, PKCS and ECDH?
Then HostMonitor should work.

What about "Outgoing mail server" options?
Port 25? May be you should connect to port 465? or 587?
Tried Implicit, Explicit options?

Such error may occur if you are using Implicit TLS option while connecting to plain port (service) that does not support encryption.

Regards
Alex
rgoebel
Posts: 42
Joined: Tue Feb 21, 2012 4:39 am

Post by rgoebel »

Hi Alex,

sorry for my late reply.
I think the problem is now solved.
After installing the Security Update For Exchange Server 2016 CU14 (KB4523171) on the exchange server, I'm able to get a secured connection TLS for pop3.

Thank you anyway.

Bye, Robert
KS-Soft
Posts: 13012
Joined: Wed Apr 03, 2002 6:00 pm
Location: USA
Contact:

Post by KS-Soft »

Thank you for information!

Regards
Alex
Post Reply