From: Lloyd Zusman <ljz@asfast.com>
Subject: Re: I'm very sorry ...
Date: Thu, 10 Oct 2002 21:12:27 -0400 [thread overview]
Message-ID: <m21y6xbwxw.fsf@asfast.com> (raw)
In-Reply-To: <m3ptuhss0p.fsf@defun.localdomain> (Jesper Harder's message of "Fri, 11 Oct 2002 03:06:46 +0200")
Jesper Harder <harder@ifa.au.dk> writes:
> Lloyd Zusman <ljz@asfast.com> writes:
>
>> [ ... ]
>
> Hey, but maybe it discovered a bug in Gnus. It shouldn't send out 8-bit
> headers by default.
>
> But when I reply to David Kågedal's message, I get this In-Reply-To
> header without 8bit chars:
>
> In-Reply-To: <u5tptuiw90p.fsf@deckard.uppsala.vtech> (David
> =?iso-8859-1?q?K=E5gedal's?= message of "Thu, 10 Oct 2002 18:31:18 +0200")
>
> Did you do customize something to change the behaviour?
I don't know. I have literally 10+ years of accumulated customizations
in my .gnus.el file, and these days, my head spins every time I try to
make sense of it. :)
What sort of customizations might affect this?
--
Lloyd Zusman
ljz@asfast.com
prev parent reply other threads:[~2002-10-11 1:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-11 0:46 Lloyd Zusman
2002-10-11 1:06 ` Jesper Harder
2002-10-11 1:12 ` Lloyd Zusman [this message]
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=m21y6xbwxw.fsf@asfast.com \
--to=ljz@asfast.com \
/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).