In message <[log in to unmask]>, Alan Yeo
<[log in to unmask]> writes
> In article <[log in to unmask]>, Donna Garverick
><[log in to unmask]> writes
>>Eben Yong wrote:
>>
>>> We had a system crash today and I wanted to copy the DL entries into a
>>> text file in order to email it to our hardware/software support group.
>>> I could not figure out how to do that so I sent off TWO screenshots
>>> instead-which is a big waste of bandwidth.
>>
>
>Its amazing that Donna can write "Eben wrote" as I thought he was
>writing using invisible ink, or should that be electrons. Each of his
>postings opened empty for me.
>
>Just interested, but anyone else have the same problem.
As per:
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: base64
Eben's article is base64 encoded, which to a mail reader (for HP3000-L)
or a newsreader (for comp.sys.hp.mpe) which does not understand base64
will look like:
V2UgaGFkIGEgc3lzdGVtIGNyYXNoIHRvZGF5IGFuZCBJIHdhbnRlZCB0byBjb3B5IHRoZSBETCBl
bnRyaWVzIGludG8gYQ0KdGV4dCBmaWxlIGluIG9yZGVyIHRvIGVtYWlsIGl0IHRvIG91ciBoYXJk
d2FyZS9zb2Z0d2FyZSBzdXBwb3J0IGdyb3VwLg0KSSBjb3VsZCBub3QgZmlndXJlIG91dCBob3cg
dG8gZG8gdGhhdCBzbyBJIHNlbnQgb2ZmIFRXTyBzY3JlZW5zaG90cw0KaW5zdGVhZC13aGljaCBp
cyBhIGJpZyB3YXN0ZSBvZiBiYW5kd2lkdGguDQoNCiANCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLQ0KDQpFYmVuIFlvbmcNCg0KTUlTIE1hbmFnZXINCg0KSGVhbHRoIFBs
YW4gb2YgU2FuIE1hdGVvDQoNCjcwMSBHYXRld2F5IEJsdmQNCg0KU291dGggU2FuIEZyYW5jaXNj
bywgQ0EgIDk0MDgwDQoNClRFTDo2NTAtNjE2LTIwMTANCg0KRkFYOjcwNy0yODEtMjY5MQ0KDQp3
d3cuaHBzbS5vcmcNCg0KZWJlbl95b25nQGhwc20ub3JnDQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0gDQogIA0KQ09ORklERU5USUFMSVRZIE5PVElDRTogIFRoaXMgZS1t
YWlsLCBpbmNsdWRpbmcgYXR0YWNobWVudHMsIGlzIGZvciB0aGUgDQpzb2xlIHVzZSBvZiB0aGUg
aW5kaXZpZHVhbChzKSB0byB3aG9tIGl0IGlzIGFkZHJlc3NlZCwgYW5kIG1heSBjb250YWluIA0K
Y29uZmlkZW50aWFsIGFuZCBwcml2aWxlZ2VkIGluZm9ybWF0aW9uLiBBbnkgdW5hdXRob3JpemVk
IHJldmlldywgdXNlLCANCmRpc2Nsb3N1cmUsIGRpc3RyaWJ1dGlvbiwgb3IgcmVwcm9kdWN0aW9u
IGlzIHByb2hpYml0ZWQuIElmIHlvdSBoYXZlIA0KcmVjZWl2ZWQgdGhpcyBlLW1haWwgaW4gZXJy
b3IsIHBsZWFzZSBub3RpZnkgdGhlIHNlbmRlciBieSByZXBseSBlLW1haWwgDQphbmQgZGVzdHJv
eSB0aGlzIG1lc3NhZ2UgYW5kIGl0cyBhdHRhY2htZW50cy4gVGhhbmsgeW91IGZvciB5b3VyIA0K
Y29vcGVyYXRpb24uICANCiANCg==
Is this what you see?
Your headers do not apparently reveal what mail or newsreader you are
using, but the Turnpike 6.02 that you will see in mine (proving that
Raven does not elide this information) parses it perfectly, as quoted by
Donna.
Having said that, I'm not sure what Eben is posting with, or whether he
can avoid a scheme that appears to obfuscate his postings for a
significant number of potential helpers.....
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
...though the above may be a clue.
I see Eben has been playing with gnuPG & WinPT (whatever they are), but
as there is no PGP encoding, or any problems with broken PGP visible, I
suspect the problem is that Outlook has been set to send Base64 by those
products, and removing them has not unset this again.
So Outlook (and OE?) wants configuring back to plain text, or at least
away from applying base64 encoding.....
--
Roy Brown 'Have nothing in your houses that you do not know to be
Kelmscott Ltd useful, or believe to be beautiful' William Morris
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
