[...]
> Yes (partially) since this is what I've guessed (more or less).
> crypt_autosign is set. I didn't read the code but my guess is that mutt
> tries to S/MIME sign the message since the original one is S/MIME, too.
>
> To verify that this is the problem (which should be reproducable I
> think), you could try unsetting $crypt_autosign and re-trying. The crash
> should go away.
Correct. After ":set crypt_autosign=no" composer says: "Security: Clear"
and I do not get crash. Other workaround (which I have been using) is to
press 'p' to show pgp-menu, which first asks you if you wish to clear
the S/MIME bit.
> Trying the other case (replying to PGP signed mail with only S/MIME
> setup and $crypt_autosign) might be interesting too.
I haven't tried that.
> I'm not sure where to fix this since I didn't read the code. Maybe that
> function should really just fail since you also set $crypt_autosmime
> (unsetting it may also make the problem disappear)...
Now I see. I had 'pgp_autosign=yes' which is deprecated now, and turned
on crypt_autosign. I replaced it with theese three and it seems to use
PGP always for signing.
set crypt_autosign=yes
set crypt_autopgp=yes
set crypt_autosmime=no
Thank you
--
Vlad
Attachment:
pgpqD8Kmdru9V.pgp
Description: PGP signature