As described also in the http://forums.gentoo.org/viewtopic-t-552362.html topic in gentoo forums, immediately after upgrading from qt 3.3.6-r4 to 3.3.8-r2, kmail denies AUTH to servers with the "username and password incorrect" pop up error. Happens independently with pop3 or imap. Number of letters obscured in the password field of each account result much longer than number of letters actually set. Problem disappears as soon as I manually reenter the passwords in each account. Reproducible: Always Steps to Reproduce: 1.Upgrade to qt-3.3.8-r2 from qt-3.3.6-r4. 2.Try receiving any mail from kmail. 3. Actual Results: Pop up errors pointing that username and password are invalid. Expected Results: Regularly receive mail. Problem disappears as soon as I reenter the passwords in each account.
Correction: Reentering the passwords manually works but only as long as I keep kmail open. Problem reappears as soon as I restart kmail.
I had the exact same problem a while ago, when those utf patches to fix a security fix went in (iirc) It only happened with me when using kmail without kwallet, do you see the same thing?
(In reply to comment #2) > It only happened with me when using kmail without kwallet, do you see the same > thing? I don't use kwallet, so I don't know really...
(In reply to comment #2) > I had the exact same problem a while ago, when those utf patches to fix a > security fix went in (iirc) > > It only happened with me when using kmail without kwallet, do you see the same > thing? > I don't use kwallet either and don't intend to, so I won't check that. However your remark about utf patches is interesting when combined with one of the post in the forum: What I have noticed is that the problem depends on complication level of password. I have three accounts configured in kmail and one with "aneasypassword" works ok, while two others with "l33t5p34k!@#" have problems (those are ofcourse not my passwords, just to show what kind of characters are used). ------------------- Buggy encoding?
I just noticed the same exact thing on my machine: Pop3 accounts with complex passwords (containing alphanumeric, caps, symbols and spaces), are the ones that get borked; like "l33t 5p34k! @#" Other pop3 accounts with simple alphabetic, low caps, no spaces or symbols pass maintain functionality; like "aneasypassword". Imap accounts with alphanumeric but WITHOUT spaces or symbols works regularly; like "l3ss34syp455".
Update: the culprit to the problem mentioned is the patch utf8-bug-qt3.diff added in qt-3.3.8-r2. Removing the diff solves the problem with kmail, but is a regression regarding the XSS problem mentioned in qt changelog (please read the http://forums.gentoo.org/viewtopic-t-552362.html topic for complete information) Where is this problem supposed to be handled, portage or KDE?
I just got a patch from the kde packager list regarding this issue. At least for this patch, the issue is only for passwords with the ! character in it. Will post shortly.
Created attachment 117020 [details, diff] patch to fix the ! encoding issue
I just tried the patch with kmail-3.5.5-r2 (current stable) and after changing kmaccount.cpp to kmail/kmaccount.cpp in the patch it worked and solved my problem. I had to logout of kde and login again for it to be effective.
I'm glad it worked out for Francois, but unfortunately over here it didn't work: May I state that I don't have ! in my passes, but many spaces and other special chars (mainly ' ). I did the following (as root): 1. ebuild /usr/portage/kde-base/kmail/kmail-3.5.6-r2.ebuild unpack 2. mv kmaccount.cpp.diff /var/tmp/portage/kde-base/kmail-3.5.6-r2/work/kmail-3.5.6/kmail/ 3. cd /var/tmp/portage/kde-base/kmail-3.5.6-r2/work/kmail-3.5.6/kmail/ 4. patch -p0 <kmaccount.cpp.diff 5. ebuild /usr/portage/kde-base/kmail/kmail-3.5.6-r2.ebuild merge Rebuilt qt with the incriminated patch. Restarted kmail, no avail. Restarted X, KDE and Kmail, no avail. Am I doing something wrong? (Cope with me, I don't have great experience with patches!)
Please ignore my last post, the patch works correctly: I had, although, to reenter my passes once again, and now kmail retains them correctly, even after shutdown and reboot. So I guess the bug is solved; when is it time to close it, now or after the next kmail revision? Sorry again for alarming anyone :)
kmail-3.5.6-r3 and kdepim-3.5.6-r3 should now have this patch in portage.
(In reply to comment #12) > kmail-3.5.6-r3 and kdepim-3.5.6-r3 should now have this patch in portage. > Nice, what about fixing the stable packages? It is as straightforward.
Arch teams, please mark kmail-3.5.5-r2 respective kdepim-3.5.5-r4 stable ASAP.
Stable for HPPA.
ia64 and x86 stable, armin76 has done that.
sparc stable.
ppc64 stable
amd64 stable Moreover Kopete suffers from the exact same issue. Any patch already out there?
amd64 stable
alpha stable
Marked ppc stable.
mips, ping!
Doesn't go anywhere. Bug 188857 ATM.
