Bug 4856

Summary: SMTP w/ POP3 (and others?) over SSL doesn't work
Product: Mageia Reporter: Kevin Bulgrien <kbulgrien>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED INVALID QA Contact:
Severity: critical    
Priority: Normal    
Version: 1   
Target Milestone: ---   
Hardware: i586   
OS: Linux   
URL: http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=2402
See Also: http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=2402
http://bugs.debian.org/638823
Whiteboard:
Source RPM: claws-mail-3.7.8-2.mga1 CVE:
Status comment:

Description Kevin Bulgrien 2012-03-09 03:40:06 CET
Receiving mail with Mageia 1 claws-mail works fine on SSL POP3 at att.yahoo.net, but sending to SMTP server does not.  Account settings and mail servers are not the problem.  It is claws-mail.

Google shows this bug being registered with many distributions where an update suddenly broke SMTP for lots of people.  It is apparently related to a gnutls change that broke backwards compatibility, and claws-mail had to change to adapt to the new API (or something like that).

The URL points to a bug upstream that has been fixed.  This package should be updated.

I am in the process of building the cauldron package to verify.  I'll report later.  The D/L to do so is horrendous.
Kevin Bulgrien 2012-03-09 03:42:46 CET

See Also: (none) => http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=2402

Kevin Bulgrien 2012-03-09 03:44:44 CET

See Also: (none) => http://bugs.debian.org/638823

Comment 1 Kevin Bulgrien 2012-03-09 04:37:59 CET
If fixed for Mageia 1, valgrind-devel will need to be pulled in from Cauldron (based on depends for building claws-mail in Cauldron).
Comment 2 Kevin Bulgrien 2012-03-09 06:01:16 CET
Unfortunately, building cauldron packages on Mageia 1 does not fix the issue.

Ok, this is embarrassing att.yahoo.net --> att.yahoo.com, and original works.  How I missed that the pop and smtp hostnames were different when they are side by side is beyond me. /:-/

Status: NEW => RESOLVED
Resolution: (none) => INVALID