From: Tassilo Horn <tsdh@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: ding@gnus.org
Subject: Re: Posting to my university's nntp server hangs
Date: Thu, 06 Mar 2014 08:37:10 +0100 [thread overview]
Message-ID: <87bnxju6ah.fsf@gnu.org> (raw)
In-Reply-To: <87ppm0qz8f.fsf@building.gnus.org> (Lars Ingebrigtsen's message of "Wed, 05 Mar 2014 19:25:36 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
>> No, one for each nntp server (gmane and my university).
>>
>> - " *server news.uni-koblenz.de nntp *nntpd**"
>> - " *server news.gmane.org nntp *nntpd**"
>>
>> And the " *server news.uni-koblenz.de nntp *nntpd**" buffer sometimes
>> contains stuff, e.g., after a `g' in *Group* it contains:
>> infko.softtech 0000003697 0000000034 y
>> infko.oopm 0000003087 0000000001 m
>> infko.mac 0000002661 0000000001 y
>
> So that's OK. Hm...
>
> Could you edebug through `nntp-request-post' and look in the
> nntp-server-buffer (whatever that is) buffer to see what the server
> says?
Ok, the problematic form in `nntp-request-post' is
(nntp-send-buffer "^[23].*\n")
and `nntp-server-buffer' is " *nntpd*" which contains this line
340 Ok, recommended ID <lf97sn$bi$2@cache.uni-koblenz.de>
And in `nntp-send-buffer' it hangs at the form
(nntp-retrieve-data
nil nntp-address nntp-port-number nntp-server-buffer
wait-for nnheader-callback-function)
which seems to be waiting for some response from the server that doesn't
arrive.
Bye,
Tassilo
next prev parent reply other threads:[~2014-03-06 7:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 9:41 Tassilo Horn
2014-03-05 14:02 ` Lars Ingebrigtsen
2014-03-05 14:12 ` Tassilo Horn
2014-03-05 17:06 ` Lars Ingebrigtsen
2014-03-05 18:16 ` Tassilo Horn
2014-03-05 18:25 ` Lars Ingebrigtsen
2014-03-06 7:37 ` Tassilo Horn [this message]
2014-03-06 12:19 ` Tassilo Horn
2014-03-06 12:56 ` Steinar Bang
2014-03-07 8:42 ` Tassilo Horn
2014-03-07 9:30 ` Steinar Bang
2014-03-07 10:19 ` Tassilo Horn
2014-03-07 11:45 ` Steinar Bang
2014-03-06 13:02 ` Eric S Fraga
2014-03-06 18:15 ` Andreas Schwab
2014-03-07 10:32 ` Eric S Fraga
2014-03-07 15:04 ` Lars Ingebrigtsen
2014-03-07 15:43 ` Tassilo Horn
2014-03-07 15:49 ` Tassilo Horn
2014-03-06 18:14 ` Andreas Schwab
2014-03-07 15:04 ` Lars 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=87bnxju6ah.fsf@gnu.org \
--to=tsdh@gnu.org \
--cc=ding@gnus.org \
--cc=larsi@gnus.org \
/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).