-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Content-ID:
I've been asking myself that same question for years now.
Not sure what version's manpage I've looked at and what I tried (unsuccessfully), but these look promising:
... (Use of this option is discouraged) - :-)
So, according to documentation (and probably due to popular demand ;) the addition of the new keyword/option and value
sslcommonname pop.dominioabsoluto.net
to the relevant server section of your fetchmailrc should help.
It does, many thanks. The relevant section is the user part, not the server part, which is funny. Yes, they warn that the proper solution is correcting the upstream server, but that is out of the question. There is no support email... this is a free account by an organization.
[in my case, the cert is self-signed, with a different CN and expired, haven't gotten round to find out how to generate a fitting cert with plesk yet ... *gah*]
I can understand that... :-) - -- Cheers Carlos E. R. (from 11.4, with Evergreen, x86_64 "Celadon" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iF4EAREIAAYFAlDgqWcACgkQja8UbcUWM1w/SgD/f8rQi0kz5of1M0KsMXHzKM6j w5hi3u+NVFu1BTcYBq0A/AuAnimSCiTb2VfTRML2gLEGhNtxHx2C4dOFOKM9XDtu =vG2a -----END PGP SIGNATURE-----