From: Simon Josefsson <jas@extundo.com>
Subject: Re: Stoping gnus reading my newsrc
Date: Wed, 19 Nov 2003 17:49:43 +0100 [thread overview]
Message-ID: <iluk75wcnh4.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m3k75wsoq4.fsf@home.tcob1.net>
sean@tcob1.net (Sean Rima) writes:
> =2D----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
Just out of curiosity, are you using Gnus to sign your messages? For
some reason they are QP encoded, but your headers does not indicate
that QP is used. I'm hoping Gnus isn't responsible for generating
that mess...
next parent reply other threads:[~2003-11-19 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m38ymdifkb.fsf@home.tcob1.net>
[not found] ` <m33ccl9wnz.fsf@defun.localdomain>
[not found] ` <m3k75wsoq4.fsf@home.tcob1.net>
2003-11-19 16:49 ` Simon Josefsson [this message]
[not found] ` <m3u150w08e.fsf@home.tcob1.net>
2003-11-20 3:15 ` Simon Josefsson
2003-11-20 9:00 ` Sean Rima
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=iluk75wcnh4.fsf@latte.josefsson.org \
--to=jas@extundo.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).