Took these on our way out west, on our three week road trip. We
stopped at the rose garden first thing in the morning after checking
out from the hotel, when it wasn't so hot.

--
Al M_c_C_a_n_n
m a c 3 5 8 (at)-n e w s g u y-(dot) c o m

On 12/10/2010 18:27, Kilgore Trout wrote:

Took these on our way out west, on our three week road trip. We
stopped at the rose garden first thing in the morning after checking
out from the hotel, when it wasn't so hot.



This newsgroup reader is misbehaving, it's encoding the images as plain
text.

MicroPlanet-Gravity/3.0.4

HTH
wolf k.

On Tue, 12 Oct 2010 19:50:16 -0400, Wolf K wrote:

On 12/10/2010 18:27, Kilgore Trout wrote:

Took these on our way out west, on our three week road trip. We
stopped at the rose garden first thing in the morning after checking
out from the hotel, when it wasn't so hot.



This newsgroup reader is misbehaving, it's encoding the images as plain
text.

MicroPlanet-Gravity/3.0.4

HTH
wolf k.

odd, as I can see them all.

Karen

wrote in
:

On Tue, 12 Oct 2010 19:50:16 -0400, Wolf K
wrote:

On 12/10/2010 18:27, Kilgore Trout wrote:

Took these on our way out west, on our three week road trip. We
stopped at the rose garden first thing in the morning after checking
out from the hotel, when it wasn't so hot.



This newsgroup reader is misbehaving, it's encoding the images as plain
text.

MicroPlanet-Gravity/3.0.4

HTH
wolf k.

odd, as I can see them all.

Karen


coming through fine as photos for me as well..

On Wed, 13 Oct 2010 09:26:33 -0500, wrote:

On Tue, 12 Oct 2010 19:50:16 -0400, Wolf K wrote:

On 12/10/2010 18:27, Kilgore Trout wrote:

Took these on our way out west, on our three week road trip. We
stopped at the rose garden first thing in the morning after checking
out from the hotel, when it wasn't so hot.



This newsgroup reader is misbehaving, it's encoding the images as plain
text.

MicroPlanet-Gravity/3.0.4

HTH
wolf k.

odd, as I can see them all.

Karen
Check your settings on sending, you may be sending yEnc files.
My newsreader does it fine but many don't have a newsreader that
interprets yEnc.

In article ,
John Szalay john.szalay.at.att.net wrote:

wrote in
:

On Tue, 12 Oct 2010 19:50:16 -0400, Wolf K
wrote:

On 12/10/2010 18:27, Kilgore Trout wrote:

Took these on our way out west, on our three week road trip. We
stopped at the rose garden first thing in the morning after checking
out from the hotel, when it wasn't so hot.



This newsgroup reader is misbehaving, it's encoding the images as plain
text.

MicroPlanet-Gravity/3.0.4

HTH
wolf k.

odd, as I can see them all.

Karen


coming through fine as photos for me as well..

Well, that's surprising. MT-Newswatcher usually decodes anything with
no problem.

In article ,
says...

On Wed, 13 Oct 2010 09:26:33 -0500, wrote:

On Tue, 12 Oct 2010 19:50:16 -0400, Wolf K wrote:

On 12/10/2010 18:27, Kilgore Trout wrote:
MicroPlanet-Gravity/3.0.4

HTH
wolf k.

odd, as I can see them all.

Karen
Check your settings on sending, you may be sending yEnc files.
My newsreader does it fine but many don't have a newsreader that
interprets yEnc.


Gravity doesn't support yEnc encoding, only yEnc decoding.

Here's the header from one:

Path: news2.newsguy.com!extra.newsguy.com!num01.iad!
npeer02.iad.highwinds-media.com!news.highwinds-media.com!feed-
me.highwinds-media.com!spln!extra.newsguy.com!newsp.newsguy.com !
news5
From: Kilgore Trout

Newsgroups:
alt.binaries.pictures.gardens,alt.binaries.picture s.scenic
Subject: Topeka KS - E.F.A. Reinisch Memorial Rose Garden - July 12
- IMG_0627a-Reinisch_Memorial_Rose_Garden.jpg [1/1]
Date: Tue, 12 Oct 2010 18:27:47 -0400
Organization: Vampire Research Center, PO Box 252, Elmhurst, NY
11373
Lines: 7607
Message-ID:
Reply-To:
NNTP-Posting-Host:
p154e4c0a5007eef2006937f88a70c7f36d42d91953a8d6e8. newsdawg.com
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
User-Agent: MicroPlanet-Gravity/3.0.4
Xref: news2.newsguy.com alt.binaries.pictures.gardens:45996
alt.binaries.pictures.scenic:124126
X-Received-Date: Tue, 12 Oct 2010 23:28:12 UTC (s02-b06.iad)

begin 755 IMG_0627a-Reinisch_Memorial_Rose_Garden.jpg
M_]C_X``02D9)1@`!`@$`M`"T``#_X1317AI9@``24DJ``@````* ``\!`@`&

....
--
Al M_c_C_a_n_n
m a c 3 5 8 (at)-n e w s g u y-(dot) c o m

In article ,
says...

In article ,
John Szalay john.szalay.at.att.net wrote:

wrote in
:

On Tue, 12 Oct 2010 19:50:16 -0400, Wolf K
wrote:

This newsgroup reader is misbehaving, it's encoding the images
as plain
text.

MicroPlanet-Gravity/3.0.4

HTH
wolf k.

odd, as I can see them all.

Karen


coming through fine as photos for me as well..

Well, that's surprising. MT-Newswatcher usually decodes anything with
no problem.

I see one odd thing, Gravity is adding these lines to the header,
even though I've selected UUENCODE:

Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-15"
Content-Transfer-Encoding: 7bit

Gravity can see and download these just fine.

--
Al M_c_C_a_n_n
m a c 3 5 8 (at)-n e w s g u y-(dot) c o m

On 13/10/2010 17:19, Kilgore Trout wrote:
In ,
says...
[...]
Well, that's surprising. MT-Newswatcher usually decodes anything with
no problem.

But Dave Moorman reports he can't see them as images, and he's using
"MT-NewsWatcher/3.5.3b3 (Intel Mac OS X)"

I see one odd thing, Gravity is adding these lines to the header,
even though I've selected UUENCODE:

Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-15"
Content-Transfer-Encoding: 7bit

Precisely. It shouldn't be encoding the images as plain text. The post
should be sent as a two part message: part one a text message (which can
be blank), and part two as a MIME (or UU-)encoded *.jpg file. Gravity
doesn't seem to be doing that. Maybe if you select MIME, Gravity will
send the message correctly. MIME was developed after UUEncode, because
UUEncode is not a good method of encoding binary files. Or so I
understand it.

Gravity can see and download these just fine.


Well, sure, it's the one that's _sending_ these messages in plain text.
Why, I don't know. IMO, there is a standards violation here. We are
(once again) faced with the consequences of freebie-writers ignoring
standards because they "know a better way".

TBird sees:

begin 755 IMG_0619a-Reinisch_Memorial_Rose_Garden.jpg
M_]C_X``02D9)1@`!`@$`M`"T``#_X2,!17AI9@``24DJ``@````* ``\!`@`&
M````A@```!`!`@`8````C````!(!`P`!`````0```!H!!0`!` ```I````!L!
Etc.

IMO, Gravity and other readers that are seeing these as images are in
fact using an external viewer (eg, the default system viewer.) If I Save
As a *.jpg file (instead of an *.eml file), I can see the image using
PMView. So I could Save As the whole lot, and then chcek them in PMView,
but I'd really rather see them in TBird as intended.

HTH
wolf k.

On Wed, 13 Oct 2010 19:18:12 -0400, Wolf K
wrote:

On 13/10/2010 17:19, Kilgore Trout wrote:
In ,
says...
[...]
Well, that's surprising. MT-Newswatcher usually decodes anything with
no problem.

But Dave Moorman reports he can't see them as images, and he's using
"MT-NewsWatcher/3.5.3b3 (Intel Mac OS X)"

I see one odd thing, Gravity is adding these lines to the header,
even though I've selected UUENCODE:

Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-15"
Content-Transfer-Encoding: 7bit

Precisely. It shouldn't be encoding the images as plain text. The post
should be sent as a two part message: part one a text message (which can
be blank), and part two as a MIME (or UU-)encoded *.jpg file. Gravity
doesn't seem to be doing that. Maybe if you select MIME, Gravity will
send the message correctly. MIME was developed after UUEncode, because
UUEncode is not a good method of encoding binary files. Or so I
understand it.

Gravity can see and download these just fine.


Well, sure, it's the one that's _sending_ these messages in plain text.
Why, I don't know. IMO, there is a standards violation here. We are
(once again) faced with the consequences of freebie-writers ignoring
standards because they "know a better way".

TBird sees:


Just another data point, Forte Agent decodes them without a problem.

On Wed, 13 Oct 2010 16:22:42 -0700, charles
wrote:

On Wed, 13 Oct 2010 19:18:12 -0400, Wolf K
wrote:

On 13/10/2010 17:19, Kilgore Trout wrote:
In ,
says...
[...]
Well, that's surprising. MT-Newswatcher usually decodes anything with
no problem.

But Dave Moorman reports he can't see them as images, and he's using
"MT-NewsWatcher/3.5.3b3 (Intel Mac OS X)"

I see one odd thing, Gravity is adding these lines to the header,
even though I've selected UUENCODE:

Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-15"
Content-Transfer-Encoding: 7bit

Precisely. It shouldn't be encoding the images as plain text. The post
should be sent as a two part message: part one a text message (which can
be blank), and part two as a MIME (or UU-)encoded *.jpg file. Gravity
doesn't seem to be doing that. Maybe if you select MIME, Gravity will
send the message correctly. MIME was developed after UUEncode, because
UUEncode is not a good method of encoding binary files. Or so I
understand it.

Gravity can see and download these just fine.


Well, sure, it's the one that's _sending_ these messages in plain text.
Why, I don't know. IMO, there is a standards violation here. We are
(once again) faced with the consequences of freebie-writers ignoring
standards because they "know a better way".

TBird sees:


Just another data point, Forte Agent decodes them without a problem.
I think I said the same thing a while ago.

On Wed, 13 Oct 2010 19:24:21 -0400, joevan
wrote:

On Wed, 13 Oct 2010 16:22:42 -0700, charles
wrote:

On Wed, 13 Oct 2010 19:18:12 -0400, Wolf K
wrote:

On 13/10/2010 17:19, Kilgore Trout wrote:
In ,
says...
[...]
Well, that's surprising. MT-Newswatcher usually decodes anything with
no problem.

But Dave Moorman reports he can't see them as images, and he's using
"MT-NewsWatcher/3.5.3b3 (Intel Mac OS X)"

I see one odd thing, Gravity is adding these lines to the header,
even though I've selected UUENCODE:

Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-15"
Content-Transfer-Encoding: 7bit

Precisely. It shouldn't be encoding the images as plain text. The post
should be sent as a two part message: part one a text message (which can
be blank), and part two as a MIME (or UU-)encoded *.jpg file. Gravity
doesn't seem to be doing that. Maybe if you select MIME, Gravity will
send the message correctly. MIME was developed after UUEncode, because
UUEncode is not a good method of encoding binary files. Or so I
understand it.

Gravity can see and download these just fine.


Well, sure, it's the one that's _sending_ these messages in plain text.
Why, I don't know. IMO, there is a standards violation here. We are
(once again) faced with the consequences of freebie-writers ignoring
standards because they "know a better way".

TBird sees:


Just another data point, Forte Agent decodes them without a problem.
I think I said the same thing a while ago.


You may have, I didn't see the post where you mentioned which
newsreader software you were using. I must have missed it somehow.

In article charles wrote:

On Wed, 13 Oct 2010 19:24:21 -0400, joevan
wrote:

On Wed, 13 Oct 2010 16:22:42 -0700, charles
wrote:

On Wed, 13 Oct 2010 19:18:12 -0400, Wolf K
wrote:

On 13/10/2010 17:19, Kilgore Trout wrote:
In ,
says...
[...]
Well, that's surprising. MT-Newswatcher usually decodes anything with
no problem.

But Dave Moorman reports he can't see them as images, and he's using
"MT-NewsWatcher/3.5.3b3 (Intel Mac OS X)"

I see one odd thing, Gravity is adding these lines to the header,
even though I've selected UUENCODE:

Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-15"
Content-Transfer-Encoding: 7bit

Precisely. It shouldn't be encoding the images as plain text. The post
should be sent as a two part message: part one a text message (which can
be blank), and part two as a MIME (or UU-)encoded *.jpg file. Gravity
doesn't seem to be doing that. Maybe if you select MIME, Gravity will
send the message correctly. MIME was developed after UUEncode, because
UUEncode is not a good method of encoding binary files. Or so I
understand it.

Gravity can see and download these just fine.


Well, sure, it's the one that's _sending_ these messages in plain text.
Why, I don't know. IMO, there is a standards violation here. We are
(once again) faced with the consequences of freebie-writers ignoring
standards because they "know a better way".

TBird sees:


Just another data point, Forte Agent decodes them without a problem.
I think I said the same thing a while ago.


You may have, I didn't see the post where you mentioned which
newsreader software you were using. I must have missed it somehow.

It's in the headers
--

09=IX

On Thu, 14 Oct 2010 12:46:03 -0700, Garrapata
wrote:

In article charles wrote:

On Wed, 13 Oct 2010 19:24:21 -0400, joevan
wrote:

On Wed, 13 Oct 2010 16:22:42 -0700, charles
wrote:

On Wed, 13 Oct 2010 19:18:12 -0400, Wolf K
wrote:

On 13/10/2010 17:19, Kilgore Trout wrote:
In ,
says...
[...]
Well, that's surprising. MT-Newswatcher usually decodes anything with
no problem.

But Dave Moorman reports he can't see them as images, and he's using
"MT-NewsWatcher/3.5.3b3 (Intel Mac OS X)"

I see one odd thing, Gravity is adding these lines to the header,
even though I've selected UUENCODE:

Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-15"
Content-Transfer-Encoding: 7bit

Precisely. It shouldn't be encoding the images as plain text. The post
should be sent as a two part message: part one a text message (which can
be blank), and part two as a MIME (or UU-)encoded *.jpg file. Gravity
doesn't seem to be doing that. Maybe if you select MIME, Gravity will
send the message correctly. MIME was developed after UUEncode, because
UUEncode is not a good method of encoding binary files. Or so I
understand it.

Gravity can see and download these just fine.


Well, sure, it's the one that's _sending_ these messages in plain text.
Why, I don't know. IMO, there is a standards violation here. We are
(once again) faced with the consequences of freebie-writers ignoring
standards because they "know a better way".

TBird sees:


Just another data point, Forte Agent decodes them without a problem.
I think I said the same thing a while ago.


You may have, I didn't see the post where you mentioned which
newsreader software you were using. I must have missed it somehow.

It's in the headers

I'm one of those people who don't study each header before replying to
a post.

In article charles wrote:

X-Newsreader: Forte Agent 6.00/32.1186

On Thu, 14 Oct 2010 12:46:03 -0700, Garrapata
wrote:

In article charles wrote:

It's in the headers

I'm one of those people who don't study each header before replying to
a post.


I don't either but I use an Agent.ini tweak which displays the poster's
newsreader at the top of the post(usually)
--

09=IX