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.

I don't know what Turnpike's default settings are, but somewhere you
should be able to ensure that the encoding information in the header is
correct.

I can still open the pictures if I Save As the message on the desktop as
a *.jpg file, and open it from there, but it would be more convenient to
see the image when I open your post.

I like the back-lighting, BTW. ;-)

HTH
Wolf K.

In article , 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?

FWIW Thunderbird is the only newsreader that does this, all others
decode the files correctly, but that's no help to you.

I don't know what Turnpike's default settings are, but somewhere you
should be able to ensure that the encoding information in the header is
correct.

It doesn't allow MIME in news posts, only in mail!
I've found Windows 7 home edition easy to live with except that the
last-ever version of Turnpike's incompatible with it and this version's
too primitive. I've tried other newsreaders but they didn't meet my
needs.

I can still open the pictures if I Save As the message on the desktop as
a *.jpg file, and open it from there, but it would be more convenient to
see the image when I open your post.

I know. I get that with M$ Office files.

I like the back-lighting, BTW. ;-)

Thanks - though maybe I should post some rubbish so that you can just
killfile me!

HTH

I'll see if anyone's in the pub tonight who's old enough to remember how
Usenet works. Something might come of it.
--
Sue ]

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.

In article , Wolf K
writes

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.

Wolf, what does Thunderbird do that indicates it's expecting a MIME
attachment? Does it give any information other than failing to decode?

And am I right in assuming you can decode Joevan's and Pat's pictures?
--
Sue ]

On Thu, 29 Sep 2011 19:34:23 +0100, Mad Cow
wrote:

In article , Wolf K
writes

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.

Wolf, what does Thunderbird do that indicates it's expecting a MIME
attachment? Does it give any information other than failing to decode?

And am I right in assuming you can decode Joevan's and Pat's pictures?
I saved the Jpg to file and will now post it with Agent Forte. See if
any difference occurs.

In article , joevan
writes
I saved the Jpg to file and will now post it with Agent Forte. See if
any difference occurs.

Thanks Joevan, good idea. I've "kept" your post so I can think of a way
to compare the encoded sections. I want to know what's happening here!
--
Sue ]

On Sat, 1 Oct 2011 22:46:23 +0100, Mad Cow
wrote:

In article , joevan
writes
I saved the Jpg to file and will now post it with Agent Forte. See if
any difference occurs.

Thanks Joevan, good idea. I've "kept" your post so I can think of a way
to compare the encoded sections. I want to know what's happening here!
So pleased to be of help.

On 29/09/2011 4:01 PM, joevan wrote:

Opened properly in Tbird, and also showed as an attachment in the status
bar.

Wolf K.

On 29/09/2011 2:34 PM, Mad Cow wrote:
In g.com, Wolf K
writes

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.

Wolf, what does Thunderbird do that indicates it's expecting a MIME
attachment? Does it give any information other than failing to decode?

And am I right in assuming you can decode Joevan's and Pat's pictures?

It just fails to decode. Joevan's and Pat's pictures decode correctly. I
see an image in the message pane, and also as an attachment (the file
name displays in the attachment bar). In this case, your pictures did
not show as attachments. Tbird obviously believes the message header
(which identifies the encoding as mime), and not the file header (which
identifies it as uuencoded). So it doesn't even try to decode the image
file.

Don't worry about it, Sue, I'm quite willing to do the Save As then Open
thing.

TBird cannot combine multi-part files, which is occasionally an issue.
It's also unreliable when decoding yEnc encoded messages, which doesn't
bother me.

Have a good day,
Wolf K.

On Thu, 29 Sep 2011 17:17:53 -0400, Wolf K
wrote:

On 29/09/2011 2:34 PM, Mad Cow wrote:
In g.com, Wolf K
writes

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.

Wolf, what does Thunderbird do that indicates it's expecting a MIME
attachment? Does it give any information other than failing to decode?

And am I right in assuming you can decode Joevan's and Pat's pictures?

It just fails to decode. Joevan's and Pat's pictures decode correctly. I
see an image in the message pane, and also as an attachment (the file
name displays in the attachment bar). In this case, your pictures did
not show as attachments. Tbird obviously believes the message header
(which identifies the encoding as mime), and not the file header (which
identifies it as uuencoded). So it doesn't even try to decode the image
file.

Don't worry about it, Sue, I'm quite willing to do the Save As then Open
thing.

TBird cannot combine multi-part files, which is occasionally an issue.
It's also unreliable when decoding yEnc encoded messages, which doesn't
bother me.

Have a good day,
Wolf K.
Agent is "the" newsreader.

On Tue, 27 Sep 2011 09:42:57 -0400, Wolf K wrote:

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.

My newsreader is Pan and it displayed the picture just fine.
--

Travis in Shoreline Washington

On 02/10/2011 1:11 AM, Travis wrote:
On Tue, 27 Sep 2011 09:42:57 -0400, Wolf K wrote:

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). [...]

My newsreader is Pan and it displayed the picture just fine.

I've filed a bug-report with Thunderbird. It does in fact use only
message header information for decoding. That is, it expects the
standard message structure. Putting encoding data within the message
body is a no-no, but it seems Turnpike does this. If there are enough
"malformed" messages out there, the bug will be fixed.

Have a good day.

Wolf K.

In article , Wolf K
writes
On 02/10/2011 1:11 AM, Travis wrote:
On Tue, 27 Sep 2011 09:42:57 -0400, Wolf K wrote:

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). [...]

My newsreader is Pan and it displayed the picture just fine.

I've filed a bug-report with Thunderbird. It does in fact use only
message header information for decoding. That is, it expects the
standard message structure. Putting encoding data within the message
body is a no-no, but it seems Turnpike does this. If there are enough
"malformed" messages out there, the bug will be fixed.


Interesting: my expert says nothing in the message header relates to
attachments. What matters is the blank line followed by 'begin 664
filename' (or 'begin 666 filename' if you have a Microsoft emanation)
and the end markers.
That means if you attach one UUencoded and one MIME encoded file to a
message they should both be decoded successfully.
I'd like to try that in an e-mail to Thunderbird since I can't try it in
news; I haven't time just now but will try to remember it when I return
home...

Happy snapping
--
Sue ]

On 03/10/2011 1:31 PM, Mad Cow wrote:
Interesting: my expert says nothing in the message header relates to
attachments. What matters is the blank line followed by 'begin 664
filename' (or 'begin 666 filename' if you have a Microsoft emanation)
and the end markers.

OK, I'll try to explain what's going on. Bewar with me. ;-)

In your message there are two lines:
"begin 644 zCistus01.jpg"

That's the file type, and it will be there whether the image is attached
or "in-line". But it is the file type, _not_ the encoding type. The
encoding applies to the message as a whole. (1)

Before that there's
"[ Section: 1/1 File: zCistus01.jpg UUencoded by: Turnpike Integrated
Version 5.02 S ]"

That refers to a message encoding method. It should be in the message
header, but there I find:

"mime-version: 1.0"

That refers to the encoding of the message as whole, attachments and
all. Since there is only one section (the jpg image) there's only one
line referring to the encoding method.

The problem is that Turnpike adds the "UUencoded" bit before that.
However, because the message header says it's mime-encoded, TB
reads/decodes the whole message as a mime-encoded message, and that's
why I see a jumble of random characters. It sees the bit about
UUencoding as part of the message body, and not as a directive to switch
decoding methods. Turnpike should _not_ refer to one encoding method in
the message header, and another one within the message body. That's very
bad manners. Really. ;-)

The problem is more complicated by the fact that in the message as sent,
the image is actually not an attachment. It's "in line". Attachments
follow the message body. Um, that's why they are called "attachments", I
guess. ;-)

By contrast: In a message I sent with an attachment, the message header
says:
mime-version:1.0

It also says, lower down:
content-type:multipart/mixed; boundary="------------080503000101000907090103

This warns the receiving news-reader that there are several parts to the
message, in different file formats, and that it will have to use
different methods to display the different parts. There is no such line
in your message, which by default means "there is only one type of
content in this message", and by default, that is always taken to be
plain text. So you see, TB just did as it was told by the instructions
that Turnpike placed in your post: it converted every chunk of 8 bits
into a text character, did not look for a boundary between data-types,
and did not look for "begin 644 zCistus01.jpg".

Obviously, other news readers can deal with mixed decoding instructions,
and decoding instructions elsewhere than in the header. TB cannot.
That's why I filed a bug-report.

And that I think, is about as clearly as I can explain the problem(s).

;-)

Wolf K.

(1) What confuses is that an internet message must be encoded before it
is sent, regardless of what types of files it contains. Displaying an
internet message takes three steps: first, decode it into the original
data; second, determine the file type(s); third, deal with each file
type as needed for display.

The reason mime and UUencode (and a few others) are used to encode
messages before they are sent is history. If you really want on know,
Wikipedia will tell you. ;-)

WK.