• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1961
  • Last Modified:

smtp;554 5.6.1 Body type not supported by Remote Host

ok, here goes.

Got one 2003 exchange server that handle SMTP domain X.com (not controlled by me)
Got one 2000 Exchange server that handle SMTP domain y.com.

User A got a SMTP adress: a@X.com that forward (E2003)) to a@Y.com.(E2000)

when someone try to mail a@X.com they will get an delivery notification failure:

From: postmaster@X.com
[mailto:postmaster@X.com]
Sent: den 14 mars 2006 13:59
Till: XXXXXX
Subject: Delivery Status Notification (Failure)


This is an automatically generated Delivery Status Notification.

Delivery to the following recipients failed.

       a@Y.com

Attachments:

Action: failed
Status: 5.6.1
Diagnostic-Code: smtp;554 5.6.1 Body type not supported by Remote Host


What to do ?
0
ulfhas4623
Asked:
ulfhas4623
  • 3
  • 3
1 Solution
 
SembeeCommented:
Any antivirus products installed on the Exchange 2000 server? Those can cause that sort of message.
I haven't seen it for a while, not with Exchange 200x, so you have to look elsewhere.

Does the remote server send email directly, or via another server, appliance etc?

Simon.
0
 
ulfhas4623Author Commented:
yes the exchange 2000 got trend installed
and the 2003 sends directly.
0
 
SembeeCommented:
What about the server that is doing the sending?
Unfortunately if it is outside of your control you may not be able to do anything about it.

Simon.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
ulfhas4623Author Commented:
Well I think the problem is on "my" exchange 2k server (smtp;554 5.6.1 Body type not supported by Remote Host), and in this case the remote host is the E2k server.
0
 
SembeeCommented:
I stick with my original diagnosis. I suspect the Antivirus. If you think that the problem is with your server then you will have to look at the AV configuration. If you cannot spot where there could be a problem, then the AV will have to be removed. There is no point in simply disabling it, as it will still have its hooks in Exchange. To test a problem with the AV you have to remove it.
Once removed, get the message sent again. If the error message continues then you know that the problem is outside of the AV.

Simon.
0
 
ulfhas4623Author Commented:
I will take a look @ the AV.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now