Hi,
At 10:18 04/02/2004, Antti Sinisalo wrote:
> When I first start mutt (with no .mutt/certs or an empty file) I get
> asked whether I want to (r)eject, accept (o)nce, (a)ccept always the
> certificate. When I accept it, mutt says "Certificate saved" and
> everything works fine. The certificate gets saved to .mutt/certs.
>
> But the next time I start mutt, the already saved certificate won't get
> used for some reason. Mutt asks me again to reject, accept once or
> accept always. And this time, when I select accept always, I get an
> error message "Warning: Couldn't save certificate". After that I can use
> mutt as usual, but the certificate is only valid for one use at a time.
I've the same problem and no solution. But it's strange that the
error doesn't occur on every system I use.
Two examples with no personal and the same global config file:
1.) debian woody with mutt from backports.org:
it works.
Mutt 1.5.5.1i (2003-11-05)
System: Linux 2.6.3 (i686) [using ncurses 5.2] [using libidn
0.3.4 (compiled with 0.3.4)]
2.) debian sid:
it does not work.
Mutt 1.5.5.1+cvs20040105i (2003-11-05)
System: Linux 2.6.3 (i686) [using ncurses 5.3] [using libidn
0.4.1 (compiled with 0.3.4)]
It's not the way mutt saves the certificates: I tried to use the one
from the working system on the one that does not - makes no difference.
Any ideas? Tell me if you need more information.
Could it have something to do with a different version of a library?
If I remember correctly on pure debian woody it worked and on pure
sarge it did not.
Regards,
Klara
Attachment:
signature.asc
Description: Digital signature