Closed Bug 130681 Opened 22 years ago Closed 14 years ago

Moz should detect that no Account is availible and start the Account Wizard

Categories

(SeaMonkey :: MailNews: Account Configuration, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: poti, Unassigned)

Details

i had an account in mozilla mail. also for sending mail. 

now i wanted mozilla to send mails through my external (windowsdefault) client.

i deleted all the accounts. cleared the "outgoing server/server name"

does:
clicking on a mailadress shows an error "an error occured while creating a
message compose window. please try again" (what does not help)

should (in my eyes):
fire up the external mail client.
that Mozilla doesn't use an external Mail client is bug 11459

marking new for the error message. Mozilla should detect that no Account is 
availible and start the Account Manager...
Status: UNCONFIRMED → NEW
Ever confirmed: true
Changing summary from "default mail program is not started up after deleting all
accounts" to "Moz should detect that no Account is availible and start the
Account Wizard".
Summary: default mail program is not started up after deleting all accounts → Moz should detect that no Account is availible and start the Account Wizard
mass re-assign.
Assignee: racham → sspitzer
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
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: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.