From: Andreas Schwab <schwab@linux-m68k.org>
To: ding@gnus.org
Subject: Re: empty Followup-to: header
Date: Sat, 10 Apr 2021 19:41:54 +0200 [thread overview]
Message-ID: <87fszy595p.fsf@igel.home> (raw)
In-Reply-To: <87k0pafdbs.fsf@zoho.eu> (Emanuel Berg's message of "Sat, 10 Apr 2021 16:01:43 +0200")
On Apr 10 2021, Emanuel Berg wrote:
> o/ can I have an empty Followup-to: header?
RFC5536 doesn't allow that. See also RFC1122.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2021-04-10 17:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 14:01 Emanuel Berg
2021-04-10 17:08 ` Emanuel Berg
2021-04-10 17:41 ` Andreas Schwab [this message]
2021-04-10 19:52 ` Emanuel Berg
2021-04-10 20:04 ` Emanuel Berg
2021-04-10 20:08 ` Emanuel Berg
2021-04-10 20:13 ` Emanuel Berg
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=87fszy595p.fsf@igel.home \
--to=schwab@linux-m68k.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).