NB> If it was Mystic changing time to zeros, it was most likely an earlier
 NB> version (ie: not the latest). The latest version was stripping the
 NB> seconds completely and only sending HH:MM. If anything it was other
 NB> systems adding in the 00 as seconds because it only understood that
 NB> format.

Yeah, this sounds about right.  Mystic's PKT processor had a maximum length
of 5 defined for its time stamp (instead of 8) so HH:MM was the maximum
length of a time stamp that it could work with.

This processor is used in a HUB situation where the hub is importing
messages and tossing to downlinks.  Given that a lot of people weren't using
Mystic as a HUB back in the day, its easy to see how it went unnoticed for as
long as it did.

It was fixed in A32 and we ran in through the mud over on FSXNET before the
release for testing purposes.

--- Mystic BBS v1.12 A34 (Windows/32)