Bug 40693 – CRAM-MD5 auth issues with KMail from KDE 3.2

• Status: RESOLVED UPSTREAM
• Product: Gentoo Linux

[Description Stuart Herbert (RETIRED) 2004-02-07 02:34:30 UTC]

Since upgrading to KDE 3.2, I'm having trouble sending email through dev.gentoo.org.  Exim is reporting that KDE 3.2 is sending an invalid CRAM-MD5 authentication token.  

The fault is intermittent - sometimes I can send email, and sometimes I can't.  When the fault occurs, stopping and restarting KMail does not clear the fault.  What does clear the fault is if I then try to send an email via an alternative SMTP server.  Works every time.

Stu

[Comment 1 Stuart Herbert (RETIRED) 2004-02-22 02:00:41 UTC]

Any progress on this bug?

This fault only happens when an attempt is made to sign the email.  Doesn't matter if it's done through the OpenPGP support, or through the crytplugin modules.  Doesn't matter if the email is successfully signed or not.

I've reproduced this fault on two machines - one was an upgrade from KDE 3.1 to KDE 3.2, the other machine KDE 3.2 was the first KDE installed.

Thanks,
Stu

[Comment 2 Stuart Herbert (RETIRED) 2004-05-11 08:36:44 UTC]

Hiya,

Still chasing this bug.  Been three months now since I could relay email through g.o's SMTP service.  Is anyone looking at this?

Thanks,
Stu

[Comment 3 Stuart Herbert (RETIRED) 2004-05-20 14:22:38 UTC]

Hiya,

Chasing this again.  This bug still occurs w/ KDE 3.2.2.

Best regards,
Stu

[Comment 4 Caleb Tennis (RETIRED) 2004-05-20 14:23:39 UTC]

KDE team = 2 people - I don't user CRAM-MD5 with Kmail so I'm of little help here.

[Comment 5 Carsten Lohrke (RETIRED) 2004-05-25 03:20:25 UTC]

-> bugs.kde.org #56319

[Comment 6 Carsten Lohrke (RETIRED) 2004-06-14 14:12:16 UTC]

hm, not in 3.2.3, but is an upstream issue

[Comment 7 Stuart Herbert (RETIRED) 2004-06-14 14:52:28 UTC]

Hiya,

If it's not fixed in KDE 3.2.3 or in CVS, it's not fixed yet ;-)

Best regards,
Stu

[Comment 8 Carsten Lohrke (RETIRED) 2004-06-14 15:08:51 UTC]

Calbe, Stuart, I'm rather new as a dev, so excuse me, if my doing is not o.k.. The "resolution description" says:

UPSTREAM -  The problem lies with the program and the developer in which we cannot fix. 

Don't we have exactly this situation here?! We cannot fix it and have to wait for a new upstream release. Am I wrong to resolve such bug reports as UPSTREAM?

[Comment 9 Carsten Lohrke (RETIRED) 2004-06-14 15:09:44 UTC]

Ugh, sorry. Caleb, of course.

[Comment 10 Stuart Herbert (RETIRED) 2004-06-14 15:10:55 UTC]

Heh.  Maybe you're right ;-)

I'd like us to leave this one open, because I'm going to have a go at debugging kmail eventually.

Best regards,
Stu

[Comment 11 Carsten Lohrke (RETIRED) 2004-06-14 15:32:06 UTC]

Ah, that's fine! :)

[Comment 12 Carsten Lohrke (RETIRED) 2004-12-14 04:23:59 UTC]

fixed upstream

[Comment 13 Carsten Lohrke (RETIRED) 2005-01-04 08:10:47 UTC]

*** Bug 76644 has been marked as a duplicate of this bug. ***