Date: Tue, 28 Dec 1999 16:15:51 +0100
Reply-To: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM>
Subject: Re: Why are there funny characters in the emails?
Content-Type: text/plain; charset="iso-8859-1"
Diana,
It contains coded information, attachments like pictures, Word files and the
like. That information can not be sent as it is via regular email, but has
to be coded to text, and normally will be decoded to its original contents
and meaning on reception. In specific cases you are able to see the coded
part of the message, looking like garbage.
Jim.
--
Y. Groeneveld, MSc IMRO TRAMARKO tel. +31 412 407 070
senior statistician, P.O. Box 1 fax. +31 412 407 080
head IT department 5350 AA BERGHEM IMRO TRAMARKO: a CRO
J.Groeneveld@ITGroups.com the Netherlands in clinical research
I wish you a merry Christmas and a happy, compatible y²°°°
"My job is to keep my computer working." - Jim Groeneveld
> -----Original Message-----
> From: Diana Noble [SMTP:diana.noble@PRUDENTIAL.COM]
> Sent: Tuesday, December 28, 1999 3:50 PM
> To: SAS-L@LISTSERV.UGA.EDU
> Subject: Why are there funny characters in the emails?
>
> Does anyone know why some people email comes through will garbled
> characters
> following the note (see below example). This one came through at 384 Kb
> of
> garbage. And more importantly, how can it be prevented (if at all)?
> No offense to the senders, I just wish to understand.
>
> <<Date: Tue, 28 Dec 1999 14:46:39 +0100
> From: nicolas.pont@UNICIBLE.CH
> Subject: Why I don't have any horizontal elevator to see the rest of the
> multidimensionnal report
>
> --0__=PA9KM3gWNHScL8YYeZRhRbLgRNA6MNpBQB05ikJVXP0bJ5uQw6DDrQpe
> Content-type: text/plain; charset=us-ascii
>
> Thanks for any help
>
> (See attached file: elevator.psp)
> --0__=PA9KM3gWNHScL8YYeZRhRbLgRNA6MNpBQB05ikJVXP0bJ5uQw6DDrQpe
> Content-type: application/octet-stream;
> name="elevator.psp"
> Content-Disposition: attachment; filename="elevator.psp"
> Content-transfer-encoding: base64
>
> UGFpbnQgU2hvcCBQcm8gSW1hZ2UgRmlsZQoaAAAAAAAEAAAAfkJLAAAALgAAAC4AAAAABAAAAA
> MA
> AAAAAAAAAFJAAQEAGAABAAAAAAEAAAAkAAAAAAABAAEAABF+QksAAQA4AAAAfkZMAAEABAAAAC
> 2+
> aDh+RkwAAgAEAAAA2L5oOH5GTAAGAAQAAAABAAAAfkZMAAcABAAAAAIAAAZ+QksAEABHFgAACA
> AA
> AAEAAAB+QksAEQAYAAAAGAAAAMgAAACWAAAAGAADAAEAAAAAAQEAfkJLABIAExYAAA4AAAAFFg
> AA
> uF8BAAUA/9j/4AAQSkZJRgABAQABLAEsAAD/2wBDAAUDBAQEAwUEBAQFBQUGBwwIBwcHBw8LCw
> kM
> EQ8SEhEPERETFhwXExQaFRERGCEYGh0dHx8fExciJCIeJBweHx7/2wBDAQUFBQcGBw4ICA4eFB
> EU
> Hh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh7/wAARCA
> CW
> AMgDASIAAhEBAx...
>
> more of this for 3 meg >>
|