---------------------------------------
BETANOTE.TXT - Notes for ViaUUCP! v1.00
---------------------------------------

We are proud to announce the opening of the beta cycle for ViaUUCP!.  This
product has been under development for quite some time now and we think
you'll be pleased to see how far along it has already come.  Of course
this is not to imply that the program is complete and ready to ship, but
it is fairly stable and useable at this point in time.

As for the remainder of the features and bug finding, thats where we are
relying on you to help pin them down for us the best you can.


DISTRIBUTION
------------
ViaUUCP! is not a free program, it is copyrighted and encapsulates
thousands of hours of development time and effort.  By using this beta
copy, you agree NOT TO DISTRIBUTE copies of this and any future beta
releases of the program by any means humanly (or otherwise) possible. This
includes being responsible for destroying all outdated versions.


BUG REPORTS
-----------
When you encounter a problem, please send us a message in the beta
conference on the ViaSoft support BBS at (909) 699-2217 detailing the
problems you're having and what we can do to recreate it.  If you're
unsure of a problem, situtation, again, address all messages into that
conference.  Please do NOT leave us message in the Fido WILDCAT
conference.


INITIAL INSTALLATION
--------------------

If you haven't already downloaded the latest evaluation copy, please do
so.  The files in this archive are only the registered ones so you'll need
to have a complete install FIRST before copying these files over the top of
your eval install.

The file is called VUBETA-x.ZIP (where x= version letter).  It's available
from the ViaUUCP! general files area.


SATELLITE SYSTEMS
-----------------
Something that you should make note of is for those of you that pick up
your news from the satellite, you should define that domain type as:

                             UUCP RecvOnly

This is important because if you don't, messages will get forwarded back to
that domains outbound directory.  For replies to go back to the appropriate
provider, simply toggle on the selection of the appropriate newsgroups.
This type has a generic meaning in that you "Only-Receive" news/mail from
their system and not send anything back.


PRODUCT DEVELOPMENT
-------------------
As has been previously mentioned, ViaUUCP has been under development for
quite some time now.  It has been designed around both PageSat and Planet
Connects satellite delivery services and thus have been put through the
rigors of the "fire house from the sky".  This means ViaUUCP! can handle
both batched rmail and rnews messages simultaneously without skipping a
beat.

You should also note that ViaUUCP! can now put these files into both DOS
and UNIX based compression formats including GZIP.  Please be careful of
using a DOS compression program when sending replies back to a UNIX
provider.  Chances are very good, they won't know what to do with it.


COST ACCOUNTING/LOGGING
-----------------------
We've already activated the cost accounting mechanism, so you should have
fun playing with it.  We've labeled it with both In/Outbound modes, so
please make note of that.

In the past, we've learned that it always helps both the customer and the
developer to have a good set of logging information to work with.  So,
we've gone ahead and put in some of the most extensive information you'll
see for quite some time.  After you get the hang of the program, you're
going to want to turn most of that stuff off by using the Log File Options
selection from the general Information screen in VUCONFIG!.  When reporting
bugs, please reference the exact message and also make note if there were
any entries placed in the ERROR.LOG file in the \VU10 directory.


EXTERNAL MAILING LISTS
----------------------
Using the TO: address (l-games@viasft.com) of the email message, external
mailing list definitions in VU are setup as follows.  First add the
'l-games' name in the Master List of Newsgroups database (From the Main
Menu in VUCONFIG). Then, add the 'l-games' portion of the address in the
AreaName field when defining a Newsgroup and be sure to specify the
newsgroup type as External Mailing List.

Then the full address 'l-games@viasft.com' should be specified as the
Moderators address.  This is where the replies will be sent to (via the
domain name in the 'Send Replies To' field).  Fairly simple.


EMAIL/QWK GATES
---------------
With ViaUUCP! comes a rather interesting feature that allows you to specify
a complete domain name an have all email messages sent to that domain
appear into a regular conference which their system can call yours using
some form of QWK program (such as wcMAIL).

In the message base on your system, the TO name field in the message
will be name pulled from the address (depending if a translation is active
or not) and the from name will be who it came from. Now the only person
that should have access to this conference on your system is whoever is
going to pick up QWK mail that is destined for that system. Then once that
system processes their QWK packet, those messages will be available to
callers on their system.

What this does is allow you to have other BBS's in your area to send and
receive email with your system using typical QWK mail programs (such as
wcMAIL) using the above addressing scheme.  Along with this comes a
complete mechanism for cost accounting as well as notification of account
balances.  This is something that people have requested for quite some time
and it's our hope that it satisfies the need to "sell" email accounts.


RELIABILITY/RESPONSIBILITY
--------------------------
Since this a completely new program, until it's been proven by YOURSELF to
be 100% stable and operational, you should NOT RELY COMPLETELY on it!
This is PARAMOUNT because ultimately YOU are responsible for your actions
and the last thing you need to do is to cause yourself problems.

However, if you find something SERIOUSLY wrong, you should contact us
voice IMMEDIATELY by dialing:

                            909-699-2215

and ask for Joe Martin.  We are confident we can resolve the problem
almost on the spot and can get you a new version very, very quickly, but
you NEED to let us know about it!


WHAT'S LEFT TO FINISH
---------------------
In the initial release, complete Email, newsgroup and FTSC echomail gating
cost accounting, external mailing lists, internal mailing lists, % Hack
rerouting is all operational.  The following will be completed shortly:

         Feature                              Completion Date
         ---------------------------------    ---------------
         UUDECODING Files                        Friday


FILE ATTACHMENTS
----------------
In the initial release of ViaUUCP! we've intentionally left out attempts at
putting in UUDECODING/ENCODING of files so we can get your feedback in
this area.  What we need is a BUNCH of email messages (batched newsgroups)
to test with.  This is a very complicated process and didn't want to let
the development cycle get bogged down with it.

So if you would be so kind as to archive up some uuencoded messages that
are 100% complete (THESE MUST BE 100% ORIGINAL) and upload them to the
support BBS, we can go over them.  We are aware of the critical nature of
"needing" file attachments (FTP requests) and will do everything we can
to make this mechanism as reliable as possible.


INSTALLING UPDATES
------------------
In order to install the latest beta version, simply copy over all the
files from the beta VUBETA-x.ZIP archive over your existing *.EXE,
*.OVR and *.HLP files (in your \VU10 directory)

08/21/95 - v1.00m
-----------------

  1)  When replying to a Newsgroup message, if you put the full
      internet address on either of the first two lines of the message
      body, ViaUUCP! will extract it out as an Email message and send it
      to that address.  For example:

                 To: j.martin@viasft.com (Joe Martin)
                 Subj: This is the replacement subject line

      The usage/formatting of the To: and Subject: lines follow the
      exact same conventions as the usage on a Email message including the
      fact that they will be removed from the message body prior to
      transmission.  As shown above, you may also override the Subject:
      line (via the Subj: keyword) as well.

      This is a highly requested feature allowing you to do a direct
      Email response to a Newsgroup message by simply adding the 'To:'
      line in the message body.  If cost accounting is enabled, the Email
      account for the appropriate user will be deducted accordingly.

  2)  When adding messages into WILDCAT!, changed the 'From:' field to
      contain the complete domain address.  This permits the [R]eply
      option to automatically contain the correct To: address.

  3)  Reworked the Duplicates database so that messages extracted as well
      as those forwarded/tossed will be properly maintained.  Please keep
      an eye on this as it has been extensively reworked.

  4)  Fixed a problem when messages were added to an internal mailing list
      they would NOT get extracted and forwarded to their respective
      subscribers.

  5)  Included a program called UUEDIT! which allows you to edit a Unix
      formatted file (D/X file) and save it correctly.  Simply use

                         UUEDIT <filename.ext>

      and to save change press [F10] and [ESC] to abort.


08/17/95 - v1.00l
-----------------

  1)  Completed creating VUUTIL!, the database repair program for ViaUUCP!.
      This program needs to be run from the \VU10 home directory.

  2)  During the development phase of VUUTIL!, a problem was found in the
      Master Newsgroup List database whereby VUUTIL! will delete nearly
      all of the entries.  This problem was a direct result of a bug in
      VUCONFIG! which has now been fixed.

      Therefore, it's recommended to delete a file called UUNLIST.DAT and
      VUCONFIG! will recreate it whenever you attempt to access the Master
      List database.  If you don't use the 'l' release (or later) versions
      of VUCONFIG!, you will continue to experience this problem.

  3)  Added ALT-F nearly everywhere inside of VUCONFIG!.

  4)  Cleaned up the missing F10-Save prompts on the Status Bar line in
      VUCONFIG!.

  5)  Added hotkey searching in the [F2] Pick WC Conf, Pick WC File Area
      and Last Extract picklists.  While in these lists, you may type
      a search string and the list will attempt to find it character by
      character.

  6)  xxxxSERV messages were being bounced back even though they were
      properly addressed to your system.  Fixed.

  7)  Response messages from xxxxSERV requests are now properly routed back
      to the local domain without having to go to your service provider
      first.

  8)  Fixed RT201 error on a blocked message.



08/09/95 - v1.00k
-----------------

  1)  Added additional checking when scanning Email out (for last extract)
      values.

  2)  When bouncing messages, if the Sender: header line is found on the
      original message, that address will be used instead of the address
      on the From: line.  This should help the issue a bit with the
      bounced mailing list messages.

  3)  Added support for forwarding Email messages extracted from your
      message bases as well as those from other domains (in the Domains DB)
      onto the respective domain without having to go to your service
      provider first.  This is a fairly extensive amount of work, so I
      would appreciate it if you can give it a thorough workout.

  4)  When local messages are 'blocked', the resultant message will now be
      added to the 'blocked message' conference.

  5)  Added a new header line called Cc: into VUCONFIG!  You may now
      control this line via Message header processing on the messages
      that get added to WILDCAT!.


08/08/95 - v1.00j
-----------------

  1)  Fixed a problem where using SNEWS or SMAIL, the last message that was
      entered by a human would be extracted out a second time.  Please
      spread the word around about this one as I'd like to get this beta
      version out to as many people as possible so we don't have any
      more complaints.

  2)  Fixed a problem where certain addresses in the message headers would
      appear in all upper case.

  3)  Added support in VUCONFIG! for deducting credits from the 'Billing
      Credits' field in the Users record (for wcBILLING) when charging
      a user for messages.

  4)  Added a new option in the User name translation (Under Mailer-Daemon)
      options.  This option will allow you to 'block' a message that is
      sent to a particular user name such as FTPMAIL, LISTSERV etc.

  5)  Added a new date option under General Settings.  You now have the
      ability to specify whether the date the message was created gets
      put into the message header when the message is added to the message
      base or the date/time of toss will be used.  This option has been
      requested to handle the wcPACK issue of keeping mail for nnn days.

  6)  Added the ability to handle Global change of message censorship
      options on the newsgroups.

  7)  Added support for ViaPAGE!.  This program will send page requests
      to users of your BBS on their pocket pagers informing them they
      have new Email waiting for them on your BBS.

      We are just now beta testing this program and if you'd like to
      help us test it, please contact Joe Martin at 909-699-2215 and
      he can set you up.

  8)  Updated the [F1] online help for the above newly added options.  If
      you're interested in how they all work, press [F1] accordingly.


07/11/95 - v1.00i
-----------------

  1)  Reset expiration date to 7/30/95.

  2)  Finished up the online help in VUCONFIG!.  There's still a few
      typo's, so don't get too excited.

  3)  Cleaned up some of the ActiveDef tests on program startup.

  4)  Work has now started on the install program.  Should have that
      complete by 07/12 in the evening.

  5)  Targeting 07/12/95 in the evening as the release of the 1st 30
      day eval 'beta'.  Because of this, we'll be phasing out the beta
      file area and opening up the beta conference to the general public.

  6)  In the future, look to see the beta releases available through the
      Main Menu option [R]..Registered Products (RegDoor).


07/07/95 - v1.00h
-----------------

  1)  Seems like awhile since the last release.  As many of you know, we're
      busy writing the documentation and during this time period we've been
      letting the bugs float to the surface.  In between doc updates,
      we'll address the 'floaters'.

      We're going to be opening up the beta version to the general public
      via the use of the 30 day eval keys.  I'm not convinced we've gotten
      all the bugs identified, so this should help tremendously.  We are
      targeting a Wednesday release (07/12/95) for the 30 day eval, so
      please pass the word around.

  2)  Added disk space checking into VUCONFIG! under General Information
      as well as in VU.  You should press [F1] on this option for specific
      details on how it all works.

      HOWEVER, upon the initial install of this version, you MUST go back
      and re-edit the individual drive settings.  This is due to the fact
      that a portion of the data record has been 'reclaimed' and it had
      old information in it for another purpose.  This is a one-time beta
      type thing.

  3)  Added in [F1] help for the UUCICO setup, adding User cost accounting
      help and miscellaneous other help topics have been updated.  Work in
      continuing in this area.

  4)  Added support for both Email and Newsgroup message 'blocking'.  This
      is done based upon the users account balance in WC.  For specifics
      on this, please refer to the [F1] help for User Cost Accounting.

  5)  Added code to wrap long header lines a bit more efficiently.

  6)  Removed the 'requirement' of the Subject: header line to be
      found in the Email message.  This should help folks out there with
      the LISTSERV messages.

  7)  Email from downlinks was being bounced for 'unknown system'.  My
      preliminary tests say this is now working fine, please test this for
      me!


06/21/95 - v1.00g
-----------------

  1)  Enabled the PROCSERV features.  Please refer to PSERV.HLP for
      specifics on how to use this.  I have temporarily forced the 'full
      screen' mode of the swap.  I may not be able to offer 'window'ed.
      But time will tell.

  2)  Be sure and copy the DISP.ZIP into your WU40\TEXT directory and
      uncompress it.  The display files have been updated.

  3)  You MUST delete UUPROC.DAT file.

  4)  Added PSERV.HLP and PSERV.HDR files under PROCSERV in Mailer-Daemon
      Configuration.  You should go back and verify the names are correct
      as the WILL BE WRONG INITIALLY!.  This is a one time change (I nixed
      the .NA files on both NEWSSERV and FILESERV).


06/20/95 - v1.00f
-----------------

  1)  Thanks to the database files supplied to me by Jim Wooddell, I
      believe I have the lockup issue put to bed.  I found a problem in
      formatting of the header lines where the line did not contain
      characters that VU would use to 'split' the line upon and thus
      would end up in a endless loop.  Roger and Allen, please re-enable
      your header line stuff and let's see if we continue to have any
      more problems.

  2)  NOTE:  You MUST DELETE UUXUSER.DAT file and re-enter your user name
      translations.  A problem was found there and if you don't do this,
      then translations won't be reliable.

  3)  You must also DELETE UURESPON.DAT as well!  This is crucial
      folks!

  4)  Enabled the INFOSERV features.  Please refer to ISERV.HLP for
      specifics on how to use this.

  5)  Be sure and copy the DISP.ZIP into your VU10\TEXT directory and
      uncompress it.  The display files have been updated.


06/19/95 - v1.00e
-----------------

  1)  Fixed a last remaining issue of detecting corrupted email headers.
      (I hope this one's put to bed)

  2)  Added 'Delete .X queue file' option to the domains definition.  This
      option allows you to save the contents of the XQUEUE.DAT file in the
      domains work directory in order to reprocess *.SVN files.  For
      specifics, use [F1] on the option.

      NOTE:  You SHOULD change this setting to Y ASAP, otherwise the file
             XQUEUE.DAT file will remain and build in size!

  3)  When appending signature lines to the message, the output
      buffer was not always being terminated.  This caused the
      'garbage' at the ends of certain messages.  Fixed this.
      Roger, please verify it for me.

  4)  Finished up adding in the NEWSSERV functions.  You should check the
      contents of the NSERV.HLP file for specifics on how it all works.
      I would like you folks to look closely at this one.

  5)  Updated the display files found in DISP.ZIP.  Be sure and copy these
      over the top of your existing ones in your \WU40\TEXT directory.

  6)  Added a new option to the Domain definition called 'Password for
      NEWSSERV msgs'.  This is part of the verification process required
      before NEWSSERV will process messages.


06/18/95 - v1.00d
-----------------

  1)  Fixed Ooops bug with unbatched Email messages being detected as
      corrupted. (I forgot to uncomment some code, sorry!)

  2)  Added mailing list subscription 'template' file.  This text file may
      be used for all of your mailing lists.  Please read the online help
      for this option under Mailer-Daemon Configuration settings.  This is
      a very powerful tool.

  3)  Extensively updated the .HDR and .HLP files for LISTSERV and
      MAILER-DAEMON.  Please uncompress the DISP.ZIP file into your
      \WU40\TEXT directory overwriting your original files!  You should
      review the contents of these files by pressing [ALT-E] on the
      appropriate one from the Mailer-Daemon Configuration screen.

  4)  Added support for automatically splitting the xSERV type response
      messages in order to handle the upcoming NEWSERV processor.

  5)  Added a large amount of Online Help [F1] for the Special Domains
      database as well as the Mailing List and Subscriptions database.
      Read it over!


06/16/95 - v1.00c
-----------------

  1)  Changed the way VU determines rnews/rmail.  Lets see if this takes
      care of you folks.

  2)  CAUTION!  Due to changes made to the Mailer-Daemon, you MUST DELETE

                UUSIG.DAT    (Signature lines database)

      There were a couple of options added such as remote modify and
      password that caused the data file format to be changed.  DON'T
      FORGET TO DO THIS!

  4)  Fixed a potential lock up problem.

  5)  Activated the new Mailer-Daemon.  Included with this release is a
      file called DISP.ZIP.  You should create a sub-directory:

                              C:\WU40\TEXT\

      and uncompress DISP.ZIP into it.  You should then make the following
      changes to show the new display file paths:

       MAILER-DAEMON Configuration 

      Help information file          : C:\WU40\TEXT\DAEMON.HLP
      Header text for response msgs  : C:\WU40\TEXT\DAEMON.HDR
      Conf num for xxxxSERV messages : 102

       LISTSERV Configuration 

      Help information file          : C:\WU40\TEXT\LSERV.HLP
      Header information file        : C:\WU40\TEXT\LSERV.HDR
      Option not available file      : C:\WU40\TEXT\LSERV.NA

       FILESERV Configuration 

      Help information file          : C:\WU40\TEXT\FSERV.HLP
      Header information file        : C:\WU40\TEXT\FSERV.HDR
      Option not available file      : C:\WU40\TEXT\FSERV.NA

       INFOSERV Configuration 

      Help information file          : C:\WU40\TEXT\ISERV.HLP
      Header information file        : C:\WU40\TEXT\ISERV.HDR

       NEWSSERV Configuration 

      Help information file          : C:\WU40\TEXT\NSERV.HLP
      Header information file        : C:\WU40\TEXT\NSERV.HDR
      Option not available file      : C:\WU40\TEXT\NSERV.NA


      Once you've done this, you should delete any old display files you
      had in the old (VU) directories.  The mailer-daemon will now allow
      your users to change their signature lines via an EMAIL message
      (from your email conference) and will make the change and send the
      response back to them in the email conference.  Pretty slick.

      Quite a bit of this documentation will be performed on the weekend,
      so look to see a fairly polished set by Monday night.

  6)  Changed the directory structure a bit.  PLEASE keep an eye on this.
      VU will now run from a subdirectory other than x:\WU40.
      This has not been fully tested yet, so beware!

  7)  Removed the 'Work directory' path option.


06/14/95 - v1.00b
-----------------

  1)  Fixed a problem where the C line of the X file would be:

                     C rmail joe.martin%joesbbs

      ViaUUCP! will now append your main domain name to the end of it
      similar to:
                     joe.martin%joesbbs@viasft.com

      This fixes the problem for systems using 'global' as their service
      provider.

  2)  Cleaned up the FTS Email/Netmail gating code.  This should
      be a bit more efficient.

  3)  Fixed a problem with internal/external mailing lists.  Please check
      these out!

  4)  Put a bandaid fix on email messages that contain Newsgroups: header
      lines.  These were coming from Global (a service provider).  ViaUUCP!
      will now make the determination upon the presence of a To: line.

  5)  Added in the Listserv stuff.  Yes folks it now works.  Due to my time
      table, I won't have a list of commands available, but look to see
      that in a message tomorrow.

  6)  Removed all the command line parameters except TNEWS, TMAIL, SNEWS,
      SMAIL.  Added a new one to replace the other Listserv type command
      line parameters with one that combines them all into one called
      XSERV.  This XSERV will look for a file called XSERV.FM in the WU40
      directory and process the messages from there.  This file contains
      all the Newsserv, Listserv etc type messages in it.  This makes it
      very simple to manage.

  7)  There will be a number of file name and directory path changes coming
      up in the next release.  This is a result of the Listserv stuff and
      the over all XSERV type processing.

  8)  Added a ton of online help.  You should review the mailing list and
      subscriptions database screens for this new information.  It also
      contains the commands that Listserv uses!  So use this to test the
      Listserv out with!

  9)  Made numerous changes to VUCONFIG! to support the new changes for
      Listserv.

 10)  When VU encounters a netmail message that gets blocked, it now sets
      the RECEIVED flag to prevent future attempts to process it.

 11)  Recompiled IndexNL! to support the new Domains database structure.


06/11/95 - v1.00a
-----------------

  1)  Fixed a problem where only the first name would be found in the
      translations database on messages extracted from your system.

  2)  Added support for Gated domains and Sub-Domains to 'force' a % Hack
      as the from address.  This resolves problems with service providers
      that don't recognize sub-domains off your your system.

  3)  Tied in the FTS message blocking.  All of the [F1] help is available
      to explain how this all works.  Please read it.  The only portion
      that does not work is the 'Hold' aspect.  I'd like to have your
      thoughts on this one before I code it.  This was a major effort, so
      please play with it.


06/08/95 - v1.00z
-----------------

  1)  Oops.  Seems in all my ernest to make the sub-domains work properly,
      I inadvertantly broke the email destinated for YOUR main/aka address.
      Fixed.

  2)  Fixed a problem where the .D/.X files were not being unmunged
      correctly.  Something worth making note of is that the name which is
      specified in the UUCP name field of the domain definition is what is
      used on BOTH the inbound and outbound file name munging.  If this
      name doesn't match that of the last name on I line of the .X file,
      then the .D file won't be recognized/determined properly.

  3)  Added code into VUCONFIG! allowing you to specify message blocking
      for FTS gated nodes.  Have a look at it and offer your input, it's
      under Mailer-Daemon setup.  It's not completely tied in yet but can
      give you a good idea whats coming.

  4)  Added a new field to permit the use of % Hack address format as the
      'From' address on outbound messages.  It's not completely tied in,
      so wait until next release for specifics.

  5)  This release is mostly a quick fix for the #1 and #2 bugs that
      cropped up.  So the new stuff thats been added, hang in there until
      the next release and most all of that will be finished.


06/07/95 - v1.00y
-----------------

                    DANGER, DANGER, WARNING, WARNING!

Do I have your attention?  <g>...  This release represents a STRUCTURE
change REQUIRING you to DELETE some files and re-input that information.
In order to keep your UUNEWS.DAT/IX (Newsgroups database files) completely
intact, follow these steps TO THE LETTER!

  a)  DO *NOT* COPY the new VUCONFIG.EXE/OVR or VU.EXE/OVR files into your
      \WU40 directory.

  b)  Run VUCONFIG! (the 'x' or earlier version) and under Domain Address
      Management, print off all of the screens that contain all the
      settings for each of your domains as well as your Sub-Domains.
      You'll need this later to re-input it.

  c)  Delete all of your domains from the domains database.  This will
      instruct VUCONFIG! to automatically unlink all the selected
      newsgroups.  Exit from VUCONFIG! and return to DOS.

  d)  From the \WU40 directory, delete the following files:

                        UUNODES.DAT/IX
                        UURESPON.DAT/IX
                        UUSUBDOM.DAT/IX

  e)  Copy the NEW 'y' release of ViaUUCP! into the \WU40 directory.

  f)  Run VUCONFIG! and reenter all of your domains and sub-domains.

  g)  CRITICAL STEP:  You will need to use the global modify newsgroups
      option to re-establish all of the 'Send Replies To: fields, all of
      the From Addr: fields and ALL of the settings from General
      Information screen to Gawd knows what else.  ANYTHING that has a
      Domain, Subdomain or address it it needs to be visited and re-saved.

  h)  Go back and reselect all of the newsgroups on a per domain basis.

  i)  When inputting ANY DOMAIN OR SUBDOMAIN ADDRESS, you must now use the
      standard DNS format similar to:

                          joesbbs.viasft.com

      Any sub-domain definition, MUST also include your main domain name
      similar to whats listed above.  This is CRUCIAL.


WHAT HAPPENED

I imagine you're wondering why this all took place.  Simple.  The entire
mechanism that we had in place for auto-mapping of primary/AKA domain names
has been replaced by a more rigid and 'exact' domain naming scheme.  This
is why you must include your main domain name when specifying sub-domains.

I have been trying to make it all work using the original flexibility, but
we conceded that since people were determined to enter the complete
address (subdomain and domain name) together, regardless of what you told
them, we knew we would be in for a big tech support struggle.

Because you folks represent a sample of the future users of ViaUUCP!, we
felt it would be better to give in and not fight it.  The old way provided
some rather nice abilities, but we could never exploit them enough because
it would take to long to "teach" everyone the rules.

The nice part about this is that % hacks, bang paths and DNS format will
now all work 100% everywhere.  Even in the Netmail/Email aspects.  (Steve
B, you own me one for this!)  So the Domain name fields had to be extended
from 25 characters which required index key changes etc.

We appologize for the extra effort required on your part, but I think in
the long run you'll appreciate the design change.

CHANGES

  1)  Added more online help information for the Sub-Domain and Name
      translation options in VUCONFIG!.  <whew>  Please make GOOD use of
      this when you re-enter your definitions.  Quite a bit of good
      information has been added here.

  2)  Fixed the weird log entries in ERROR.LOG.  (At least I hope I did).
      This was toughie to kill.

  3)  Please remember any subdomains MUST now be setup in DNS format, no
      more bang path formats.  VU will handle the inbound bag path, %
      hack and DNS formats just fine however.

  4)  % Hacks, Bang paths and DNS formats are now supported on
      inbound/outbound netmail/email messages.  (Don't know why you'd want
      to use bang paths though)

  5)  Now that I've rewritten that, I think I'll get back to the Listserv
      stuff.  PLEASE people keep a very close eye on this.  The entire
      email addressing side of things has been changed, so before letting
      mail 'just go' to your service provider, check it first!


06/04/95 - v1.00x
-----------------

  1)  Fixed the reversed address issue with the gated PKT files.

  2)  Updated the online help to reflect same.


06/03/95 - v1.00w
-----------------

  1)  Fixed a problem with the censor that if you specified a replacement
      string that was part of the original string, VU would go into an
      endless loop trying figure out what to do.

  2)  Added online help [F1] to all the censorship options.

  3)  Fixed a lockup problem associated with signature lines being added
      to outbound email messages.  Please keep an eye on the lock up issue
      as this is a very elusive problem and often times extremely
      difficult to pin down.

  4)  Finished up the preliminarys of the Email to Netmail side of things.
      You are free to try it.  Quite a bit of energy has gone into this and
      the ONLY format that email messages addressed to your gate which will
      be supported is:

             j.martin%f602.n207.z1.fidonet.org@fidogate.isol.com

      Using the above definition, the gates domain name MUST be

                              fidogate

      And your address (isol.com) can be ANY of your AKA's or main domain
      name.  If you follow the above steps, it will work for you.  Do NOT
      use:
                           fidogate.isol.com

      as the gates address because this will NOT work!

      I have spent hours and hours trying to support the other formats only
      to find myself reinventing the wheel.  This is because ViaUUCP!
      thinks the fidonet or any other network is a sub-domain off of the
      gate. This is done to ensure that response messages (replies) come
      back through your system and not some other gate.  This benefit alone
      justifies the use (at least to me!)  Thoughts?

      NOTE: In the above example, you should substitute your domain address
            with 'isol.com' and your gates domain name (Pick something for
            now, NO spaces) should replace 'fidogate'.

  5)  Added about 80 percent of the Domain Definitions online help.  Please
      refer to this when using the Netmail/Email gating.

  6)  Found a problem with the subdomains database in that the definitions
      were being stored as lowercase when the checking was being done in
      upper case.  Please go back and edit every sub-domain definition and
      make sure you move the cursor (Green highlight bar) PAST the site
      name field followed by pressing F10.  If the definition was saved
      correctly, you will see the Sub-Domain names now appear in uppercase
      in the browser.

  7)  I have been all over the Email addressing scheme of this release, so
      PLEASE be on the lookout for weird problems.  If they were to occur,
      now would be the MOST likely time.

  8)  Once we've proved the stability of this release, we'll look into
      the possibity of using 'mapped' fido names.

  9)  Added the ability to pick and choose the flag settings on the Email
      messages that get gated to Netmail.  This should satisfy the majority
      of people <fingers crossed>.  See VUCONFIG! for this one.

 10)  Numerous shuffling of the fields in the Domain Definition in
      VUCONFIG!  This was for better organization.


05/30/95 - v1.00v
-----------------

  1)  Added a new option called Censorship to ViaUUCP! (we'll call this the
      ALLEN CARY option).  This option allows you to change dirty words to
      those not-so-dirty on both the inbound and outbound newsgroup
      messages.  This option ONLY affects messages that are physically added
      to your message bases.  Any messages forwarded (ones that did NOT
      originate from your system) will be left completely in tact.  No
      censorship is done on Email messages.

      On the Gen Info screen in VUCONFIG! you will notice there is a two
      new options there.

           Enable message censorship: Y
           Censored by: message     : xxxxxxxxxxxxxxxxxxxxxxxxx

      NOTE:  Because previously used space in the UUCONFIG.DAT file was
             used for this option, you MIGHT have to use Ctrl-Y on the
             Censored by: field to clear the '@' characters.  This is one
             time thing which will only be found in this release so not
             to worry.

      Enable message censorship is a global option allowing you to specify
      on a per newsgroup basis whether or not ViaUUCP! should check bot
      inbound and outbound newsgroup messages for words or phrases found
      in the Censorship database (On the Main menu in VUCONFIG!)

      Censored by: message is a line that you can define that will be added
      to the beginning of each message that has been censored (changes
      were made).  This is a subtle reminder to the reader thats it's been
      modified by an external source.  If you don't want that line to
      appear, simply leave it blank.

      Now on the Main Menu option Censorship Management, in the typical
      fashion, you may add, delete and modify word or phrase definitions to
      be searched for and replaced by.  You may use a single word such as
      the common 4 letter ones, or entire sentences to be searched for.
      When specifying sentences, bear in mind that the entire sentence
      will be searched for, not the individual components of the sentence.

      You have a choice as to how the matched word will be modified.  You
      may replace the string with a new string or replace it with
      *******'s characters..  Your choice.  The stars method is recommended
      for speed reasons.

      As a side note, when censored messages are added to the message base,
      they will have their line lengths verified and wrapped accordingly.
      But this is ONLY for that current line.  The entire paragraph will
      not be reformatted.  This follows the current method.  Now on the
      extraction of messages, if you tell VU to save the changes to the
      message base, then NO FORMATTING will be performed at all.  The
      word(s) are simply replaced.  This is another good reason for using
      the "Replace w/Stars" option as it won't affect the format of the
      message.

      Now on the newsgroups definitions, you have two new options as well.
      One to allow the censorship process and another one to allow you to
      save the censorship changes BACK TO THE ORIGINAL MESSAGE in the BBS.
      Yes you read that right.

  2)  Added new option to allow you to specify how many Newsgroups will be
      processed on the TO: line of the newsgroup message.  Due to the
      number of people cross-posting messages, this option can be enabled
      on a domain by domain basis allowing you to limit the number of
      "allowed" cross posts.  This option has a limited purpose, but if it
      suits you, by all means, use it.  It may be found in the Domains
      Database when modifying a domain definition.

      A value of 0 and 50 means unlimited number of newsgroups can be
      processed (limited to memory of course) and value between that range
      is the number to be enforced.

  3)  Added more of the Email to Netmail stuff in, but it's not complete.
      Please refrain from discussing it until it's completed.


05/29/95 - v1.00u
-----------------

  1)  When scanning out mail from a QWK mail conference, your primary
      domain was used as the from address.  This now reflects the
      sub-domains (and your domain) combined addresses.  Small oversight
      on our part, sorry.

  2)  Fixed a lockup problem in ViaUUCP! when using the Reset Last Extract
      option in VUCONFIG! and then immediately running VU SMAIL.

  3)  Something that was not mentioned in the 't' release regarding the
      To:/Subj: keywords in the first two lines of the message body was
      that whatever is allowed in those lines is also allowed in the
      messages ORIGINAL To: line as well.  This means you can put names in
      parenthesis etc.

  4)  Added new option in Domain Management in VUCONFIG! called Kill
      processed .MSG files.  This is used to delete the message (.MSG file)
      after the conversion from netmail to Email has taken place.  This
      keeps your netmail directory in check.

  5)  Rearrainged a number of options on the Edit Domain Definition screen.

  6)  Added support for inbound netmail messages to be gated to the
      internet.  For this to work, the basis premise is this, .MSG files
      in the netmail directory will be scanned for the following:

       a)  Destination address the same as the gate's Primary Address.

       b)  TO: name on the message matches that defined in VUCONFIG! for
           that gate.  (Edit Domain Definition Screen)

       c)  Received flag has NOT been set (Message Status).

      If all three conditions are met, the message will be loaded in and
      after the address has been qualified (with the INTL, TOPT and FMPT
      lines) the first line of the message is then interpreted to see if
      it contains the traditional:

                     To: j.martin@viasft.com (Joe Martin)

      destination system.  Notice that you are allowed to specify the real
      users name in parenthesis as shown (if desired).  If the message is
      completely intact, it will be converted and added to the domain
      listed in the "Send Replies To" fields EMAIL.TO file for later packing
      and/or DAT/XQT file creation.  The resultant Email message will not
      contain this special To: line or any of the ^AINTL, ^Axxx lines that
      were previously in the message body.

      NOTE: Please make sure you've specified domains in BOTH the Send
            Replies to as well as the From address fields.

      Once the message has been gated, depending on the setup, ViaUUCP!
      will do either of two things.  Set the "Received" on the .MSG file
      (so it won't be processed a second time) or delete the .MSG file
      altogether.  See "Kill netmail after processing" option.

  7)  PLEASE MAKE NOTE:  In order for the Netmail to Email conversion to
      work properly, in addition to the above guide lines, please be sure
      you are using a REAL domain style name in the Domain Name field of
      the Gate definition.  It must NOT contain any spaces and will be
      considered a "sub-domain" off of your system.  So the appropriate DNS
      system name specifications apply.

      This important because of you look at the resultant Email message,
      you'll note that the from address has this gates domain definition
      as a subdomain off of the selected From address of your domain name.
      This might sound more confusing than what it is, but you should
      check the resultant messages FROM: line to see what I'm referring to.

  8)  Activated support for verifying the origin address of the message (in
      that gates nodelist).  If the option to verify is turned on and thwe
      address doesn't exist in the nodelsit, the message will not be sent
      as indicated in the log file.

  9)  The next release will have the Email to Netmail msg conversions.


05/27/95 - v1.00t
-----------------

  1)  Created a new program called IndexNL!.  This will be used to compile
      your standard nodelist file(s) into a format usable by ViaUUCP!.
      The resulting file called NDLIST.IX will be located in the "gated"
      node work directory and will be used (if so configured) to verify
      the from/to addresses on the Netmail messages going thru this gate
      definition.  Each gate has its own nodelist/pointlist combination.

      The compiler keeps track of the date/time of the last run and can be
      overriden with the /F (force compile) parameter so you can run it
      from a batch file right after you've recompiled your mail nodelist
      for your front end mailer.  This program should be executed from the
      \WU40 directory (normally with no parameters) similar to:

                                   INDEXNL

      The reason for the delay in beta releases was due to the fact that
      this compiler is now completely ready for Lynxmail when the time is
      right.  It uses the same basic format (but it NOT ciompatible with)
      as IMNC from InterMail systems and is a fair amount faster than
      their version as well.  The release with ViaUUCP! doesn't have all
      the goodies that the one for Lynxmail will have as it's simply not
      needed.

      Since the Email/Netmail stuff is still not complete, there's little
      need for you to be concerned about it's use (That will change in the
      next few releases tho).

  2)  Made appropriate changes in VUCONFIG! for changes in #1.  When
      specifying the nodelist/pointlist path, typical definitions are:

                  Nodelist : C:\IM\NODELIST\NODELIST.*
                  Pointlist: C:\IM\NODELIST\FDNODE.PVT

      The extensions on the file names may be left blank and the most
      recent version will be used.  When IndexNL! determines which nodelist
      file in that directory is to be used, it will check for a numeric
      extension and the most recent file will be used.  If you specify a
      complete file name (including extension), then only that one file
      will be used.

  3)  Added support for scanning QWK/Email gate conferences.  This is
      automatically included in the SMAIL parameter.  The cost accounting
      has also been activated for the QWK/Gate, so please keep an eye on
      it.

  4)  Added support for the infamous To: and Subj: lines in the first *two*
      lines of the body of the message.  You can mix and match as needed
      and the following rules apply:

          Usage:    To: j.martin@viasft.com (Joe Martin)
                    Subj: This is the replacement subject line
                    Subject: This is the same as the Subj: line
                    Subj:

      A couple of things worth noting here.  First off, upper/lower case is
      insignificant as well as spaces before and after the To:/Subj: lines,
      in otherwords

                    to:j.martin@viasft.com  (Joe Martin)
                    SUBJECT:    New subject line

      will all work.  When defining the To: line, if an optional name is
      found in parenthesis, it will be used on the outbound email message
      if a user name translation is not found (in that case it will be
      replaced). You should also note that you can use both forms
      (abbreviated and long) of the subject keyword listed above.  You may
      also specify a BLANK subject line by simply specifying the Subject:
      keyword.

      As a last note, when ViaUUCP! picks up a 'replacement' To:/Subj:
      line, it will delete the specification from the message body on the
      outbound message (the one in the message base will be left intact).
      This should remove the clutter from the message.  If anyone has
      thoughts otherwise, I'm open to ideas.

      We're quite removed from the QWK mail world here, so if we've done
      something out of the ordinary, SPEAK UP.  <g>...


05/22/95 - v1.00s
-----------------

  1)  Fixed the QEMM #13 errors with the global add stuff.  Thanks to
      everyone (especially Tim) for their patience with this one.  Now I
      can finally go back to the Netmail/Email issue.


05/21/95 - v1.00r
-----------------

  1)  Added new option on the global modify menu in VUCONFIG!.  You may now
      modify the "Last Extract" value on a individual conference.  The last
      extract value is explained above, but now instead of requiring and
      external editor to make changes, you may do so by using this option
      and highlighting the desired conference and pressing [ENTER].  This
      change was made possible by the modifications made in version 'q'.

  2)  Found a problem with scanning messages out of the message bases.
      We'll call this the Jack Haney fix. <g>...  Gawd what a nightmare.
      While the problem had been reported only in Email, it was purely
      coincidence.  This would have truely affected newsgroups as well.
      Jack, please try this and curse me if it doesn't work! (tell me tho)
      Thanks for your patience Jack...

  3)  Sorry about the delay with the Netmail/Email issue, but I've been
      trying to put the above issue to bed for some time now.  Once the DNS
      issue for Steve Burke is put to bed, then normal work will resume.


05/20/95 - v1.00q
-----------------

  1)  Due to a couple of peoples complaints regarding the startup/shutdown
      time of ViaUUCP!, I've gone ahead and completely revamped the way
      ViaUUCP! handles the .MPF file and message paths.  I've tested it here
      on my system with 16,000 conferences and the load time has been
      significantly reduced.  Jack, Angel, have at it!

      Since this drastic change is centered around scanning of email and
      newsgroups messages, please keep an extra careful eye out for any
      anomolies.  I am releasing this with a reasonably short test period,
      so be on the lookout (I just want you folks to play with ASAP).

  2)  Removed the Database Lock Count field and replaced it with one called
      Pre-load message paths.  This option is used inconjunction with the
      changes made in #1.  If you have a large amount of newsgroups, you
      might want to toggle this option to N.

  3)  Started a partial add of scanning out of netmail (to email) messages.
      It doesn't work yet, so don't bother saying anything until it's
      finished.


05/18/95 - v1.00p
-----------------

  1)  Fixed a problem where the address of a converted % hack would be
      incorrect.

  2)  Novell notify now works properly.

  3)  Added support for the newer two letter Geographical top-level
      domains.  These are commonly found on international DNS formatted
      messages.

  4)  Per Steve's request:

                      user.name@joesbbs.paradise.com
                      user.name%joesbbs@paradise.com
                      paradise.com!joesbbs!user.name

      are now considered to be identical.  Special code has been added to
      determine which is YOUR local address when converting/interpreting
      the above formats.  <this stuff hurts my brain>

  5)  In order for this to be properly supported, the sub-domains database
      must have the ENTIRE address entered (less user name).  So for a
      sub-domain off of 'paradise.com' called 'joesbbs', you would specify:

                           paradise.com!joesbbs

      You may enter the addresses in VUCONFIG! in any format desired and
      the automatic translation will take place (you might have to add in a
      user name first and remove it after it gets deciphered).


05/17/95 - v1.00o
-----------------

  1)  This release represents a complete overhaul of the email addressing
      translation (not to be confused with user translation) used within
      ViaUUCP!.  Due to the problems associated with some pretty wild
      combinations that could appear on the C line of the .X file, I
      decided that it was time to make it deal with the world.  So what
      changed you say?

      ViaUUCP! now has a built-in mechanism to automatically convert every
      address into the standard "bang path" format.  This means an address
      like
                           j.martin@viasft.com
      translates to
                            viasft.com!j.martin

      The same applies to percent hacks.  So:

                        j.martin%joesbbs@viasft.com
      translates to
                        viasft.com!joesbbs!j.martin

      What this does is permit a standardization of an address format that
      ViaUUCP! has to ultimately deal with.  This makes my life SOOO much
      easier.  Not too worry though, this doesn't affect you on the outside
      much.  <g>...

  2)  Due to changes in #1, the .X files C line interpretation has also
      been drastically altered.  Here's the new rules...

         A)  If only people(s) names appear, then if the address on the
             messages TO line is not "local", then your primary domains
             address is appended to the end of the users name in whatever
             original format the TO line was in (ie: BangPath of DNS).  If
             the TO line was considered local (one of your AKA's), then
             that address is appended to the users name.  Multiple user
             names are support separated by spaces or commas or any
             combination there of.

         B)  If the address(es) were already a valid unix address, they are
             left alone.

         C)  Any combination of user names, mixed with % hack, bang path
             and DNS addressing schemes are now supported on the same line.
             This should cover just about anything the Unix world can throw
             at us.  So when ViaUUCP! processes the message, if multiple
             address definitions appear on the C line, after the
             conversion process discussed above is complete, it will
             handle each address separately for the same message.

         D)  All the translation process is put into the log file, so make
             sure you have the ^ log option enabled and you'll see what it
             found and what it translated it to.

  3)  Updated VUCONFIG! with the automatic conversion to bang path
      addressing in the various fields.  (You'll know 'em when you cross
      'em).

  4)  Changed the name of the % Hack option to now be called Email/QWK
      Gating.  I feel this is a bit more explanitory and less confusing
      than the % Hack name.  Thoughts?

  5)  Since so much has changed, it's time to very carefully observe
      ViaUUCP!'s reliability and accuracy for the next few versions.  I've
      broken 'er good, so keep an eye on 'er matey!

  6)  Now if you folks leave me alone, I'll do the Netmail/Email gating
      stuff!  <g>...


05/16/95 - v1.00n-1
-------------------

  1)  Some .X files were coming in that only had a user name on them
      (instead of the full address as shown below)

                       C rmail j.martin@viasft.com

      Added code to handle not only this but multiple user names as well.
      So if the C line came in as:

                      C rmail j.martin,m.hart,tim.nelson

      those three user names (at whatever the domain was found on the To:
      line) would receive the message (after translation etc).

  2)  There has been some confusion ever since 'm' where the TO address
      information is now being pulled from the .X file with regards to
      external mailing lists.

      Since most messages come in with a .X file, if the C line contains
      the user name that SUBSCRIBED to that list, then that user will
      receive the message as private email.  This is 100% normal.  Now, if
      you want that external mailing list to be put into a "newsgroup"
      style conference for all to read, then the name on the C line of the
      .X file MUST NOT BE THE USERS NAME.  It must be the name used in the
      External mailing List definition (Area Name field) in the newsgroups
      database.

      The way to make this happen is to have that user unsubscribe from
      that mailing list, and re-subscribe using a ficticious name which you
      will use in place of the old Area Name.  You might even be able to
      have that user subscribe with a user name of the actual mailing list.
      Then ViaUUCP! will properly move that email message into the external
      mailing list definition.

      Now if the name on the C line of the .X file is the actual name of
      the mailing list, then nothing needs to be done.

      The bottom line is simple.  What ever name is found on the C line of
      the .X file is what will be used to create the ultimate TO address.
      So when ViaUUCP! pulls the user name from that address, it's that
      user name that will get checked to see if it's an external maillist
      or a real user.

  3)  When using the % Hack definition in the Sub-Domains database, you
      should specify everything to the RIGHT of the percent (%) character.
      So a full address of j.martin%joesbbs@viasft.com should have a
      definition name (in the Sub-Domains DB) of:

                             joesbbs@viasft.com

      Then any messages with the user name found to the LEFT of the percent
      character (in the above example - j.martin) will be subject to
      translation and the message will be added to the defined QWK mail
      conference in WC. This was previously mis-stated causing you folks
      the confusion.  Sorry about that!

  4)  Fixed the outbound newsgroup translation so that the name in the ()'s
      will now reflect the non-translated name.

  5)  When doing a global add in VUCONFIG!, added support for checking to
      see if WILDCAT! is up and running.  If so, then the process is
      aborted.

  6)  From the Newsgroups database screen, you make now press:

                                  F5-Sort

      to change the sort order of the newsgroups listed.  You can toggle
      between the various settings including displaying the "gated"
      newsgroups.


05/14/95 - v1.00n
-----------------

  1)  This release is focused primarily on VUCONFIG!.  Before running the
      option outlined below, it is imperative to make sure you have a good
      backup of your WILDCAT! data files as VUCONFIG! can now permanately
      alter them.  While VUCONFIG! has been extensively tested here, you
      may not have the same results.

  2)  Added support when doing a Global Add of newsgroups, you now have the
      ability to add to WILDCAT! at the same time.  Quite a number of
      people have requested this and although we said we weren't going to
      do it, well, so we lied!  <g>...  This version encompasses nearly two
      full days of work to get this option added in.  For those of you that
      were waiting for more features in VU, hang in there, we'll get to
      them.

      A new file called IMPORT.LOG contains all the info regarding the
      importation process.


05/10/95 - v1.00m
-----------------

  1)  Fixed the Email Signature lines not being picked up (except for the
      DEFAULT).

  2)  Outbound Newsgroup name translation is now active.  You asked, and
      you got it!  <g>...

  3)  Forwarding from a RecvOnly domain definition will no longer forward
      messages onto the domain that replies should be going through.

  4)  Names found in the C line of the .X file are now being used in place
      of the name/address found on the actual message.  This should make
      certain folks happy, especially those with external mailing lists.

  5)  When #4 was taken care of, I went back through and verified how the
      translations database performs its duties.  Presently, immediately
      after the message header information has been loaded, the translation
      takes place.  This is before any determination (short of being
      destined for your system) it done as to the type of mail it is.

      Now, please read the following very carefully.

      This means you can re-route mail addressed to a user to a external
      mailing list (in the newsgroups database) by creating a name
      translation (to the name of the mailing list) and then it will be
      picked up as an external mailing list and routed to a particular
      conference.

      A number of people expressed an interest in this, and you not only
      got your request, but much much more if you really put your minds to
      it. (i.e. - a specific user can have his own personal email
      conference and so on) <g>... (Who says we don't serve here!)


05/07/95 - v1.00l
-----------------

  1)  Fixed the RT201 error on scanning Email conference.  Added additional
      logging to better distinguish scanning of mailing List conference and
      the Email conference message bases.

  2)  Updated the descriptions (see above) on how % Hacks work and added in
      an explanation for External mailing Lists as well as the UUCP.MPF
      file.


05/06/95 - v1.00k
-----------------

  1)  Initial beta release.
