273523 - Newsgroup names with colons lost after stop and restart of thunderbird

Status: RESOLVED INCOMPLETE

(Thunderbird :: General, defect)

Description

[Chris Cranford]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

If I subscribe to a newsgroup that contains a ':' (colon) in its name, the
newsgroup works fine until Thunderbird is stopped and restarted.  Once it is
restarted, the newsgroup name is truncated at the ':' (colon) character and can
no longer be found on the newsgroup server because the names do not match.

Thunderbird notates that the newsgroup cannot be found and that I can
unsubscribe from it.  The only way to resolve it is to unsubscribe and
resubscribe to the newsgroup again but this must be done upon startup of
Thunderbird each time.

Reproducible: Always
Steps to Reproduce:
1. Connect to newsgroup server and subscribe to newsgroup with ':' (colon) in name
2. Shutdown thunderbird
3. Restart thunderbird and navigate to news server newsgroup with ':'
4. You'll notice name is truncated and that thunderbird indicates it cannot find
   the newsgroup on the server.

Actual Results:  
Had to resubscribe to the newsgroup again

Expected Results:  
Never truncated the newsgroup name that contains a ':'.

Comment 1

[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 2

[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 3

[Chris Cranford]

(In reply to comment #0)

I noticed this bug was closed due to inactivity.  can anyone else confirm that this continues to be a problem?

Comment 4

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

(In reply to comment #3)
> I noticed this bug was closed due to inactivity.  can anyone else confirm that
> this continues to be a problem?

No one has confirmed, lack of information for >2 years, resolving incomplete.

Please comment if the issue still occurs in the latest supported Thunderbird 2.0.0.x or trunk nightlies.