133500 - Mail rejected with smtp;554 5.6.1 Body type not supported by Remote Host

Status: RESOLVED INVALID

(MailNews Core :: Backend, defect)

Description

[Peter B. West]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9+) Gecko/20020325
BuildID:    2002032508

At some mail addresses, mail is bounced with the following Diagnostic-code:
smtp;554 5.6.1 Body type not supported by Remote Host


Reproducible: Sometimes
Steps to Reproduce:
1.Send mail to a rejecting address
2.
3.

Actual Results:  Delivery Status notification (Failure) is returned from my ISP.
 It includes the diagnostic message noted above

Expected Results:  Mail is delivered

So far, I have found this problem with only two addresses.  To one address, I
have tried sending the same message (and attachment) using Netscape 4.75,
successfully.

Massage failures have occurred with simple messages devoid of attachments.

Comment 1

[Peter B. West]

I am seeing this bug more and more, and it is rendering mozilla mail useless for
me.  Mail with attachments is bouncing back from servers all over the place.  I
need to know:
1) Is it a mozilla bug?
  If so, I can find another mail agent until it is fixed.
2) Is this a problem with the configuration of opposing firewalls?
   If so, for each likely culprit, I need to know what I can tell the sysadm to
get the problem fixed.

Can I have some feedback on this one please.

Comment 2

[Alistair Y. Lewars]

Reporter:

Are you still experiencing this bug with the latest build?  This bug was
reported in March, so it might have been fixed.  If you are still experiencing
it, do you experience the same with any other email clients?  Also, please
submit an attachment of the email (email attachments also) that triggers this
bug to this bug report so that we can try it out for ourselves.  Thanks.

Comment 3

[Peter B. West]

My apologies for not clearing this bug earlier.  The problem was simple: I was
using 8-bit characters (iso-8859-15) in some of my messages, and my mail setting
was to send 8-bit characters "as is."  I had not run into the problem before,
because receiving systems, obviously, were able to handle 8-bit.

Comment 4

[Pedro Madeira]

*** Bug 194060 has been marked as a duplicate of this bug. ***

Comment 5

[Pedro Madeira]

I have news regarding this bug.
It seems that the windows mozilla client (please refer to bug 194060 for more
details) sent an image with character coding iso8859-1 and the problem was
reproduced.

Do you think the option use "quoted printable" MIME encoding when sending
regular messages that use an 8-bit character set has anything to do about it?

Perhaps this option has to be on by default?

Any comments extremely apreciated

Comment 6

[Peter B. West]

Pedro,
I'm not sure of your situation, but I assume that the message contained an image
as attachment.  In that case, how was the image encoded?  Was it already in Mime
format?  If it was encoded into 8-bit bytes, then the transmission will fail if
sent as-is to a host that only supports 7-bit.