From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: [Rob Browning <rlb@defaultvalue.org>] Re: Bug#139487: Gnus: nntp backend doesn't reauthenticate after a dropped connection
Date: Mon, 15 Apr 2002 21:03:24 -0400 [thread overview]
Message-ID: <2nu1qccv4z.fsf@zsh.cs.rochester.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 188 bytes --]
Did anyone else encounter this problem?
According to the source code, Gnus will send AUTHINFO to the server
when received 480. But I don't have a server to verify. Anyone?
ShengHuo
[-- Attachment #2: Type: message/rfc822, Size: 2656 bytes --]
From: Rob Browning <rlb@defaultvalue.org>
To: bug-gnu-emacs@gnu.org
Cc: 139487-forwarded@bugs.debian.org, Andrew Stribblehill <a.d.stribblehill@durham.ac.uk>
Subject: Re: Bug#139487: Gnus: nntp backend doesn't reauthenticate after a dropped connection
Date: Sun, 14 Apr 2002 00:25:43 -0500
This was reported recently, but I don't have a server I can use to
verify the bug.
Thanks
Andrew Stribblehill <a.d.stribblehill@durham.ac.uk> writes:
> Package: emacs21
> Version: 21.1-7
> Severity: normal
>
> When I connect to an NNTP server which requires AUTHINFO stuff, all
> works fine. Gnus asks me for my username and password then connects
> perfectly.
>
> If I leave it idle for longer than the server's timeout period, the
> connection drops.
>
> Subsequently, a re-connect (e.g. with 'g' in the Groups buffer) fails
> to authenticate, despite the server repeatedly sending the 'Require
> AUTHINFO' status message (240?).
>
> I'll happily provide further information if required.
>
> -- System Information
> Debian Release: 3.0
> Architecture: i386
> Kernel: Linux womble 2.4.16 #1 Wed Dec 19 11:48:46 GMT 2001 i686
> Locale: LANG=C, LC_CTYPE=C
>
> Versions of packages emacs21 depends on:
> ii dpkg 1.9.19 Package maintenance system for Deb
> ii emacsen-common 1.4.15 Common facilities for all emacsen.
> ii libc6 2.2.5-3 GNU C Library: Shared libraries an
> ii libjpeg62 6b-5 The Independent JPEG Group's JPEG
> ii liblockfile1 1.03 NFS-safe locking library, includes
> ii libncurses5 5.2.20020112a-5 Shared libraries for terminal hand
> ii libpng2 1.0.12-3 PNG library - runtime
> ii libtiff3g 3.5.5-6 Tag Image File Format library
> ii xaw3dg 1.5-12 Xaw3d widget set
> ii xlibs 4.1.0-14 X Window System client libraries
> ii zlib1g 1:1.1.4-1 compression library - runtime
>
> --
> Andrew Stribblehill <ads@debian.org>
> Systems programmer, IT Service, University of Durham, England
>
>
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD
_______________________________________________
Bug-gnu-emacs mailing list
Bug-gnu-emacs@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-gnu-emacs
reply other threads:[~2002-04-16 1:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2nu1qccv4z.fsf@zsh.cs.rochester.edu \
--to=zsh@cs.rochester.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).