From: Russ Allbery <rra@stanford.edu>
Subject: Re: RFC-2047 vs. INN Compatibility Issue
Date: Sat, 24 May 2003 12:44:40 -0700 [thread overview]
Message-ID: <ylu1bkku3b.fsf@windlord.stanford.edu> (raw)
In-Reply-To: <20030524155517.GA24987@merlin.emma.line.org> (Matthias Andree's message of "Sat, 24 May 2003 17:55:17 +0200")
Matthias Andree <matthias.andree@gmx.de> writes:
> Gnus just generated an article that news.cis.dfn.de aka
> news.fu-berlin.de didn't accept (they run some INN version I can't
> figure out via NNTP as they put me into NNRPD directly rather than
> INND). Their server complained 441 437 Missing "Subject" header.
> What happened? Gnus generated a header like this in a reply:
> Newsgroups: de.comm.software.mailserver
> Followup-To: poster
> Subject:
> =?iso-8859-15?q?Re:_kein_Anmeldung_mit_pop3_m=F6glich_bei_courier-imap?=
> Looks like this is fine according to RFC-2822 and 2047, but it is not a
> recommended way to encode the header, rfc2047.el encodes too much
> currently.
All versions of INN will reject that. (It's a long-standing bug in the
INN header parsing.)
--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
next prev parent reply other threads:[~2003-05-24 19:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-24 15:55 Matthias Andree
2003-05-24 19:44 ` Russ Allbery [this message]
2003-05-26 18:40 ` Matthias Andree
2003-05-26 19:38 ` Russ Allbery
2003-05-28 17:28 ` Dave Love
2003-05-28 19:12 ` Russ Allbery
2003-05-28 17:27 ` Dave Love
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=ylu1bkku3b.fsf@windlord.stanford.edu \
--to=rra@stanford.edu \
/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).