Closed Bug 129055 Opened 23 years ago Closed 13 years ago

[RFE] Allow change of server type (IMAP to POP)

Categories

(MailNews Core :: Account Manager, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 87948

People

(Reporter: a.f.3, Unassigned)

References

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.8+) Gecko/20020304 BuildID: I finally had to totally delete my imap e-mail account and reinstall to POP to be able to send without getting all kinds of errors. Being able to simple change the account to POP without delete/reinstall, like one can with netscape 4.x would have been a huge improvement Reproducible: Always Steps to Reproduce: 1. open an imap account 2. try to change it to a pop account 3. Actual Results: can't do it Expected Results: should be able to do it. I lost e-mail messages because of the bug
Related: bug 87948, which was duped to bug 14295. That bug was fixed, but the server type still cannot be changed (bug 14295 comment 97). Confirming -> Annount Manager
Assignee: mscott → racham
Severity: normal → enhancement
Component: Networking: IMAP → Account Manager
OS: Windows XP → All
QA Contact: huang → nbaca
Hardware: PC → All
Summary: IMAP doesn't work; account can be changed to POP → [RFE] Allow change of server type (IMAP to POP)
Status: UNCONFIRMED → NEW
Ever confirmed: true
mass re-assign.
Assignee: racham → sspitzer
*** Bug 240395 has been marked as a duplicate of this bug. ***
*** Bug 239161 has been marked as a duplicate of this bug. ***
*** Bug 247793 has been marked as a duplicate of this bug. ***
*** Bug 247793 has been marked as a duplicate of this bug. ***
Product: Browser → Seamonkey
Assignee: sspitzer → mail
QA Contact: nbaca
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
Status: NEW → UNCONFIRMED
tbird too would be nice also from pop->imap
This seems like a valid RFE for MailNews Core so I'm moving it there.
Assignee: mail → nobody
Status: UNCONFIRMED → NEW
Component: MailNews: Account Configuration → Account Manager
Ever confirmed: true
Product: SeaMonkey → MailNews Core
QA Contact: account-manager
(In reply to comment #8) > tbird too would be nice also from pop->imap Agreed! The problem seems to be there is no way in the UI to alter the protocol / mailserver type, once an account is created. This is aggravated by the way the automatic account creation dialog goes off and does.... something... and picks one of the possible options apparently at random (maybe it does some sensible checks, but there is no way to tell what it's doing). So, and if/when it picks something sub-optimal, there is no way to change it. That's a major usability bug!
I'd say this is a dupe of 87948, that the switching code should be universal to allow both directions. But maybe it is not that easy.
Depends on: 87948
So duping, please reopen if you find any difference.
Status: NEW → RESOLVED
Closed: 13 years ago
No longer depends on: 87948
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.