Easy to misaddress an email address not in history abook

VERIFIED FIXED in M14

Status

P3
normal
VERIFIED FIXED
19 years ago
10 years ago

People

(Reporter: chriss, Assigned: bugzilla)

Tracking

Trunk
x86
Windows 98

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

19 years ago
Build ID: 2000010408

This should be fixed by beta. It's probably already on your radar, but I'm
filing just in case it isn't. This is partially a UI bug and partially features
not being fully implemented.

If I type a name of someone who isn't in my history address book and hit send, I
get no indication that the mail message doesn't have a proper address.

For example:
1) In compose window type "Eric Krock" (assuming Erick Krock isn't in your abook)
2) Notice that after hitting return you see: "Eric Krock@netscape.com"
3) If you hit send, the email goes to eric@netscape.com and krock@netscape.com

This is very easy to miss and results in misaddressed email.

There needs to be some better indication that the email address was not found in
the abook. The minimum case would be to place the first and last names on their
own lines. Better would be to tell the user that then name was not found in the
abook (or directory), etc.

Updated

19 years ago
QA Contact: lchiang → esther

Updated

19 years ago
Assignee: phil → ducarroz

Updated

19 years ago
Target Milestone: M14

Comment 1

19 years ago
Reassign to ducarroz. I think the beta stopper is to turn:

  foo bar

into

  foo@defaultdomain.com
  bar@defaultdomain.com

on separate lines, as chriss suggests. Further autocomplete hints (like putting
red text after "foo bar") will have to wait until autocomplete is fully implemented.
(Reporter)

Comment 2

19 years ago
I concur with Phil. Marking this beta1
Keywords: beta1

Comment 3

19 years ago
Putting on PDT+ radar for beta1.
Whiteboard: [PDT+]
(Assignee)

Comment 4

19 years ago
I have a fix. Now if we don't find a match, I am extracting all the potential 
addresses from the search string and add to them if necessary a domain. However, 
in case of several addresses, The UI we show them on the same line with a comma 
separator. I am not creating new rows, we have already enough problem with the 
addressing widget.

example:
John Wayne@somewhere.com    --> John@<domain>, Wayne@somewhere.com
"John Wayne"@somewhere.com  --> "John Wayne"@somewhere.com
John, Wayne                 --> John@<domain>, Wayne@<domain>

Status: NEW → ASSIGNED
Whiteboard: [PDT+] → [PDT+]Fix in hand, waiting for review
(Assignee)

Comment 5

19 years ago
Fixed and checked in
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
Whiteboard: [PDT+]Fix in hand, waiting for review

Comment 6

19 years ago
Using trunk build 2000-03-30-09 on win98 -08 on linux and mac this is fixed per 
example of fix.   Verified.
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.