Mystic v1.12 A34 is released on www.mysticbbs.com

[---WHATSNEW---]

! Fixed a bug which could cause a bad memory reference error in various
places within Mystic.

! MUTIL PostTextFile wasn't taking into consideration the tear and origin
lines when posting to a networked base while splitting large posts into
multiple messages.

+ -VER commandline option in Mystic now prints the OS information too.

+ Increased buffer size when writing message text to JAM bases to 32k up
from 8k

+ Mystic JAM will no longer strip spaces from the right side of MSGID tags
in JAM to help work around a bug with GTPower.

! JAM Reply CRC and Msg To CRC were not always converted to lower cased
before calculated. As per JAM specs all CRC calculated on string must be
lower cased first. Packing message bases will regenerate these.

+ Reduced the time it takes to calculate Message Index Reader statistics
by about 60%. Statistics may be calculated incorrectly unless all bases
have been ran through the message base packer once to regenerate CRC values

! Fixed a bug which could cause some node processes to not detect when a
user hangs up, possibly resulting in a ghosted user or even a stuck
process.

+ Added a new internal protocol Xmodem/CRC. This protocol can be added by
creating @XMODEMCRC in your Protocl Configuration and has not had much
testing. **This is experimental; it may or may not stick around**

+ When shutting down MIS2, it no longer prompts to press a key when closing
but instead displays a "shutdown complete" message and pauses 1.5 seconds

+ When editing a file entry in a file base there is now a (H)atch command
which allows files to be hatched to all networked systems linked to that
file base. Files to be hatched will have a "Hatch pending" text or a
Hatched flag if the request was already processed.

+ Mystic now creates "filebone.out" semaphore file whenever a new file is
requested to be hatched.

+ MUTIL TIC processor will now scan for requested hatches. Any files
requested to be hatched will have an appropriate TIC file created
in each linked node's filebox, and the file will be copied to each
linked node's filebox.

+ In addition to existing /E to view networked message bases linked to a
node, the echomail node editor now has a /F to view and edit networked
file bases linked to a node.

+ Significant stability improvements to MIS2 along with some minor cosmetic
changes.

! Changed PKT addressing on pass-through echomail so that BBBS systems with
its security feature enabled will not reject packets.

+ In the echomail nodes editor, when enabling a FileBox with a blank filebox
location, Mystic will now give the option to automatically generate and
create a directory for that node. The format used by Mystic for the
directory is as follows:

Root filebox directory = <mystic root path> + "/filebox/"

Each directory is created under the root location with the format of:

<domain>_z<zone>n<net>n<node> (p<point> appended only for points)

Example for 21:1/108@fsxnet when installed to c:\mystic would be:

c:\mystic\filebox\fsxnet_z21n1n108\

<ALPHA 1.12 A34 RELEASED>

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (1:129/215)

Awesome work g00r00!!!!!

On 08:12 23/06 , g00r00 wrote:

Mystic v1.12 A34 is released on www.mysticbbs.com

[---WHATSNEW---]

! Fixed a bug which could cause a bad memory reference error in various
places within Mystic.

! MUTIL PostTextFile wasn't taking into consideration the tear and origin
lines when posting to a networked base while splitting large posts into
multiple messages.

+ -VER commandline option in Mystic now prints the OS information too.

+ Increased buffer size when writing message text to JAM bases to 32k up
from 8k

+ Mystic JAM will no longer strip spaces from the right side of MSGID tags
in JAM to help work around a bug with GTPower.

! JAM Reply CRC and Msg To CRC were not always converted to lower cased
before calculated. As per JAM specs all CRC calculated on string must be
lower cased first. Packing message bases will regenerate these.

+ Reduced the time it takes to calculate Message Index Reader statistics
by about 60%. Statistics may be calculated incorrectly unless all bases
have been ran through the message base packer once to regenerate CRC values

! Fixed a bug which could cause some node processes to not detect when a
user hangs up, possibly resulting in a ghosted user or even a stuck
process.

+ Added a new internal protocol Xmodem/CRC. This protocol can be added by
creating @XMODEMCRC in your Protocl Configuration and has not had much
testing. **This is experimental; it may or may not stick around**

+ When shutting down MIS2, it no longer prompts to press a key when closing
but instead displays a "shutdown complete" message and pauses 1.5 seconds

+ When editing a file entry in a file base there is now a (H)atch command
which allows files to be hatched to all networked systems linked to that
file base. Files to be hatched will have a "Hatch pending" text or a
Hatched flag if the request was already processed.

+ Mystic now creates "filebone.out" semaphore file whenever a new file is
requested to be hatched.

+ MUTIL TIC processor will now scan for requested hatches. Any files
requested to be hatched will have an appropriate TIC file created
in each linked node's filebox, and the file will be copied to each
linked node's filebox.

+ In addition to existing /E to view networked message bases linked to a
node, the echomail node editor now has a /F to view and edit networked
file bases linked to a node.

+ Significant stability improvements to MIS2 along with some minor cosmetic
changes.

! Changed PKT addressing on pass-through echomail so that BBBS systems with
its security feature enabled will not reject packets.

+ In the echomail nodes editor, when enabling a FileBox with a blank filebox
location, Mystic will now give the option to automatically generate and
create a directory for that node. The format used by Mystic for the
directory is as follows:

Root filebox directory = <mystic root path> + "/filebox/"

Each directory is created under the root location with the format of:

<domain>_z<zone>n<net>n<node> (p<point> appended only for points)

Example for 21:1/108@fsxnet when installed to c:\mystic would be:

c:\mystic\filebox\fsxnet_z21n1n108\

<ALPHA 1.12 A34 RELEASED>

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (1:129/215)

--
yrNews Usenet Reader for iOS
http://appstore.com/yrNewsUsenetReader

--- Mystic BBS/NNTP v1.12 A33 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (1:130/210)

Hi g00r00,

I recently had a qodem report an issue with ANSI arrow keys and mystic
BBSes:

https://github.com/klamonte/qodem/issues/65

I discovered that qodem was sending key sequences via its telnet
essentially byte-by-byte (verified with wireshark), and buffering a
sequence into a single write() seems to have made the issue go away.

However, I wanted to mention this to you because other connection
methods (e.g. dialup or really slow/spotty telnet/socket/ssh) or BBS
clients might also break those sequences into separate read()'s too.
It looked like mystic's ANSI reader was seeing the first single-byte
read containing only ESC and then returning that ESC, rather than
waiting with some timeout to see if more bytes are coming like
ncurses.

Anyway, just wanted to pass that along. If you think there is more
qodem should be doing, please feel free to drop in on the github
issue.

Cheers!


-Kevin Lamonte

... MultiMail, the new multi-platform, multi-format offline reader!
--- MultiMail/Linux v0.49
* Origin: Vertrauen - vert.synchro.net (1:103/705)