Ron,
I
can't do that! That would be the RIGHT way to fix it! Where's
the job security? What am I going to do with our
expensive issue tracking system? How am I
supposed to bill for overtime? I was planning to build some kind
of
complex, CPU-intensive process! How am I going
to explain to the customer that we DON'T need 30 more
servers?!
What
will happen to Dell and Compaq if we stop buying servers and use our obsolete
quad-1.5GHz machines from
last
month? What will happen to Siebel if we don't have any more
issues?! The economy could be in
ruins!
Heh
heh...
Actually, you're (obviously) right. That would
be better, but I, personally, just needed something quick for one of
my
"knows just enough to be dangerous" clients. I'm going
to go ahead and load up the message in XML format
and
scrub it with a COM Object for the OWA-like rip-off
interface I'm working on. This will replace the iMail
web
interface in about 2 weeks
anyway.
Which actually brings up another problem... when you
Reply, Reply All, or Forward an HTML message through
the
web interface... is there an "undocumented" tag that allows you to bring
up the reply/reply all/forward message
in
HTML format with the "-----Original Message----" junk or should I
just pull up the original message and add the
reply information and ">" symbols
afterwards?
For
example, for this message:
The
<i>formatted</i> <b>message</b>.
On reply, the tag
<!--IMAIL.MessageBodyReply--> gives me:
>Subject: Test message.
>
> My formated message.
with
HTML stripped out and the ">" symbol in front of every line. Where I
would expect:
>Subject: Test message.
>
> My <i>formatted</i>
<b>message</b>.
-Norm
Norm,
Have you
considered putting the textarea-display method *inside* the BeginIfHTMLMessage
block, so that it's used only when displaying html messages? The would keep
your plain-text messages displayed in the normal manner.
Then you
could add a simple script to the onLoad event of the readmail.html body
tag that would strip all tags from that textarea field, if it was present, and
replace its contents with the santized version, for better readability.
As an added bonus, you could save the original html in a hidden input field
(via the same JS), and create a link to let you open the original html message
in a new window, if desired (if it was from a trusted source, for
example).
