On 11/21/16, Wilfred van Velzen pondered and said...
 
 Wv> Your the Z1C, your system plays an important part as a mail hub. Mystic
 Wv> has known bugs...
 Wv> 
 Wv> So if you intend to use mystic's mail tosser you will cause problems in
 Wv> the net.

This is not correct. If he is planning on using a Mystic BBS and it's tosser to
receive packets in to his BBS then there are no known issues. If he is
planning on using the same tosser to send content generated at his BBS then
again there are no known issues that that will arise.

If he intends to toss incoming packets on to other configured echo nodes
and these are nodes with no other connection to Fidonet (they are not meshed
aka FidoWeb style) then there are no known issues.

The known issue arises only when he opts to toss incoming packets to other
configured echonodes that are also in a meshed environment with other systems
whereby dupe traffic is created. In this case packets being tossed by the
tosser and sent to echo nodes are presently having the message creation time
stamp seconds field being set to 00 and not left untouched.

This for some meshed systems causes problems for their dupe detection.

I post this reply to offer a more complete view of the situation rather than
just simply stating 'no don't use it' etc. As in reality Mystic BBS 1.12 A31
can happily be used in many cases by sysops, and is. :)

Best, Paul

--- Mystic BBS v1.12 A31 (Windows)