[hmmm...  did it again...  answered my question as I was composing it...
but thought the group might be interested...]

Original question
=================

Greetings!

This is a minor annoyance, but I thought I'd ask about it anyway.  If
I postpone a message and send it, say, three days later, the "^From "
line that gets sent with the message (at least in my own bcc'd copy)
contains the date and time corresponding to when I last postponed the
message (i.e., three days ago).

So my bcc'd copy of such a message that I send will have the
"correct" date in the Date: header, i.e., the Date: header will
contain the date and time at which I sent the message.  But the
"^From " line will have a date from three days ago (in my current
example).  

This messes up the date-received order of a mail folder.  I realize I
could sort the folder by date, and the message would appear in the
correct order, but sometimes I need to sort by date-received.  Can I
somehow get mutt to send "fresh" "^From " lines when sending
postponed messages?

This seems like a bug to me, as it misrepresents the date and time a
message was received.

Thanks!
David

Answer
======

The stale "^From " lines were showing up in my bcc copies, so I thought I
better see if they showed up in actual received copies of the
postponed-but-then-sent messages.  So I went into my postponed folder
and sent a message to another of my accounts.  The "^From " line contained
the "fresh" date, i.e., a time which occurred after the message was
actually sent.

Then it dawned on me:  when I keep copies of non-mailing-list email that
I send to folks, I use *fcc*, not bcc to keep a copy!  And fcc just
blindly appends the message to a file, whereas actually sending the
message, a recipient (whether a To:, Cc:, or Bcc: recipient) has the
advantage of their local mail transport agent inserting the correct
date in the "^From " line.  (Oh yeah, I forgot that the MTA does that.
[sound of palm hitting head])

So, now I'll bcc myself instead of fcc'ing a folder when I send
previously postponed messages.

No bug.  User error! :-)

-- 
Live in a world of your own, but always welcome visitors.

Reply via email to