I run a remote point, when I write a message on my point and poll my
boss node (my mystic bbs) messages get sent just fine. So mystic then polls its boss node 340/400 then when mystic polls that boss the next time, that message I wrote on my point gets sent back to mystic and is populated in the correct echo, still no problem, however the next time
my point polls my mystic board that message gets sent to my point. So on

So if I am understanding it, your hub is sending echomail back to you that originated from your system? If thats true then that seems like an issue on the hub that is sending mail back to you, no?

Its difficult for me to comment further than that without seeing the actual packets or more details.

that the messages I send from my point, do not include seen by 202.1
just 202? Is this something I have set up wrong or is a limitation of

SEEN-BY lines do not work with point systems unfortunantely so there will never be a seen-by entry for "202.1". This is not a Mystic limitation, its a FidoNet limitation.

Its of course possible something else is going on that is either a configuration issue or a bug but I think I will need very specific details to figure that out.

--- Mystic BBS v1.12 A46 2020/05/11 (Windows/64)
* Origin: Sector 7 | Mystic WHQ (1:129/215)

On Sat May 16 2020 20:51:50, Rick Smith wrote to g00r00:

Yep, so if I am understanding you then 1:340/400 is sending you
duplicate messages and Mystic is catching them as a duplicate.
The question is why is 340/400 sending you messages that
originated from you as it should not be. What system is
340/400? It sounds like the issue is with 340/400, and Mystic is
properly catching the duplicate loop.

So it goes <340/202.1> message written -----> Mystic BBS
(340/202)-------> SBBS 340/400 SBBS 340/400 ----->Mystic BBS
340/202-------> point 340/202.1 (DUPE)

1) 340/400 shouldn't send the message back to 340/202 first off.

2) 340/202 should catch it as a dupe before it is sent back to the
point.

From what I've gathered from previous postings, 340/202.1 (Golded) is using the same message base files as 340/202 (Mystic)? Or was this
changed recently?

Rick and I have basicly the same setup

uplink 340/400
our main fidonet 201 for me and 202 for Rick both running Mystic

point configuration
binkd for mailer
hpt (husky) for tosser
golded for message editor

I think the problem is with 400 or hpt, something somewhere I think is stripping off the seenbys or just ignoring them.

everytime I enter a message on my point (201.2), it does the same thing, it comes back as a dupe, but, I do not see a dupe mystic (a46)

but shouldn't mystic be stopping a dupe from continuing down the line??

Micheal

... Please Captain not in front of the Klingons
--- GoldED+/LNX 1.1.5-b20180707
* Origin: Mike's Mansion - Portland, OR - mansion.dynv6.net:2323 (1:340/201)

So it goes <340/202.1> message written -----> Mystic BBS
(340/202)-------> SBBS 340/400
SBBS 340/400 ----->Mystic BBS 340/202-------> point 340/202.1 (DUPE)

I've understood the order the very first time you explained it, so you don't have to keep trying to reexplain each time. :)

340/202 is sending a message to 340/400 and then 340/400 is turning around
and sending that message right back to 340/202. That shouldn't happen. So that is why I am saying we need to start there and see whats up with
340/400.

--- Mystic BBS v1.12 A46 2020/05/16 (Windows/64)
* Origin: Sector 7 | Mystic WHQ (1:129/215)

//Hello Nicholas, //

On *17.05.20* At *7:54:16* you replied to a post in *MYSTIC*
from *Rick Smith* About *"Mystic tosser?"*.

In that case, Mystic is catching them as dupes properly, and placing them in your DUPES area. This is the way it's supposed to be, is it not?

Yes that does seem the way it should be.

Just as well, the dupes are on your point also, because you're utilizing the same Mystic message bases with Golded. So it seems your Mystic BBS
may not be "sending" your point the dupes, but in fact they're already there because you're seeing them with Golded in the DUPE base on your Mystic system, if that makes sense.

Just to be clear my golded setup uses a mailer and tosser and so does my winpoint system neither of them just point to my mystic msg base,also on the point side they do not show in the "dupes" area they are being tossed into the actual echo areas. They do get tossed into the dupes area on the mystic system.

With that said, it seems the problem does in fact lie with 340/400.

This is probably accurate, as netmail addressed to my point does not get routed to me through my boss node, I still have to poll 340/400 with my point to get any netmail addressed to it.




Regards ...
Rick Smith

--- WinPoint Beta 5 (359.1)
* Origin: Abacus Sysop Point..... bbs.abon.us:2323 (1:340/202.1)

//Hello mark, //

On *17.05.20* At *9:36:13* you replied to a post in *MYSTIC*
from *Rick Smith* About *"Mystic tosser?"*.

this is starting to look like your point software is not properly detecting the dupes...

I definitley thought of that too. However two completley different point software setups behave the same way..Logically (at least in my head) leads me to believe its not the point setups, but who knows, right?



Regards ...
Rick Smith

--- WinPoint Beta 5 (359.1)
* Origin: Abacus Sysop Point..... bbs.abon.us:2323 (1:340/202.1)

//Hello g00r00, //

On *5/17/2020* At *11:57:01* you replied to a post in *MYSTIC*
from *Rick Smith* About *"Re: Mystic tosser?"*.

I've understood the order the very first time you explained it, so you don't have to keep trying to reexplain each time. :)

Got it, apologies...

340/202 is sending a message to 340/400 and then 340/400 is turning around and sending that message right back to 340/202. That shouldn't happen.
So that is why I am saying we need to start there and see whats up with 340/400.

Ok I will reach out to him and see if he has any ideas.

Regards ...
Rick Smith

--- WinPoint Beta 5 (359.1)
* Origin: Abacus Sysop Point..... bbs.abon.us:2323 (1:340/202.1)

//Hello g00r00, //

On *17.05.20* At *11:57:01* you replied to a post in *MYSTIC*
from *Rick Smith* About *"Re: Mystic tosser?"*.

340/202 is sending a message to 340/400 and then 340/400 is turning around and sending that message right back to 340/202. That shouldn't happen.
So that is why I am saying we need to start there and see whats up with 340/400.

I did reach out to see if he had any ideas, I do not know if I remembered to mention to you or not, but it also has the same behavior with the fsxnet hub.

Regards ...
Rick Smith

--- WinPoint Beta 5 (359.1)
* Origin: Abacus Sysop Point..... bbs.abon.us:2323 (1:340/202.1)

Hello g00r00!
was wondering, what does kill kludge do in multi.ini ?? it just says its on by default but does not explain what does it mean? disallow viewing of kludges or???

Michael

... What is mind? No matter! What is matter? Never mind! - Homer S.
--- GoldED+/LNX 1.1.5-b20180707
* Origin: Mike's Test Point - Portland, OR (1:340/201.3)

Hello Micheal,

On Sun May 17 2020 08:04:30, Micheal Pierce wrote to Nicholas Boel:

point configuration
binkd for mailer
hpt (husky) for tosser
golded for message editor

I think the problem is with 400 or hpt, something somewhere I think is stripping off the seenbys or just ignoring them.

I can tell you the problem isn't with HPT, as I use it as well. You may want to have a chat with 340/400 and see why it's being sent back to you.

but shouldn't mystic be stopping a dupe from continuing down the
line??

I would think so - so there may be a possibility of the boss node sending the dupe to the point when it shouldn't. However, 340/400 shouldn't be sending the message back to either one of your systems in the first place. So there may be more than one issue here.

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- GoldED+/LNX 1.1.5-b20181215
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

netmail addressed to my point does not get routed to me through my
boss node, I still have to poll 340/400 with my point to get any netmail addressed to it.

340/400 has some work to do, then... they've either not updated to the latest sbbsecho

runing build date 4/29/20 (was a bunch of months out of date)

or their routing rules need some love but that's all a
topic for another area if/when that operator decides to ask ;)

what area in sbbsecho do I need to show to you (note I will put in * for any pw)?


---

Rob Starr
Lord Time SysOp of
Time Warp of the Future BBS
Telnet://Time.Synchro.Net:24
ICQ # 11868133 or # 70398519 Jabber : lordtime2000@gmail.com
Astra : lord_time
X-Box : Lord Time 2000 Skype : lordtime@tds.net
* Origin: Time Warp of the Future BBS - Home of League 10 (1:340/400)

But the fact still remains that 340/400 is sending your original message back to you, which it shouldn't be.

This is probably accurate, as netmail addressed to my point does not get routed to me through my boss node, I still have to poll 340/400 with my point to get any netmail addressed to it.

Sounds like 340/400 has both your Mystic setup and your point configured on his
system, which he shouldn't. He should only have your Mystic system configured, and route any points you may have through that. That may or may not be the issue in this case though. Could be his dupe checker isn't set high enough, or is disabled completely? Another good place for him to look would be if he has "Circular Path Detection" enabled.

I don't have there point setup in my sbbsecho, only there main node number as for the Circular Path Detection, look at it now, it's not set (turn off)


---

Rob Starr
Lord Time SysOp of
Time Warp of the Future BBS
Telnet://Time.Synchro.Net:24
ICQ # 11868133 or # 70398519 Jabber : lordtime2000@gmail.com
Astra : lord_time
X-Box : Lord Time 2000 Skype : lordtime@tds.net
* Origin: Time Warp of the Future BBS - Home of League 10 (1:340/400)

//Hello g00r00, //

On *5/17/2020* At *17:32:10* you replied to a post in *MYSTIC*
from *Rick Smith* About *"Re: Mystic tosser?"*.

Assuming you are using Windows or Linux, can you upgrade to the version that is at:

www.mysticbbs.com/downloads/prealpha

And see if that fixes things for you?

Ill give it a try and get back to you

Regards ...
Rick Smith

--- WinPoint Beta 5 (359.1)
* Origin: Abacus Sysop Point..... bbs.abon.us:2323 (1:340/202.1)

Re: Mystic tosser?
By: Nicholas Boel to mark lewis on Mon May 18 2020 17:22:44

do you have any other "ALL" entries that might be affecting the
routing of points?

are these the only point netmails routing through your system?

Netmail isn't the problem. This topic involves echomail.

netmail is/was involved because the points were having to poll the
BOSS' uplink to get their routed netmails... not sure if that has been solved... that's where i came in and the two topics have split from
there with the same subject line...

The issues have been resolved with the latest pre-alphas - turned out that it was not a synchronet issue.


Micheal

... ...follow the yellow brick PATH...
--- GoldED+/LNX 1.1.5-b20180707
* Origin: Mike's Mansion - Portland, OR - mansion.dynv6.net:2323 (1:340/201)

netmail is/was involved because the points were having to poll the BOSS' uplink to get their routed netmails... not sure if that has bee

The issues have been resolved with the latest pre-alphas - turned out
that it was not a synchronet issue.

For clarification there was no change to Netmail in Mystic any time recently.

The netmail PKTs I saw coming from the Synchronet system that were sent out a few weeks ago were addressed to the wrong system which is why they were not going through. There wasn't anything I could do on the Mystic side to fix that. I think that is what Mark was refering to.

(What I just changed in Mystic was something specific to the very recent A46 pre-alphas only, so it would only affect people using the test-only
versions that happen to feed a point).

--- Mystic BBS v1.12 A46 2020/05/19 (Windows/32)
* Origin: Sector 7 | Mystic WHQ (1:129/215)

netmail is/was involved because the points were having to

poll the

BOSS' uplink to get their routed netmails... not sure if

that has bee

The issues have been resolved with the latest pre-alphas - turned
out that it was not a synchronet issue.

For clarification there was no change to Netmail in Mystic any time recently.

The netmail PKTs I saw coming from the Synchronet system that were
sent out a few weeks ago were addressed to the wrong system which is
why they were not going through. There wasn't anything I could do on
the Mystic side to fix that. I think that is what Mark was refering
to.

(What I just changed in Mystic was something specific to the very
recent A46 pre-alphas only, so it would only affect people using the test-only versions that happen to feed a point).

ooops, I forgot that there were multible "point" related issues, though both now do seem to be fixed, points can now send routed netmail again with the latest synchronet builds and the letest mystic builds now works for points as it should :-)

now, about those lottery numbers :-)

Micheal

... Be scared. Be very a'scared! - Crow
--- GoldED+/LNX 1.1.5-b20180707
* Origin: Mike's Mansion - Portland, OR - mansion.dynv6.net:2323 (1:340/201)