Ok...

For some reason half the nodes had the wrong address in the primary. Surprised no 21:3/0's went past that was in there too.. but all is
right in that part of the world.

I've replaced the problematic move with another redirect and then del of the temporary file which appears just fine and dandy.

Tear line fixed. And thinking about it, I still don't know what the @MSGID is for, but I don't think I've ever had one....

Spec


--- SuperBBS v1.17-3 (Eval)
* Origin: <Shoot'n the breeze on The Lower Planes> (21:3/101)

For some reason half the nodes had the wrong address in the
primary. Surprised no 21:3/0's went past that was in there too..
but all is right in that part of the world.

I did see a 21:3/0 in there too..

Tear line fixed. And thinking about it, I still don't know what the
@MSGID is for, but I don't think I've ever had one....

Oh, maybe not.. I never really looked that close.

Some older software never knew about it, so in those cases it's not going
to get one.

--- SuperBBS v1.17-3 (Eval)
* Origin: <Shoot'n the breeze on The Lower Planes> (21:3/101)

That looks good.

Ttyl :-),
Al

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

On Sun, 1 Dec 2019 14:31:00 +1100
"Spectre -> All" <0@101.3.21> wrote:

Tear line fixed. And thinking about it, I still don't know what the
@MSGID is for, but I don't think I've ever had one....

Which is unfortunate. MSGID is used for dupe checking and the REPLY kludge. Every editor should add a MSGID and a REPLY kludge. Without that reply linking does not work.

---
* Origin: (21:1/151)

Tear line fixed. And thinking about it, I still don't know

what the

@MSGID is for, but I don't think I've ever had one....

Which is unfortunate. MSGID is used for dupe checking and the REPLY kludge. Every editor should add a MSGID and a REPLY kludge. Without
that reply linking does not work.

Ok, so how does it do it? Maybe I can construct something to go in with the UTC
kludge I've got going. Perhaps google doesn't like bbs or ftc from here, or my
googlefu is weak, but very hard to find any real information on it.

Spec


--- SuperBBS v1.17-3 (Eval)
* Origin: <Shoot'n the breeze on The Lower Planes> (21:3/101)

On Mon, 2 Dec 2019 03:26:00 +1100
"Spectre -> Oli" <0@101.3.21> wrote:

Which is unfortunate. MSGID is used for dupe checking and the
REPLY kludge. Every editor should add a MSGID and a REPLY
kludge. Without that reply linking does not work.

Ok, so how does it do it? Maybe I can construct something to go in
with the UTC kludge I've got going. Perhaps google doesn't like bbs
or ftc from here, or my googlefu is weak, but very hard to find any
real information on it.

It's hard to find Fidonet stuff with Google.

http://ftsc.org/docs/fts-0009.001

---
* Origin: (21:1/151)

It's hard to find Fidonet stuff with Google. http://ftsc.org/docs/fts-0009.001

It seems fairly straight forward, just need to find a way to dump a sequential hex number to a data file and add it to the queue of mashing that goes on now.
Just start at 000001 and keep on going from there. No idea how to manage that from a batch file as yet. Probably easier to store the number as a decimal and
then push a hex conversion into the message. What the number is won't matter locally, as it'll have no idea about them, and so long as they keep increasing outside all will be well.

Spec

*** THE READER V4.50 [freeware]
--- SuperBBS v1.17-3 (Eval)
* Origin: Scrawled in haste at The Lower Planes (21:3/101)

MSGID: 21:3/101 2a1f3453
REPLYID: 21:1/151 5de413c8
TZUTC: 1100

Did you just pull a @MSGID and @REPLYID out of you butt?

That's pretty amazing, well done!

Ttyl :-),
Al

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

MSGID: 21:3/101 2a1f3453
REPLYID: 21:1/151 5de413c8

Did you just pull a @MSGID and @REPLYID out of you butt?

Ahh no, I don't know where they came from. REPLYID 21:1 ?? I'm in 21:3...


Spec


--- SuperBBS v1.17-3 (Eval)
* Origin: <Shoot'n the breeze on The Lower Planes> (21:3/101)

Hello Spectre,

MSGID: 21:3/101 2a1f3453
REPLYID: 21:1/151 5de413c8

Did you just pull a @MSGID and @REPLYID out of you butt?

Ahh no, I don't know where they came from. REPLYID 21:1 ?? I'm in
21:3...

That is a good MSGID for 21:3/101, and also a good REPLYID for 21:1/151 with the correct ID also.


Ttyl :-),
Al

--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

On Mon, 2 Dec 2019 14:35:00 +1100
"Spectre -> Al" <0@101.3.21> wrote:

MSGID: 21:3/101 2a1f3453
REPLYID: 21:1/151 5de413c8

Did you just pull a @MSGID and @REPLYID out of you butt?

Ahh no, I don't know where they came from. REPLYID 21:1 ?? I'm in
21:3...

I think it has something to do with "*** THE READER V4.50 [freeware]"

---
* Origin: (21:1/151)

I think it has something to do with "*** THE READER V4.50 [freeware]"

Maybe, I don't really know. All of them go through the same ice editor and get
fed the same UTZ kludge the same way. I'll bang out a test from the BBS and from the Reader.

Spec


--- SuperBBS v1.17-3 (Eval)
* Origin: <Shoot'n the breeze on The Lower Planes> (21:3/101)