Gnus development mailing list
 help / color / mirror / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: ding@gnus.org
Subject: Re: Posting to my university's nntp server hangs
Date: Fri, 07 Mar 2014 16:49:21 +0100	[thread overview]
Message-ID: <87txba2em6.fsf@gnu.org> (raw)
In-Reply-To: <87r46eauaz.fsf@gnu.org> (Tassilo Horn's message of "Fri, 07 Mar 2014 16:43:16 +0100")

Tassilo Horn <tsdh@gnu.org> writes:

>>> here's another info.  I think, I've had that problem once before and
>>> solved it by not using a secure connection to that server.  At least the
>>> comment in my ~/.gnus.el seems to indicate that.
>>> (add-to-list 'gnus-secondary-select-methods
>>>              '(nntp "Uni"
>>>                     (nntp-address "news.uni-koblenz.de")
>>>
>>>                     ;; TODO: Why the heck do I get those endless hangs when
>>>                     ;; sending away messages via this account with TLS or
>>>                     ;; SSL?!?
>>>
>>>                     ;; (nntp-open-connection-function nntp-open-tls-stream)
>>>                     ;; (nntp-port-number 563)
>>>                     ))
>>> Maybe now Gnus uses a TLS stream by default, and that's why I get the
>>> issue again?
>>
>> Sounds like the NNTP server in question does something weird when
>> you're using TLS.  Perhaps it's not flushing the output correctly or
>> something?
>
> Might be.  Then I'll contact our datacenter.  The Inn version they are
> using is pretty outdated anyway.

Ok, that really seems to be the case.  When I use

(add-to-list 'gnus-secondary-select-methods
	     '(nntp "Uni"
		    (nntp-address "news.uni-koblenz.de")
		    (nntp-open-connection-function nntp-open-plain-stream)
		    (nntp-port-number 119)))

as a select method ensuring that it won't upgrade to TLS, I can post
without issues.

Bye,
Tassilo



  reply	other threads:[~2014-03-07 15:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-05  9:41 Tassilo Horn
2014-03-05 14:02 ` Lars Ingebrigtsen
2014-03-05 14:12   ` Tassilo Horn
2014-03-05 17:06     ` Lars Ingebrigtsen
2014-03-05 18:16       ` Tassilo Horn
2014-03-05 18:25         ` Lars Ingebrigtsen
2014-03-06  7:37           ` Tassilo Horn
2014-03-06 12:19             ` Tassilo Horn
2014-03-06 12:56               ` Steinar Bang
2014-03-07  8:42                 ` Tassilo Horn
2014-03-07  9:30                   ` Steinar Bang
2014-03-07 10:19                     ` Tassilo Horn
2014-03-07 11:45                       ` Steinar Bang
2014-03-06 13:02               ` Eric S Fraga
2014-03-06 18:15                 ` Andreas Schwab
2014-03-07 10:32                   ` Eric S Fraga
2014-03-07 15:04               ` Lars Ingebrigtsen
2014-03-07 15:43                 ` Tassilo Horn
2014-03-07 15:49                   ` Tassilo Horn [this message]
2014-03-06 18:14             ` Andreas Schwab
2014-03-07 15:04             ` Lars Ingebrigtsen

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=87txba2em6.fsf@gnu.org \
    --to=tsdh@gnu.org \
    --cc=ding@gnus.org \
    --cc=larsi@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).