Hello Jonathan, a lot of new Icedove versions got released since your bug report. So to get a current status I would like to ask if the behaviour is still exist?
On Thu, Jul 22, 2010 at 01:30:47PM -0400, Jonathan Blanton wrote: > Package: icedove > Version: 3.0.5-1 > Severity: normal > Tags: upstream > > > When using IMAPS, Icedove displays a warning if the hostname on the SSL > certificate doesn't match the hostname of the mail server. Icedove > allows the user to make an exception for the server, and has an option > to "Permanently store this ecxeption". The exception is not permanently > stored, regardless of the status of the checkbox. > > At my workplace, our mail server is mail.example.com. This hostname is > a DNS alias that points to either mail1.example.com or > mail2.example.com. Each server has an SSL certificate for its true > hostname, i.e. mail1.example.com has a certificate for > mail1.example.com. When I connect to mail.example.com, Icedove receives > a certificate for either mail1.example.com or mail2.example.com and pops > up a warning about the mismatch. The warning message pops up at > seemingly random intervals. Sometimes it will operate for hours with no > warning; other times it will pop up the warning multiple times in a row. > > I have also seen this error with Mozilla Thunderbird 3.0.x. I don't > know if it's still present in Thunderbird 3.1. > > Prior to the relase of Thunderbird 3.0, there was an extension called > "Remember Mismatched Domains". That extension fixed the problem. > However, Thunderbird and Icedove 3.x have that functionality built in, > so the extension does not support those versions. > > My workaround has been to explicitly use mail1.example.com or > mail2.example.com in the mail settings. If I do that, I don't get any > SSL errors. However, that's only a workaround, not a fix. Regards Carsten
