Your message dated Sat, 21 Nov 2015 18:10:03 +0100
with message-id <2252955.rzdPbTLSFE@tuxin>
and subject line Close because of lack of informations
has caused the Debian Bug report #757418,
regarding kmail: fails to fetch SSL certificates for pop
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 ow...@bugs.debian.org
immediately.)
--
757418: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757418
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kmail
Version: 4:4.4.11.1+l10n-3+b1
Severity: normal
Dear Maintainer,
I installed kmail on Debian 7.5 and lxde.
I configured it to pop mail from my pop account(s).
I tried to download e-mail.
kmail failed to fetch and recognise the SSL certificates required.
The error message showed the certificate (after a few clicks)
of the server, but did not show the CA certificates.
I tried several times, with and without kleopatra installed.
the server happens to vps-unixweb4.totalhostingplus.com .
I used iceweasel to obtain the server certificate, then
used openssl x509 to display it.
It contained a URL so I used wget to obtain a copy of the certificate
of the intermediate CA
the Server certificate obtained by iceweasel has the same
fingerprint as the server certificate display by kmail.
According to "openssl verify ...", the intermediate certificate
validly signs the server certificate.
It would be nice if in future kmail can handle a chain of
certificates for pop over SSL and using TLS.
Thank you very much indeed for maintaining kmail..
with best regards from
Richard Betham
-- System Information:
Debian Release: 7.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i586)
Kernel: Linux 3.2.0-4-486
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages kmail depends on:
ii kde-runtime 4:4.8.4-2
ii kdepim-runtime 4:4.4.11.1-6
ii kdepimlibs-kio-plugins 4:4.8.4-2
ii libakonadi-contact4 4:4.8.4-2
ii libakonadi-kde4 4:4.8.4-2
ii libc6 2.13-38+deb7u3
ii libgcc1 1:4.7.2-5
ii libgpgme++2 4:4.8.4-2
ii libkabc4 4:4.8.4-2
ii libkcal4 4:4.8.4-2
ii libkcmutils4 4:4.8.4-4
ii libkde3support4 4:4.8.4-4
ii libkdecore5 4:4.8.4-4
ii libkdepim4 4:4.4.11.1+l10n-3+b1
ii libkdeui5 4:4.8.4-4
ii libkhtml5 4:4.8.4-4
ii libkimap4 4:4.8.4-2
ii libkio5 4:4.8.4-4
ii libkldap4 4:4.8.4-2
ii libkleo4 4:4.4.11.1+l10n-3+b1
ii libkmime4 4:4.8.4-2
ii libknotifyconfig4 4:4.8.4-4
ii libkontactinterface4 4:4.8.4-2
ii libkparts4 4:4.8.4-4
ii libkpgp4 4:4.4.11.1+l10n-3+b1
ii libkpimidentities4 4:4.8.4-2
ii libkpimtextedit4 4:4.8.4-2
ii libkpimutils4 4:4.8.4-2
ii libkresources4 4:4.8.4-2
ii libksieve4 4:4.4.11.1+l10n-3+b1
ii libktnef4 4:4.8.4-2
ii libmailtransport4 4:4.8.4-2
ii libmessagecore4 4:4.4.11.1+l10n-3+b1
ii libmessagelist4 4:4.4.11.1+l10n-3+b1
ii libmimelib4 4:4.4.11.1+l10n-3+b1
ii libnepomuk4 4:4.8.4-4
ii libphonon4 4:4.6.0.0-3
ii libqt4-dbus 4:4.8.2+dfsg-11
ii libqt4-network 4:4.8.2+dfsg-11
ii libqt4-qt3support 4:4.8.2+dfsg-11
ii libqt4-xml 4:4.8.2+dfsg-11
ii libqtcore4 4:4.8.2+dfsg-11
ii libqtgui4 4:4.8.2+dfsg-11
ii libstdc++6 4.7.2-5
ii libthreadweaver4 4:4.8.4-4
ii perl 5.14.2-21+deb7u1
ii phonon 4:4.6.0.0-3
Versions of packages kmail recommends:
ii gnupg-agent 2.0.19-2+deb7u2
ii gnupg2 2.0.19-2+deb7u2
ii pinentry-gtk2 [pinentry-x11] 0.8.1-1
Versions of packages kmail suggests:
ii bogofilter 1.2.2+dfsg1-2
pn clamav | f-prot-installer <none>
pn kaddressbook <none>
ii kleopatra 4:4.4.11.1+l10n-3+b1
ii procmail 3.22-20
-- no debconf information
--- End Message ---
--- Begin Message ---
Hey,
Thanks for reporting the bug, but there was no update for several months now
but the bug is marked as moreinfo, so closing these bugs.
If it is still an issue, please add these infos and reopen the bug again.
Regards,
sandro
--- End Message ---