Holy shit, I just got a dozen or so dupes in fsxNet again and they weren't thrown in my dupe echo. This is pretty annoying. I wish we could get to the bottom of this or get it solved somehow. :(

--- Mystic BBS v1.12 A46 2020/03/18 (Linux/64)
* Origin: monterey bbs (21:1/168)

ryan wrote (2020-04-11):

Holy shit, I just got a dozen or so dupes in fsxNet again and they weren't thrown in my dupe echo.

I've got 11 dupes. They all went the same route

@PATH: (...) 4/106 1/133 100 (...)

One of these nodes is mot likely responsible. 1/133 shouldn't be in the path. Old Mystic version with major FTN bugs, not fit for fidoweb routing.

This is pretty annoying. I wish we could get to
the bottom of this or get it solved somehow. :(

Mystic problem, talk to the author of the software. Or get a decent tosser that
recognizes dupes.

---
* Origin: (21:3/102)

Hello Oli,

I've got 11 dupes. They all went the same route

@PATH: (...) 4/106 1/133 100 (...)

One of these nodes is mot likely responsible. 1/133 shouldn't be in
the path. Old Mystic version with major FTN bugs, not fit for fidoweb routing.

Yes, 1/133 is in the path. He asked me for a feed I think for redundency. That node has been accepting but not sending mail for a week or so, I suspect a stuck tosser. He has been connected here for some time.

I also got a bunch of dupes when his node started tossing again. Some where my long line test messages and they were not truncated at 256 characters so they were changed from the first messages that went around.

My node was certainly in those seen-by's so they shouldn't have come back here but they did and I suppose others saw them too.

This is pretty annoying. I wish we could get to
the bottom of this or get it solved somehow. :(

Mystic problem, talk to the author of the software. Or get a decent
tosser that recognizes dupes.

If g00r00 was about I would certainly support his efforts but without him being
here that is a rather hard road to travel.

I am going to delink 1/133. That will solve this problem but it doesn't solve the issue we are currently faced with.

Ttyl :-),
Al

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

Re: dupes. again.
By: ryan to All on Sat Apr 11 2020 11:14 am

the bottom of this or get it solved somehow. :(

Hello Ryan

How about upgrading to the latest Alpha, I'm running 04/09/20
maybe, just maybe that may help.

I think Netsurge upgraded one of his boxes to the same.



Havok

... The name of the popular lubricant WD-40 stands for "Water Displacement, 40th formula".

---
þ Synchronet þ Gray Matter BBS | graymatterbbs.com:2332
* Origin: fsxNet FTN<>QWK Gateway (21:4/10)

Hello Havok,

the bottom of this or get it solved somehow. :(

How about upgrading to the latest Alpha, I'm running 04/09/20
maybe, just maybe that may help.

No, that will not help. The current A46 mutil is truncating long lines in messages at 256 characters, among other issues with seen-by's.

I think Netsurge upgraded one of his boxes to the same.

I have hope that the mutil in A45 may work for our purposes here in fsxNet although that version also changes messages in transit. That makes it unfit for
use in Fidonet.

There are grave issues with mutils tossing currently. I'm sure they could be fixed if there is a will to do that.

If g00r00 will work toward that he has my support although I haven't seen him here or otherwise for some time.

Ttyl :-),
Al

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

Re: dupes. again.
By: Al to Havok on Sat Apr 11 2020 01:54 pm

If g00r00 will work toward that he has my support although I haven't seen him here or otherwise for some time.

I guess we will wait and see then!

g00r00 is a pretty smart guy I'm sure he will figure it out...

Havok

... Every instructor assumes you have nothing to do but study for his course.

---
þ Synchronet þ Gray Matter BBS | graymatterbbs.com:2332
* Origin: fsxNet FTN<>QWK Gateway (21:4/10)

Hello Havok,

If g00r00 will work toward that he has my support although I
haven't seen him here or otherwise for some time.

I guess we will wait and see then!

Yep, that's all we can do.

g00r00 is a pretty smart guy I'm sure he will figure it out...

Also true. Looking at Mystic BBS I think g00r00 is a master programmer and can work this all out in time.

These issues are not an issue for most BBSs. These problems just come into play
for the hubs and nodes moving mail.

Ttyl :-),
Al

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

How about upgrading to the latest Alpha, I'm running 04/09/20
maybe, just maybe that may help.

I'm actually a bit nervous about that. I think mismatched alphas of mystic
are probably a significant part of why we're dealing with this in the first place.

--- Mystic BBS v1.12 A46 2020/03/18 (Linux/64)
* Origin: monterey bbs (21:1/168)

Re: dupes. again.
By: Al to Havok on Sat Apr 11 2020 03:12 pm

These issues are not an issue for most BBSs. These problems just come into play for the hubs and nodes moving mail.

Hello Al

Isn't hub and nodes moving mail the same thing?


Just a thought...

Havok

... The English may not like music, but they absolutely love the noise it makes

---
þ Synchronet þ Gray Matter BBS | graymatterbbs.com:2332
* Origin: fsxNet FTN<>QWK Gateway (21:4/10)

Hello Havok,

These issues are not an issue for most BBSs. These problems just
come into play for the hubs and nodes moving mail.

Isn't hub and nodes moving mail the same thing?

No, a hub is a node who others rely on to get mail/files. They are setup with the purpose of moving mail/files quickly and efficiently to connected nodes.

A hub node such as 21:1/100 21:2/100 and so on are setup for that purpose.

I am not a hub although I do have quite a few links and my goal is the same, to
move mail/files quickly to connected nodes. I do the same although I don't have
any kind of hub status.

Ttyl :-),
Al

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

I'm actually a bit nervous about that. I think mismatched alphas of
mystic are probably a significant part of why we're dealing with this in the first place.

The latest alpha just adds some functionality to QWK hubbing, I don't think anything was changes with mutil.

|15frank |08// |15netsurge
|07disksh0p|08!|07bbs |08% |07bbs.diskshop.ca |08% |07mystic goodness |11SciNet |03ftn hq |08% |07https://scinet-ftn.org

--- Mystic BBS v1.12 A46 2020/04/09 (Linux/64)
* Origin: % disksh0p!bbs % bbs.diskshop.ca % SciNet ftn hq % (21:4/154)

Hello Havok,

Isn't hub and nodes moving mail the same thing?

No, a hub is a node who others rely on to get mail/files. They are
setup with the purpose of moving mail/files quickly and efficiently to connected nodes.

One further note.. :)

The hubs are all meshed together. Each hub sends messages to each other hub so they well get and deal with many dupes. That way any node in any net can be fed
mail by that nodes hub and will get all messages in the net.

That is probably the biggest difference between a hub and a node.

Ttyl :-),
Al

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

On 04-11-20 11:14, ryan wrote to All <=-

Holy shit, I just got a dozen or so dupes in fsxNet again and they
weren't thrown in my dupe echo. This is pretty annoying. I wish we
could get to the bottom of this or get it solved somehow. :(

I saw a bunch of old messages today.


... Political Season: Does this mean we can shoot them?!?!
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)

I have hope that the mutil in A45 may work for our purposes here in
fsxNet although that version also changes messages in transit. That
makes it unfit for use in Fidonet.

There are grave issues with mutils tossing currently. I'm sure they
could be fixed if there is a will to do that.

If g00r00 will work toward that he has my support although I haven't
seen him here or otherwise for some time.

Does pkt have message_id to look for ?

--- Mystic BBS v1.12 A46 2020/04/09 (Windows/64)
* Origin: SpaceSST BBS (21:1/129)

Hello gallaxial,

If g00r00 will work toward that he has my support although I
haven't seen him here or otherwise for some time.

Does pkt have message_id to look for ?

Are you refering the the .bad pkt we were talking about?

The message with the D'Bridge 4 tear line and "if you build it he will come" in
the origin line does not have a msgid or any message body at all.

No to, no from and no subject either. The date is 06 Apr 20 00:00:00.

I think that is all that remains of a message that has somehow become corrupt.

Ttyl :-),
Al

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

Re: Re: dupes. again.
By: ryan to Havok on Sat Apr 11 2020 04:18 pm

I'm actually a bit nervous about that. I think mismatched alphas of mystic are probably a significant part of why we're dealing with this in the first place.

Your most likely right, wait for a bit and I'm sure g00r00 will have it
all fixed up!

Havok

... Mother Nature is a Bitch.

---
þ Synchronet þ Gray Matter BBS | graymatterbbs.com:2332
* Origin: fsxNet FTN<>QWK Gateway (21:4/10)

Re: dupes. again.
By: Al to Havok on Sat Apr 11 2020 04:58 pm

The hubs are all meshed together. Each hub sends messages to each other hub so they well get and deal with many dupes. That way any node in any net can be fed mail by that nodes hub and will get all messages in the net.

Morning Al

Interesting I guess I read the post wrong!

But keep it up feed my brain....

Thanks...

Havok

... Seeing is deceiving. It's eating that's believing.

---
þ Synchronet þ Gray Matter BBS | graymatterbbs.com:2332
* Origin: fsxNet FTN<>QWK Gateway (21:4/10)

On 11 Apr 2020, Al said the following...

Hello gallaxial,

If g00r00 will work toward that he has my support although I
haven't seen him here or otherwise for some time.

Does pkt have message_id to look for ?

Are you refering the the .bad pkt we were talking about?

The message with the D'Bridge 4 tear line and "if you build it he will come" in the origin line does not have a msgid or any message body at
all.

No to, no from and no subject either. The date is 06 Apr 20 00:00:00.

I think that is all that remains of a message that has somehow become corrupt.

I look a .pkt it does not refer of the origin of post and the pass thru
none , i do not think fido tech have a dup check or a control about that

--- Mystic BBS v1.12 A46 2020/04/09 (Windows/64)
* Origin: SpaceSST BBS (21:1/129)

Vk3jed wrote to ryan <=-

I saw a bunch of old messages today.

Apparently Magicka is handling these as I am not seeing them.
<knocks-on-wood>


... "Hired goons????" - Homer
--- MultiMail
* Origin: Possum Lodge South * possumso.fsxnet.nz:7636/SSH:2122 (21:4/134)

Hello gallaxial,

I look a .pkt it does not refer of the origin of post and the
pass thru none , i do not think fido tech have a dup check or a
control about that

I'm not exactly sure what you said there. Every .pkt has an origin address and a destination address and will contain one or more messages to be tosssed.

As long as the data is intact there should be no problem tossing those messages
where they need to go.

Looking at the latest .bad pkt I have here it looks like that message in the AFTERSHOCK area it looks like it originated at 21:1/133 (the path line). I know
that is not right.

I got another that appeared to be from 21:1/106, a similar situation but wrong.

Bad input I think is to problem here.

I have two of these empty messages in the AFTERSHOCK area here on 6 Apr 20. No from, no to, no subject and no message body at all. That's where this seems to all start.

With a little luck it's over now. ;)

Ttyl :-),
Al

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

On 11 Apr 2020 at 11:14a, ryan pondered and said...

Holy shit, I just got a dozen or so dupes in fsxNet again and they
weren't thrown in my dupe echo. This is pretty annoying. I wish we could get to the bottom of this or get it solved somehow. :(

You and me both. Will revisit what the HUBs are running in the coming days.

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

On 11 Apr 2020 at 01:20p, Al pondered and said...

@REPLY: 21:3/102 5e922436
@MSGID: 21:4/106 5e922932
@CHRS: UTF-8 2
@TZUTC: -0700
@TID: hpt/lnx 1.9.0-cur 2019-12-05
@PATH: 4/106 100 1/100
107
Hello Oli,

First post.

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

On 11 Apr 2020 at 01:20p, Al pondered and said...

@REPLY: 21:3/102 5e922436
@MSGID: 21:4/106 5e922932
@CHRS: UTF-8 2
@TZUTC: -0700
@TID: hpt/lnx 1.9.0-cur 2019-12-05
@PATH: 4/106 1/133 100
Hello Oli,

I've got 11 dupes. They all went the same route

Second post...

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

Hello Avon,

On 11 Apr 2020 at 01:20p, Al pondered and said...

@REPLY: 21:3/102 5e922436
@MSGID: 21:4/106 5e922932
@CHRS: UTF-8 2
@TZUTC: -0700
@TID: hpt/lnx 1.9.0-cur 2019-12-05
@PATH: 4/106 1/133 100
Hello Oli,

I've got 11 dupes. They all went the same route

Second post...

21:1/133 had a stuck tosser (that's a guess on my part) for a week or so and then tossed everything in his inbound. They went dupidy dupidy doo for some reason.

Strange, 21:1/133 has been connected here for some time, more than 6 months I think and it has not caused trouble that I know of.

I got them all back here as well although they were all caught as dupes.

Ttyl :-),
Al

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

On 12 Apr 2020, Al said the following...

21:1/133 had a stuck tosser (that's a guess on my part) for a week or so and then tossed everything in his inbound. They went dupidy dupidy doo
for some reason.

Strange, 21:1/133 has been connected here for some time, more than 6 months I think and it has not caused trouble that I know of.

Hello all,

Looks like my system caused some issues? I apologise for any inconvenience.
You are correct - my system crashed, and it took me about a week to notice. There was a pile of packets to process when I restarted, and it looks like
some of them caused some dupes.

I know my version of Mystic is a bit outdated, but I'm not really sure that
the dupe issue caused by message mangling has actually been fixed in more recent versions, but if someone more knowlegable can point me to a more
stable recent build, I'd be happy to upgrade to that version.

I'm getting feeds from Al and Avon for redundancy, but if that's causing
dupes, feel free to disconnect me Al.

Anyway, sorry for being under the radar. Work is busy during the best of
times, but we are an essential service and short staffed, so work and stress are at an all-time high right about now.

I hope everyone is coping as best as you can.

Ian

--- Mystic BBS v1.12 A42 2019/02/01 (Linux/64)
* Origin: The Parity Error BBS - Kelowna BC (21:1/133)