12/07/93
--------
 CAM-MAIL.EXE
 ------------
  RELEASED version 1.40 of Cam-Mail.
  Added - File attachment support in REP packets.  Please be aware that
          your users must be using an offline reader that supports the
          PCBoard style of File Attachments.  The only ones that I know
          of right now that support this are Camster <g> and RoboMail.
  Added - A new command line switch has been added called /NOCHECK
          If you have a LOT of conferences on your system, you'll find
          that it might take a while for the "Initializing Door.." to
          take place.  What is happening is that the door is checking
          for any public conferences that the user isn't registered in.
          By adding this switch, the door won't check for public
          conferences.
  Added - A new command line switch has been added called /READ
          What this means is that if a user downloads a QWK packet and
          a message is addressed to them, then the READ flag in the
          message is updated.  Some Sysops like this, while others
          don't.  It's simply preference.
  Added - A new command line switch has been added called /NETCONF
          What this means is that if you are a HUB and you want to
          limit the the conferences your NODES have access to (only
          NetStatus Conferences), then add this command line switch
          to your MAIL batch file.
          This will also only create a CONTROL.DAT file according to
          the conferences they have netstatus in.

  Fixed - The Mail door wasn't working properly with the "R" flag set
          in a users account with USERSM.EXE.  It would only work if a
          user had NetStatus.  It should work with or without
          netstatus.  It also would only with if the message had not
          been read by the person to whom it was adddressed to.
  Fixed - Hopefully the problem with the door not working properly
          with time has been fixed.  I was able to get the door to do
          some weird things and finally spotted the potential problem.
          If you were having problems with the door and timelimit,
          please let me know if this fixed your problem.
  Fixed - On the last release I forgot to mention that if a user was
          using an internal protocol, and they simply didn't start
          their transfer, the door would report the transfer was
          successful (opps)..  I fixed it in the last release, but
          thought I had better mention it before I forget (it's been
          bugging me for the last two days <arg>).
  Fixed - The internal protocols didn't work with the Fossil version
          when uploading a .REP/.PTR file.
  Fixed - When someone was uploading a .REP/.PTR file using the
          internal protocols, the door was closing a file twice and
          freeing some memory twice (opps).  This could cause anything
          to happen.  After I had uploaded around 6 .REP packets, it
          locked up my machine <arg>..

09/04/93
--------
 PRESCAN.EXE
 -----------
  Fixed    -  If a user contained more than Two seperate names (meaning
              something like JON DE BUCK), prescan wouldn't work
              properly with PCBoard.

08/17/93
--------
 CAM-MAIL.EXE
 ------------
  Fixed    -  If you had around 8,000 conferences defined in PCBSetup,
              the door would most likely give a out of memory error.
              This should no longer happen.  I've tested the current
              code with 24,000 conferences and it worked just fine.
              Although, PCBSM wouldn't work and locked up my machine
              due to the increase number of conferences.  Time to give
              Clark Development a phone call <g>.

08/12/93
--------
 CAM-MAIL.EXE
 ------------
  Fixed    -  When uploading a REP packet, it was possible that the
              door might end up doing WEIRD things when a message was
              REJECTED.  This was because I wasn't updating the number
              of message blocks <arg>.

  Fixed    -  In the new code that supported file attachments, I was
              going out of my index array.  This basically would carry
              over into the next variable (which wasn't anything too
              important, but one never knows what might happen).

08/11/93
--------
 NETSM.EXE
 ---------
  Added    -  You can now define in each conference whether PRIVATE
              MAIL should be echoed.  The default is NO.

 EXPORT.EXE
 ----------
  Modified -  The program will now work with Private Mail.  I also
              changed the program so GROUP/SENDER Passwords would not
              be echoed.  Also, COMMENTS to the Sysop cannot be echoed
              as well.

08/09/93
--------
 IMPORT/EXPORT.EXE(S)
 --------------------
  Modified -  The tosser of Cam-Mail has undergone some BIG changes.
              Basically, the tosser will not import messages unless you
              have NETSTATUS.

              Also, when checking for Duplicate messages, the old
              version of the software created a file called CRC.DAT.
              The program now creates a file called bbsid.CRC (where
              bbsid represents the name of the QWK packet(s) that you
              are inserting).  This will allow for the program to keep
              smaller CRC files for each network and will make sure
              that messages are being imported from each network.  Some
              people post the same message in several networks.
              Although the chances of a message not being imported
              between different networks is very unlikely, this is
              definately the better way to go.

              To tosser also now puts the version number on the tagline
              to avoid any problems with networks that want a version
              number on the tagline.

08/05/93
--------
 CAM-MAIL.EXE
 ------------
  Fixed - Opps...  The door was sending file attachments *IF* a user
          had the necessary security level AND there was a file
          attached to any message (this includes messages that the user
          didn't even have in their packet).  Basically, the door was
          sending file attachments when it wasn't suppose to <arg>.

08/04/93
--------
 CAM-MAIL.EXE
 ------------
  Added   - File attachments are now added to a QWK packet.
  Added   - Use the /REPLACE@ codes command line switch if you want
            your Bulletins and News and GoodBye files replaced with
            the appropriate ANSI color codes or the @macro@ codes.

            Because more and more readers are supporting @ codes, I've
            made the default set not to replace @ codes.  The Camster
            Reader is one example that supports @ codes internally.

07/31/93
--------
 CAM-MAIL.EXE
 ------------
  Fixed   - When a @USER@ was found in the TO field, it wasn't being
            replaced by the users real name <sigh>..
  Added   - Support for the CNAMES.ADD file was implemented.  That's
            the ONLY thing that was added.  File attachments and such
            will be coming.

07/05/93
--------
 CAM-MAIL.EXE
 ------------
  Added   - Added the /SWAP variable so CAM-MAIL.EXE has enough memory
            for some compressors like ARJ.

07/01/93
--------
 CAM-MAIL.EXE
 ------------
  Fixed   - If a user wanted to RESET their message pointers, the HIGH
            and LOW options were REVERSED <arg>.  In other words, if
            a user wasted to get the last 50 messages, they would need
            to do RESET 0 HIGH-50.  Well, what would actually happen
            is it was treated as a LOW+50 <g>.

            This isn't documented in the CAMUSER.DOC file, so here's
            how to use it:

                 TO: CAM-MAIL
            SUBJECT: CONFIG
              Text would contain:
              RESET confnumber LOW+/HIGH-/MessageNumber
              repeat as many times as you want

            So if I wanted to reset conferences #'s 0,5,6, and 9 I
            would do something like this:

                 TO: CAM-MAIL
            SUBJECT: CONFIG
              RESET 0 HIGH-50
              RESET 5 LOW
              RESET 6 300
              RESET 9 HIGH

            What would happen is conference #0 would be reset to the
            message pointer HighMessageNumber-50.  Conference #5
            would be reset to the LowMessageNumber.  Conference #6
            would be reset to MessageNumber 300.  Conference #9
            would br reset to HighMessageNumber.

06/28/93
--------
 CAM-MAIL.EXE
 ------------
  Added   - Cam-Mail wasn't supporting Expired Security Levels.  I had
            actually started implementing it at one stage, but must of
            gotten a phone call or something and forgot to add the rest
            of the code (as parts of it was in place, I didn't even
            know it).  Cam-Mail will now look at the expired date and
            use the appropriate logic on Public Conferences.

            If the door isn't working how you expect it to, please let
            me know so I can fix it (assuming there is something
            wrong <g>).

06/24/93
--------
 CAM-MAIL.EXE
 ------------
  Fixed   - If a user downloaded a mail packet in an Alias conference,
            the mail was not be FLAGGED as PERSONAL mail.  Meaning,
            it wouldn't show up in their reader or in the mail scan
            as personal mail.

06/16/93
--------
 CAM-MAIL.EXE
 ------------
  Removed - Cam-Mail now longer processes Bulletins or WELCOME or NEWS
            files for PCBoard @ codes.  It leaves them in.  It's up to
            the reader to handle this (Camster does and so should
            all of the other readers <g>).

06/11/93
--------
 CAM-MAIL.EXE
 ------------
  Removed - If an invalid conference was selected (meaning no name was
            defined), Cam-Mail would issue an "Invalid Conference"
            message and would pause for 2 seconds.  I removed the
            2 second delay because some people thought it was hanging
            if they used the SELECT;ALL command and had a lot of
            conferences defined that weren't defined.

06/10/93
--------
 IMPORT.EXE
 ----------
  Fixed - The <BBSID>.LOG file contained the wrong conference
          information when using the /LOG option.

06/09/93
--------
 USERSM.EXE
 ----------
  Fixed - The U and Y flags were not working inside the NetWork
          Conference (Individual).

06/03/93
--------
 CAM-MAIL.EXE/EXPORT.EXE/IMPORT.EXE
 ----------------------------------
  Added - These programs will now leave alone the Extended Status
          byte to be compatible PCBoard 15.0.

          By doing this, the Camster Reader can take advantage of the
          new information which makes things look real slick!!

06/02/93
--------
 CMSETUP.EXE/CAM-MAIL.EXE
 -----------
  Fixed    - PCBoard 15.0 now allows users to scan the Recent Upload
             directory if you have it defined as Private.  See their
             WHATSNEW history on WHY they did this.

             I changed the routines so the Recent Upload can be
             selected in the New File Scanning area whether this flag
             is set to YES or NO.

05/26/93
--------
 CAM-MAIL.EXE
 ------------
  Fixed    - If you had your DIR files Text Delimeter Character set at
             anything than position 35 (or thereabouts), the |
             character would be displayed.  This was incorrect.  The
             Door will now remove the | character and replace it
             with a space.

05/24/93
--------
 CAM-MAIL.EXE
 ------------
  Fixed    - If a user did the Operator Page option and the Sysop
             had the page bell turned on, a user could hit the
             Space Bar to enter Chat Mode, but couldn't get out
             without the help of the Sysop.  The other way to get
             out would require the drop of carrier.

  Enhanced - Combined the FOSSIL/COMM support into one EXE.  This
             should fix any problems with confusion <g>.  Don't know
             why I didn't do it a long time ago.

05/17/93
--------
 CAM-MAIL.EXE
 ------------
  Enhanced - When updating mail waiting flags, it will no longer use a
             case sensitive compare on the Name.

  Added    - You can use a GENERIC FORCE file to make sure that everyone
             is getting a specific conference.  Just use the name of
             FORCE and these conferences will be added.  This file will
             ONLY be used if a FORCExx file cannot be found.  Please be
             aware that Record #1 in the USERS file will NOT be forced
             to get the conference.  So if you try and see if this
             file really works, make sure you log on as a normal user
             and not as the Sysop.

             Some other fixes were made (minor), but they were fixed.

 IMPORT.EXE
 ----------

  Enhanced - When updating mail waiting flags, it will no longer use a
             case sensitive compare on the Name.
  Fixed    - The "qwkname was not deleted due to..." message contained
             garbage.  I forgot to pass the name of the QWK packet to
             the log file, which caused garbage to appear.

  Fixed    - Rosemail does not conform to the MESSAGES.DAT standard.  I
             added some code so the /KILLQWK option would work
             correctly with RoseMail and QWK packets.

05/03/93
--------
  Released an update for PCBoard 15.0 called v1.35

05/01/93
--------
 CAM-MAIL/EXPORT/IMPORT.EXE

  Fixed - There was a bug in the converting a date to a number.  This
          could cause unknown results or causing the program to abort
          immediately.

  Fixed - The High and Low numbers were reversed in the LOG file when
          using EXPORT.EXE.

04/28/93
--------
  Back from vacation....

 CAM-MAIL/EXPORT/IMPORT.EXE

  Fixed - The .IDX file could sometimes be created incorrectly.  This
          could cause hangs or HUGE .IDX files.

04/06/93
--------
 CAM-MAIL/EXPORT/IMPORT.EXE

  Fixed - If a message base is corrupted somehow and these programs
          would update the .IDX file, it could do it incorrectly.
          This would happen very rarely, but it was possible.  PCBoard
          would simply recreate the .IDX if it wasn't created properly.

04/03/93
--------
 CAM-MAIL/EXPORT/IMPORT.EXE

  Fixed - When creating a .IDX file, sometimes the previous message
          would go into a non existing message area.  This would simply
          duplicate a file being read twice (in certain cases).

04/02/93
--------
 IMPORT.EXE

  Added    - If you use the /OLDINDEX swtich and the .NDX file doesn't
             exist, IMPORT will now create the file.
  Added    - If the .IDX file doesn't exist, IMPORT will now create it.
  Fixed    - I wasn't closing the .IDX file <g>..  Eventually you would
             run out of file handles and the program would abort.

04/01/93
--------
 IMPORT.EXE

  Added    - If you use the /KILLQWK paramter, I've modified it to put
             a message in your LOG file stating why your QWK file was
             not deleted.

             You need to be using the /LOG option in order for this
             message to be written.

04/01/93
--------
 PRESCAN.EXE/LOCALCAM.EXE

  Modified - Prescan/Localcam was calling PCB145.EXE.  It now calls
             PCBOARD.EXE for proper support of PCBoard 15.0.

03/31/93
--------
 EXPORT.EXE

  Enhanced - EXPORT now uses the .IDX files for information.  The .NDX
             format is no longer supported for this program.

  Added    - If a .IDX file has not been updated, then EXPORT will
             update it for proper usage.

03/30/93
--------
 IMPORT.EXE

  Added    - Use the /OLDINDEX switch if you want to update the .NDX
             files used by PCBoard 14.5 or below.

  Added    - IMPORT.EXE will update the .IDX file if it hasn't been
             updated by other Third Party Software.

  Enhanced - IMPORT.EXE will now use the .IDX file for file updating.
             This means that .NDX files are no longer needed by IMPORT.

03/29/93
--------
 CAM-MAIL.EXE

  Enhanced - Mail Waiting flags are now updated faster.
  Fixed    - I was 99% compatible with the 15.0 code.  However, I
             missed one part in the USERS.SYS code (due to PCBoard 15.0
             creating a larger file).  That has now been fixed.
             Cam-Mail will now be compatible with any PCBoard USERS.SYS
             file.

  Changed  - Cam-Mail no longer maintains the .NDX file UNLESS you use
             the /OLDINDEX switch on the command-line.

             You use the /OLDINDEX switch to maintain compatibility with
             old PCBoard Third Party Software (Such as Qmail <g>) that do
             not recognize the new message format.

  Added    - If you have programs that don't update the .IDX file,
             Cam-Mail will update the .IDX file for you.  This will
             slow down the process (not by much), but at least your
             users will be getting their mail.  PCBoard does the EXACT
             same thing.

             What happens is when uploading/downloading a mail packet
             and Cam-Mail scans a conference, it will first check the
             .IDX file and see if it is up to par.  If it's not, then
             Cam-Mail will update the .IDX and will work correctly.
