Re: [Mutt] #3323: Sending postponed messages doesn't save a copy in
#3323: Sending postponed messages doesn't save a copy in $record
-------------------------------+--------------------------------------------
Reporter: antonio@xxxxxxxx | Owner: mutt-dev
Type: defect | Status: closed
Priority: minor | Milestone:
Component: mutt | Version: 1.5.20
Resolution: invalid | Keywords:
-------------------------------+--------------------------------------------
Changes (by agriffis):
* status: new => closed
* resolution: => invalid
Comment:
This is by design. Mutt saves the values of some variables (including
`$record`) in the message header when it writes to the postponed folder so
those variables can be restored when the message is recalled. As such,
the postponed folder is not intended to be written by programs other than
mutt, or at least one shouldn't attempt to recall messages that mutt did
not write there.
To accomplish something similar to what you're doing, you can use `git
imap-send` to save to a folder other than postponed, then use alt-e in
mutt to resend the message.
--
Ticket URL: <http://dev.mutt.org/trac/ticket/3323#comment:1>
Mutt <http://www.mutt.org/>
The Mutt mail user agent