I just got 32 dupes from you, and when I tried to send you netmail @21:3/101 I'm not even showing that as a valid node address. Can we get a current nodelist pushed out? I was told that Mystic doesn't even use the nodelists anymore, but apparently that's not the case.
---

-Dallas Vinson

--- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)
* Origin: Before the Web (21:4/102)

I just got 32 dupes from you, and when I tried to send you netmail @21:3/101 I'm not even showing that as a valid node address. Can we

Shrug, its beyond my control... you should find they have different paths on �them. ALso worth noting, its pointless trying to send me netmail I can't �really process it, it just gets deleted. I can manually send them out �occasionally but thats about it.

Spec


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

Hello Spectre,

Shrug, its beyond my control... you should find they have different
paths on them.

I think there was a hick up, upstream a little.

ALso worth noting, its pointless trying to send me netmail I can't
really process it, it just gets deleted. I can manually send them
out occasionally but thats about it.

That's odd. I ran FE for a time and it handled netmail OK. Does SuperBBS use Jam or Hudson message bases? If you haven't already tried, try setting your netmail base to Hudson in SuperBBS and FE, it might work better for you.

I suppose I almost always prefer echomail even at times when netmail would be better.

Ttyl :-),
Al

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

Re: Dupes and Node address
By: Al to Spectre on Tue Dec 24 2019 03:05 am

Shrug, its beyond my control... you should find they have different
paths on them.

I think there was a hick up, upstream a little.

So I've just noticed, that I didnt receive the original message from Spectre. (But I have received others, so its not a hub down issue...)

Comparing what I have here, with what's on 21:3/100 I see a couple of messages missing. When christmas is done and dusted, might have to research this.

The first one is where is the original to this thread? It has these details: X-FTN-MSGID 21:3/101 01190a27
X-FTN-REPLY 21:4/102 dc5fc91e
X-FTN-PID THE READER V4.50 [freeware]
X-FTN-SEEN-BY 3/100 101
X-FTN-PATH 3/101

when_written 5E00C02C 0294 Tue Dec 24 2019 12:25 am UTC+11:00
when_imported 5E01F053 9258 Tue Dec 24 2019 10:02 pm AEDT

Spectre, I suspect there is also something screwy with your time - this implies
it took 9.5hrs between being written by you and received by me - and as I read
it SBBS says it was 23.2hrs ago - but the previous and next messages where only 2hrs ago.
...deon


... In every revolution, there's one man with a vision. Kirk, stardate unknown --- SBBSecho 3.10-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

That's odd. I ran FE for a time and it handled netmail OK. Does
SuperBBS use Jam or Hudson message bases? If you haven't already
tried, try setting your netmail base to Hudson in SuperBBS and FE,
it might work better for you.

The problem I have is that FE spews so many errors out into the netmail �queue,
that I gave up and delete them daily. Usually over size errors. I �actually prefer to handle netmail in FD but its all over the place.

Spec


--- SuperBBS v1.17-3 (Eval)
* Origin: (21:3/101)

details: X-FTN-MSGID 21:3/101 01190a27 X-FTN-REPLY 21:4/102 dc5fc91e X-FTN-PID THE READER V4.50 [freeware] X-FTN-SEEN-BY
3/100 101 X-FTN-PATH 3/101

Interesting it seems to be missing its UTZ also... I can't confirm that my �script is working reliably, but it is an observation.

when_written 5E00C02C 0294 Tue Dec 24 2019 12:25 am UTC+11:00 when_imported 5E01F053 9258 Tue Dec 24 2019 10:02 pm AEDT

Or is that where it got to.. :)

Spectre, I suspect there is also something screwy with your time - this implies it took 9.5hrs between being written by you and received
by me - and as I read it SBBS says it was 23.2hrs ago - but the
previous and next messages where only 2hrs ago. ...deon

Anything is possible, but it is a very odd value. What was the content of �this
message it might help shed some light on things. I have a number of �problems from different vectors here.

A total of 9 DOS vm's none of which remain in time sync. Each run through �the
start.bat loop they do an ntp time synchronisation. After that, there is �the regular SuperBBS messaging system, the reader, FastEcho's message send �facility in FEUTIL (Probably missing the UTZ) which would help account for �the time discrepancy but it remains an odd number. And after all that, �whatever FrontDoor has done with it. I find it a little hit and miss on �polling for some reason, and occasionally have to pop crash/immediate on �packets just sitting there.

Spec


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

Hello Spectre,

The problem I have is that FE spews so many errors out into the
netmail queue, that I gave up and delete them daily. Usually over size errors. I actually prefer to handle netmail in FD but its all over
the place.

Were these errors related to large messages? I saw that at one time with FE and
solved it using the OS/2 version by setting the buffers to large, somewhere in the FE config.

It was messages in the file announcement echoes that were causing me grief. That might happen today in the FSX_BOT area.

Ttyl :-),
Al

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

Usualy over size errors. I actually prefer to handle netmail

Were these errors related to large messages? I saw that at one time

Yes ;) Don't think I've seen any buffering settings in the setup. Unless �there are messages larger than 32k I can't see the buffering making much �difference, that appears to be its minimum..

Spec


--- SuperBBS v1.17-3 (Eval)
* Origin: (21:3/101)

Usualy over size errors. I actually prefer to handle netmail

Were these errors related to large messages? I saw that at one time

Yes ;) Don't think I've seen any buffering settings in the setup. Unless there
are messages larger than 32k I can't see the buffering making much difference,
that appears to be its minimum..

Spec


--- SuperBBS v1.17-3 (Eval)
* Origin: (21:3/101)

Hello Spectre,

Were these errors related to large messages? I saw that at one
time

Yes ;) Don't think I've seen any buffering settings in the setup.
Unless there are messages larger than 32k I can't see the buffering
making much difference, that appears to be its minimum..

The FE146X.EXE is a 32bit DPMI version, might get you over the hump. I only had
to walk back a few messages in FSX_BOT to find a 51Kb message.. :)

Ttyl :-),
Al

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

Hello Spectre,

The FE146X.EXE is a 32bit DPMI version, might get you over the hump. I only had to walk back a few messages in FSX_BOT to find a 51Kb
message.. :)

Make that a 16bit DPMI version.

Ttyl :-),
Al

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

On 24 Dec 2019 at 11:35p, Alterego pondered and said...

So I've just noticed, that I didnt receive the original message from Spectre. (But I have received others, so its not a hub down issue...)

Comparing what I have here, with what's on 21:3/100 I see a couple of messages missing. When christmas is done and dusted, might have to research this.

So if I understand you right it's missing messages from 3/101 not making it
to 3/100

I agree with the Christmas thing... my body/head is full of too much food and drink to make too much sense of much right now :)

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

The FE146X.EXE is a 32bit DPMI version, might get you over the hump.

I'm using the DPMI version now. I couldn't get past memory problems with the �regular DOS version. I s'pose it makes sense theres something over 32k to �produce those errors.... didn't think to hard about it, I never see them ;) �Alright I'll bang it up to 64k and see what happens.

Spec


--- SuperBBS v1.17-3 (Eval)
* Origin: (21:3/101)

The FE146X.EXE is a 32bit DPMI version, might get you over the hump.

I'm using the DPMI version now. I couldn't get past memory problems with the regular DOS version. I s'pose it makes sense theres something over 32k to produce those errors.... didn't think to hard about it, I never see them ;) Alright I'll bang it up to 64k and see what happens.

Spec


--- SuperBBS v1.17-3 (Eval)
* Origin: (21:3/101)

Re: Re: Dupes and Node address
By: Avon to Alterego on Thu Dec 26 2019 10:12 am

So if I understand you right it's missing messages from 3/101 not making it to 3/100

No, I see messages on 3/100 - that I've sent up, but I dont see those messages making it to 2/116.

Or another way, I see folks replying to messages to Spectre (from 2/116), but I
havent seen the original message. So they are obviously leaving 3/100 - and getting to some folks/nets, but not making it to 2/100 and/or 2/116.

The first validation, would be to see if those missing messages are on Hub 2. ...deon


... A stockbroker is someone who invests your money until it is all gone.
--- SBBSecho 3.10-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

On 26 Dec 2019 at 03:08p, Alterego pondered and said...

No, I see messages on 3/100 - that I've sent up, but I dont see those messages making it to 2/116.

Or another way, I see folks replying to messages to Spectre (from
2/116), but I havent seen the original message. So they are obviously leaving 3/100 - and getting to some folks/nets, but not making it to
2/100 and/or 2/116.

The first validation, would be to see if those missing messages are on
Hub 2. ...deon

It could be a couple of things..

The first being if they went MIA via 1/100 it would be because I recall
borking some .clo and .hlo files when I cut over to HPT.. I ended up with two for some nodes and that did not end well. So it's entirely possible during
that cut over some packets to nodes went MIA

The second idea is that I have a suspicion all may not be well with Mystic BinkP and/or MUTIL and in saying that I have a hunch some packets may be getting lost in the process of creating Binkley Style Outbound mailer.. hence the initial cut over to BinkD which Oli seemed to feel dealt to his missing packets.

My plan is to work with Solaris and first update NET to BinkD so that we get all traffic off Mystic BinkP server for now and test this theory out..
It will also speedup traffic to NET 2 nodes a lot :)

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Re: Re: Dupes and Node address
By: Avon to Alterego on Thu Dec 26 2019 05:20 pm

My plan is to work with Solaris and first update NET to BinkD so that we get all traffic off Mystic BinkP server for now and test this theory out.. It will also speedup traffic to NET 2 nodes a lot :)

I'm looking forward to that :)
...deon


... Homosexuality must be hereditory -- most gays have heterosexual parents. --- SBBSecho 3.10-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

On 26 Dec 2019 at 04:58p, Alterego pondered and said...

I'm looking forward to that :)

I'll keep you (and the rest of the gang) posted.

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)