Closed Bug 361962 Opened 18 years ago Closed 14 years ago

email to <user> instead of <user@host> cannot be sent

Categories

(MailNews Core :: Composition, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 312818

People

(Reporter: sparr0, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1) Gecko/20060601 Firefox/2.0 (Ubuntu-edgy)
Build Identifier: Thunderbird version 1.5.0.8 (20061115)

thunderbird will not let me send an email to an email address without a hostname, it produces an error dialog when i try ("foo is not a valid email address because it is not of the form user@host.  You must correct it before sending the e-mail.").  also, when i try to leave the address field with just a name in it by hitting enter or tab, or clicking elsewhere, autocomplete is forced if it is available, a seperate but directly related bug that might not deserve its own bug report.

Reproducible: Always

Steps to Reproduce:
1. To: foo
2. Send


Actual Results:  
error dialog

Expected Results:  
email sent to 'foo'
OS: Linux → All
Hardware: PC → All
Version: unspecified → 1.5
(In reply to comment #0)
> thunderbird will not let me send an email to an email address without a
> hostname, it produces an error dialog when i try ("foo is not a valid email
> address because it is not of the form user@host.  You must correct it before
> sending the e-mail.").  

True.  Seamonkey does the same thing.  See bug 312818; this may be a dupe, but it's hard to tell because that bug is full of differing reports.


> also, when i try to leave the address field with just a
> name in it by hitting enter or tab, or clicking elsewhere, autocomplete is
> forced if it is available, a seperate but directly related bug that might not
> deserve its own bug report.

Does the autocompletion not solve the first part of the problem?

You can turn off autocompletion entirely; you can also turn off only the add-domain part of autocomplete by tweaking either:
  mail.identity.default.autocompleteToMyDomain  (should default to False)
or
  mail.identity._idX_.autocompleteToMyDomain
to change it for a particular identity.  You'll have to poke around to figure out which _idX_ value corresponds to which identity, assuming you have several.
Component: Message Compose Window → MailNews: Composition
Product: Thunderbird → Core
Version: 1.5 → Trunk
Assignee: mscott → nobody
QA Contact: message-compose → composition
Thanks for the tips for disabling autocompletion, but that was mostly a side issue.  No, autocompletion doesnt 'solve' the first part of the problem.  I want to use email addresses with no domain, not have a domain added to them.
Product: Core → MailNews Core
Clarence, under what circumstances don't you need the domain name (intranet?), and what problems does it cause if it autocompletes?

bienevenu, "I want to use email addresses with no domain, not have a domain added to them."
Severity: minor → enhancement
Is it the case that autocompleting to your/a domain won't do the right thing? I understand on some intranets the domain name is not required, but is it specifically forbidden?

We have to balance this use case with the 99% case, where the user has made a mistake by not having a domain. Perhaps we could make it a warning instead of forbidding it...
It has been a while, so I am working from memory...  I believe that, at the time, I was working in an environment where emails to "foo" vs "foo@bar.com" were handled differently by the spam filter (in various combinations with other factors, such as internal or external connection, smtp authentication, etc).  I think that a warning would be the best course, possibly with some wording that "user" it is likely to send to "user@mail_server_you_are_using".
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.