I'm getting quite a few emails like this:
https://www.dropbox.com/s/jny6d81ml6lm6c1/StrangeRendering.jpg?draw=1

The text in Agent looks encrypted. Possibly from Android devices?

QEdlbmVIZXNrZXR0IFRoZSBtZWNoYW5pY2FsIFogdG9sZXJhbmNlcyBjYW4ndCBiZSB0aGF0IGZh
ciBvZmYuIA0KU29tZWhvdyBhIHdyb25nIHZhbHVlIGhhcyBnb3R0ZW4gcHV0IGluIHRoZSBjb2Rl
IHJlbGF0aW5nIHN0ZXBzIHRvIFosIEkgc3VzcGVjdC4NCkxvb2sgYXQgdGhlIEcgY29kZSdzIFog
dmFsdWVzIQ0KDQpJIGhhZCB0byByYWlzZSBteSB0ZW1wZXJhdHVyZSBmcm9tIGFib3V0IDI0MCB0
byAyNzAgYWZ0ZXIgc3dpdGNoaW5nIGZyb20gYSBicmFzcyBub3p6bGUgdG8gdGhlIGhhcmRlbmVk
etc, etc

Terry

On Tue, 31 Aug 2021 15:02:41 +0100, Terry Pinnell <me@somewhere.invalid>
declaimed the following:

>I'm getting quite a few emails like this:
>https://www.dropbox.com/s/jny6d81ml6lm6c1/StrangeRendering.jpg?draw=1
>
>The text in Agent looks encrypted. Possibly from Android devices?
>

We'd need to see the headers to tell what it thinks the message content
is.

>QEdlbmVIZXNrZXR0IFRoZSBtZWNoYW5pY2FsIFogdG9sZXJhbmNlcyBjYW4ndCBiZSB0aGF0IGZh
>ciBvZmYuIA0KU29tZWhvdyBhIHdyb25nIHZhbHVlIGhhcyBnb3R0ZW4gcHV0IGluIHRoZSBjb2Rl
>IHJlbGF0aW5nIHN0ZXBzIHRvIFosIEkgc3VzcGVjdC4NCkxvb2sgYXQgdGhlIEcgY29kZSdzIFog
>dmFsdWVzIQ0KDQpJIGhhZCB0byByYWlzZSBteSB0ZW1wZXJhdHVyZSBmcm9tIGFib3V0IDI0MCB0
>byAyNzAgYWZ0ZXIgc3dpdGNoaW5nIGZyb20gYSBicmFzcyBub3p6bGUgdG8gdGhlIGhhcmRlbmVk
>etc, etc

However, that is base64 encoded...

>>> import base64
>>> base64.decodebytes(b"QEdlbmVIZXNrZXR0IFRoZSBtZWNoYW5pY2FsIFogdG9sZXJhbmNlcyBjYW4ndCBiZSB0aGF0IGZh")
b"@GeneHeskett The mechanical Z tolerances can't be that fa"
>>>

and Agent should be able to decode a properly identified (MIME headers)
message.

--
Wulfraed Dennis Lee Bieber AF6VN
wlfraed@ix.netcom.com http://wlfraed.microdiversity.freeddns.org/

Dennis Lee Bieber <wlfraed@ix.netcom.com> wrote:

>On Tue, 31 Aug 2021 15:02:41 +0100, Terry Pinnell <me@somewhere.invalid>
>declaimed the following:
>
>>I'm getting quite a few emails like this:
>>https://www.dropbox.com/s/jny6d81ml6lm6c1/StrangeRendering.jpg?draw=1
>>
>>The text in Agent looks encrypted. Possibly from Android devices?
>>
>
> We'd need to see the headers to tell what it thinks the message content
>is.
>
>>QEdlbmVIZXNrZXR0IFRoZSBtZWNoYW5pY2FsIFogdG9sZXJhbmNlcyBjYW4ndCBiZSB0aGF0IGZh
>>ciBvZmYuIA0KU29tZWhvdyBhIHdyb25nIHZhbHVlIGhhcyBnb3R0ZW4gcHV0IGluIHRoZSBjb2Rl
>>IHJlbGF0aW5nIHN0ZXBzIHRvIFosIEkgc3VzcGVjdC4NCkxvb2sgYXQgdGhlIEcgY29kZSdzIFog
>>dmFsdWVzIQ0KDQpJIGhhZCB0byByYWlzZSBteSB0ZW1wZXJhdHVyZSBmcm9tIGFib3V0IDI0MCB0
>>byAyNzAgYWZ0ZXIgc3dpdGNoaW5nIGZyb20gYSBicmFzcyBub3p6bGUgdG8gdGhlIGhhcmRlbmVk
>>etc, etc
>
> However, that is base64 encoded...
>
>>>> import base64
>>>> base64.decodebytes(b"QEdlbmVIZXNrZXR0IFRoZSBtZWNoYW5pY2FsIFogdG9sZXJhbmNlcyBjYW4ndCBiZSB0aGF0IGZh")
>b"@GeneHeskett The mechanical Z tolerances can't be that fa"
>>>>
>
>and Agent should be able to decode a properly identified (MIME headers)
>message.

Thanks Dennis. Without risking disrespecting the privacy of the sender
I'm not comfortable with posting the entire 83 line header. The only
lines that look remotely relevant to me are these.

Line 58: MIME-Version: 1.0
Line 59: Content-Disposition: inline
Line 80: Content-Type: Text/Plain; charset="utf-8"
Line 81: Content-Transfer-Encoding: base64

Agent's Help for the 'Add MIME Type dialog' says:
Use this dialog to add a MIME type to the Type/Subtype, Extensions,
Applications list box.
Type
----
Enter the MIME type that you want to add to the "Type/Subtype..." list
box.

Subtype
------
Enter the subtype that you want to add to the "Type/Subtype..." list
box.

But that leaves me no wiser about the two entries I need!

Terry

Terry Pinnell <me@somewhere.invalid> wrote:

>Dennis Lee Bieber <wlfraed@ix.netcom.com> wrote:
>
>>On Tue, 31 Aug 2021 15:02:41 +0100, Terry Pinnell <me@somewhere.invalid>
>>declaimed the following:
>>
>>>I'm getting quite a few emails like this:
>>>https://www.dropbox.com/s/jny6d81ml6lm6c1/StrangeRendering.jpg?draw=1
>>>
>>>The text in Agent looks encrypted. Possibly from Android devices?
>>>
>>
>> We'd need to see the headers to tell what it thinks the message content
>>is.
>>
>>>QEdlbmVIZXNrZXR0IFRoZSBtZWNoYW5pY2FsIFogdG9sZXJhbmNlcyBjYW4ndCBiZSB0aGF0IGZh
>>>ciBvZmYuIA0KU29tZWhvdyBhIHdyb25nIHZhbHVlIGhhcyBnb3R0ZW4gcHV0IGluIHRoZSBjb2Rl
>>>IHJlbGF0aW5nIHN0ZXBzIHRvIFosIEkgc3VzcGVjdC4NCkxvb2sgYXQgdGhlIEcgY29kZSdzIFog
>>>dmFsdWVzIQ0KDQpJIGhhZCB0byByYWlzZSBteSB0ZW1wZXJhdHVyZSBmcm9tIGFib3V0IDI0MCB0
>>>byAyNzAgYWZ0ZXIgc3dpdGNoaW5nIGZyb20gYSBicmFzcyBub3p6bGUgdG8gdGhlIGhhcmRlbmVk
>>>etc, etc
>>
>> However, that is base64 encoded...
>>
>>>>> import base64
>>>>> base64.decodebytes(b"QEdlbmVIZXNrZXR0IFRoZSBtZWNoYW5pY2FsIFogdG9sZXJhbmNlcyBjYW4ndCBiZSB0aGF0IGZh")
>>b"@GeneHeskett The mechanical Z tolerances can't be that fa"
>>>>>
>>
>>and Agent should be able to decode a properly identified (MIME headers)
>>message.
>
>
>Thanks Dennis. Without risking disrespecting the privacy of the sender
>I'm not comfortable with posting the entire 83 line header. The only
>lines that look remotely relevant to me are these.
>
>Line 58: MIME-Version: 1.0
>Line 59: Content-Disposition: inline
>Line 80: Content-Type: Text/Plain; charset="utf-8"
>Line 81: Content-Transfer-Encoding: base64
>
>Agent's Help for the 'Add MIME Type dialog' says:
>Use this dialog to add a MIME type to the Type/Subtype, Extensions,
>Applications list box.
>Type
>----
>Enter the MIME type that you want to add to the "Type/Subtype..." list
>box.
>
>Subtype
>------
>Enter the subtype that you want to add to the "Type/Subtype..." list
>box.
>
>But that leaves me no wiser about the two entries I need!
>
>Terry

I meant to add this screenshot of my current MIME types, which already
includes a text/plain entry (opening in my text editor):
https://www.dropbox.com/s/6b9ijxk4kyrerbe/MIME-Types.jpg?raw=1

But is it not possible to get Agent to display it without that extra
step?

Terry

On Tue, 31 Aug 2021 20:44:49 +0100, Terry Pinnell <me@somewhere.invalid>
declaimed the following:

>>Line 58: MIME-Version: 1.0
>>Line 59: Content-Disposition: inline
>>Line 80: Content-Type: Text/Plain; charset="utf-8"
>>Line 81: Content-Transfer-Encoding: base64

I'd expect Agent would translate that.

>>Agent's Help for the 'Add MIME Type dialog' says:
>>Use this dialog to add a MIME type to the Type/Subtype, Extensions,
>>Applications list box.

Probably not relevant, it is mostly to associate embedded (multi-part)
content with external viewing programs.

>
>I meant to add this screenshot of my current MIME types, which already
>includes a text/plain entry (opening in my text editor):
>https://www.dropbox.com/s/6b9ijxk4kyrerbe/MIME-Types.jpg?raw=1
>

Unfortunately, you did not highlight the relevant entry when you made
that screen shot. I'm curious if your text/plain entry has

[X] Display when inline

Many newsgroups will strip attachments anyway...

Trying an experiment:

INSERT / File Attachment

though the [Attachments] button may give more options

--
Wulfraed Dennis Lee Bieber AF6VN
wlfraed@ix.netcom.com http://wlfraed.microdiversity.freeddns.org/

On Tue, 31 Aug 2021 16:02:10 -0400, Dennis Lee Bieber
<wlfraed@ix.netcom.com> declaimed the following:

> Many newsgroups will strip attachments anyway...
>
> Trying an experiment:
>
> INSERT / File Attachment
>
>though the [Attachments] button may give more options

... Aaaaannnndddd... the attachment WAS stripped...

--
Wulfraed Dennis Lee Bieber AF6VN
wlfraed@ix.netcom.com http://wlfraed.microdiversity.freeddns.org/

Dennis Lee Bieber <wlfraed@ix.netcom.com> wrote:

> ... Aaaaannnndddd... the attachment WAS stripped...

As it should be for a text only newsgroup. The suggested practice is to put the
binary up someplace and provide a link to it. There are free sites available
that make this quite easy, like imagur...

--
Usenet: The world's first (and best) social network.

On Tue, 31 Aug 2021 15:02:41 +0100, Terry Pinnell wrote:

> I'm getting quite a few emails like this:
> https://www.dropbox.com/s/jny6d81ml6lm6c1/StrangeRendering.jpg?draw=1
>
> The text in Agent looks encrypted. Possibly from Android devices?
>
> QEdlbmVIZXNrZXR0IFRoZSBtZWNoYW5pY2FsIFogdG9sZXJhbmNlcyBjYW4ndCBiZSB0aGF0IGZh
> ciBvZmYuIA0KU29tZWhvdyBhIHdyb25nIHZhbHVlIGhhcyBnb3R0ZW4gcHV0IGluIHRoZSBjb2Rl
> IHJlbGF0aW5nIHN0ZXBzIHRvIFosIEkgc3VzcGVjdC4NCkxvb2sgYXQgdGhlIEcgY29kZSdzIFog
> dmFsdWVzIQ0KDQpJIGhhZCB0byByYWlzZSBteSB0ZW1wZXJhdHVyZSBmcm9tIGFib3V0IDI0MCB0
> byAyNzAgYWZ0ZXIgc3dpdGNoaW5nIGZyb20gYSBicmFzcyBub3p6bGUgdG8gdGhlIGhhcmRlbmVk
> etc, etc
>
> Terry

Turn off "View >> Display as Raw Message".

Ctrl+R turns this on and off. You may have accidentally pressed Ctrl+R once.

FYI: see this item in the Agent Newsreader FAQ:

Attachments appear as blocks of code instead of as icons.
<https://web.archive.org/web/20200627063700/http://www.forteinc.com/agent/faq.php#3681E47795B0585285256C1F005A88F1>

If the Wayback timeline bar covers the article, you maty need to scroll up a bit.

--
Kind regards
Ralph

Ralph Fox <-rf-nz-@-.invalid> wrote:

>On Tue, 31 Aug 2021 15:02:41 +0100, Terry Pinnell wrote:
>
>> I'm getting quite a few emails like this:
>> https://www.dropbox.com/s/jny6d81ml6lm6c1/StrangeRendering.jpg?draw=1
>>
>> The text in Agent looks encrypted. Possibly from Android devices?
>>
>> QEdlbmVIZXNrZXR0IFRoZSBtZWNoYW5pY2FsIFogdG9sZXJhbmNlcyBjYW4ndCBiZSB0aGF0IGZh
>> ciBvZmYuIA0KU29tZWhvdyBhIHdyb25nIHZhbHVlIGhhcyBnb3R0ZW4gcHV0IGluIHRoZSBjb2Rl
>> IHJlbGF0aW5nIHN0ZXBzIHRvIFosIEkgc3VzcGVjdC4NCkxvb2sgYXQgdGhlIEcgY29kZSdzIFog
>> dmFsdWVzIQ0KDQpJIGhhZCB0byByYWlzZSBteSB0ZW1wZXJhdHVyZSBmcm9tIGFib3V0IDI0MCB0
>> byAyNzAgYWZ0ZXIgc3dpdGNoaW5nIGZyb20gYSBicmFzcyBub3p6bGUgdG8gdGhlIGhhcmRlbmVk
>> etc, etc
>>
>> Terry
>
>
>Turn off "View >> Display as Raw Message".
>
>Ctrl+R turns this on and off. You may have accidentally pressed Ctrl+R once.
>
>
>
>FYI: see this item in the Agent Newsreader FAQ:
>
> Attachments appear as blocks of code instead of as icons.
> <https://web.archive.org/web/20200627063700/http://www.forteinc.com/agent/faq.php#3681E47795B0585285256C1F005A88F1>
>
>If the Wayback timeline bar covers the article, you maty need to scroll up a bit.

Duh, thanks Ralph, it was indeed as simple as that!

Terry