Bug 1044743 - "Warning: Couldn't save certificate" when connecting to IMAP server
Summary: "Warning: Couldn't save certificate" when connecting to IMAP server
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: mutt
Version: 20
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: jpacner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-18 21:58 UTC by Jakub Kucharski
Modified: 2014-08-31 23:17 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 499390
Environment:
Last Closed: 2014-03-04 20:21:07 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Jakub Kucharski 2013-12-18 21:58:06 UTC 
Description of problem:
mutt can't save an SSL certficate on start.

Version-Release number of selected component (if applicable):
mutt-1.5.21-26.fc20

How reproducible:
Always

Steps to Reproduce:
1. start mutt, it connects to IMAP server
2. answer (a)ccept at the mutt "SSL Certficate check" dialog
3. I get "Warning: Couldn't save certificate", normal connection proceeds
  
Actual results:
When I use mutt to connect to an IMAP server the mutt "SSL Certficate check (certificate 1 of 3 in chain)" causes the following dialog to be presented:
(r)eject, accept (o)nce, (a)ccept always

When I (a)ccept the certificate I get "Warning: Couldn't save certificate"
Mutt goes on to properly connect to the IMAP server, download messages, etc.
This now occurs _everytime_ I start mutt.

Expected results:
Saved SSL Certificate.

Note:
This bug was reported for Fedora 11 (https://bugzilla.redhat.com/show_bug.cgi?id=499390) , but I see it's back in Fedora 20, so I cloned it.
Comment 1 Lon Hohberger 2014-03-04 19:00:16 UTC 
In .muttrc, do you have a line like this?

set certificate_file=~/.mutt/certificates

(then mkdir ~/.mutt)

Mutt doesn't have a default certificate store.
Comment 2 Jakub Kucharski 2014-03-04 20:17:42 UTC 
Yes. Thank you. That helped.
Note You need to log in before you can comment on or make changes to this bug.