From: Wes Hardaker <wes@hardakers.net>
Subject: Re: Exaggerated use of Face and X-Face
Date: Thu, 22 Apr 2004 14:28:45 -0700 [thread overview]
Message-ID: <sdn053bt2q.fsf@wes.hardakers.net> (raw)
In-Reply-To: <v93c6vdhrp.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Thu, 22 Apr 2004 19:50:02 +0200")
>>>>> On Thu, 22 Apr 2004 19:50:02 +0200, Reiner Steib <4.uce.03.r.s@nurfuerspam.de> said:
>> Sigh. Mail readers really should ignore unknown headers by default.
Reiner> At least for news (I'm not sure about mail):
Well, I use gnus more for mail than news...
--
"In the bathtub of history the truth is harder to hold than the soap,
and much more difficult to find." -- Terry Pratchett
next prev parent reply other threads:[~2004-04-22 21:28 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
2004-04-22 21:28 ` Wes Hardaker [this message]
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=sdn053bt2q.fsf@wes.hardakers.net \
--to=wes@hardakers.net \
/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).