Cyrus 2.2 NNTP problems after some idle time



14 years ago
14 years ago


(Reporter: nik, Assigned: mscott)


Firefox Tracking Flags

(Not tracked)




14 years ago
User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Build Identifier: Mozilla Thunderbird (1.0.2 20050317)

After some idle time, I try to post a message to the newsgroup on
Cyrus Imap 2.2 server (SSL and authentication are required).

Thunderbird complains about the error and shows the message box with
server message, which reads "NNTP server is ready OK+" or something
like that.

Reproducible: Always

Steps to Reproduce:
1.Setup Cyrus Imap 22 with SSL (authentication is required) NNTP on FreeBSD 5.4
2.Setup the account in Thunderbird
3.wait about 30 minutes 
4.try to post the message

Actual Results:  
The message is not posted, but copied to "Sent Items".
If I try to post it again shortly after that, it works.

Expected Results:  
Just to post the message at the first time.

I don't know, the standard theme. Russian and English dictionaries, weather 

I am having two IMAP accounts there, one of them is on the same server as NNTP.
The same software package (Cyrus IMAP 2.2) No problems with IMAP.

BTW, I am using Russian version of Thunderbird.
Also, I experienced the same problem in 1.0 version.

Comment 1

14 years ago
Just one more comment.

If before posting a message you explicitly request a connection with NNTP,
requesting all new messages to NNTP account for instance, that this
error does not emerge.
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:
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.
Last Resolved: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.