From: Matthias Wiehl <mwiehl@gmx.de>
Cc: ding@gnus.org
Subject: Re: My From header causes strange effects
Date: 25 Oct 2000 17:04:52 +0200 [thread overview]
Message-ID: <873dhlc67f.fsf@fulmine.dhs.org> (raw)
In-Reply-To: <vaf4s21jf63.fsf@lucy.cs.uni-dortmund.de>
On 25 Oct 2000, Kai Großjohann wrote:
> My From header looks like this:
>
> From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai =?iso-8859-1?q?Gro=DFjoha?=
> =?iso-8859-1?q?nn?=)
Which is, as far as I can tell, a correctly encoded header value.
> This causes many followups to my messages to start with:
>
> Kai Großjoha nn writes
I've seen such an attribution in an article that was posted using
"knews". I experienced that this program quite frequently does
strange things with article headers (especially with qp-encoded ones),
so my opinion on this would be that Gnus is not to blame here.
--
Matthias Wiehl <mwiehl@gmx.de> * <http://linux.unixcity.de/mwiehl/>
next prev parent reply other threads:[~2000-10-25 15:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-25 12:09 Kai Großjohann
2000-10-25 15:04 ` Matthias Wiehl [this message]
2000-10-25 21:45 ` Kai Großjohann
2000-10-25 23:06 ` ShengHuo ZHU
2000-10-27 22:35 ` Matthias Wiehl
2000-10-25 15:48 ` Paul Jarc
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=873dhlc67f.fsf@fulmine.dhs.org \
--to=mwiehl@gmx.de \
--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).