 |
[Design] Provide safe "Message Source" display in Chandler
Bob Wyman
Wed, 29 Jan 2003 04:03:44 -0500
This is a multi-part message in MIME format.
------=_NextPart_000_001B_01C2C74B.6AA30B60
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Like Outlook Express does, it would excellent if Chandler provided a
means by which email message source could be inspected prior to opening
an email message. The message source should contain all bytes which are
associated with the message and should be a simple text display. I have
personally found the OE facility that allows this to be very useful to
me in inspecting "suspect" messages. Often, a scan of the headers is
sufficient to detect spam, however, being able to view the message
source is better. Note: Outlook only allows viewing the message headers.
This is not sufficient to protect one's self.
An ideal system of viewing "message source" would, while still
presenting what was basically a text view, also flag various components
of the source to allow me to more easily figure out what was there. For
instance, HTML could be shown in one color or font, while javascript or
vbscript would be in another color.=20
Further, an ideal system would probably present me with a list or
count of the most dangerous bits to be inspected. i.e. it would tell me
that there were 15 bits of javascript that needed to be inspected and
would allow me to position quickly to them. An ideal system would also
allow me to inspect the "signatures" associated with any scripts that
might be in the message...
I realize that these tools would only be most useful to folk with a
solid technical background. But, given that many of us are precisely
this type of folk, it would be nice if we were to build a few toys and
tools for our benefit even if others can't use them...
=20
bob wyman
=20
------=_NextPart_000_001B_01C2C74B.6AA30B60
Content-Type: text/html;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<TITLE>Message</TITLE>
<META content=3D"MSHTML 6.00.2800.1126" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D456145408-29012003><FONT face=3DArial =
size=3D2> =20
Like Outlook Express does, it would excellent if Chandler provided a =
means by=20
which email message source could be inspected prior to opening an email =
message.=20
The message source should contain all bytes which are associated with =
the=20
message and should be a simple text display. I have personally found the =
OE=20
facility that allows this to be very useful to me in inspecting =
"suspect"=20
messages. Often, a scan of the headers is sufficient to detect spam, =
however,=20
being able to view the message source is better. Note: Outlook only =
allows=20
viewing the message headers. This is not sufficient to protect one's=20
self.</FONT></SPAN></DIV>
<DIV><SPAN class=3D456145408-29012003><FONT face=3DArial =
size=3D2> =20
An ideal system of viewing "message source" would, while still =
presenting what=20
was basically a text view, also flag various components of the source to =
allow=20
me to more easily figure out what was there. For instance, HTML could be =
shown=20
in one color or font, while javascript or vbscript would be in another =
color.=20
</FONT></SPAN></DIV>
<DIV><SPAN class=3D456145408-29012003> <FONT =
face=3DArial=20
size=3D2>Further, an ideal system would probably present me with a list =
or count=20
of the most dangerous bits to be inspected. i.e. it would tell me that =
there=20
were 15 bits of javascript that needed to be inspected and would allow =
me to=20
position quickly to them. An ideal system would also allow me to inspect =
the=20
"signatures" associated with any scripts that might be in the=20
message...</FONT></SPAN></DIV>
<DIV><SPAN class=3D456145408-29012003> <FONT =
face=3DArial=20
size=3D2> I realize that these tools would only be most =
useful to folk=20
with a solid technical background. But, given that many of us are =
precisely this=20
type of folk, it would be nice if we were to build a few toys and tools =
for our=20
benefit even if others can't use them...</FONT></SPAN></DIV>
<DIV><SPAN class=3D456145408-29012003><FONT face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN =
class=3D456145408-29012003> =20
<FONT face=3DArial size=3D2>bob wyman</FONT></SPAN></DIV>
<DIV><SPAN class=3D456145408-29012003><FONT face=3DArial=20
size=3D2></FONT></SPAN> </DIV></BODY></HTML>
------=_NextPart_000_001B_01C2C74B.6AA30B60--
|
