Version 6.0

- Compose and send messages from your nym.alias.net style pseudonym accounts. Specify
  your nym accounts by selecting Sysop|Personal Pseudonym Accounts from the remailer 
  window.

- Moved the menus around a little.

Version 5.9a

- Manual button in the "other" configuration for requesting a stats update.

Version 5.9

- Post to USENET groups from the compose window. Instead of an address, enter as follows:

	News: group1, group2, group[n]
  
  This works with both the standard post and remail functions. Multiple group posting 
  only if your mail2news configuration is setup to allow this.

Version 5.8c

- Fixed problem with improperly formatted destination addresses which could cause Juno 
  to hang, stalling the remailer if running unattended.

- Reliability stats can now be requested on a 1, 2, 4, or 8 hour interval in addition
  to daily or with each run.

Version 5.8b

- Shows current uptime in main window caption (if applicable).

Version 5.8a

- Bug fix: if the address is missing in the lower portion of a received stats message,
  the remailer would add the zero-length entry to the list of valid direct destinations. By 
  string comparison, EVERY address appeared to be a valid direct destination effectively
  turning off middle mode ops.

- List boxes for remailer lists (rerouting remailers and remailer list for message 
  composition) now show latency.

Version 5.8

- New messages and replies can be routed through remailers from the compose window.

Version 5.7b

- From: field added to reply/compose window. Again, this does not allow an e-mail address
  to be specified. Only the real name portion.

Version 5.7

- Smart middleman mode. Requires that you have a regular statistics update, so I suggest
  you configure the remailer to send a blank message to <rlist@anon.efga.org> each run, 
  or once per day, depending on how many of these things you are willing to have 
  accumulate in your nonremailer folder.

  If the remailer sees this kind of incoming message, it will copy the body of the
  message to a file called STATS.LST in the remailer directory. The remailer will then
  look at this file for decisions about where messages may go without being re-routed, and
  what remailer to send them through if they need to be re-routed. 

  Since there may be additional addresses, such as the nym server send@ addresses, or
  other "friendlies", another mechanism is provided to allow these and other destinations
  to be mailed directly without re-routing the message. In addition to all of the remailers
  listed in the stats updates, any addresses in the file NOREMAIL.LST will be mailed 
  directly without re-routing. This file can be edited by selecting Remailer|Middleman 
  Operation|Direct-Routing Addresses.

  If messages are being sent to an address not present on the list of remailers or 
  direct-routing addresses, they will be encrypted and sent through a reliable remailer
  on the list which has these attributes:

	1) "cpunk" AND "pgp" AND NOT "middle"
        2) An uptime rating equal to or greater than your threshold setting.

  If no remailers meet this criteria, smart-middleman mode is disabled until the stats
  allow for this mode of operation

- If you're running PGP 5.0i, undecipherable messages have been stuck in your
  incoming directory, and "discarded" with every run, but didn't show in the
  nonremailer folder. This has been fixed.

- Outgoing messages can now be specified to be from something other than
  "Anonymous Remailer". You cannot change the e-mail address (Juno limitation).
  There is also a specification for manually composed messages, so they can be
  from something such as "Remailer Admin" or whatever.

- Nymserver was enabled regardless of setting. This should no longer be the case.

Version 5.6b

- Cover messages batch processed, instead of a new DOS window for each.

Version 5.6a

- Cover traffic generator runs automatically depending on settings in the remailer 
  configuration. Can be set to run min-max times each run.

Version 5.6

- Cover traffic generator. Creates and sends a message to any remailer's /dev/null.
  You will need to supply a list of remailers, and you need the public key for each.
  The selected remailer is chosen randomly from the list. You will find this under 
  the file menu.

Version 5.5

- PGP 5.0i support. The file you need is:

	ftp://ftp.westfalen.de/homepages/hugo/pgp/pgp50ibi.zip

  I installed this in a new directory. Be sure to make a backup of your keyrings
  and then rename them to the new keyfile names as directed in the INSTALL.TXT file
  that comes with 5.0i. There's little point in doing this upgrade unless you
  intend to generate a second key of the DH/DSS varity, so that should be your next
  step. The passphrase for the RSA and DH/DSS keys MUST BE THE SAME! Don't forget to
  add the new key to PUBKEY.TXT in the remailer directory. 

  Be sure to run INSTALL.BAT (either option is fine).

  Configuring the remailer:

  Set the new PGP directory, then check 5.0i next to that box.

  That's it. After a few sessions, I have only one complaint: For some reason, if the 
  file that gets passed to PGP has a leading blank line, or doesn't start with the 
  PGP header, you get this message:

    Opening "NUL", type text

  It still works, but I don't like to see messages like this that don't make sense.

  As usual, report problems to grit_remailer@juno.com .

- Replies now include the text "<sender> wrote:" to help decipher on-going threads.

Version 5.4a

- Message reprocessing failed to copy all headers, and dropped all but the first
  line of multi-line headers. It now copies the entire message verbatim.

Version 5.4

- Added auto-fetching of the remailer statistics table by e-mail or GetWeb server.

Version 5.3a

- Stats list a set of identifying information to help detect the presence of 
  multiple remailers being operated by a single individual. The information
  is subjected to a one-way function to prevent the leak of actual system
  settings or user information.

Version 5.3

- Improved header processing. Multi-line headers on incoming messages are now 
  recognized. This should prevent false triggering of the spam filter when a
  message is addressed to multiple remailers.

Version 5.2b

- Clicking on the status line will shrink/expand window for smaller footprint.

- Stat messages now reflect the figures for the remailer prior to the batch run. 
  Figures were often distorted before due to the way messages are counted during
  operation.

Version 5.2a

- Updated the stats message

Version 5.2

- Added support for non-PGP messages. It seems to work, but should be considered
  a beta feature.

Version 5.1b

- Bug fix. Adding a new message in the message manager while in the outbox could end
  up with the new message being deleted on exit if any messages in the outbox had
  been deleted prior to creating the new message.

Version 5.1a

- Did some work on the PGP close detection. There should no longer be a delay required
  after the window closes.

Version 5.1

- Deleting messages in the message manager was rather slow. Now messages are marked
  as deleted (removed from the list of messages) and removed as a batch from the 
  actual mailbox file when you switch mailboxes or exit the message manager. Works 
  much smoother.

Version 5.0b

- Added a better password input box (shows **** instead of the characters typed). 

- In the message manager, if you hold down the shift key when clicking on the 
  decrypt button, a password box will pop up. I have an alias or two than comes into
  the remailer, and requires different passwords for decryption. Also, if you decrypt
  a message that has an encrypted message nested within, it will detect this and give
  you the option to decrypt that as well.

Version 5.0a

- The Anonymous-Post-To: function within the nym service was broken. Would not accept
  the pasword as correct, even though it was. This should fix that.

Version 4.9

- There were still problems with extensive cross-posting causing problems with the
  Juno address-length limit of 128 characters. I fixed this for good. As many groups
  as possible are allowed up to the point where the length of the resultant address
  would cause a problem, then any extras are trashed.

Version 4.8

- Added an experimental nym service to the remailer. See the included file 
  NYMHELP.TXT for a basic explanation. This version will send NYMHELP.TXT in 
  response to a message with the subject "nym-help". You may wish to update your
  HELP.TXT to reflect this addition if you will be allowing use of the nym services.

- Made some changes to the way the remailer accepts USENET posts. I suggest blocking
  all mail2news & m2n addresses that require the Newsgroups: header so you don't get
  bounces from them complaining about the messages not having that header. The message
  will still be posted, though it will be through the service you have defined in the
  configuration. I have included these in my destination blocks:

  m2n@alpha.jpunix.com
  mail2news@anon.lcs.mit.edu
  mail2news_nospam@anon.lcs.mit.edu
  mail2news@basement.replay.com
  mail2news@myriad.alias.net
  mail2news@news.demon.co.uk
  mail2news@nym.alias.net
  
  This problem arises when a message is formatted as follows:

  >::
  >Request-Remailing-To: mail2news@anon.lcs.mit.edu
  >
  >##
  >Subject: whatever
  >Newsgroups: alt.whatever

  In the above example, the remailer will attempt to send the message to both the 
  mail2news address AND the newsgroups via the internally configured mail2news server.
  If the server specified in the message is not blocked, it will receive the message
  (as it should), but without a Newsgroups: header (bad thing). Then you get the bounce.

  By blocking these specific server addresses, the remailer will still act on the 
  Newsgroups: specification, and send the message through the configured server, but will
  not send the message to the specified server (good thing). No bounces this way.

Version 4.7

- Opened up the file server portion of the remailer. Make additions as follows to
  REMAILER.INI. In the example below, a message with subject "remailer-info" will
  send STUFF.TXT if it exists in the remailer directory. A path can be specified,
  but it is relative to the remailer directory. Also, maximum message size (bytes)
  can be set so big files are broken up.

    [FileServer]
    MaxMessageSize=59500
    remailer-info=stuff.txt

  The above MaxMessageSize is the default. The help and key commands are build in 
  as before, but can be overridden by providing a specification as shown above. The
  message is failed if the file doesn't exist. No limits are set on the number of 
  specifications you can have.

Version 4.6

- Code refinement & new look

- Message editor update & font choice for edit windows

- Removed auto-block-request code. Requests for blocking need to be handled
  manually (was taking up too much space for a seldom used feature).

Version 4.5

- Message formatting tolorances adjusted (long story).

Version 4.4

- Added source blocking. Works on the From: address, so forged messages will 
  pass unless the From: field contains blocked text.

- Fails messages with a destination address greater than 128 characters in
  length. Juno chokes if the addresses are longer than this.

- The message manager it seems has never been able to display messages with
  no text. Therefore, if you have been running a remailer for a while now,
  you might find your nonremailer folder full of blank messages, since all of 
  those messages will now be visible.

- Manually inserted text files in sysop replies are now searched for the 
  \junoaddress variable so it can be replaced with your juno account.

- Always logs Juno start times, block requests, block confirmations, session 
  stats. Other events logged only if /log is present on the command-line.
  
- Blocks are now based on individual addresses. Used to block all if any of them
  were bad.

Version 4.3

- Added simple pseudo-random message reordering. 

