Subj : Re: >er ter ter ter long lines (paragraphs)
To   : John Smith
From : g00r00
Date : Sun Apr 19 2020 06:32 pm

 JS> The path does have a role to play but path lines are not the same as

Thanks for the explaination, but please realize I wrote a tosser and multiple
mailers from scratch that implement these things so I do understand what they
are. :)

 JS> Mystic doesn't seem to be looking at the path now either.

It does check path when tossing against the address associated to the message
base being processed, as long as the address associated is a 3D address only. I
can see the logging in my test network from circular PATH checking.  If you
have a specific situation where you think that isn't the case then let me know.

 JS> My details are sketchy at best. I'm sure there is an FTSC doc that talks
 JS> about SEEN+BYs that could give you better direction that I can. I'll
 JS> take a look and see what I can find and pass the filename to you.

I am not looking for any direction on SEEN-BY lines at the moment.

They are implemented correctly in Mystic, but as said the dupe checking based
on them was intentionally disabled a while back (a long long time ago). They
don't work well past 3D addresses and at least back in the day they were
commonly stripped or trimmed.

The PATH checking and CRC is mostly sufficient in dupe loops unless you're
intentionally setting up a situation (which I think you guys are) that creates
a "bad topology" as defined in FTSC.  Ironically the FTSC for SEEN-BY and PATH
will actually tell you that their purpose is to identify and dissolve those
"bad" topologies.

Anyway I don't mind re-enabling it though if you're willing to test it.

--- Mystic BBS v1.12 A46 2020/04/17 (Windows/64)
 * Origin: Sector 7 (1:129/215)

.