I don't understand why it would be an issue now. That conversation has been done for months now. Everything was working fine, until 11am or so yesterday.
Because anything mail server related can change any time.
The certificate at pop.verizon.net (which is now same as pop.aol.com) does not include pop.verizon.net server name.
---
Correction: it "did not".
Right now pop.verizon.net does *not* point to pop.aol.com anymore, which it did when I wrote my first reply above.
And the certificate is good again.
I can't know if it'll last.