Wednesday, April 18, 2007

500 Non RFC-Compliant responses received; there was a SMTP communication problem with the recipient's email server.


Error: 500 Non RFC-Compliant responses received; there was a SMTP communication problem with the recipient's email server. Please contact your system administrator. <chapbr2.chapredcross.org #5.5.0 SMTP; 500 Non RFC-compliant response received>


Cause: Client copied and paste several SMTP addresses into outlook. These SMTP addresses are taken from access database, or some other database application such as Microsoft word, excel, or Client has local distribution list created on his or her outlook.

Exchange is %percent RFC compliant product.

When Client is copying and pasting SMTP addresses into outlook, outlook application seems to be putting extra space, between multiple E-mail addresses, therefore mail is bouncing.

To prevent this being happen, space must be eliminated. Based on experience this error is most likely Occurred on Outlook 2002 platform.



Solution

This is the easiest, (work around) way to get away with this error, Break the E-mail messages into smaller groups and try it again. This will prevent the space issues within outlook (Smaller groups) and message will go trough

Permanent solution would be

• Create a DL (distribution List) on AD (active Directory)

• Create External Contacts for each SMTP address, A

• Add all the External Contacts to this DL as a member.

Making use Microsoft word is selected as a word editor and also

Within outlook by going

  • Tools
  • Options
  • E-mail options
  • Advance E-mail Options
  • Allow Comma as address separator
  • Make sure it is selected

Description: A user at our chapter received the following when sending an e-mail to her instructors. This is just two of the notifications, but they're all the same.


To check if the problem was related to her list size, she re-sent the e-mail with only 33 recipients. It still fails.


Your message did not reach some or all of the intended recipients.

Subject: Instructor Needed for Saturday 3/31 9:30-1:30pm. Please Respond! Sent: 3/30/2007 9:36 AM

The following recipient(s) could not be reached: username@wowway.com on 3/30/2007 9:36 AM


There was a SMTP communication problem with the recipient's email server. Please contact your system administrator. <chapbr2.chapredcross.org #5.5.0 SMTP; 500 Non RFC-compliant response received> username@wowway.com on 3/30/2007 9:36 AM There was a SMTP communication problem with the recipient's email server. Please contact your system administrator. <chapbr2.chapredcross.org #5.5.0 SMTP; 500 Non RFC-compliant response received>

some of the dedicated mail gateways might be causing this problem as well



3 comments:

Oz Ozugurlu said...

This has been brought up so many times where I work. All the cases are indication the DL( distribution List) all these people have are Local DL. They are private build DL list, and the way client is composing e-mail is
Putting one person on to “section”, and adding the Local DL into BCC, and clicking on send button on outlook 2002.
I have discovered, some of these SMTP addresses have illegal character in them, such as missing @ part, or not having FQDN.
Moat of the time, there is human being generated error in one of the SMTP addresses causing this problem.

oz

Anonymous said...

One would think that the message would be sent to the mail recipents that have valid addresses. and report back the ones that failed, rather than having the whole4 message fail. but 6 of one and 1/2 dox of another I guess.
Silly little problem that blows up to a big one when the information is not disseminated. Sigh!

Oz Ozugurlu said...

To be honest most of these type of problems went away after we changed the SMTP appliance we were using, can’t tell the name (-:, but I can certainly tell you what we used instead, IronPort one of the BEST mail appliance in the market and ROCK solid for sure, never failed me once over 3 years
--oz