Closed Bug 102642 Opened 23 years ago Closed 23 years ago

SMAPI can't distinguish mail accounts with same user name

Categories

(MailNews Core :: Simple MAPI, defect, P3)

x86
Windows 2000
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: yulian, Assigned: rdayal)

References

Details

With same user name but different account name and password, SMAPI can not
distinguish them and always brings up new message window with first created mail
account.

Repro steps:

1. Set up multiple mail accounts (for example, abc@netscape.com and
abc@aol.com)in Mozilla test profile.
2. Launch Mozilla and select the test profile
3. In Prefs, select "Use Mozilla Mail as the default mai l application"
4. With Mozilla running, launch MSWord and attempt to send an email
5. In Mozilla Mail dialog, enter username and password for abc@aol.com which was
created later than abc@netscape.com

Actual result: new message window is launched with abc@netscape.com

Expected result: new message window is launched with abc@aol.com
Priority: -- → P3
Keywords: nsbranch-
Mark as depedent to meta bug 103807
Blocks: 103807
This bug may be irrelevant since the logon dialog is no longer launched. 
Yulian, are you able to select the proper sender from the drop down in the
Compose window?
with 10-11 0.9.4 Wins build to test,
yes, the proper sender can be selected from the drop down in the Compose window.


Blocks: 107067
Keywords: nsbranch-
No dialog is displayed at the time of Login to enter user name. Also proper user
mail account can be selected from the drop down in Compose Wnd thus allowing to
distinguish different mail accounts for the same username / profile. Marking as
Fixed.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Trix: Pls add your verify. Thx.
verified on mozilla & netscape trunk builds 2002022703. A profile containing
multiple email accounts for SMAPI allows the user to select any email account in
the compose window.
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.