#3653: Fcc empty on postponed emails
-------------------------+----------------------
Reporter: muttbug111 | Owner: me
Type: defect | Status: assigned
Priority: major | Milestone:
Component: mutt | Version: 1.5.21
Resolution: | Keywords:
-------------------------+----------------------
Changes (by me):
* owner: mutt-dev => me
* status: new => assigned
Comment:
I was able to replicated this issue.
send.c:1519
if (!fcc[0] && !(flags & (SENDPOSTPONED)) && (!(flags & SENDBATCH) ||
(quadoption (OPT_COPY) & 0x1)))
when a message is being recalled, the SENDPOSTPONED bit is set in "flags",
so
even though fcc is empty, we skip the body of the if-statement which sets
a
default fcc value.
Presumably that check is there so that if the user did not want a copy of
the
message to be saved, they could set fcc to the empty string. But as the
submitter noted, a missing x-mutt-fcc is also treated as an empty fcc (it
implicitly assumes that every message in the Drafts folder was placed
there by
Mutt).
In order to preseve the ability for the user to keep an empty fcc, the
default
fcc should be generated if the x-mutt-fcc was missing. At first glance it
appears we can't necessarily do this in mutt_get_postponed() because in
the
normal situation we do not select fcc until after send-hooks have fired,
and
that could potentially affect the default fcc calculation ($save_name,
$force_name).
So perhaps a flag needs to be set to force generation of the fcc when
required. mutt_get_postponed() does replace the `flags' value, so it
looks
like a new flag like SENDPOSTPONEDFCC can indicate the presence of the
x-mutt-fcc and the check at line 1519 can be changed to !(flags &
SENDPOSTPONEDFCC).
--
Ticket URL: <http://dev.mutt.org/trac/ticket/3653#comment:1>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
