I'm seeing a mildly annoying behaviour when using postponed messages
in mutt-1.0.1i:
- compose a message
- postpone it, at time T1
- edit it again later; even postpone it again
- use the f command (edit-fcc) from the compose menu to set to save
a copy to a file
- send the message, at time T2
The copy of the message saved to file has the timestamp in the "From "
mailbox envelope header (not the "From:" RFC 822 header) set to T1 and
the "Date:" header set to T2. This can be a bit disconcerting if there
is a significant interval between T1 and T2, and you then sort the saved
file by received date (which looks at the "From " envelope). I would
have expected the "From " envelope header to be set to T2, as that would
be the timestamp when it was placed in the file.
The time of the first postpone is also propogated through successive
postpones; for some reason, mutt thinks that first postpone date is
significant enough to save. Any idea why?
Thanks,
Wayne Chapeskie
