4.2: Outbound email - message body missing

[nkendrick]

Hi,

I have pulled the contents of this message from the middle of another post of mine about email in general as it may be a bug/problem:

I can send emails from 4.2 to other Sugar users and they arrive fine, but if the same messages are viewed in Outlook 2000, 2002 and 2003 there is no message body - I can however see the entire message in Squirrelmail (a mailbox Web interface), but Squirrelmail implies there is an attachment to the message (which there is not) and if you click on the 'attachment' you get:

Body retrieval error. The reason for this is most probably that the message is malformed.
Command: FETCH 6160 BODY[2]
Response: OK
Message: Fetch completed.
FETCH line:

Anyone else seeing (or not seeing!) this? Encoding problem??

[reaj]

Hi,

I'm experiencing the same problem.

Sugar Open Source version 4.2.0.

-reaj

[jpenn]

I too am having the same problem.

When recipients of my emails view the mail, they can see the SIG only, but none of the body text. It seems this only happens when viewing the email through certain mail applications (showing fine through verizon web mail client, not showing fine in outlook or even mail2web web interface).

[therapyselect]

I have the same probelms too. When viewing the eMails in Thunderbird there is no content. We are using 4.2 Professional.

Is there any bug report for this? If not, in my opinion it's worth to create one.

[metamend]

We have the same issue as well - the subject line is there, but the body content is missing. When I view the archived email in Sugar, I can see the body content, but only in IE. In Firefox it is missing... we have several clients who have noticed this too. Any help here would be appreciated.

[metamend]

One of my staff had this to say about the missing body content issue:

What sugar is now doing is encoding a "plain text" e-mail in 8-bit with
the character set defined as iso-8859-1. Don't know why, but this is
what renders the "plain text" e-mail invisible to e-mail clients. Here
is a copy of the e-mail source from one of our own messages to a client.


> Content-Type: multipart/alternative;
> boundary="b1_5595389314a725a35167d4d1c93970a8"
>
>
> --b1_5595389314a725a35167d4d1c93970a8
> Content-Type: text/plain; charset = "iso-8859-1"
> Content-Transfer-Encoding: 8bit
>
> BODY CONTENT SNIPPED
>
> --b1_5595389314a725a35167d4d1c93970a8
> Content-Type: text/html; charset = "iso-8859-1"
> Content-Transfer-Encoding: 8bit
>
>
> --b1_5595389314a725a35167d4d1c93970a8--

I am using Thunderbird and it does not show the body either. you have
to view the message source to see the above.

[sugarchris]

Valid bug. I'll get it fixed for the next patch.

[kenlyle]

Thanks, Chris...and perhaps modify the pre-release test suite to trap these critters earlier?

[therapyselect]

We still have these problems in 4.2.0a. Any news?

[sugarchris]

Unfortunately, for those of you having these encoding problems, the "big" fix is going to be forthcoming still. The current plan is to get the collection of fixes ready for 4.5 which is stil months away.

The good news is that if you are willing to be a "beta" (my word, not Sugar's) tester for InboundEmail, I'm willing to put up newer code. The deal, of course, is that you confirm for me that the issue is addressed/still broken.

That work? I still have *a lot* of work to do to get this ready for testing, so it will be a while yet, but I promise to get something up here.