• RNtrack version 2.0.3

    From Michael Dukelsky@2:5020/1042 to All on Fri Jan 31 19:08:56 2020
    Hello All,

    A new version 2.0.3 of the netmail tracker RNtrack has been published here:

    https://sourceforge.net/projects/ftrack-as/files/RNtrack/2.0.3/

    What's new:

    2.0.3 2020-01-31 (Subversion rev.260)
    ------------------------------------
    # add RNtrack configuration files from 2:5020/1042

    2.0.2 2020-01-30 (Subversion rev.257)
    ------------------------------------
    # upgrade smapi library from v.2.4.1 to v.2.5.1
    ! fix Visual Studio 6 build
    # add Windows x64 build
    # add Visual Studio 2019 solution
    # update Russian manual
    # make a new translation of the amended manual from Russian into English
    # add manual in the form of man-pages and plain text in English
    # change default path of configuration file
    # change the log date format to ISO 8601

    The smapi library v.2.5.1 was stolen from hpt. The previous version was bad when working with JAM and Squish messages bases. Hopefully working with these types of message bases will be better.

    If you have never used RNtrack, just to provide you insight into what it can do
    here are the comments from my RNtrack configuration file:

    \
    \ Inbound netmail processing
    \

    \ Messages in packets *.pkt received in passwordless sessions

    \ Delete 'local' flag if it is present in a message to my net.

    \ Delete 'sent' flag if it is present in a message to my net.

    \ Delete 'received' flag if it is present in a message to my net.

    \ Move netmail to my net to a separate message base.

    \ Other messages: move them to jail
    \ and send a notification to my home point.

    \ Send by standard routing the messages to my net received
    \ in the insecure inbound adding a line to the message
    \ saying that it was received in a passwordless session

    \ Messages unpacked by tosser from the secure inbound

    \ Delete 'local' flag if it is present.

    \ Delete 'sent' flag if it is present.

    \ Delete 'received' flag if it is present.

    \ Copy the message to 'netcpy' message base for temporary storage
    \ in case any problems are later detected.

    \ The sender of the looped message that arrived
    \ for the seventh time is not in the nodelist - delete the message
    \ and send a notification to my home point.

    \ Send back to sender the loop message that has come to us seventh time.

    \ A loop message is discovered for the first time.
    \ Send a notification to my home point.

    \ A message has come with attached file not to us.
    \ Kill the file and send the message back.

    \ Scan the same message base for the second time in order to send
    \ the message created during the previous scanning immediately

    \ A loop mail is detected. Put it aside to the loop mail message base
    \ to postpone its processing for a day, in the hope that during this
    \ time the problem that caused the looping will be solved.

    \ Send messages to my node from human beings (not from robots)
    \ and confirmation receipts to my home point

    \ Delete messages to my node from robots and messages to robots

    \ Copy messages from me to 'mail.sent' message base
    \ setting the 'sent' flag. Messages from 'Ping_Robot' are excluded
    \ from copying.

    \ Move the message without 'sent' or 'locked' flags to 'mail.out' message base

    \
    \ Outbound netmail processing
    \

    \ Once a day, return looped messages to processing

    \ Unpack outbound to 'netmail.tmp' once a day, as routing could change.
    \ Messages will be placed back in outbound in accordance with the new routing.

    \ Reply to ARQ.

    \ Scan the outbound netmail message base.

    \ If both the recipient and the sender are not in the nodelist,
    \ kill the message and send a notification to my home point.

    \ Kill an old letter from a sysop that is not in the nodelist
    \ and send a notification to my home point.

    \ Receiver is not in the nodelist. Send the message back to sender
    \ and send a notification to my home point.

    \ Sender is not in the nodelist. Prepend a line about it to the message body
    \ and send a notification to my home point.

    \ Return the old message to sender
    \ and send a notification to my home point.

    \ Delete an old message from a robot.

    \ Route to my home point.

    \ Hold for my points.

    \ Include routing generated by the Fidoroute program
    \ from the Husky project


    Michael

    ... node (at) f1042 (dot) ru
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: Moscow, Russia (2:5020/1042)