Gnus development mailing list
 help / color / mirror / Atom feed
From: XeCycle <XeCycle@Gmail.com>
To: ding@gnus.org
Subject: Re: nntp-send-authinfo doesn't look at nntp-port-number
Date: Thu, 23 Feb 2012 20:49:58 +0800	[thread overview]
Message-ID: <871uplww7d.fsf@Gmail.com> (raw)
In-Reply-To: <b4md395ernm.fsf@jpl.org>

[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]

Katsumi Yamaoka <yamaoka@jpl.org> writes:

[...]

> Maybe the following patch will make it work.  Er, but I don't
> know whether it's right to add "nntps" and "snews"...
>
> --- nntp.el~	2012-02-15 09:22:23.734375000 +0000
> +++ nntp.el	2012-02-23 11:02:16.234375000 +0000
> @@ -1197,7 +1197,8 @@
>            (nth 0 (auth-source-search :max 1
>                                       :host (list nntp-address
>                                                   (nnoo-current-server 'nntp))
> -                                     :port '("119" "nntp"))))
> +                                     :port '("119" "nntp"
> +					     "563" "nntps" "snews"))))
>           (auth-user (plist-get auth-info :user))
>           (auth-force (plist-get auth-info :force))
>           (auth-passwd (plist-get auth-info :secret))

Thanks for this, but is there no way to check the defined port
number?  That would be more robust.

-- 
Carl Lei (XeCycle)
Department of Physics, Shanghai Jiao Tong University
OpenPGP public key: 7795E591
Fingerprint: 1FB6 7F1F D45D F681 C845 27F7 8D71 8EC4 7795 E591

[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]

  reply	other threads:[~2012-02-23 12:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23  6:38 XeCycle
2012-02-23 11:05 ` Katsumi Yamaoka
2012-02-23 12:49   ` XeCycle [this message]
2012-02-23 23:11     ` Katsumi Yamaoka
2012-02-24 15:42       ` Ted Zlatanov
2012-02-25  0:41         ` Katsumi Yamaoka

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=871uplww7d.fsf@Gmail.com \
    --to=xecycle@gmail.com \
    --cc=ding@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).