402939 - Incomplete processing of ISP error messages

Status: RESOLVED DUPLICATE of bug 197134

(Thunderbird :: General, defect)

Description

[Peter]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8.1.9) Gecko/20071025 Firefox/2.0.0.9
Build Identifier: 2.0.0.6 (20070728)

I was trying to send a message to a number of addees.  I 
received the following error message from the:

"An error occurred while sending mail . The mail server 
responded 5.1.1: not our customer. 
Please verify that your email address is correct 
in your Mail Preferences and try again"

I'll first observe that the last sentence which I have seen
repeated in several error messages is wrong:  1.  There is nothing 
wrong with my email address.  2.  "Mail Preferences" is a term
I believe left over from Netscape.  The current terminology is 
Tools-Account Settings.

When this error message is generated it prevents the message from
being sent to anyone else in the list.  I finally had to send the 
message to each individual and in the process identified the  
addee that generated the error message which, of course, was 
last in the list.

I contacted the ISP and told them I didn't think much of their
methodology.  They responded with the observation that Thunderbird
is not very good at processing error signals and recommended
using their mail client or Outlook Express.  I smelled a fight.

However, I first used Outlook Express.  Sending out the same message
as before I received the following error message:

"The message could not be sent because one of the recipients
was rejected by the server. The rejected e-mail address was
'[e-mail]'. Subject 'test', Account: 'mail.comcast.net',
 Server: 'smtp.comcast.net', Protocol: SMTP, Server
Response: '551 not our customer', Port: 25, Secure(SSL):
No, Server Error: 551, Error Number: 0x800CCC79"

I don't know if OE requests more information or all the information
above is present and TB does not process it but the difference is 
striking.  With OE, I could have quickly identified the problem and
moved on.

I guess this is not a bug in the sense that it precludes s/w operation but it certainly prevents efficient operation.
 


Reproducible: Always

Steps to Reproduce:
1. send a message to a non-customer of comcast.net (my same ISP)
2.
3.
Actual Results:  
get an ambiguous error message

Expected Results:  
identify the non-customer and give an accurate error message