Re: 554 5.6.1 Body type not supported by Remote Host
- From: "Rich Matheisen [MVP]" <richnews@xxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 01 Jun 2006 20:29:20 -0400
EmailAdmin <EmailAdmin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Just to clarify, I don't have an ISP but my Exchange servers route outbound
e-mails to my W2K3 ISA Server with IIS SMTP enabled on the DMZ. Questions...
Is it better to turn off the 8bitmime on the W2K3 ISA server or the one
Exchange server that is doing the SMTP relay for my non-Exchange applications
(e.g., apps on UNIX server)?
Turn it off on the Exchange servers. The ISA server shouldn't be
acting as a SMTP server, just a proxy.
Or if I have to change Exchange, do I have to turn off 8bitmime on all the
Exchange servers?
No, but it's usually better, for a consistency POV, to do so.
When you say that following (see below), if I turn off the 8bitmime on
either the Exchange SMTP server or the W2K3 ISA server, what happens to the
8bitmime e-mail that is sent from the application?
Nothing. Your SMTP servers don't advertise 8bitmime so the sending
application shouldn't be sending messages in that format. That's the
purpose of advertising the capabilities in ESMTP keywords.
Does it fail to deliver
or does it get converted?
Neither should happen. The message should be sent in 7-bit MIME
format.
I guess what I'm asking is what happens when an
8bitmime e-mail hits a server that doesn't advertise 8bitmime?
You get the 5.6.1 error that you were asking about. :)
"If you don't accept messages in that format the sending application
won;t deliver them that way. Then, when you encounter a host that
can't handle 8bitmime it won't matter."
One other thing, our developer changed the UNIX program to send it as 7bit,
but it didn't go thru to the recipient. Any ideas why?
What would happen if the SMTP relay server (Exchange, in this case,
but feel free to substitute sendmail, postfix, qmail, etc. as the MTA)
only accepted SMTP and not ESMTP? How would the message be sent in
that situation?
------Boundary.20050106102315
Content-Type: text/plain; name="message.txt"; charset=US-ASCII
Content-Disposition: inline; filename="message.txt"
Content-Transfer-Encoding: 7bit
Well, changing the encoding to 7bit without ensuring that the data
contains only 7-bit data won't work. :)
If you have a need to send 8-bit data then play it safe and use base64
encoding.
------Boundary.20050106102315
Content-Type: application/pdf; name="BillTo50131000.pdf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="BillTo50131000.pdf"
------Boundary.20050106102315
I doubt that a PDF file contains only 7-bit data.
--
Rich Matheisen
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
Don't send mail to this address mailto:h.pott@xxxxxxxxxxxxx
Or to these, either: mailto:h.pott@xxxxxxxxxxxxxxx mailto:melvin.mcphucknuckle@xxxxxxxxxxxxx mailto:melvin.mcphucknuckle@xxxxxxxxxxxxxxx
.
- Follow-Ups:
- Re: 554 5.6.1 Body type not supported by Remote Host
- From: EmailAdmin
- Re: 554 5.6.1 Body type not supported by Remote Host
- References:
- Re: 554 5.6.1 Body type not supported by Remote Host
- From: Rich Matheisen [MVP]
- Re: 554 5.6.1 Body type not supported by Remote Host
- Prev by Date: Re: Customize the GAL
- Next by Date: Re: Authenticated Users Can't Relay SMTP
- Previous by thread: Re: 554 5.6.1 Body type not supported by Remote Host
- Next by thread: Re: 554 5.6.1 Body type not supported by Remote Host
- Index(es):
Relevant Pages
|
