Closed Bug 114775 Opened 23 years ago Closed 23 years ago

Unable to send mail after deleting accounts in an activated profile

Categories

(SeaMonkey :: MailNews: Account Configuration, defect, P1)

PowerPC
Mac System 9.x
defect

Tracking

(Not tracked)

VERIFIED WORKSFORME
mozilla1.0

People

(Reporter: sfraser_bugs, Assigned: racham)

Details

(Whiteboard: needinfo)

I got into a state where I was unable to send mail from my netscape.com profile; on sending mail, I would get an error dialog about being unable to contact the SMTP server. I verified that my SMTP server settings in the Account Manager were correct. Sspitzer came down and helped me, and we found the following prefs in my prefs file: user_pref("mail.smtpserver.smtp1.redirector_type", "netscape"); for an account that should have just been using nsmail-1. The profile was created with a 6.2.1 build on Mac OS X, and I went through Activation (which created a netscape.net account) at the start. I later deleted this account.
This bug sounds very similar to Bugscape bug 9440 (http://bugscape.mcom.com/show_bug.cgi?id=9440). In this case I don't have to delete the activated account to experience the send problem. I am unable to send from my nsmail-1 account at anytime. If you think this is a duplicate then I will close this bug since it should actually be in Bugscape(due to Activation issue).
I don't see in the bugscape bug mention of the "redirector_type" pref issue, but if it is there, then I'd agree this is a dup.
Bhuvan, if you think this is the same, can you mark this INVALID and Simon to the bugscape bug? Otherwise, nominating for nsbeta1.
Status: NEW → ASSIGNED
Keywords: nsbeta1
Keywords: nsbeta1nsbeta1+
Priority: -- → P1
Target Milestone: --- → mozilla0.9.9
Target Milestone: mozilla0.9.9 → mozilla1.0
The fix in here calls for clearing all prefs related to the webmail/(aol) account deleted and set any other prefs (like default SMTP server after deletion properly) required. If bugscape bug http://bugscape.mcom.com/show_bug.cgi?id=9440 is fixed, we wouldn't get into this state. Then, the cases we need to worry about will be the ones where user had made manual changes to the default settings and later deletes webmail account. Ninoschka, Can you try making webmail account a default account and it's smtp server as a default server and then delete that account. I think we may run into the problem. Can you check on this one. I will move this bug to bugscape.
Bugscape bug #9440 is already fixed. This would allow the user to enter a separate smtp server for their nsmail account when they have gone thru activation. Which means that they wont get into this situation where they have to use the webmail smtp server. Like bhuvan mentioned then, the cases we need to worry about will be the ones where user had made manual changes to the default settings and later deletes webmail account.
Mail News bug team needs to know: does "manual" mean hand-editing prefs.js file?
Whiteboard: needinfo
Trunk build 2002-03-22: WinMe, Mac 10.1.3 This appears to be working for me with the latest builds. "manual" in this case does not mean editing the prefs. It means going into Account Settings and changing the defaults. The following scenario is logged in Bugscape# 12794). - New profile - Add a Webmail account (smtp.netscape.net is the default) - Add an IMAP account (now nsmail-1 is the default) - In Account Settings, go to Outgoing SMTP Server panel, Advanced and change the default back to smtp.netscape.net. - Add a different IMAP account (i.e. nsmail-2) Actual Results: Problems sending from all accounts. I would suggest marking this bug as Worksforme.
Ninoschka, You meant bugscape bug 12795 (sending problems with accounts added after changing the webmail smtpserver to be the default via smtpServer list)..right ? Per various tests ran by Ninoschka, marking this as WorksForMe.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Correct, I meant bugscape# 12795, thanks. Marking Verified Worksforme.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.