From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: dates in *Drafts*
Date: Thu, 19 Oct 2006 20:40:36 +0900 [thread overview]
Message-ID: <b4mods8y1mz.fsf@jpl.org> (raw)
In-Reply-To: <b4m1wp68g4a.fsf@jpl.org>
>>>>> In <b4m1wp68g4a.fsf@jpl.org> Katsumi Yamaoka wrote:
>>>>>> In <87fydmlrel.fsf@jidanni.org> Dan Jacobson wrote:
>> OK, works now, but note that the user must now have a Ph.D. in order
>> to get the dates turned on in *Drafts*.
> I think it's a good idea that there's always the Date header in
> drafts. I'd like to do it when I have time.
I made changes in the trunk so that Gnus adds the Date header
when saving a draft message by default. The Date header made
then is unchanged when sending the draft with no modification.
This meets RFC2822, the section 3.6.1:
3.6.1. The origination date field
[...]
The origination date specifies the date and time at which the creator
of the message indicated that the message was complete and ready to
enter the mail delivery system. For instance, this might be the time
that a user pushes the "send" or "submit" button in an application
program. In any case, it is specifically not intended to convey the
time that the message is actually transported, but rather the time at
which the human or other creator of the message has put the message
into its final form, ready for transport. (For example, a portable
computer user who is not connected to a network might queue a message
for delivery. The origination date is intended to contain the date
and time that the user queued the message, not the time when the user
connected to the network to send the message.)
parent reply other threads:[~2006-10-19 11:40 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <b4m1wp68g4a.fsf@jpl.org>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b4mods8y1mz.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).