• Mystic tosser?

    From Rick Smith@1:340/202.1 to g00r00 on Saturday, May 16, 2020 17:17:49
    Greetings g00r00,

    I am going to do my best to explain my question/concern..

    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 my point system gets it as a dupe? It has been pointed out by others 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 mystic or something else? Obviosly this is not a huge problem, just my OCD....<VBG>

    Regards ...
    Rick Smith
    A Friend will help you move, a good friend will help you move a body!

    --- WinPoint Beta 5 (359.1)
    * Origin: Abacus Sysop Point..... bbs.abon.us:2323 (1:340/202.1)
  • From g00r00@1:129/215 to Rick Smith on Saturday, May 16, 2020 17:22:43
    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)
  • From mark lewis@1:3634/12 to g00r00 on Saturday, May 16, 2020 18:52:24
    Re: Re: Mystic tosser?
    By: g00r00 to Rick Smith on Sat May 16 2020 17:22:43


    g00r00> SEEN-BY lines do not work with point systems unfortunantely so

    sure they do... the standard 2D net/node is added like normal... either the point does it or the BOSS node, one of the two... at that point, everything else is the same as any other time... the tosser just needs to remember that the message came from the point address when it processed the original packet header from the point system... parsing of the control lines may also be necessary, in some cases...

    g00r00> there will never be a seen-by entry for "202.1". This is not a
    g00r00> Mystic limitation, its a FidoNet limitation.

    correct on all three accounts :)


    )\/(ark
    --- SBBSecho 3.11-Linux
    * Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)
  • From g00r00@1:129/215 to mark lewis on Saturday, May 16, 2020 19:38:40
    g00r00> SEEN-BY lines do not work with point systems unfortunantely so
    g00r00> there will never be a seen-by entry for "202.1". This is not a
    g00r00> Mystic limitation, its a FidoNet limitation.

    sure they do... the standard 2D net/node is added like normal... either the point does it or the BOSS node, one of the two... at that point,

    I added the text back that you removed from what I said, since what I actually said and what you quoted mean two different things.

    If you read his original message or my quote, I was responding to where he says "the SEEN-BY does not include 202.1 it only shows 202" Again, there should
    not be a 202.1 SEEN-BY because FidoNet does not support it.

    Everything else you describe is of course how points work with SEEN-BY but
    its also not what we were discussing. :)

    --- Mystic BBS v1.12 A46 2020/05/11 (Windows/64)
    * Origin: Sector 7 | Mystic WHQ (1:129/215)
  • From Rick Smith@1:340/202.1 to g00r00 on Saturday, May 16, 2020 16:20:39
    //Hello g00r00, //

    On *16.05.20* At *17:22:43* you replied to a post in *MYSTIC*
    from *Rick Smith* About *"Re: Mystic tosser?"*.


    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.

    Not exactley sorry my fingers dont always accuratly depict what I am thinking<VBG>

    Ok so I write a message on my laptop (point 1:340/202.1) when I am finished I poll my uplink which is my mystic bbs (1:340/202) mystic then polls its hub with the new echomail (1:340/400). When mystic then polls hub again to receive packets that echo message that was written on point then comes to mystic (1:340/202) as new mail, then when I poll mystic with my point I get that message as new mail therefore now as a dupe message, so everything I write on my point has two copies the original message I wrote then the one that returns after the above routing happens.

    Granted fido routing is not my forte but somewhere I would think that it would be known that the message originated on my point and presumably not be sent to my point as new mail? Of course I could be completely wrong.


    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.


    Id be happy to send you anything you like to have a look at it... As soon as I save and send this very message it will be in the mystic message area here on my point and in about 10 minutes it will be listed there twice, and show one of them as new and unread/

    Regards ...
    Rick Smith

    --- WinPoint Beta 5 (359.1)
    * Origin: Abacus Sysop Point..... bbs.abon.us:2323 (1:340/202.1)
  • From g00r00@1:129/215 to Rick Smith on Saturday, May 16, 2020 21:30:31
    Ok so I write a message on my laptop (point 1:340/202.1) when I am finished I poll my uplink which is my mystic bbs (1:340/202) mystic then polls its hub with the new echomail (1:340/400). When mystic then polls hub again to receive packets that echo message that was written on point then comes to mystic (1:340/202) as new mail, then when I poll mystic
    with my point I get that message as new mail therefore now as a dupe

    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.

    --- Mystic BBS v1.12 A46 2020/05/16 (Windows/64)
    * Origin: Sector 7 | Mystic WHQ (1:129/215)
  • From Rick Smith@1:340/202.1 to g00r00 on Saturday, May 16, 2020 19:58:07
    //Hello g00r00, //

    On *16.05.20* At *21:30:31* you replied to a post in *MYSTIC*
    from *Rick Smith* About *"Re: Mystic tosser?"*.



    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.

    340/400 is SBBS but the dupes arent on mystic, they are when I poll mystic with my point I get the dupes on my point from my mystic system, I would this mystic which is my points uplink would not send my point the dupes as I sent the mystic system the original message?

    Regards ...
    Rick Smith

    --- WinPoint Beta 5 (359.1)
    * Origin: Abacus Sysop Point..... bbs.abon.us:2323 (1:340/202.1)
  • From Rick Smith@1:340/202.1 to g00r00 on Saturday, May 16, 2020 20:51:50
    //Hello g00r00, //

    On *16.05.20* At *21:30:31* you replied to a post in *MYSTIC*
    from *Rick Smith* About *"Re: Mystic tosser?"*.




    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)




    Regards ...
    Rick Smith

    --- WinPoint Beta 5 (359.1)
    * Origin: Abacus Sysop Point..... bbs.abon.us:2323 (1:340/202.1)
  • From Rick Smith@1:340/202.1 to g00r00 on Saturday, May 16, 2020 20:53:41
    //Hello g00r00, //

    On *16.05.20* At *21:30:31* you replied to a post in *MYSTIC*
    from *Rick Smith* About *"Re: Mystic tosser?"*.



    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.


    Real quick I tried it from my point to my mystic then on to fsxnet also mystic and the message still made it back to my point as a dupe.. just an fyi

    Regards ...
    Rick Smith

    --- WinPoint Beta 5 (359.1)
    * Origin: Abacus Sysop Point..... bbs.abon.us:2323 (1:340/202.1)
  • From Rick Smith@1:340/202 to Rick Smith on Sunday, May 17, 2020 00:16:30
    Yep, so if I am understanding you then 1:340/400 is sending you duplic messages and Mystic is catching them as a duplicate. The question is

    ok so I just logged on to my mystic system and noticed that the dupes showing up on my point system (sent from point) are also in the dupes area of the bbs if that helps you.

    ---
    Regards,

    Rick // Nitro

    --- Mystic BBS v1.12 A46 2020/04/29 (Windows/64)
    * Origin: Abacus BBS! ---> bbs.abon.us:2323 (1:340/202)
  • From Nicholas Boel@1:154/10 to Rick Smith on Sunday, May 17, 2020 07:41:54
    Hello Rick,

    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?

    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)
  • From Nicholas Boel@1:154/10 to Rick Smith on Sunday, May 17, 2020 07:54:16
    Hello Rick,

    On Sun May 17 2020 00:16:30, Rick Smith wrote to Rick Smith:

    Yep, so if I am understanding you then 1:340/400 is sending
    you duplic
    messages and Mystic is catching them as a duplicate. The
    question is

    ok so I just logged on to my mystic system and noticed that the dupes showing up on my point system (sent from point) are also in the dupes
    area of the bbs if that helps you.

    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?

    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.

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

    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)
  • From mark lewis@1:3634/12 to Rick Smith on Sunday, May 17, 2020 09:36:13
    Re: Mystic tosser?
    By: Rick Smith to g00r00 on Sat May 16 2020 20:53:41


    Real quick I tried it from my point to my mystic then on to fsxnet
    also mystic and the message still made it back to my point as a
    dupe.. just an fyi

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


    )\/(ark
    --- SBBSecho 3.11-Linux
    * Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)
  • From g00r00@1:129/215 to Rick Smith on Sunday, May 17, 2020 11:57:01
    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)
  • From Micheal Pierce@1:340/201 to Nicholas Boel on Sunday, May 17, 2020 08:04:31
    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)
  • From mark lewis@1:3634/12 to Micheal Pierce on Sunday, May 17, 2020 13:32:48
    Re: Mystic tosser?
    By: Micheal Pierce to Nicholas Boel on Sun May 17 2020 08:04:31


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

    that depends... some tossers have the (global) option to send detected dupes on to links while not importing them into the local message base... sbbsecho is one of those...

    this option is available because of the fidoweb type distribution where dupes are expected and desired... why? to try to ensure that a system doesn't miss any posts in an echo... yes, it is dupe hell but properly written tossers should be able to handle it without problems... the key is the seenbys...


    )\/(ark
    --- SBBSecho 3.11-Linux
    * Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)
  • From Rick Smith@1:340/202.1 to Nicholas Boel on Sunday, May 17, 2020 07:44:37
    //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)
  • From Rick Smith@1:340/202.1 to mark lewis on Sunday, May 17, 2020 07:48:39
    //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)
  • From g00r00@1:129/215 to Micheal Pierce on Sunday, May 17, 2020 13:48:43
    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??

    PATH and SEEN-BY dupe checking will not be applied in this case because its a point, and point addressing is not supported in PATH and SEEN-BY.

    The remaining method for dupe checking then would be CRC checks against messages that previous arrived. But since this message never arrived before, it will not be seen as a duplicate.

    The issue is the uplink system should not be sending a message back to its origin system. So we need to start there and figure out why that is happening. If I could look at that PKT file sent back from 340 with the duplicate message I may be able to see what is happening.

    --- Mystic BBS v1.12 A46 2020/05/16 (Windows/64)
    * Origin: Sector 7 | Mystic WHQ (1:129/215)
  • From Rick Smith@1:340/202.1 to g00r00 on Sunday, May 17, 2020 17:42:21
    //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)
  • From Rick Smith@1:340/202.1 to g00r00 on Sunday, May 17, 2020 17:52:16
    //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)
  • From Michael Pierce@1:340/201.3 to g00r00 on Sunday, May 17, 2020 11:25:30
    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)
  • From Al@1:153/757 to Micheal Pierce on Sunday, May 17, 2020 12:15:00
    Hello Micheal,

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

    Mystic has had problems reading and writing seen-bys. I think A45 had problems. TTBOMK the current A46 version does not, in fact A46 seem to be working well in the echomail area from what I have seen.

    I've been reading of Rick's and now your problems with dupes and I'm not sure just what is going on. It sounds like both yours and Rick's Mystic is catching the dupes and putting them in the dupe area but I don't know why 340/400 is sending those messages back to you guys.

    I'm sure there is an explanation but I don't know what it is yet.

    Ttyl :-),
    Al

    --- GoldED+/LNX
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)
  • From g00r00@1:129/215 to Rick Smith on Sunday, May 17, 2020 16:06:07
    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.

    I host a point system myself and I will test there and also I will set up a hub/node/point network here when I have some time to see if I can get to bottom of things.

    You're right that seeing it on two hubs is very suspect! The non-Mystic hub should not be sending those messages back, but it doesn't mean that there is not a Mystic issue somewhere.

    --- Mystic BBS v1.12 A46 2020/05/16 (Windows/64)
    * Origin: Sector 7 | Mystic WHQ (1:129/215)
  • From g00r00@1:129/215 to Michael Pierce on Sunday, May 17, 2020 16:07:16
    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???

    There is no kill kludge option, that is left over from many years ago. I'll take a look at the default mutil.ini and remove it for future releases. You can just delete it from the file, its unused.

    Thanks for asking/letting me know about it.

    --- Mystic BBS v1.12 A46 2020/05/16 (Windows/64)
    * Origin: Sector 7 | Mystic WHQ (1:129/215)
  • From g00r00@1:129/215 to Al on Sunday, May 17, 2020 16:14:58
    Mystic has had problems reading and writing seen-bys. I think A45 had problems. TTBOMK the current A46 version does not, in fact A46 seem to
    be working well in the echomail area from what I have seen.

    It was A43 so it was a while ago (released March 2019).

    Even if he were using A43 that particular issue wouldn't effect this situation because the issue was with wrapping long seen-by lines (it was still using the abbrivated notation at the start of the line). His outbound message would only have one SEEN-BY (his 202 node) so it'd be unaffected.

    To my knowledge there was never a reading/writing issue just notation on new lines. It was wrong by spec but many tossers didn't seem to have a problem reading the abbrivated notation anyway (thats how it went 6+ years unnoticed!).

    I'm going to do some testing here to see if I can reproduce it.

    --- Mystic BBS v1.12 A46 2020/05/16 (Windows/64)
    * Origin: Sector 7 | Mystic WHQ (1:129/215)
  • From g00r00@1:129/215 to Rick Smith on Sunday, May 17, 2020 16:21:50
    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...

    No need to apologize I just didn't want you to keep spending your time on explaining it :)

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

    Capturing the PKT files sent to the hub or received from the hub with the message in question would be the best thing for me to have. But I can try to set up a local test here to see if I can reproduce and capture that very thing.

    --- Mystic BBS v1.12 A46 2020/05/16 (Windows/64)
    * Origin: Sector 7 | Mystic WHQ (1:129/215)
  • From mark lewis@1:3634/12 to Rick Smith on Sunday, May 17, 2020 16:48:15
    Re: Mystic tosser?
    By: Rick Smith to Nicholas Boel on Sun May 17 2020 07:44:37


    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 or their routing rules need some love but that's all a topic for another area if/when that operator decides to ask ;)


    )\/(ark
    --- SBBSecho 3.11-Linux
    * Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)
  • From g00r00@1:129/215 to Rick Smith on Sunday, May 17, 2020 17:32:10
    Ok I will reach out to him and see if he has any ideas.

    Capturing the PKT files sent to the hub or received from the hub with the message in question would be the best thing for me to have. But I can
    try to set up a local test here to see if I can reproduce and capture
    that very thing.

    Hi Rick,

    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?

    Thanks!

    --- Mystic BBS v1.12 A46 2020/05/16 (Windows/64)
    * Origin: Sector 7 | Mystic WHQ (1:129/215)
  • From Nicholas Boel@1:154/10 to Micheal Pierce on Sunday, May 17, 2020 16:55:34
    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)
  • From Nicholas Boel@1:154/10 to Rick Smith on Sunday, May 17, 2020 17:01:24
    Hello Rick,

    On Sun May 17 2020 07:44:36, Rick Smith wrote to Nicholas Boel:

    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.

    Ah ok. I thought I remember it differently when you first setup the point and was asking about Golded and using Mystic's message bases. So it's possible Mystic catches it as a dupe (not importing it into the actual echoarea) but forwards it on anyway?

    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.

    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)
  • From g00r00@1:129/215 to Nicholas Boel on Sunday, May 17, 2020 18:40:01
    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.

    I have another theory: The message isn't being re-sent from his hub at all, its just being reimported into Mystic by Mystic.

    When I re-enabled SEEN-BY dupe checking a few weeks ago I may have accidentally disabled the address checking for point systems that prevents the message from tossing back to itself. The latest version (dated 5/17) should not have that problem.

    --- Mystic BBS v1.12 A46 2020/05/17 (Windows/64)
    * Origin: Sector 7 | Mystic WHQ (1:129/215)
  • From Robert E Starr JR@1:340/400 to mark lewis on Sunday, May 17, 2020 15:42:59
    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)
  • From Micheal Pierce@1:340/201 to g00r00 on Sunday, May 17, 2020 16:56:54


    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.

    I have another theory: The message isn't being re-sent from his hub
    at all, its just being reimported into Mystic by Mystic.

    When I re-enabled SEEN-BY dupe checking a few weeks ago I may have accidentally disabled the address checking for point systems that
    prevents the message from tossing back to itself. The latest version (dated 5/17) should not have that problem.

    I can't test that because my main system (boss node) is on raspberry
    though I did update my test point to the latest, and it came right back

    Micheal


    ... Floggings will continue until morale improves
    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Mike's Mansion - Portland, OR - mansion.dynv6.net:2323 (1:340/201)
  • From g00r00@1:129/215 to Micheal Pierce on Sunday, May 17, 2020 22:09:53
    I can't test that because my main system (boss node) is on raspberry though I did update my test point to the latest, and it came right back

    Micheal

    Ahh okay, well then I will have to make you a Pi version. Stand by I'll try
    to get that done for you in the next hour or two.

    --- Mystic BBS v1.12 A46 2020/05/17 (Windows/64)
    * Origin: Sector 7 | Mystic WHQ (1:129/215)
  • From g00r00@1:129/215 to Micheal Pierce on Sunday, May 17, 2020 22:40:11
    I can't test that because my main system (boss node) is on raspberry though I did update my test point to the latest, and it came right back

    Hi Miachel,

    I've updated the Pi version now on the site!

    --- Mystic BBS v1.12 A46 2020/05/17 (Windows/64)
    * Origin: Sector 7 | Mystic WHQ (1:129/215)
  • From Robert E Starr JR@1:340/400 to Nicholas Boel on Sunday, May 17, 2020 19:04:09

    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)
  • From Rick Smith@1:340/202.1 to g00r00 on Sunday, May 17, 2020 18:19:42
    //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)
  • From Rick Smith@1:340/202.1 to g00r00 on Sunday, May 17, 2020 19:34:10
    //Hello g00r00, //

    On *17.05.20* At *18:40:01* you replied to a post in *MYSTIC*
    from *Nicholas Boel* About *"Re: Mystic tosser?"*.


    When I re-enabled SEEN-BY dupe checking a few weeks ago I may have accidentally disabled the address checking for point systems that prevents the message from tossing back to itself. The latest version (dated 5/17) should not have that problem.

    OK I upgraded to todays alpha, sent a message out from point and did not get it delivered back to me so whatever you did may have fixed it I will keep an eye on it.


    Regards ...
    Rick Smith

    --- WinPoint Beta 5 (359.1)
    * Origin: Abacus Sysop Point..... bbs.abon.us:2323 (1:340/202.1)
  • From mark lewis@1:3634/12 to Robert E Starr JR on Monday, May 18, 2020 06:47:56
    Re: Re: Mystic tosser?
    By: Robert E Starr JR to Nicholas Boel on Sun May 17 2020 19:04:09


    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.

    RESJ> I don't have there point setup in my sbbsecho, only there main
    RESJ> node number

    in your sbbsecho.ini, what does the section for 1:340/202 look like? does it start like this

    [node:1:340/202]

    or

    [node:1:340/202.ALL]

    or

    something else?

    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?

    if you have other points routing through your system, do they also exhibit this problem?

    we really really should take this to one of the SYNC_* or dovenet sync support areas since it is majorly offtopic in here...


    )\/(ark
    --- SBBSecho 3.11-Linux
    * Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)
  • From g00r00@1:129/215 to Rick Smith on Monday, May 18, 2020 00:36:35
    OK I upgraded to todays alpha, sent a message out from point and did not get it delivered back to me so whatever you did may have fixed it I will keep an eye on it.

    Great to hear! Thanks for letting me know. More reason to release a final
    A46 soon.

    --- Mystic BBS v1.12 A46 2020/05/17 (Windows/64)
    * Origin: Sector 7 | Mystic WHQ (1:129/215)
  • From Micheal Pierce@1:340/201.2 to g00r00 on Monday, May 18, 2020 07:04:56

    I can't test that because my main system (boss node) is on
    raspberry though I did update my test point to the latest, and it
    came right back

    Micheal

    Ahh okay, well then I will have to make you a Pi version. Stand by
    I'll try to get that done for you in the next hour or two.
    just tested, and its fixed ... yay!!!


    Micheal

    ... Gone crazy, be back later, please leave message.
    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Mike's Other Point - Portland, OR - mansion.dynv6.net: (1:340/201.2)
  • From Nicholas Boel@1:154/10 to g00r00 on Monday, May 18, 2020 17:12:22
    Hello g00r00,

    On Sun May 17 2020 18:40:00, g00r00 wrote to Nicholas Boel:

    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.

    I have another theory: The message isn't being re-sent from his hub
    at all, its just being reimported into Mystic by Mystic.

    I do believe he said he watches it leave his system and go to 340/400. But..

    When I re-enabled SEEN-BY dupe checking a few weeks ago I may have accidentally disabled the address checking for point systems that
    prevents the message from tossing back to itself. The latest version (dated 5/17) should not have that problem.

    .. If this is happening, it's giving the hub a reason to send it back. ;)

    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)
  • From Nicholas Boel@1:154/10 to Robert E Starr JR on Monday, May 18, 2020 17:17:42
    Hello Robert,

    On Sun May 17 2020 19:04:08, Robert E Starr JR wrote to Nicholas Boel:

    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)

    Try enabling Circular Path Detection.

    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)
  • From Nicholas Boel@1:154/10 to mark lewis on Monday, May 18, 2020 17:22:44
    Hello mark,

    On Mon May 18 2020 06:47:56, mark lewis wrote to Robert E Starr JR:

    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.

    if you have other points routing through your system, do they also
    exhibit this problem?

    So far two points are having the same problem, with the same software for their boss nodes, and same uplink (340/400).

    we really really should take this to one of the SYNC_* or dovenet sync support areas since it is majorly offtopic in here...

    The topic started here, and involves Mystic. Why wouldn't we want to get it solved here as well just because both Mystic and Synchronet are in the equasion?\

    Calm your tiddies, mark.

    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)
  • From mark lewis@1:3634/12 to Nicholas Boel on Tuesday, May 19, 2020 05:43:51
    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...


    )\/(ark
    --- SBBSecho 3.11-Linux
    * Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)
  • From Micheal Pierce@1:340/201 to mark lewis on Tuesday, May 19, 2020 05:46:11


    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)
  • From g00r00@1:129/215 to Micheal Pierce on Tuesday, May 19, 2020 11:27:21
    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)
  • From Micheal Pierce@1:340/201 to g00r00 on Tuesday, May 19, 2020 09:58:05
    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)
  • From g00r00@1:129/215 to Micheal Pierce on Tuesday, May 19, 2020 16:12:57
    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 :-)

    Good to hear! I figured it got fixed since I hadn't heard more about it!

    The old Mystic releases should be fine too its just a couple of the "test A46" versions that had the Mystic-related issue (as a result of enabling the
    SEEN-BY dupe checking).

    --- Mystic BBS v1.12 A46 2020/05/19 (Windows/32)
    * Origin: Sector 7 | Mystic WHQ (1:129/215)
  • From Jeff Smith@1:282/1031 to Rick Smith on Thursday, May 21, 2020 21:10:54

    Hello Rick!

    16 May 20 16:20, you wrote to g00r00:

    Ok so I write a message on my laptop (point 1:340/202.1) when I am finished I poll my uplink which is my mystic bbs (1:340/202) mystic
    then polls its hub with the new echomail (1:340/400). When mystic then polls hub again to receive packets that echo message that was written
    on point then comes to mystic (1:340/202) as new mail, then when I
    poll mystic with my point I get that message as new mail therefore now
    as a dupe message, so everything I write on my point has two copies
    the original message I wrote then the one that returns after the above routing happens.

    If I understand correctly. A message originating on a point (/202.1) gets
    sent to and processed by (202.0) and then sent to and processed by (/400.0) then (/400.0) sends the same message back to (/202.0).

    It would seem that (/400.0) should be looking at any /202.* AKA as /202.0
    and since /202 would be in the seen-by's then (/404.0) would avoid sending
    the same message back to (/202.0).

    I have Mystic, BBBS, and Synchronet setup here on Linux 64 PC's and use
    point AKA on several of the and haven't run into a point issue

    Jeff


    --- Mystic v1.12 A46 (2020/04/11) GoldED+/LNX 1.1.5-b20170303
    * Origin: The OuijaBoard BBS - bbs.ouijabrd.net (1:282/1031)