Hello Gevorg, On Fri, Jan 16, 2015 at 04:24:40PM -0500, Gevorg Abrahamian wrote: > Hello Carsten, > > Thank you very much for your quick response and for support of Icedove and > especially Debian. > > I am sorry but I don't know how to try TLSv1.1 or how I ended up using > SSLv3. All my mails are configured to use SSL/TLS setting over port 993. If > by TLSv1.1 you mean, STARTTLS setting, I tried that but was unable to > connect (I doubt my company server allows for that).
please take a look into /usr/share/doc/icedove/README.Debian there we have documented such things and point to websites with further informations. If something is missed, patches are welcome. ;) > After I changed the number of maximum connections to cache to 3 from 5, > Icedove didn't crash for the rest of the day but I cannot imagine that was > the "fix". I've changed it back to 5 now to see if it will again crash and > give me a reproducible case to at least figure out which server is giving me > the challenge. Thanks again for your explanation! Of course Icedove doesn't have to crash, there is something going definately wrong. But we need to excately at what point Icedove is crashing. I believe the bug isn't directly inside the icedove binary and comes more from nss or related. Please try to combine the various logging methods described on the wiki page. By further thinking it's possibly that only one server is provoke this behavior. Please check for credentials before appending logs to this report. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
