On 27/09/2011 1:52 PM, Mad Cow wrote:
In . com, Wolf K
writes
On 27/09/2011 8:29 AM, Mad Cow wrote:
[ Section: 1/1 File: zCistus01.jpg UUencoded by: Turnpike Integrated Version
5.02 S ]

begin 644 zCistus01.jpg
M_]C_X``02D9)1@`!`0$`2`!(``#_X1E017AI9@``34T`*@````@` #`$/``(`
M```&````G@$0``(````.````I`$2``,````!``$```$:``4`` ``!````L@$;
M``4````!````N@$H``,````!``(```$R``(````4````P@$[``(````!```
[etc]

As you can see, your image doesn't open automatically in my news reader
(Thunderbird). The reason is that the the header shows the message as
encoded in mime, but the message body itself shows that it's uuencoded.
(These are both methods of encoding non-text files so they can be
transmitted as text files, because all mail/news traffic is in text
characters only.) Your news reader is Turnpike: it has placed incorrect
encoding data in the header, so Thunderbird "reads" the file as text
instead of as an image.

The header says "MIME-Version: 1.0" (same as yours) but that's in the
header of every message whether it has an attachment or not. Everything
I can see in the header makes sense and none of it refers to the
attachment. If you're seeing something I can't, paste it into a reply:
there's probably nothing I can do but why not share the frustration?

Exactly, the header for the message says "mime", but the header for the
jpg file says "uuencoded by..." That mismatch between header and segment
is what causes the problem.

I'll file a bug report, maybe someone in the TB group will notice.

Have a good day,
wolf k.