TID: Mystic BBS 1.12 A43
MSGID: 3:770/100 e23429da
REPLY: 1:3634/12.73 5ca0f072
TZUTC: 1300
On 31 Mar 2019 at 12:53p, mark lewis pondered and said...
 
 ml> well, there's the problem... there must be a net on the first address of
 ml> each line... if they are all in net1, it should look like this:

Ah. Thanks, is there someone in the specs for this in FTN land that you can
point me to the requirement? When Al or I flag this with James it would be
helpful to be able to point him to it.

I took a look at another post from a node in fsxNet and indeed there are no
NET lines stated at the start of each SEEN-BY

It's the first time it seems to have been an issue for anyone/system though.

[snip]

@TID: Mystic BBS 1.12 A43
@MSGID: 21:4/137 98af6bc5
@REPLY: 19305.fsx-fsx_gen@21:1/109 2105d695
@TZUTC: -0600
@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
@SEEN-BY: 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168
@SEEN-BY: 169 171 172 173 174 175 176 177 178 179 181 182 183 184 185 186 187
@SEEN-BY: 188 189 190 191 192 193 195 197 199 200 999 2/100 3/100 4/10 100 101
@SEEN-BY: 102 104 105 106 107 108 109 11 110 112 114 116 117 118 119 121 122
12
@SEEN-BY: 124 125 128 129 131 133 134 135 136 137 138 139 140 141 143 144 145
@SEEN-BY: 146 147 148 150 151
@PATH: 4/137 100 1/100

[snip]

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)
SEEN-BY: 15/2 57/0 103/705 123/1970 153/250 154/10 203/0 221/0 226/17
SEEN-BY: 226/100 229/107 354 426 452 1014 240/5832 249/206 317 267/800
SEEN-BY: 280/464 5003 292/624 854 317/2 3 322/757 342/200 393/68 396/45
SEEN-BY: 423/120 712/848 770/0 1 10 100 330 340 772/0 1 500 2452/250
PATH: 770/100 1 280/464 229/426