Gnus development mailing list
 help / color / mirror / Atom feed
From: asjo@koldfront.dk (Adam Sjøgren)
To: ding@gnus.org
Subject: Setting gnus-check-new-newsgroups to nil --> gnus-secondary-select-methods ignored
Date: Tue, 06 Jul 2010 22:51:34 +0200	[thread overview]
Message-ID: <87fwzwfi5l.fsf@topper.koldfront.dk> (raw)

If you, as I do, set gnus-check-new-newsgroups to nil, then Gnus will
happily ignore any configuration you have added to servers in
gnus-secondary-select-methods.

So putting this in your Gnus:

  (setq gnus-check-new-newsgroups nil)
  (setq gnus-secondary-select-methods
        '(
          (nntp "news.gmane.org"
                (nntp-open-connection-function nntp-open-tls-stream)
                (nntp-port-number 563)
                (nntp-address "snews.gmane.org"))
          ))

will make Gnus connect to news.gmane.org on port 119(!)

If you let gnus-check-new-newsgroups have its default value, then the
configuration in gnus-secondary-select-methods is used, and in the above
case the connection will be encrypted on port 563 to snews.gmane.org.

I am guessing that what happens when gnus-check-new-newsgroups isn't
nil, is that somehow the gnus-server-method-cache is initialized
"correctly", while it otherwise gets initialized "wrong", mistaking
secondary-select-method servers for foreign servers.

Do I make any sense at all?


  Best regards,

    Adam

-- 
 "My internal clock is on Tokyo time."                        Adam Sjøgren
                                                         asjo@koldfront.dk




             reply	other threads:[~2010-07-06 20:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-06 20:51 Adam Sjøgren [this message]
2010-07-06 20:58 ` Adam Sjøgren
2010-07-06 23:57   ` [PATCH] Avoid opening secondary select methods as foreign servers Adam Sjøgren
2010-07-17 20:13     ` Adam Sjøgren
2010-08-03 19:10       ` Ted Zlatanov
2010-08-08 13:59         ` Adam Sjøgren
2010-08-08 14:14           ` Adam Sjøgren
2010-08-09 14:12             ` Ted Zlatanov

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=87fwzwfi5l.fsf@topper.koldfront.dk \
    --to=asjo@koldfront.dk \
    --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).