[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Subscribing to a foreign group from an NNTP server is rather easy.
You just specify nntp
as method and the address of the NNTP
server as the, uhm, address.
If the NNTP server is located at a non-standard port, setting the third element of the select method to this port number should allow you to connect to the right port. You'll have to edit the group info for that (see section 2.9 Foreign Groups).
The name of the foreign group can be the same as a native group. In fact, you can subscribe to the same group from as many different servers you feel like. There will be no name collisions.
The following variables can be used to create a virtual nntp
server:
nntp-server-opened-hook
MODE READER
to the server with the
nntp-send-mode-reader
function. This function should always be
present in this hook.
nntp-authinfo-function
nntp-send-authinfo
, which looks
through your `~/.authinfo' (or whatever you've set the
nntp-authinfo-file
variable to) for applicable entries. If none
are found, it will prompt you for a login name and a password. The
format of the `~/.authinfo' file is (almost) the same as the
ftp
`~/.netrc' file, which is defined in the ftp
manual page, but here are the salient facts:
The valid tokens include `machine', `login', `password',
`default'. In addition Gnus introduces two new tokens, not present
in the original `.netrc'/ftp
syntax, namely `port' and
`force'. (This is the only way the `.authinfo' file format
deviates from the `.netrc' file format.) `port' is used to
indicate what port on the server the credentials apply to and
`force' is explained below.
Here's an example file:
machine news.uio.no login larsi password geheimnis machine nntp.ifi.uio.no login larsi force yes |
The token/value pairs may appear in any order; `machine' doesn't have to be first, for instance.
In this example, both login name and password have been supplied for the former server, while the latter has only the login name listed, and the user will be prompted for the password. The latter also has the `force' tag, which means that the authinfo will be sent to the nntp server upon connection; the default (i.e., when there is not `force' tag) is to not send authinfo to the nntp server until the nntp server asks for it.
You can also add `default' lines that will apply to all servers that don't have matching `machine' lines.
default force yes |
This will force sending `AUTHINFO' commands to all servers not previously mentioned.
Remember to not leave the `~/.authinfo' file world-readable.
nntp-server-action-alist
(setq nntp-server-action-alist '(("innd" (ding)))) |
You probably don't want to do that, though.
The default value is
'(("nntpd 1\\.5\\.11t" (remove-hook 'nntp-server-opened-hook 'nntp-send-mode-reader))) |
This ensures that Gnus doesn't send the MODE READER
command to
nntpd 1.5.11t, since that command chokes that server, I've been told.
nntp-maximum-request
head
commands. To
speed things up, the back end sends lots of these commands without
waiting for reply, and then reads all the replies. This is controlled
by the nntp-maximum-request
variable, and is 400 by default. If
your network is buggy, you should set this to 1.
nntp-connection-timeout
nntp
groups that you connect to
regularly, you're sure to have problems with NNTP servers not
responding properly, or being too loaded to reply within reasonable
time. This is can lead to awkward problems, which can be helped
somewhat by setting nntp-connection-timeout
. This is an integer
that says how many seconds the nntp
back end should wait for a
connection before giving up. If it is nil
, which is the default,
no timeouts are done.
nntp-server-hook
nntp-buggy-select
nil
if your select routine is buggy.
nntp-nov-is-evil
t
, but nntp
usually checks automatically whether NOV
can be used.
nntp-xover-commands
("XOVER"
"XOVERVIEW")
.
nntp-nov-gap
nntp
normally sends just one big request for NOV lines to
the server. The server responds with one huge list of lines. However,
if you have read articles 2-5000 in the group, and only want to read
article 1 and 5001, that means that nntp
will fetch 4999 NOV
lines that you will not need. This variable says how
big a gap between two consecutive articles is allowed to be before the
XOVER
request is split into several request. Note that if your
network is fast, setting this variable to a really small number means
that fetching will probably be slower. If this variable is nil
,
nntp
will never split requests. The default is 5.
nntp-prepare-server-hook
nntp-warn-about-losing-connection
nil
, some noise will be made when a
server closes connection.
nntp-record-commands
nil
, nntp
will log all commands it sends to the
NNTP server (along with a timestamp) in the `*nntp-log*'
buffer. This is useful if you are debugging a Gnus/NNTP connection
that doesn't seem to work.
nntp-open-connection-function
nntp-open-connection-function
parameter, Gnus will use that function to establish the connection.
Five pre-made functions are supplied. These functions can be grouped in
two categories: direct connection functions (three pre-made), and
indirect ones (two pre-made).
nntp-prepare-post-hook
Message-ID
header in the article and the news server provides the
recommended ID, it will be added to the article before running this
hook. It is useful to make Cancel-Lock
headers even if you
inhibit Gnus to add a Message-ID
header, you could say:
(add-hook 'nntp-prepare-post-hook 'canlock-insert-header) |
Note that not all servers support the recommended ID. This works for INN versions 2.3.0 and later, for instance.
nntp-read-timeout
6.2.1.1 Direct Functions Connecting directly to the server. 6.2.1.2 Indirect Functions Connecting indirectly to the server. 6.2.1.3 Common Variables Understood by several connection functions.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |