[ME} Subject prefixes and Juno (for Ann)

["Robert J. Hansen" <cortana@xxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

1.  Juno is not a conventional email service.  Last I checked, Juno
doesn't support POP3, IMAP or SMTP.  It uses its own proprietary
protocol to send email between clients and Juno's servers.  For all I
know, Juno doesn't have any other fields (on the client side) besides
Subject, From, To and Date.

2.  Juno is not an ISP.  It's a service available in the US where you
dial into a central server and get email off it.  Since it doesn't
use any open standards, you're locked into using Juno's own
proprietary mailer.  In other words, Ann probably can't switch to a
"real" emailer like Outlook.  (Notice how I put "real" in quotes
there?  That's because Outlook isn't much of a real email client,
either... but I'll spare you that rant.)

3.  I think Ann's right.  Every other mailing list that I'm on save
one prepends a short character sequence to its traffic, whether it be
the Continuing Time's [CT], whether it be Helix Code's
[Evolution-hackers] and [Evolution], etc.  The only one that doesn't
do this is the Open Java Ceyptographic Extension email list, upon
which people have been quietly begging the list maintainer for a year
now to prefix it with [OJCE].

4.  I'm going to start inserting [ME] in my response headers for time
being, as a convenience for Ann and others.

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.8 for non-commercial use <http://www.pgp.com>

iQA/AwUBOjI/C5gOGKeCwjkrEQLAOgCfbwbLOqbj3D7qujTtBCwQVM7EzRUAn34e
OVOwS1k+VD4SwcpPbMw/asbZ
=ocdb
-----END PGP SIGNATURE-----