[GreenKeys] ITTY Protocol Problems - Revisit

[William Bytheway]

Now that I'm back from dragging the fifth wheel RV to the
ocean for the last three days, I can look at the memory leak
in the new RTTYApp.  I'm a little miffed by some comments
about problems users have experienced, most problems could
have been resolved at the users end.  The biggest complainers
never contacted me directly (which seems obvious, since I'm
the one that will have to fix it).
  
The IP address work-around for more restrictive ISP's was 
simple, use either of the two address below (the second one
is a registered domain name, don't screw up the spelling):

   itty (at) 207.207.72.42
   itty (at) 207-207-72-32.ip.theriver.com

Other issues of sending Rich Text and HTML messages is 
something we warned users about, but for some reason, HTML
was still part of many messages.  Can I recommend using
an old version of Eudora Lite (vintage 1995) exclusively 
for ITTY? Eudora Lite doesn't support HTML or Rich Text.

The RTTYApp version was in it's "Alpha" testing phase, I 
appreciate all of the constructive comments.  Here us a
summary of the most recent improvements:

1.  No longer have to specify "itty@" in lower case, 
    it is now case insensitive.
2.  Implemented the "Bad-Boy" carriage return at line 
    75 to keep from pounding a hole in the paper. This 
    feature is not meant to replace the nominal max line 
    at 72, but to rather protect against a really bad 
    mistake by the sender.
3.  Senders can use multiple addresses, Bcc: and Cc: in 
    the email.  No restrictions.
4.  Most ASCII characters are translated into the closest
    equivalent BAUDOT equivalent.  But it's best to format
    the data input using the BAUDOT character set.

I may also include code to delete (without warning to the
sender) any message that contain bad language. I'll resist
the move unless it becomes a real problem.

73,
K7TTY