Closed Bug 243002 Opened 20 years ago Closed 20 years ago

error message on sending eMail doesn't show wrong adress - I can't send my eMail without removing broken adress

Categories

(MailNews Core :: Networking: SMTP, defect)

x86
Windows 98
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 197134

People

(Reporter: eMailBugzilla.10.gaensler, Assigned: sspitzer)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Win98; de-AT; rv:1.7b) Gecko/20040316
Build Identifier: Mozilla/5.0 (Windows; U; Win98; de-AT; rv:1.7b) Gecko/20040316

I am using GMX eMail with Mozilla eMail application and if I want to send an
eMail to a domain which doesn't exist, an error-message appears that says:
"5.1.2 {...} Cannot resolve your domain"

Now I have to look at each email-adress to find out which one is the wrong.

Reproducible: Always
Steps to Reproduce:
1. create an account at gmx.com (or use an existing) and configure Mozilla eMail
that you can use it to send emails
2. write a new email to "somebody@salzburggr.at" and try to send it


Actual Results:  
I got an error message which says that one of my recipient email adresses is
wrong (see details above) and my email can not be sendt until I remove this
wrong adress (which I have to find out - and this takes a lot of time with 200
or more recipients)

Expected Results:  
1. send my email  IMPORTANT!    (including the wrong adresses)
2. and write myself an email which names the wrong adresses (that I could remove
them the next time I want to use this set of adresses)

couldn't try to use an other email-service. got this error with gmx.de
Summary: error message on sending eMail doesn't show wrong eMail - I can't send my eMail without removing broken adress → error message on sending eMail doesn't show wrong adress - I can't send my eMail without removing broken adress

*** This bug has been marked as a duplicate of 197134 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.