Not long ago I migrated from one vm to another so I could update the OS of the vm. I had lots of hostname and ip issues after the migration along with lots of times spent correcting files all over the place.
I just noticed today that pop email over port 995 is using the wrong certificate - it shows the wrong hostname.
I did some digging and our /etc/dovecot/sni.conf has the wrong hostname listed in it :
# DO NOT MODIFY THE NEXT LINE:
# This version of dovecot supports: wildcards, multi local_name, explict maincert local_name.
# Main cert for SNI
local_name "server2.example.com" {
ssl_cert = </etc/dovecot/ssl/dovecot.crt
ssl_key = </etc/dovecot/ssl/dovecot.key
}
# END - Main cert for SNI
I imagine the above is at least part of the problem if not the entirety of it.
That should be server.example.com. server2.example.com was the temporary hostname used on the vm before we migrated everything over from the original vm. I didn't realize it until today because I had added an exception in my email client to ignore the cert error so I was able to retrieve email. I figured it was just a dns issue at the time which would correct itself.
Yes, I am using the hostname server.example.com as my mailserver to connect to port 995 for email.
I double checked in WHM and the services ssl cert is correct so I do not understand why it is wrong for dovecot. Any advice on where I go from here to correct this?
I just noticed today that pop email over port 995 is using the wrong certificate - it shows the wrong hostname.
I did some digging and our /etc/dovecot/sni.conf has the wrong hostname listed in it :
# DO NOT MODIFY THE NEXT LINE:
# This version of dovecot supports: wildcards, multi local_name, explict maincert local_name.
# Main cert for SNI
local_name "server2.example.com" {
ssl_cert = </etc/dovecot/ssl/dovecot.crt
ssl_key = </etc/dovecot/ssl/dovecot.key
}
# END - Main cert for SNI
I imagine the above is at least part of the problem if not the entirety of it.
That should be server.example.com. server2.example.com was the temporary hostname used on the vm before we migrated everything over from the original vm. I didn't realize it until today because I had added an exception in my email client to ignore the cert error so I was able to retrieve email. I figured it was just a dns issue at the time which would correct itself.
Yes, I am using the hostname server.example.com as my mailserver to connect to port 995 for email.
I double checked in WHM and the services ssl cert is correct so I do not understand why it is wrong for dovecot. Any advice on where I go from here to correct this?