On Thu, May 14, 2009 at 10:24:49PM +0200, Michelle Konzack wrote: > Am 2009-05-13 11:09:49, schrieb Robin Lee Powell: > > Warning: Couldn't save certificate > > > > The problem here is that it's already saved the certificate > > successfully, as far as I can tell. It's somehow deciding that the > > cert it itself saved doesn't match what it's getting from the same > > server. > > > > > What mutt version? > > > > Mutt 1.5.18 (2008-05-17) > > This sound like a misconfiguration in a folder-hook or something similar > because I have (in the last 12 weeks) installed 14 Lenny Severs and all > are with mutt. There is not a singel problem with the SMTP engine in > mutt and of course, I use SSL/TLS to, since otherwise I could not access > my Courier IMAP server.
For testing purposes, I stripped my .muttrc to only the following: set folder=imaps://rpow...@engineyard.com@secure.emailsrvr.com/ set spoolfile=imaps://rpow...@engineyard.com@secure.emailsrvr.com/ set certificate_file=~/Mail-ey/certs Then I deleted ~/Mail-ey/certs The first time, I accept the cert, and it gets correctly saved to ~/Mail-ey/certs Every subsequent time, it asks me to accept the cert again, and when I do it complains that it can't save it. It's not so much the complaining about not saving; it shouldn't even be *asking*. The cert is *right there*. Did the first poster not include a patch to solve this? I thought I saw one. -Robin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
