Hi,

* Saad Kadhi [02-07-24 00:27:26 +0200] wrote:
> After postponing a second message and closing Mutt, I
> restarted the application and recalled the postponed
> messages. Immediately after answering yes to the "recall
> postpone.." question, Mutt segfaults and dumps core. After
> removing all the postponed messages but one, the recall
> function works correctly (not extensively tested).

That surely is not intended... ;-)

I'm too lazy trying to reproduce it here, but why not
contact the port maintainer first? Maybe the OpenBSD port
contains some patches causing your trouble? If he (she? ;-)
has no solutions you should consider reporting a bugreport
using the flea(1) utility comming with mutt.

If you're sure that it's not a configuration problem, you
may want to store a copy of your postpone file containing
two dummy messages (which cause the segfault) somewhere on
the web. Don't send attachements to the list, just post the
URL.

   bye, Rocco

Reply via email to