Fix nntp connection problems with the Typhoon server

* nntp.el (nntp-open-connection): Use HELP as the capability command
instead of CAPABILITY because Typhoon v2.2.2.503 chokes completely on
unknown commands.  And CAPABILITY is an unknown command (bug#12763).

diff --git a/lisp/ChangeLog b/lisp/ChangeLog
index 9ff2c02..463be0d 100644 (file)
--- a/lisp/ChangeLog
+++ b/lisp/ChangeLog
@@ -1,3 +1,9 @@
+2012-12-27  Lars Ingebrigtsen  <larsi@gnus.org>
+
+       * nntp.el (nntp-open-connection): Use HELP as the capability command
+       instead of CAPABILITY because Typhoon v2.2.2.503 chokes completely on
+       unknown commands.  And CAPABILITY is an unknown command (bug#12763).
+
 2012-12-27  Wolfgang Jenkner  <wjenkner@inode.at>
 
        * gnus-spec.el (gnus-face-face-function): Don't use nil as no-op face

diff --git a/lisp/nntp.el b/lisp/nntp.el
index be5d1e6..e131c51 100644 (file)
--- a/lisp/nntp.el
+++ b/lisp/nntp.el
@@ -1282,7 +1282,7 @@ If SEND-IF-FORCE, only send authinfo to the server if the
                     "nntpd" pbuffer nntp-address nntp-port-number
                     :type (cadr (assoc nntp-open-connection-function map))
                     :end-of-command "^\\([2345]\\|[.]\\).*\n"
-                    :capability-command "CAPABILITIES\r\n"
+                    :capability-command "HELP\r\n"
                     :success "^3"
                     :starttls-function
                     (lambda (capabilities)