Gnus development mailing list
 help / color / mirror / Atom feed
From: Brian May <bmay@csse.monash.edu.au>
Subject: Re: Bugs in PGnus
Date: 25 Nov 1999 10:07:40 +1100	[thread overview]
Message-ID: <t4izow3sd37.fsf@silas-1.cc.monash.edu.au> (raw)
In-Reply-To: <vafhfiex3n8.fsf@lucy.cs.uni-dortmund.de>

>>>>> "Kai" == Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:

    Kai> Have you tried setting nntp-record-commands to t, then
    Kai> compare traces of the communication between Gnus and the NNTP
    Kai> server at uni and at home?

Here is what I get when I try to fetch an article (by message-id)
at Monash Uni:

19991125T093917.704 newsserver.cc.monash.edu.au HEAD <38385A79.8410721@mcn.net>
19991125T093917.902 newsserver.cc.monash.edu.au ARTICLE <38385A79.8410721@mcn.net>

This is what happens when PGnus knows the message number:
19991125T093927.248 newsserver.cc.monash.edu.au ARTICLE 34480

At home, the first two commands would look more like (edited to
look like the expected form):
19991125T093917.704 newsserver.cc.monash.edu.au HEAD <38385A79.8410721@mcn.net>
19991125T093917.902 newsserver.cc.monash.edu.au ARTICLE 34479

ie PGnus is able to find the message number just by looking at the
header. My guess is it does this via the Xref header. So, the
obvious problem is that PGnus cannot interpret the Xref header here
at Uni - I don't know why, it looks OK to me:

Xref: towncrier.cc.monash.edu.au rec.aviation.ifr:52840 rec.aviation:34480

Hang on... Perhaps PGnus is confused with the "towncrier.cc.monash.edu.au"
bit - my newsserver is setup as "newserver.cc.monash.edu.au":

[504] [dec16:bmay] ~ >host newsserver.cc.monash.edu.au 
newsserver.cc.monash.edu.au has address 130.194.1.90
newsserver.cc.monash.edu.au mail is handled (pri=20) by mx.cc.monash.edu.au
newsserver.cc.monash.edu.au mail is handled (pri=10) by towncrier.cc.monash.edu.au
[505] [dec16:bmay] ~ >host towncrier.cc.monash.edu.au
towncrier.cc.monash.edu.au has address 130.194.1.90
towncrier.cc.monash.edu.au mail is handled (pri=20) by mx.cc.monash.edu.au
towncrier.cc.monash.edu.au mail is handled (pri=10) by towncrier.cc.monash.edu.au

(note: they both have the same IP address).

However, I tried changing gnus-select-method to use towncrier, but
it didn't help.

Is there anyway to debug why PGnus doesn't like the Xref
header (assuming my assumptions are correct)?
-- 
Brian May <bmay@csse.monash.edu.au>


  parent reply	other threads:[~1999-11-24 23:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-22  0:51 Brian May
1999-11-22  2:15 ` Shenghuo ZHU
1999-11-22  2:59   ` Brian May
1999-11-22  3:45     ` Shenghuo ZHU
1999-11-22  9:43 ` Kai Großjohann
1999-11-22 23:43   ` Brian May
1999-11-23 21:44     ` Kai Großjohann
1999-11-24 23:07   ` Brian May [this message]
1999-11-25  9:18     ` Kai Großjohann
1999-11-28 23:39       ` Brian May
1999-11-29  2:46         ` Brian May
1999-12-01 19:16     ` Lars Magne Ingebrigtsen
1999-12-02  1:32       ` Brian May
1999-12-06  4:10         ` Lars Magne Ingebrigtsen
1999-12-06 23:11           ` Brian May
1999-12-07 18:09             ` Shenghuo ZHU
1999-12-01 19:22 ` Lars Magne Ingebrigtsen

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=t4izow3sd37.fsf@silas-1.cc.monash.edu.au \
    --to=bmay@csse.monash.edu.au \
    /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).