From: Russ Allbery <rra@stanford.edu>
Subject: Re: day of week in Date header?
Date: 06 May 2000 00:52:31 -0700 [thread overview]
Message-ID: <ylr9bguncw.fsf@windlord.stanford.edu> (raw)
In-Reply-To: Jesper Harder's message of "Sat, 06 May 2000 04:09:35 GMT"
Jesper Harder <jesper_harder@hotmail.com> writes:
> I get this list from the news-server at sunsite.auc.dk, and I know that
> it strips away the original date-header and inserts a new one -- this
> happens to mailing list messages and normal Usenet messages, too. The
> news-server at my ISP also does this.
> I don't think this behaviour actually violates rfc-1036, but it /is/
> wrong according to grandson-of-1036.
It violates a MUST in the current USEFOR draft, for what it's worth, and
has been the cause of spews in the past.
--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
next prev parent reply other threads:[~2000-05-06 7:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-05 17:47 Kai Großjohann
2000-05-05 18:59 ` Shenghuo ZHU
2000-05-05 20:58 ` Kai Großjohann
2000-05-05 21:07 ` Shenghuo ZHU
2000-05-05 21:56 ` Kai Großjohann
2000-05-05 22:20 ` Kai Großjohann
2000-05-06 4:09 ` Jesper Harder
2000-05-06 7:52 ` Russ Allbery [this message]
2000-05-06 11:37 ` Kai Großjohann
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=ylr9bguncw.fsf@windlord.stanford.edu \
--to=rra@stanford.edu \
/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).