home *** CD-ROM | disk | FTP | other *** search
- ****************
- version 1.10
- ****************
-
- - Name Service Added. See Docs because this is a little complex.
-
- - Messages to points with file attaches are now ALWAYS treated as if
- 2DaPoint was running in Node mode.
-
- - Major clean-up: Packets now end with #13#0 instead of #32#0.
-
- - Minor clean-up: Full Path & Filename no longer appear in subject line
- of messages that had Freqs or Fattachs.
-
- - End of line comments now allowed in control file. Use the semi-colon just
- like a full line comment.
-
- ****************
- version 1.20
- ****************
-
- - Name Remapping/Substitution Added. See Docs.
-
- - Multiple Fattaches, Multiple PassThru Fattaches, & Multiple Freqs
- are now supported in the Subject line.
-
- - Passthru files now can be optionally killed.
-
- - Major Clean-up: AVL tree containing Names & addresses is now initialized
- even if there are no names/addrs in the Names section of your control file.
-
- - Minor Clean-up: Full name must now be found in Names section of control
- file, not just a subset of it.
-
- - 2DaPoint no longer generates DLO/DUT files.
-
- - Back-to-basics look. Old style was overkill!
-
- ****************
- version 1.30
- ****************
-
- - Full Zone Support! Except for Zone 0. Any msg that has Zone 0 in it's
- origin or destination address will have Zone 0 replaced with YOUR Zone.
-
- - 2DaPoint will now log it's activities to a text file, 2DAPOINT.LOG.
-
- - Using the -B command line parameter will cause 2DaPoint to use BIOS
- screen writes. Default is direct video writes.
-
- - Major Clean-up: Any message in your netmail directory that is echomail
- (denoted by the ^APATH kludge) is now sent to its intended destination
- & then killed.
-
- ***NOTE****: If you forward/copy a msg from an echomail area into your
- netmail dir, it will be handled like a normal netmail message ONLY IF
- you remove the ^APATH kludge
-
- - Minor Clean-up: words in the subject line that are over 8 characters are
- no longer truncated to 8 chars. (Thanks Jack)
-
- - Minor Clean-up: Messages that had the kill bit set & were marked as HOLD
- from the control file were being killed immediately.
-
- - Minor Clean-up: PassThru file attaches that were supposed to be killed are
- now DELETED, not just truncated.
-
- - Minor Clean-up: Msgs that have been received & have the KillSent bit set
- are no longer killed.
-
- ***************************
- version 1.31 - Bug Fix!
- ***************************
-
- - Messages without MSGID's were causing problems with the software. Programs
- like Areafix & Raid don't generate MSGID's for example. The problem was
- actually in the CRC value; it wasn't being initialized in the proper palce
- so the CRC string being written was totally random & could contain the #0.
-
- - EchoMail messages are now recognized by the "AREA:" statement instead of
- the PATH kludge.
-
- ****************
- version 1.40
- ****************
-
- - 2DaPoint now uses BinkleyTerm 2.50's 4D .PNT directory format. All
- support for Pseudo PointNet/PrivateNet has been dropped.
- Upgrade to 4D, 3D FakeNet is obsolete!!!
-
- - SetBit/StripBit options have been added. This allows you to define two
- seperate bitmasks to be used on msg attributes. These masks may used to
- always set the private bit on or always set the crash bit off for example.
-
- - Mis-Addressing notification. With the Notify option enable, any msg that
- comes into your system & get redirected with cause 2DaPoint to send a msg
- to the originator of that message, telling them where they can reach the
- person they mis-addressed their msg to.
-
- - UTC support. 2DaPoint will now compute the time in the VIA tearline in
- terms of UTC if you have your TZ envirment variable set correctly.
-
- - The 286 version will now identify itself as such.
-
- - Major Clen-up: In an effort to reduce redunant code, 2DaPoint will now
- leave any echomail msg in your netmail dir ALONE. Previous versions
- would recognize that it was EchoMail, but put in kludges before the
- AREA: line. In order for this to be avoided, an entire new procedure
- would have to be written that'd chew up memory & .EXE file size. I
- can't say that I feel it's be worth it. ConfMail & Qmail will pickup
- the echomail addressed to another node that is in your netmail dir
- & send on it's way wo/alteration.
-
- ***************************
- version 1.41 - Bug Fix!
- ***************************
-
- - The TZ enviroment variable wasn't being recognized 100% of the time.
-
- - The ^AVia Kudges will now be maintained @ the bottom of the msg. They
- were getting moved to the top before the msg body.
-
- - The temporary storage area for Kludges has been increased four-fold from
- 512 bytes to 2048 bytes. This should do it. ;)
-
- - Hard Carraige Returns are now being used in the FYI msgs instead of Soft.
-
- ****************
- Version 1.50
- ****************
-
- - EchoMail Processing is Back. Echomail msgs in your netmail msg dir will
- be sent to their proper destination verbatim (no changes in the kludge
- lines, etc). ie, correctly. ;)
-
- - PassThru File Requests!
-
- - Passwords are now supported in Freqs. Any word that starts the the password
- delimitter, !, will be used as a password (including multi-freqs).
-
- - Wildcards are now supported in Fattaches (including Multiple).
-
- - Generated packets can now have passwords embedded into the header for secure
- enviroments.
-
- - ZoneGating. With this enabled, msgs to other zones are automatically send to
- Origin_Zone:Origin_Zone/Destintaion_Zone.0
-
- - The Via lines are now hidden behin a kludge instead of using the tear line
- ie, ^AVia instead of ---Via. Via Lines where also shortened to remove the
- "-286".
-
- - You can now specify where the log file is generated.
-
- - There are now 5 seperate errorlevels that 2DaPoint will exit with.
-
- - When 2DaPoint is run on point systems, mail will not be written into .PNT
- dirs; instead, the mail will be bundled for that point's host.
-
- - Executables in the .ARJ are no longer compressed with PKLite.
-
- - 2DaPoint now properly encodes the 2+ packet headers ID.
-
- - You may have your node number set to 0.