Subj : IZ echomail and seenby's
To   : Tommi Koivula
From : mark lewis
Date : Wed May 27 2015 02:08 pm


28 May 15 02:57, you wrote to Paul Quinn:

PQ>> --- D'Bridge 3.99
PQ>>  * Origin: Many Glacier -- Protect - Preserve - Conserve (2:292/854)
PQ>> SEEN-BY: 221/1 280/5555 640/305 384 1384 690/682
PQ>> PATH: 292/854 280/5555 640/384

PQ>> --- SBBSecho 2.27-Win32
PQ>>  * Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
PQ>> SEEN-BY: 221/1 280/5555 640/305 384 1384 690/682
PQ>> PATH: 249/303 280/464 5555 640/384

TK> Both of these messages have address of origin on PATH line, but not on
TK> SEENBY line.

right... some software adds their address to the seenbys and some doesn't...

here's what FTS-0004 has to say about seenbys...

[quote]
   4. 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.
[/quote]

note the two hilited lines... strict reading of that line might suggest that
each system that gets a message add their address to the seenbys... another
view is like that used today where the sending system adds the addresses of the
systems it is sending the message to... nothing is really said about what an
originating system should do with its address and the seenbys... on one hand,
it makes sense to add it, on the other, it is in the origin and the first in
the path so it should be apparent that it saw it already...

then think about what happens when a point originates an echomail message...
take this one for example ;)

TK> I have received also some .PKT's from Andrew's FE, but I didn't find any
TK> failures yet.

that's a good thing :)

)\/(ark

... That old thing? It is a pretty good work of fiction, though!
---
* Origin:  (1:3634/12.73)