From: Karsten Thygesen <karthy@kom.auc.dk>
Subject: Re: NNTP problem when posting - Bug?
Date: Fri, 17 Apr 1998 19:22:10 GMT [thread overview]
Message-ID: <yd8iuo86yot.fsf@dacia.kom.auc.dk> (raw)
In-Reply-To: <yd8sonfv5bn.fsf@yugo.kom.auc.dk>
>>>>> "Karsten" == Karsten Thygesen <karthy@kom.auc.dk> writes:
Karsten> I have a problem with gnus talking to a Typhoon newsserver,
Karsten> and it appears, that gnus is not complying to RFC977 for
Karsten> posting.
Karsten> The problem is the "end of article" sequence, which is
Karsten> wrong. Here is the output of a snoop on the network:
Karsten> 752: 5843 770d 0a2d 2d2d 2d2d 454e 4420 5047
Karsten> XCw..-----END PG 768: 5020 5349 474e 4154 5552 452d
Karsten> 2d2d 2d2d P SIGNATURE----- 784: 0a2e 0d0a ....
Karsten> So the article is terminated with
Karsten> -----\n.\r\n
Karsten> and it should be
Karsten> -----\r\n.\r\n according to RFC977
Karsten> Sometimes, gnus is doing "the right thing", so I'm a little
Karsten> confused about this. Is my assumptions correct?
After further investigation, I found out, that the right behavior
depends on whenever an article is terminated with a newline or
not. This is a bug.
Anyway - the nntp-encode-text method in nntp.el from qgnus solves the
problem, so how about in-cooperating this method in the next release of
gnus?
Best,
Karsten
who can post again :-)
--
M.Sc.E.E, Sys/Net-administrator, BOFH, Aalborg University, Denmark
http://www.kom.auc.dk/~karthy/ for more information.
SunSITE Denmark Manager (http://sunsite.auc.dk/)
# $Id: .signature,v 1.1 1997/06/18 08:30:00 karthy Exp $
.
next prev parent reply other threads:[~1998-04-17 19:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-15 8:48 Karsten Thygesen
1998-04-17 19:22 ` Karsten Thygesen [this message]
1998-04-17 22:35 ` Lars Balker Rasmussen
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=yd8iuo86yot.fsf@dacia.kom.auc.dk \
--to=karthy@kom.auc.dk \
/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).