Closed
Bug 1765752
Opened 2 years ago
Closed 2 years ago
NNTP server hostname change causes infinite "would you like to subscribe" popups
Categories
(MailNews Core :: General, defect)
Tracking
(thunderbird_esr91 unaffected)
RESOLVED
FIXED
101 Branch
Tracking | Status | |
---|---|---|
thunderbird_esr91 | --- | unaffected |
People
(Reporter: manikulin, Assigned: rnons)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
Steps to reproduce:
- Create news account for news.mozilla.giganews.com
- Subscribe to mozilla.test
- Read some messages, add some tags
- In the account preferences change host name to news.mozilla.org
- Try to read more messages from the newsgroup
Actual results:
Thunderbird 101.0a1: severe troubles making account unusable
- Multiple popups "Would you like to subscribe to mozilla.test?" appears on each action
- After restart several "m.test" folders is shown for the account
Thunderbird 91: sudden lost of history
- State of messages (read, star, tags) are lost similar to the Bug #548966
Expected results:
Earlier received headers are preserved, new messages are fetched from the new host.
A several years old real life case: switch from news.gmane.org to news.gmane.io.
Updated•2 years ago
|
Summary: NNTP server change causes infinite "would you like to subscribe" popups → NNTP server hostname change causes infinite "would you like to subscribe" popups
Assignee | ||
Comment 1•2 years ago
|
||
Because the news url still contains the old hostname, match both hostname and realhostname when finding server.
Updated•2 years ago
|
Assignee: nobody → remotenonsense
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Assignee | ||
Updated•2 years ago
|
Pushed by mkmelin@iki.fi:
https://hg.mozilla.org/comm-central/rev/57b510bfb7db
Newsgroup should still work after changing hostname. r=mkmelin
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Updated•2 years ago
|
Target Milestone: --- → 101 Branch
Thank you, I have not try hard, but I do not see the problem any more in the scenario I faced it previous time.
You need to log in
before you can comment on or make changes to this bug.
Description
•