118945 - Change to news server won't stick

Status: RESOLVED WORKSFORME

(SeaMonkey :: MailNews: Account Configuration, defect)

Description

[Håkan Waara]

If you go into a news account, and change the server URI, it won't stick
immediately -- as it should. Hopefully, it works after a restart at least (I
haven't tried).

Steps to reproduce:

1. Open Account Settings and go to Server Settings for a news account.
2. Edit the news server to something invalid, that you know won't work.
3. Now click OK and go to the news account in the folderpane, and download
messages, refresh your subscribe list etc. -- it does everything using the old URI.

I think this is quite major. AFAIK, the whole point of the ability to edit the
news server 'live' would be that it would stick. Cavin, can you help here?

Comment 1

[Erland Lewin]

See my bug #119558 describing a similar problem with a mail account under Linux.

Comment 2

[Cavin Song]

HHåkan, can you tell me what build you were runnning on when you had this 
problem?  This could be a dup of bug 113590 but I'm not sure.  I just tried it 
(changing from 'news.mozilla.org' to 'news.mozilla.org123') and it correctly 
reported that it could not connect to server 'news.mozilla.org123' and no news 
were downloaded.

Comment 3

[(not reading, please use [e-mail] instead)]

mass re-assign.

Comment 4

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 5

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420

Comment 6

[Karsten Düsterloh]

WFM by now.