TIP: Click on subject to list as thread! ANSI
echo: ftsc_public
to: Paul Hayton
from: Andrew Leary
date: 2019-04-01 05:26:00
subject: SEEN-BY

Hello Paul!

01 Apr 19 12:15, you wrote to all:

 PH> Mark is saying that Mystic SEEN-BY lines may be incorrect in that at
 PH> the start of each line he says there should be a reference to the NET
 PH> like this example he gave.

 PH> When James is back on deck I was going to feed this info back to him
 PH> but wanted to do due diligence first and find FTSC docs that explain
 PH> this requirement.

 PH> At the moment I can't find anything except in FTS-0004 where there's a
 PH> section about SEEN-BY but no mention of the need to start each line
 PH> with a NET/NODE combo.

 PH> Can someone point me to where I can reference this need and provide
 PH> any commentary about this subject please?

http://ftsc.org/docs/fsc-0074.001 has this to say:

  3. Seen-by Lines

  Seen-by lines are the focus of EchoMail distribution control
  information.  They are used to determine which addresses
  (systems) have received messages.  There can be as many seen-
  by lines as required to store the necessary information.

  Seen-by lines consist of "SEEN-BY:", followed by a list
  of net/node numbers corresponding to the systems which have
  received that message.  The net/node number of each system to
  which a message is exported is added to the seen-by lines at
  the time of export.

  There shall be exactly one set of seen-by lines in a message.
  Seen-by lines:

    -  Shall follow the origin line.

    -  Shall begin with the nine character literal: _

            SEEN-BY:

    -  Shall contain a list of net/node numbers.

    -  Shall be no more than 80 characters long including the
       required literal.

  The complete lines might look like:

            SEEN-BY: 104/1 501 132/101 113 136/601 1014/1
            SEEN-BY: 1014/2 3

  The list of net/node numbers:

    -  Shall identify at least one address. "Blank" seen-by
       lines shall not be transmitted.

    -  Shall be sorted in ascending net/node order.

    -  Shall not contain repeated node numbers.

    -  Shall use only "2D" net/node notation.

    -  May use short form address notation where a net number is
       listed once on any one line.  These 2 lines are
       equivalent:

            SEEN-BY: 104/1 104/501 132/101 132/113 136/601
            SEEN-BY: 104/1 501 132/101 113 136/601

  Some implementations insert a Ctrl-A (0x01) immediately
  preceding the SEEN-BY: literal (^ASEEN-BY:).

  Six months after adoption of this document the ^ASEEN-BY:
  format shall be processed equally with the SEEN-BY: format
  when either occurs in received packets.
_

The critical phrase is:  "May use short form address notation where a net 
number is listed once on any one line."

My interpretation is that the net number must be listed at least once on any 
one SEEN-BY line.

Regards,

Andrew

--- GoldED+/LNX 1.1.5-b20180707
                                                     
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)

SOURCE: echomail via QWK@dmine.net

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.