I see 2 ways to make the situation better:
a.) help upstream use system certificates if that is not already functional and build debian package so that works
b.) improve the error messages in the case where there is no entry for the Repository to be something more useful like:
| The server for repository 'Gmail' has a fingerprint that cannot be
| verified. If you trust the fingerprint of
| 'f3043dd689a2e7dddfbef82703a6c65ea9b634c1' then you need to update the
| 'Repository Gmail' entry in offlineimaprc to include:
| ssl = yes
| cert_fingerprint = f3043dd689a2e7dddfbef82703a6c65ea9b634c1
'a' is definitely useful, but I suspect will not fix the issue for everyone.
I see 2 ways to make the situation better: dddfbef82703a6c 65ea9b634c1' then you need to update the ddfbef82703a6c6 5ea9b634c1
a.) help upstream use system certificates if that is not already functional and build debian package so that works
b.) improve the error messages in the case where there is no entry for the Repository to be something more useful like:
| The server for repository 'Gmail' has a fingerprint that cannot be
| verified. If you trust the fingerprint of
| 'f3043dd689a2e7
| 'Repository Gmail' entry in offlineimaprc to include:
| ssl = yes
| cert_fingerprint = f3043dd689a2e7d
'a' is definitely useful, but I suspect will not fix the issue for everyone.