Go to the first, previous, next, last section, table of contents.


6.2.1.1 Direct Functions

These functions are called direct because they open a direct connection between your machine and the NNTP server. The behavior of these functions is also affected by commonly understood variables (see section 6.2.1.3 Common Variables).

nntp-open-network-stream
This is the default, and simply connects to some port or other on the remote system.
nntp-open-ssl-stream
Opens a connection to a server over a secure channel. To use this you must have OpenSSL (http://www.openssl.org) or SSLeay installed (ftp://ftp.psy.uq.oz.au/pub/Crypto/SSL, and you also need `ssl.el' (from the W3 distribution, for instance). You then define a server as follows:
;; Type `C-c C-c' after you've finished editing.
;;
;; "snews" is port 563 and is predefined in our /etc/services
;;
(nntp "snews.bar.com"
      (nntp-open-connection-function nntp-open-ssl-stream)
      (nntp-port-number "snews")
      (nntp-address "snews.bar.com"))
nntp-open-telnet-stream
Opens a connection to an NNTP server by simply `telnet''ing it. You might wonder why this function exists, since we have the default nntp-open-network-stream which would do the job. (One of) the reason(s) is that if you are behind a firewall but have direct connections to the outside world thanks to a command wrapper like runsocks, you can use it like this:
(nntp "socksified"
      (nntp-pre-command "runsocks")
      (nntp-open-connection-function nntp-open-telnet-stream)
      (nntp-address "the.news.server"))
With the default method, you would need to wrap your whole Emacs session, which is not a good idea.


Go to the first, previous, next, last section, table of contents.