On 2013-05-30 11:18, Charles Cazabon wrote: > If this does fix the issue, I'd really like to see Debian revert this broken > patch -- breaking existing configs and reducing compatibility with correct > servers is not a good tradeoff for trying to make MSexchange work.
Well, the patch in only in Debian since 2013-05-17 and only in the "unstable" distribution. "unstable" is exactly for finding such problems and fixing them before the package reaches "testing". Anyway, I would love to see a fix for MSexChange compatibility with the new SSL library, that does not break other IMAP servers. To my regret, the MS product has still a very high market share, notwithstanding much better free alternatives exist. Do you think, one could make the SSL version an option, defaulting, of course, to the original value? And with a check for the Python version? Or maybe the problem can be solved in a totally different manner. I only came to this solution by "trial and error". (For Debian, versions before 2.7 are not relevant, because we target Debian "8.0" and maybe "7.0" via backports, which both have Python 2.7, even "6.0" had 2.6.) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
