Date:         Wed, 23 Jun 2004 08:54:03 -0400
Reply-To:     bogdan romocea <br44092@GAWAB.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         bogdan romocea <br44092@GAWAB.COM>
Subject:      Re: ODS EMAIL and Content-Transfer-Encoding

I fully agree about HTML email, it's really bad. Allan, see
http://www.birdhouse.org/etc/evilmail.html
and then drop HTML email for good.


-----Original Message-----
From: David L. Cassell [mailto:cassell.david@EPAMAIL.EPA.GOV]
Sent: Tuesday, June 22, 2004 8:17 PM
To: SAS-L@LISTSERV.UGA.EDU
Subject: Re: ODS EMAIL and Content-Transfer-Encoding


"Allan B. Christensen" <abc@DK2NET.DK> wrote:
> It seems that e-mails generated using ODS with HTML are by default
sent
> out with Content-Transfer-Encoding as quoted-printable, which means
that
> "=" is quoted as "=3d", among other things. For some reason these
quoted
> values are interpreted literally by some email clients, making them
> virtually unreadable.
>
> Is there a way to specify Content-Transfer-Encoding in ODS to select
> another option. Or is there another explanation for the behavior?

Let me first point out that many people *hate* to get their email as
HTML.  If you are being forced to do this by Pointy-Haired Bosses, then
there's little you can do to solve this problem.  But I know at least
one
programmer who has procmail automatically throw anything sent in HTML
straight in /dev/null .

Second, where is the problem?  If you need to have quoted-printable
content, then you need to address the problem of people with
uncooperative
email MUAs (Mail User Agents).  If you need to send your emails to these
clients, then don't you need to drop the HTML?

I don't know of a way to alter the Content-Transfer-Encoding default,
but
that doesn't mean someone like Andre or Richard won't see my post and
toss
out the answer instantly...

David
--
David Cassell, CSC
Cassell.David@epa.gov
Senior computing specialist
mathematical statistician