g00r00 has eyes on this an is planning to update the prealphas
and I think that is what you'll want. Should be soonish.
Noted thanks.
There is another prealpha dated 2020/04/21. I haven't done any testing
as yet but before I report anything perhaps this one should be tested?
I'm going to try some local tossing and see what I can see..
I have only done a few quick tests but it looks to me that Mystic
(mutil) is looking at seen-by's and/or path lines now and not tossing
mail to linked nodes that are listed there.
This is all looking much better now.. :)
I have only done a few quick tests but it looks to me that Mystic
(mutil) is looking at seen-by's and/or path lines now and not tossing
mail to linked nodes
I have only done a few quick tests but it looks to me that Mystic
(mutil) is looking at seen-by's and/or path lines now and not
tossing mail to linked nodes
OK Al it's updated at 1/100... see what you think,
I have only done a few quick tests but it looks to me that Mystic
(mutil) is looking at seen-by's and/or path lines now and not
tossing mail to linked nodes
OK Al it's updated at 1/100... see what you think,
Currently messages I write in Mystic are not going anywhere. I don't
know if this is my issue or a bigger problem.
That should say "1 echo" I think.
I'm still not certain if this is my issue or a bigger problem.
Once the hubs are updated I think that'll tell the story. I am not going to see the changes with seen-bys directly but I think the hubs will. I will benefit fro m those changes though as we all will.
@REPLY: 21:1/101 d7d31684
@MSGID: 21:4/106 5ea1dbc1
@CHRS: UTF-8 2
@TZUTC: -0700
@TID: hpt/lnx 1.9.0-cur 2020-04-15
@PATH: 4/106 100 1/100
The one thing I noticed is through 1/100, the seen-bys are now
missing:
@REPLY: 21:1/101 d7d31684
@MSGID: 21:4/106 5ea1dbc1
@CHRS: UTF-8 2
@TZUTC: -0700
@TID: hpt/lnx 1.9.0-cur 2020-04-15
@PATH: 4/106 100 1/100
Either that, or they are just not displaying now...
Was that a recent post? There was an issue 2 or 3 days back with MSGID
and the l ike but path and seen-bys were all there.
@REPLY: 21:1/186 1d2c2943
@MSGID: 21:4/106 5ea2517b
@CHRS: UTF-8 2
@TZUTC: -0700
@TID: hpt/lnx 1.9.0-cur 2020-04-15
@PATH: 4/106 100 1/100
Was that a recent post? There was an issue 2 or 3 days back withYup. That was one from today. Here the kludge lines from your message: Seems something isn't quite right yet...
MSGID and the l ike but path and seen-bys were all there.
X-FTN-REPLY 21:1/186 1d2c2943
X-FTN-MSGID 21:4/106 5ea2517b
Is this the message you were referring too?
@TZUTC: 1000
@MSGID: 466.fsx_net@21:2/116 23079ed9
@REPLY: 21:1/186 16c33953
@PID: Synchronet 3.17c-Linux Mar 11 2020 GCC
@TID: SBBSecho 3.10-Linux r3.151 Mar 11 2020 GCC 8.3.0
@CHRS: CP437 2
@NOTE: SlyEdit 1.72 (2020-03-04) (ICE style)
@PATH: 2/116 3/100 1/100
Yup. That was one from today. Here the kludge lines from your message:
@REPLY: 21:1/186 1d2c2943
@MSGID: 21:4/106 5ea2517b
@CHRS: UTF-8 2
@TZUTC: -0700
@TID: hpt/lnx 1.9.0-cur 2020-04-15
@PATH: 4/106 100 1/100
Seems something isn't quite right yet...
@REPLY: 21:1/186 16c33953
@MSGID: 21:4/106 5ea26b3f
@CHRS: UTF-8 2
@TZUTC: -0700
@TID: hpt/lnx 1.9.0-cur 2020-04-15
@SEEN-BY: 1/1 100 101 109 116 125 126 130 133 135 150 157 158 165 174
181 184
@SEEN-BY: 1/186 189 190 193 195 198 202 204 205 206 207 208 209 210 995 2/100
@SEEN-BY: 3/100 4/10 100 105 106 122 124 131 134 136 143 147 165 166 168 169
@SEEN-BY: 4/171 172 173 5/100
@PATH: 4/106 100 1/100
Yup. That was one from today. Here the kludge lines from your message
@REPLY: 21:1/186 1d2c2943
@MSGID: 21:4/106 5ea2517b
@CHRS: UTF-8 2
@TZUTC: -0700
@TID: hpt/lnx 1.9.0-cur 2020-04-15
@PATH: 4/106 100 1/100
My posts wouldn't have much in the way of path & seenbys when they get
to your node, but there should be a short seen-by line.
Seems something isn't quite right yet...
Can you do a quick 'n dirty fresh install of A46 and see if you can
get a message out of it on a Linux64 box? I'm really curious how it
works for someone else?
Can you do a quick 'n dirty fresh install of A46 and see if you can get a message out of it on a Linux64 box? I'm really curious how it works for someone else?In the mean time I see sPINOZa has posted with A46 2020/04/21.
What the ... ?
I'm goin' to bed!
That is correct, my test was actually a test to see if there is a L64 problem as you mentioned in your message, but it seems to be working.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 412 |
Nodes: | 16 (2 / 14) |
Uptime: | 23:51:22 |
Calls: | 8,626 |
Calls today: | 12 |
Files: | 13,238 |
Messages: | 5,936,892 |