I'm surprised that the discussion of images showing up as "ASCII" in web-messaging is
centering around IMail Server without apparent consideration for either
a) the encoding used in the sent attachment or
b) the browser type and version used by the client.
For example, testing shows that Netscape Navigator versions 4.06 and 4.08 cannot
interpret Uuencoded images, but renders them, instead as "garbage" - a jumbled ASCII
equivalent. Internet Explorer since version 4.0 is able to display Uuencoded images
correctly. Both platforms display MIME encoded images properly.
Have these two factors, brower-type and attachment encoding, been eliminated
as possible culprits?
Michael
> ----------------------------------------------------------------------
>
> From: "Mike Varre" <[EMAIL PROTECTED]>
> Subject: [IMail Forum] Damn images as ASCII
> Date: Wed, 28 Feb 2001 09:34:06 -0500
>
> Is anyone else sick of Ipswitch telling them that they dont know why some
> people have images show up as ASCII in web messaging? Im tired of
> it. I have
> paid almost $2000 for an email solution that does not send images
> correctly.
> What am I suppose to tell my clients when they complain about this? "Im
> sorry sir, I bought an inferior product?" I cant say that, I don't even
> fully believe that is true. Many things about this product are
> great. It is
> the few bugs and bad things about it that make it bad. And what makes it
> worse is that it takes so long for them to get fixed.
>
>
> Regards,
>
> Michael Varre
> Project Engineer
> goChatPlus
> ----------------------------------------------------------------------
>W�±ëâ²+a¶Úÿ 0��0�×!r�¿²êi¢»�¨¥�x%�Ël�Ù¥¶�Þ騽ç_®��+%�Ë@�
Ü�+Þ¡ûa�Éb²Ø¬jö¢�¦åy«a¶Úÿ 0�¨¥j·!�÷�¢oâ�¨¥~�î��%�Ëb¦Ì"µÈ\¢o
