[Evolution] Bug#623486: marked as done (evolution: Unable to contact IMAP corporate server: Could not find a suitable authentication type: code 0xffffffff)

Tue Jul 10 00:18:09 UTC 2012

Your message dated Tue, 10 Jul 2012 02:09:59 +0200
with message-id <1341878999.11115.316.camel at thinker.domain.lan>
and subject line #623486 evolution: Unable to contact IMAP corporate server: Could not find a suitable authentication type: code 0xffffffff
has caused the Debian Bug report #623486,
regarding evolution: Unable to contact IMAP corporate server: Could not find a suitable authentication type: code 0xffffffff
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)

-- 
623486: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623486
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Guilhem Bonnefille <guilhem.bonnefille at gmail.com>
Subject: evolution: Unable to contact IMAP corporate server: Could not find a suitable authentication type: code 0xffffffff
Date: Wed, 20 Apr 2011 18:50:11 +0200
Size: 8682
URL: <http://lists.alioth.debian.org/pipermail/pkg-evolution-maintainers/attachments/20120710/6452bd3a/attachment-0002.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: =?ISO-8859-1?Q?No=EBl_K=F6the?= <noel at debian.org>
Subject: #623486 evolution: Unable to contact IMAP corporate server: Could not find a suitable authentication type: code 0xffffffff
Date: Tue, 10 Jul 2012 02:09:59 +0200
Size: 2926
URL: <http://lists.alioth.debian.org/pipermail/pkg-evolution-maintainers/attachments/20120710/6452bd3a/attachment-0003.mht>