Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

good emails in the badmail folder on the gateway server

Posted on 2009-04-02
4
362 Views
Last Modified: 2012-05-06
Hi,
I have windows 2000 domain environment, 2 exchange 2003 servers on 2003 boxes, 2 exchange 5.5 on 2000 boxes, one gateway server with GFI mailessential 14 on 2003 box, one domain name, exchange 5.5 about to be retired after last weekend migration from exchg 5.5 to 2k3.
All servers behind the asa 5540 FW, outbound email goes out directly from exchange 5.5 box to the firewall.

The problem is that a lot of good emails going to the badmail folder on the gateway with this error;

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

I got this error when I opened the *.bad file in notepad.

Can you please help me with this, it is been going on for a while and that was one of the reasons why we upgraded exchange.
0
Comment
Question by:Shando1971
  • 2
  • 2
4 Comments
 
LVL 13

Expert Comment

by:FearNoMore
ID: 24056879
Body type not supported?....
Hmm....I thik its a problem with 8 bit MIME
Have you tried this article?
http://support.microsoft.com/?id=262168
 
0
 

Author Comment

by:Shando1971
ID: 24059204
I saw that article last night, but I have the smtp on the gateway (no exchange there) which is 2003 machine, and the clients that this error message belongs to is on the new exchange server, I don't think that this article is applicable to my situation.
0
 
LVL 13

Accepted Solution

by:
FearNoMore earned 500 total points
ID: 24059420
You dont need to have Exchange on the gateway......the gateway is an SMTP relay box.....
and the problem occurs when the SMTP service advertises the 8 BIT MIME...thats what the article talk about.
3 years back when I had 5.5 in my environment...i too faced a similar issue....
This article is what helped me resolve my issue
However if you feel that this is not applicable to your environment then you could try calling MS to check what they have to say about it.
Either ways you are going to decommission Exchange 5.5 soon....so you wouldnt be facing this issue for long
 
0
 

Author Comment

by:Shando1971
ID: 24287459
problem resolved after upgrading to exchange 2003.
0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Find out what you should include to make the best professional email signature for your organization.
In-place Upgrading Dirsync to Azure AD Connect
In this video we show how to create a User Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Mailb…
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …

856 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question