When sending an encrypted mail, mutt crahes when it tries to find out what key to use based on the recipient's address. I searched for the problem and found ¹ which also contains a patch that solves the problem. Version 1.5.22-r6 is also fixed, so it would be easiest and best to mark it stable and remove r5 from portage as soon as appropriately possible. ¹ http://permalink.gmane.org/gmane.mail.mutt.devel/21951 Cheers Reproducible: Always Steps to Reproduce: Write a mail and enable ecryption. Send the mail. Mutt starts looking for a key that matches the recipient's mail address. Actual Results: Mutt crashes with a segfault in rfc822_parse_adrlist (top=top@entry=0x0, s=0x0) at rfc822.c:387
I can confirm this bug. Run into it some days ago. Updating to the currently unstable version 1.5.23-r6 fixes this problem.
I can confirm this bug, too. The patch described in the previously referred-to mail.mutt.devel posting fixes the problem in my case. This patch is included in mutt-1.5.23-r6's patch at lines 1637--1638. For those not wanting to upgrade to mutt-1.5.23-r6 but stay with the stable mutt-mutt-1.5.23-r5, I'll attach a small patch to this bug report which shall be placed in /etc/portage/patches/mail-client/mutt/ Just re-compile mutt to make use of this patch. It'll has to be removed when 1.5.23-r6 or later becomes stable, though.
Created attachment 400706 [details, diff] Patch from http://permalink.gmane.org/gmane.mail.mutt.devel/21951 for mail-client/mutt-1.5.23-r5
There's no good reason not to run -r6 IMO, it just awaits stabilisation.
(In reply to Fabian Groffen from comment #4) > There's no good reason not to run -r6 IMO, it just awaits stabilisation. Can you create a stabilization bug?
only PPC pending, considering this bug as fixed.
