Hi Paul,

On 2016-11-22 16:30:30, you wrote to me:

 Wv>> Your the Z1C, your system plays an important part as a mail hub.
 Wv>> Mystic has known bugs...
 Wv>>
 Wv>> So if you intend to use mystic's mail tosser you will cause problems
 Wv>> in the net.

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

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

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

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

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

Ok... ;)

Bye, Wilfred.

--- FMail-W32 1.73.4.41-B20161119