| Home |
| Search |
| Today's Posts |
|
#8
14-10-2010, 12:22 AM
posted to alt.binaries.pictures.gardens,alt.binaries.pictures.scenic
|
|||
|
|||
Topeka KS - E.F.A. Reinisch Memorial Rose Garden - July 12 - IMG_0618a-Reinisch_Memorial_Rose_Garden.jpg [0/1]
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. |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|
Threaded Mode
