#1128408 Subject mangled for postponed messages

Package:
neomutt
Source:
neomutt
Description:
command line mail reader based on Mutt, with added features
Submitter:
Toni Mueller
Date:
2026-03-11 03:15:01 UTC
Severity:
normal
Tags:
#1128408#5
Date:
2026-02-19 12:28:31 UTC
From:
To:
Hi,

I am using neomutt and am running into the following problem:

When I am composing a message and then postpone it, the subject gets
changed to "...", and the original subject is lost.

I haven't tried to run a newer binary, but both the Debian changelog and
the release notes on Github don't indicate anything regarding this
issue.


Cheers,
Toni
#1128408#12
Date:
2026-02-19 17:39:16 UTC
From:
To:
Hi Toni,

So we are talking at least about trixie.

Could you send a reproducer here? For instance, at least the subject of
the postponed email, though the full headers/body would be better for
reproducibility.

Also, do you set any custom neomutt configs possibly related to that?
Sending a sample of your config (with any personal info removed) could
help too.

I plan to add newer versions of neomutt to trixie-backports, so if it's
solved in unstable/testing, you will be able to get it.

Cheers,
Charles
#1128408#17
Date:
2026-02-19 18:03:42 UTC
From:
To:
Hi Charles,

yes, I'm on Trixie.

I have just hit "reply" on this very message, then wrote a few words,
then postponed the message, then hit "m" for writing a new mail, then
responded "yes" to the question of whether I wanted to use one of the
postponed messages, then selected this message, and voila:

    Subject: ...

Compare to the original subject:

    Subject: Re: Bug#1128408: Subject mangled for postponed messages

Before filing the bug report, I had already checked on my IMAP server
that the email was already stored with the mangled subject when I
postponed it, not mangled when I pulled it back.

You should be able to reproduce the bug by executing this procedure with
this bug report message.

I have created a sanitized version of the config. Not using it is not an
option, as I need to specify where my mailboxen are, how to login etc.

Thank you!


Cheers,
Toni
#1128408#22
Date:
2026-02-20 14:40:46 UTC
From:
To:
Hi Toni,

My bad, I said vim, but it's actually neovim, though my nvim
configuration is pretty small and barebones (will attach here, maybe you
can try it or set EDITOR to nano and see if it still truncates).

Just had the time to test in trixie today and the procedure here doesn't
truncate the Subject header.

Hum, could it be the editor doing stuff behind neomutt's back?

Oops, sorry, forget to say there would be a lot of personal/confidential
info in there.

Maybe you can grep by the message subject, id or the trucated subject
and send only that part.

Hehehehehe it happens. I'm looking at your configs but nothing pops up
to my eyes as being the root cause for this weird behaviour.

So TLDR is I can't reproduce it on sid or trixie :-( Though I have
uploaded yesterday testing's version to backports, it's waiting in  the
NEW queue and should be available soon.

Cheers,
Charles
#1128408#29
Date:
2026-03-11 03:13:29 UTC
From:
To:
Hi Toni,

I did found the answer today talking to flatcap, the main upstream
developer!

So, this is a new feature which defaults to yes for encrypted and
autocrypting mail. Please, check the crypt_protected_headers_subject
option in the manual or online [1].

Cheers,
Charles

[1] https://neomutt.org/guide/reference#3-95-%C2%A0crypt_protected_headers_subject