Hallo Gerald,
Du meintest am 08.01.00 zum Thema "UNIVESA adaptor": (h�h�...) ;-)
GK> From: "Gerald Kucera" <[EMAIL PROTECTED]>
GK> You probably have noticed my bad English but it is not my mother
GK> language.
Not bad - for a german... ;-))
GK> P.S.: I do not understand what happend to the same text I sent as an
GK> attachment to the List on 5. Jan.
Here's a quote of this mail:
----------------------------------------------------------------------
From: "Gerald Kucera" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
Header-To: [EMAIL PROTECTED]
* This message is in MIME format.
--MIME-multipart-message-boundary-947111979
Content-type: text/plain; charset=ISO-8859-1
*Content-transfer-encoding: quoted-printable*
----------------------------------------------------------------------
This is the important information to understand what happened,
especially the last line saying that you used "quoted-printable" as
the method for "content-transfer-encoding" in Arachne's e-mail
program InSight. You can change that to "8-bit encoding" in the
setup screens of Arachne (don't know which one just now...), which
would enable you to use german characters that could not be written
with a "7-bit encoding" method. But you have to fill out the table
in that same setup screen striking the refering keys on your keyboard
that you wish to use. And don't forget to use a "." for every key
that you don't want to use.
"Quoted-printable" is a method to send other types of files than
plain ascii text across the e-mail servers of the internet. Glenn
has fallen into that bad habit recently and wants to apply an
"arachne.gif" to every mail he sends... (Warning: I'm only joking,
Glenn). Netscape and Outlook Express users usually think it's a good
idea to apply some kind of visiting-card in a graphic file-format
to their e-mail, expecting that everyone uses their mailreader enabling
him to look at this visiting-card easily. This blows up their "Hi, I'm
XY - just testing!" mail up to some 10-20k for the servers to transport it.
This next quote from your mail is the beginning of that ascii text you
wrote to Jorge, but now in another format "message/rfc822", because you
attached it to your mail. The method to encode it was "base64" and I
would have to use an external decoder for this part of your mail to be
able to read it (PKTXCODE, for example, because I don't use Arachne to
read my mails). I won't do this, though, because I know what's in there:
-----------------------------------------------------------------------
--MIME-multipart-message-boundary-947111979
Content-Type: message/rfc822 ;name=5q0EL003.rfc
Content-Transfer-Encoding: base64
UmV0dXJuLVBhdGg6IDxrdWNlcmFAbmlrb2NpdHkuZGU+ClJlY2VpdmVkOiBmcm9tIHRva2Fp
[..] (meaning: cut out everything up to this next line)
--MIME-multipart-message-boundary-947111979--
--- Arachne V1.50;s.r.c.
----------------------------------------------------------------------
This brings up a question for me: Are the Arachne mail users on
this list able to decode a "base64"-encoded attachment with InSight?
As far as I know the UUENCODE/DECODE.EXE delivered with Arachne can
only handle this method and not "base64" - but perhaps I'm wrong?
Hans-Juergen
--
## CrossPoint v3.11 ##
* ZQWKPro v1.1 [unregistered]
-+- OLMS 2000 UNREG
