Hi all

I'm just following up a chat I had with Mark and Al in the BBBS Support echo concerning SEEN-BY lines

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

[snip]

@SEEN-BY: 1/1 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115
@SEEN-BY: 1/116 117 118 119 120 121 122 123 124 125 127 128 129 130 131 133 134
@SEEN-BY: 1/135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151

[snip]

whereas Mystic is creating SEEN-BY likes this.

[snip]

@SEEN-BY: 1/1 100 101 102 103 104 105 106 107 108 109 110 111 112 113
114 115
@SEEN-BY: 116 117 118 119 120 121 122 123 124 125 127 128 129 130 131
133 134
@SEEN-BY: 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149
150 151

[snip]

in both examples all nodes are members of NET 1

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

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

[snip]

Seen-by Lines

There can be many seen-by lines at the end of Conference
Mail messages, and they are the real "meat" of the control
information. They are used to determine the systems to
receive the exported messages. The format of the line is:

SEEN-BY: 132/101 113 136/601 1014/1

The net/node numbers correspond to the net/node numbers of
the systems having already received the message. In this way
a message is never sent to a system twice. In a conference
with many participants the number of seen-by lines can be
very large. This line is added if it is not already a part
of the message, or added to if it already exists, each time
a message is exported to other systems. This is a REQUIRED
field, and Conference Mail will not function correctly if
this field is not put in place by other Echomail compatible
programs.

[snip]

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

With thanks.

Best, Paul

--- E:avon@bbs.nz ------ W:bbs.nz ---
--- K:keybase.io/avon --------------

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

Hello Paul!

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

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

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

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

Can someone point me to where I can reference this need and provide
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:<space>", 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:<space>

- 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)

On 01 Apr 2019 at 05:26a, Andrew Leary pondered and said...

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.

Thanks Andrew, that's really helpful :)

I'll pass that info back along to James.

Best, Paul

--- E:avon@bbs.nz ------ W:bbs.nz ---
--- K:keybase.io/avon --------------

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)