Open Bug 56669 Opened 24 years ago Updated 13 years ago

extend the account wizard / account manager to handle new incoming server types

Categories

(SeaMonkey :: MailNews: Account Configuration, defect)

defect
Not set
normal

Tracking

(Not tracked)

People

(Reporter: sspitzer, Unassigned)

References

Details

(Whiteboard: [Halloween2011Bug])

now that we have movemail, (and hopefully one day exchange and other stuff) we need to make it so other incoming server types can plug into the account wizard and account manager UI. from bug #11049, alecf wrote: As for getting the front end correct, we need to start using categories to represent the server types. Then, we can populate the frontend (the wizard) with a list of server types. My suggestion is to reflect it into RDF and then construct the combo box with a <template> - This will also allow us (at some point) to add the same combo box to change the server type in the account manager.
*** Bug 27853 has been marked as a duplicate of this bug. ***
more bugs to racham.
Assignee: sspitzer → racham
QA Contact: esther → nbaca
Depends on: 11049
Suggest Platform=ALL, OS=Unix (we don't have the latter => OS=All ?)
Linux is what we use for *nix, and unless you can put forth a serious case that non intel is more affected than intel please leave PC alone.
Before there was Linux (x86) all Unix machines were BIG-ENDIAN (m68k, SPARC and so on...). Only Linux is LITTLE-ENDIAN. And "Linux" (for BugZilla OS) is not-so-good because it runs on both LITTLE-ENDIAN and BIG-ENDIAN machines, endian-depending bugs may cause problems (like "bug only occurs on Linux big endian" and QA verifies on Linux little endian... bum !!).
You people are insane. Debate this on IRC or something.
OS: Linux → All
Hardware: PC → All
please excuse my comments, this bug is clearly All/All, i somehow missed that in reading the comments.
After reading all comments of this bug again... I agree... I am insane... sort of... ;-( Sorry !!!
When will this be implemented ? This is more or less the last "blocker" which prevents us from using the Zilla... ;-((
the wizard may not be extensible yet, account manager is, see http://bugzilla.mozilla.org/show_bug.cgi?id=107068 someone could add a movemail extension, to get some UI in account manager.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.9
Target Milestone: mozilla0.9.9 → Future
Assignee: racham → pkw
Status: ASSIGNED → NEW
This was fixed (for movemail at least) in Bug 107833 and Bug 212804.
Assignee: pkw → nobody
Product: Browser → Seamonkey
Assignee: nobody → mail
QA Contact: nbaca
Priority: P3 → --
Target Milestone: Future → ---
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
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
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
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
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
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
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
Ever confirmed: true
Status: RESOLVED → UNCONFIRMED
Ever confirmed: false
Resolution: EXPIRED → ---
Whiteboard: [Halloween2011Bug]
Still valid.
Status: UNCONFIRMED → NEW
Ever confirmed: true
You need to log in before you can comment on or make changes to this bug.