Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: Exaggerated use of Face and X-Face
Date: Thu, 22 Apr 2004 19:50:02 +0200	[thread overview]
Message-ID: <v93c6vdhrp.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <sdk7087zav.fsf@wes.hardakers.net>

On Thu, Apr 22 2004, Wes Hardaker wrote:

>>>>>> On Thu, 22 Apr 2004, Reiner Steib <4.uce.03.r.s@nurfuerspam.de> said:
>
> Reiner> Don't you think that using four (X-)Face headers is a bit too much?
> Reiner> Personally, I don't care too much about it, but some people already
> Reiner> complain about Gnus users with a single Face (or even X-Face) header.
>
> Sigh.  Mail readers really should ignore unknown headers by default.

At least for news (I'm not sure about mail):

,----[ rfc1036.txt ]
|     Certain headers are required, and certain other headers are
|     optional.  Any unrecognized headers are allowed, and will be passed
|     through unchanged.  [...]
`----

> However, I've had to turn off my Face header for everything but this
> mailing list because people asked me to stop putting it in there
> (including my boss and my parents).

In which way did it annoy them?

The usual arguments in Usenet [1] are bandwidth and that people claim
that "Face:" should begin with "X-" (experimental header).  Yes, I
know Lars position about this:

,----[ <news:m3of6lmq9a.fsf@quimbies.gnus.org> ]
| > I thought it was against some RFC (or at least against some
| > convention), to have non-standard headers without the "X-" prefix.
| 
| Yes, that's true, but I intend Face to become a standard header.  :-)
`----

Maybe Lars refers to the last item here:

,----[ draft-ietf-usefor-article-11.txt ]
| 4.2.1.  Naming of Headers
| 
|    [...]
|    Whilst relaying agents MUST accept, and pass on unaltered, any non-
|    variant header whose header-name is syntactically correct, and
|    reading agents MUST enable them to be displayed, at least optionally,
|    posting and injecting agents SHOULD NOT generate headers other than
|      o headers established by this standard or any extension to it;
|      o those recognized by other IETF-established standards, notably the
|        Email standard [RFC 2822] and its extensions, excluding any
|        explicitly deprecated for Netnews (e.g. see section 9.2.1 for the
|        deprecated Disposition-Notification-To-header); or,
|        alternatively, those listed in some future IANA registry of
|        recognized headers;
|      o experimental headers beginning with "X-" (as defined in 4.2.5.1);
|      o on a provisional basis only, headers related to new protocols
|        under development which are the subject of (or intended to be the
|        subject of) some IETF-approved RFC (whether Informational,
|        Experimental or Standards-Track).
`----

(I'm not sure that these references are the most recent standards.)

Concerning "bandwidth": Someone in gnu.emacs.gnus wrote that a French
ISP planned to ban "Face" headers.  See the Thread before
<news:v9d68jxsfp.fsf@marauder.physik.uni-ulm.de>.

Bye, Reiner.

[1] See e.g. the thread around
    <news:v9lloj1g8k.fsf@marauder.physik.uni-ulm.de> in
    de.comm.software.newsreader (in German).
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/




  reply	other threads:[~2004-04-22 17:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-21 16:39 [Q] why using spam.el ? Didier Verna
2004-04-21 18:19 ` Ted Zlatanov
2004-04-21 20:10   ` Jonas Steverud
2004-04-22 10:45   ` Didier Verna
2004-04-22 11:30     ` Exaggerated use of Face and X-Face (was: [Q] why using spam.el ?) Reiner Steib
2004-04-22 16:27       ` Exaggerated use of Face and X-Face Wes Hardaker
2004-04-22 17:50         ` Reiner Steib [this message]
2004-04-22 21:28           ` Wes Hardaker
2004-04-22 21:41         ` Steve Youngs

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=v93c6vdhrp.fsf@marauder.physik.uni-ulm.de \
    --to=4.uce.03.r.s@nurfuerspam.de \
    --cc=reiner.steib@gmx.de \
    /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).