Open Bug 411568 Opened 17 years ago Updated 2 years ago

Newsreader can't access newsgroup with @ sign

Categories

(MailNews Core :: Networking: NNTP, defect)

defect

Tracking

(Not tracked)

People

(Reporter: bj0nes, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11 Build Identifier: version 3.0a1pre (2008010903) I would like to read a newsgroup called @last. I can subscribe to it, but the headers won't download and I can't see anything. Noticed the problem first in 2.0.0.9; there it appears to download the headers but you still can't view any messages. All other groups on the server appear fine, it's only the one starting with @ that is a problem. The group appears fine in other readers. I have tried on W2K & XP, same result. Reproducible: Always Steps to Reproduce: 1. Subscribe to group with name starting in "@" 2. Try to Get Messages 3. It doesn't do anything Actual Results: Could not see any messages. Expected Results: Download headers.
Mailnews internally uses news: URIs to handle protocol states. As defined in RFC 1738, the presence of the `@' character should be used to differentiate between a news:<message-id> and a news:<group> format. We should be encoding this character as %40 internally.
Status: UNCONFIRMED → NEW
Component: Mail Window Front End → Networking: News
Ever confirmed: true
OS: Windows XP → All
Product: Thunderbird → Core
QA Contact: front-end → networking.news
Hardware: PC → All
Summary: Newsreader can't access newsgroup starting with @ sign ie. @last → Newsreader can't access newsgroup with @ sign
Product: Core → MailNews Core
Just to update - I have just upgraded to Thunderbird 3.0 and the problem still exists.
This bug still appears in Thunderbird 3.0.1.
There is generally no need to post "this bug still appears in XXX" unless there would be some reason to suggest that it wouldn't appear. In particular, once we have stable release versions (Thunderbird 3.0.x), most updates will just contain security fixes.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.