Subj : Re: Nlcheck report
To   : Stas Mishchenkov
From : Wilfred van Velzen
Date : Mon Nov 11 2024 14:17:53

Hi Stas,

On 2024-11-10 20:30:02, you wrote to me:

 WvV>> It is defined in FTS-5001! In section: "5.6. Mail Period Flags"

 WvV>> It is only wrong if it is the same as the default ZMH, for the zone the
 WvV>> node is in.

 SM> http://ftsc.org/docs/fts-5001.006


 SM> === Import Windows Clipboard Start ===
 SM> 5.6. Mail Period Flags
 SM> ----------------------

 SM>   The Mail Period Flags indicate compliance with another zone's ZMH.
 SM>   Since ZMH is mandatory within one's own zone, it is not indicated.

 SM>   These flags have the form "#nn" or !nn where nn is the UTC hour the
 SM>   mail period begins, # indicates Bell 212A compatibility, and !
 SM>   indicates incompatibility with Bell 212A.  For example:

 SM>     Flag   Meaning

 SM>     #02    Zone 2 mail hour (02:30 - 03:30 UTC)
 SM>     #08    Zone 4 mail hour (08:00 - 09:00 UTC)
 SM>     #09    Zone 1 mail hour (09:00 - 10:00 UTC)
 SM>     #17    Zone 3 mail hour (17:00 - 18:00 UTC)

 SM>   The above listing of the ZMH for each individual zone is only given
 SM>   for your convenience. It was correct at the time of this writing,
 SM>   but could be changed at any time by following the procedures
 SM>   established in Fidonet policy. The FTSC has no role in determining
 SM>   the Mail Hour of any Zone. You'll find an up-to-date list in the
 SM>   comments at the end of the Fidonet Nodelist.

 SM>   NOTE:  When applicable, the mail period flags may be strung together
 SM>   with no intervening commas, e.g. "#02#09".
 SM> === Import Windows Clipboard End ===

 SM> Nothing about #20.

I red it as any number after # would be correct, but apparently it must be one of the current ZMH's that are actually used. But not necessarily the ones listed above in het fts document...

Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
 * Origin: NPC Station (2:280/464)

.