We have ticketing system which is using IMAP for connecting to Exchange and it creates a ticket after fetching email from Mailbox using IMAP on Port 993 . They started complaining that it stopped working.
We are having 3 Exchange 2013 CAS servers in CASArray with Windows NLB and 4 mb servers in DAG.
Internal domain is different and external domain is Different. Wild Card cert is being used with DNS name xxxxx.xx.xx
Ticketing system is connecting to xxxxx.xx.xx on Port 993.
xxxxx.xx.xx is mapped to Virtual IP which is pointing to CAS servers.
As it was a Wild Card cert, could not map it to IMAP , so used the
Set-IMAPSettings -X509CertificateName xxxxx.xx.xx
During this time I found out a Cert which was a local cert generated and from a Local CA and was installed on the CAS servers , it had expired. I renewed it etc. and after rebooting, ticketing system started working.
But new issue came up, where some Application Users started complaining that their code is not sending email on Port 587.
Actually, we have always asked the internal users to Use Port 25 without Authentication and we had given access only from Servers ( that too only for internal users).
For Relay , we have a different connector and we add IP's if someone wants to send email to Outside world using code.
So these coders started using Port 587 without information and using their ID's and as the Connector is enabled for Exchange User, they were able to send emails, but now it stopped working and they are complaining.
So, I am not sure how can I check , because as far as I know we can bind only one Cert to SMTP,so i cannot bind the newly generated local CA cert.
Can anyone suggest.