253523 - nntp with inn2-ssl, reply post to news is successful but thunderbird hangs in compose window

Status: RESOLVED INCOMPLETE

(Thunderbird :: General, defect)

Description

[Romain DEGEZ]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040719 Firefox/0.9.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040719 Firefox/0.9.1

When replying to a post on a newsgroup located on a inn2-ssl news server.
(so we are using thunderbird news client with ssl :-), the compose window hang
when sending the reply.

In the case of a normal post, everything is fine.

The problem is the same with or without authentication.

It's working fine with thunderbird 0.6

Reproducible: Always
Steps to Reproduce:
1.Configure your news account to use ssl
2.post a message to a newsgroups
3.reply to this message

Actual Results:  
The window 'Sending Messages - Re: test' pop-up displaying :
Status: Posting message...
Progress: (0%, no progress ;-)
and the cancel button

I can cancel the window but the message isn't gone.

Expected Results:  
The reply should have been posted on the news server.

Package: mozilla-thunderbird
Priority: optional
Section: mail
Installed-Size: 32092
Maintainer: Alexander Sack <[e-mail]>
Architecture: i386
Version: 0.7.1-3

with

Package: mozilla-thunderbird-enigmail
Priority: optional
Section: mail
Installed-Size: 1028
Maintainer: Alexander Sack <[e-mail]>
Architecture: i386
Source: enigmail
Version: 2:0.84.2-2

Debian unstable 2.6.6-1-686

Comment 1

[Zer0halo]

This seems to be related to bug 247226 <a
href="http://bugzilla.mozilla.org/show_bug.cgi?id=247226">. However, in my
experience, TB times out most of the time (but not "all" the time) when making a
new post to a newsgroup over SSL, not just when replying to an existing post.
I'm using the 24-08-04 build and the problem remains (as well as it 0.7.3).

Please is it possible to fix? It makes TB unusable for those of us who have to
post to newsgroups over SSL (such as corporate newsgroups). Thanks!

Comment 2

[Stef Walter]

I experienced this problem as well. It seems the SSL implementation of INN
doesn't play well with NSS. If I setup connections (on the server side) to go
through stunnel instead it all works perfect.

Comment 3

[llanero]

Hi all!

This is still happening in TB 1.0.2. The version of inn2-ssl is 2.4.2. It
happens both with linux/windows TB.

Nate, can you explain how you use use stunnel with inetd to workaround the bug?

Thanks!

Comment 4

[llanero]

I'll reply myself:

nntps stream tcp nowait root /usr/sbin/stunnel stunnel -r localhost:nntp

This is, inn2 is running localy in daemon mode, we just forward traffic using an
encripted connection. Cert and key at /etc/ssl/certs/stunnel.pem (Debian Woody).

This way TB works OK!

Comment 5

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 6

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.

Comment 7

[Carl P. Corliss]

this is still an issue in the latest version of thunderbird (1.5.0.7). Is someone going to look into this ever?

Comment 8

[Wayne Mery (:wsmwk)]

according to comment 0, this is a regression - worked in TB 0.6 !
setting bug 247226 as possible blocker

bug 307531 and bug 345358 also document posting issues

Comment 9

[Wayne Mery (:wsmwk)]

was previously expired and now no response so closing incomplete.
Carlos, if you still see this in v2 please reopen the bug.

Comment 10

[Julien ÉLIE]

The bug is still present in Thunderbird v2 (and by the way also in SeaMonkey).
As I tell in bug 247226, is it possible to know what patch caused this regression?
Indeed, Thunderbird 0.6 is the last version which is working fine as for this
issue. In the release notes of Thunderbird 0.7, there is a bug fix for "a
potential hang when reading imap over SSL". Could that fix bring along the nntp
over SSL bug?

I believe it would be a good start to understand the problem and what is going
on.

Comment 11

[Julien ÉLIE]

It appeared to be a bug in INN (a news server).  Fixed in INN 2.4.5:

* Fixed the "alarm signal" around SSL_read in nnrpd: it allows a proper disconnection of news clients which were previously hanging when posting an article through a SSL connection. Moreover, the clienttimeout parameter now works on SSL connections. Thanks to Matija Nalis for the patch.

* SO_KEEPALIVE is now implemented for SSL TCP connections on systems which support it, allowing system detection and closing the dead TCP SSL connections automatically after system-specified time. Thanks to Matija Nalis for the patch.