Bug#556123: kdepim-runtime: akonadi_imap_resource and CommuniGate Pro IMAP Server 5.1.16
Package: kdepim-runtime
Version: 4:4.3.2-1
Severity: important
Tags: patch
Akonadi imap resource (akonadi_imap_resource) is unable to communicate with CommuniGate Pro IMAP
server. The problem is that it requires IMAP4rev1 capability on the
server. But server returns IMAP4REV1.
The fix is really a very simple. Just change in
kdepim-runtime/resources/imap/imapaccount.cpp to add
Qt::CaseInsensitive:
if ( !m_capabilities.contains( capability, Qt::CaseInsensitive ) ) {
missing << capability;
}
After that you can easily connect to CommuniGate Pro.
Best regards,
Sergey.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (990, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.30-2-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages kdepim-runtime depends on:
ii kdebase-runtime 4:4.3.2-1 runtime components from the offici
ii kdelibs5 4:4.3.2-2 core libraries for all KDE 4 appli
ii kdepimlibs5 4:4.3.2-1 core libraries for KDE PIM 4 appli
ii libakonadiprivate1 1.2.1-1 libraries for the Akonadi PIM stor
ii libc6 2.10.1-1 GNU C Library: Shared libraries
ii libgcc1 1:4.4.1-5 GCC support library
ii libknotificationitem-1-1 4:4.3.2-1 library for new way of handling sy
ii libqt4-dbus 4:4.5.3-4 Qt 4 D-Bus module
ii libqt4-network 4:4.5.3-4 Qt 4 network module
ii libqt4-qt3support 4:4.5.3-4 Qt 3 compatibility library for Qt
ii libqt4-sql 4:4.5.3-4 Qt 4 SQL module
ii libqt4-xml 4:4.5.3-4 Qt 4 XML module
ii libqtcore4 4:4.5.3-4 Qt 4 core module
ii libqtgui4 4:4.5.3-4 Qt 4 GUI module
ii libsoprano4 2.3.1+dfsg.1-1 libraries for the Soprano RDF fram
ii libstdc++6 4.4.1-5 The GNU Standard C++ Library v3
ii libstrigiqtdbusclient0 0.7.0-1+b2 library for writing D-Bus clients
ii libxml2 2.7.6.dfsg-1 GNOME XML library
kdepim-runtime recommends no packages.
kdepim-runtime suggests no packages.
-- no debconf information
Reply to: