Re: [fetchmail-devel] Workaround for unavoidable SSL CommonName mismatch?

[Matthias A. <mat...@gm...>]

"Daniel Richard G." <sk...@iS...> writes:

> I think that there wouldn't even be a need to introduce a new keyword; 
> this semantic could reasonably be stuffed into "aka". So that, for the 
> above-described scenario, I could say
>
> 	poll mail.mydomain.com aka mail.webhost.com protocol pop3
> 		username ... password ... ssl fetchall
>
> and have everything work dandily.

Well, fetchmail is in fact talking to mail.mydomain.com, so allowing
certificates for other domains on the server wouldn't be the right thing
to do. You can however obtain the server's certificate fingerprint (run
fetchmail with -v (in verbose mode)) and then use the sslfingerprint
option to suppress the warning. Fetchmail will then abort the connection
if the fingerprint does not match.

-- 
Matthias Andree