Greetings g00r00!


I have separate netmail for all my networks on mystic bbs however I get my fido addy on via line I wonder if anyone knows what I could possible have set wrong?

INTL 21:1/190 21:1/190
@TOPT 1
@MSGID: 21:1/190 e8628348
@TZUTC: -0800

-+-
Regards,

Rick // Nitro

-+- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
+ Origin: Abacus BBS! ---> bbs.abon.us:2323 (21:1/190)
@Via 1:340/202 @20201103.223845.UTC hpt/lnx 1.9.0-cur 2020-10-1


----
Regards,


Rick Smith (Nitro)

... Life is too short to take BBSing seriously
--- GoldED+/LNX 1.1.5-b20180707
* Origin: ----> Abacus Sysop Point --->>>>bbs.abon.us:2323 (77:1/130.1)

I have separate netmail for all my networks on mystic bbs however I get
my fido addy on via line I wonder if anyone knows what I could possible have set wrong?
@Via 1:340/202 @20201103.223845.UTC hpt/lnx 1.9.0-cur 2020-10-1

It looks like this was added via HPT so I am not sure how to help here.

The MSGID comes from Mystic and that part looks like its using the correct address at least.

I have to admit though that I do not test anymore with separate Netmail bases for each network so its possible something could be addressed wrong. I would probably have to try to set up a test here.

Sorry I just don't have a good idea or answer for you this time. My only idea is to try to set up a test here.

Maybe Netsurge will have some insight for us?

--- Mystic BBS v1.12 A47 2020/10/31 (Windows/64)
* Origin: Sector 7 | Mystic WHQ (77:1/138)

Greetings g00r00!

Tuesday November 03 2020 18:36, you wrote to me about an urgent matter!:

It looks like this was added via HPT so I am not sure how to help
here.

The MSGID comes from Mystic and that part looks like its using the
correct address at least.

I have to admit though that I do not test anymore with separate
Netmail bases for each network so its possible something could be addressed wrong. I would probably have to try to set up a test here.

Yeah I cant figure it out... Netsurge is helping me, he thought you might know something about it... I used to have a single netmail area but I switched to 5 separate ones to make sure it wasnt getting confused...<VBG>



----
Regards,


Rick Smith (Nitro)

... Ura BBS addict when you consider BBSing better than coffee
--- GoldED+/LNX 1.1.5-b20180707
* Origin: ----> Abacus Sysop Point --->>>>bbs.abon.us:2323 (77:1/130.1)

Yeah I cant figure it out... Netsurge is helping me, he thought you
might know something about it... I used to have a single netmail area
but I switched to 5 separate ones to make sure it wasnt getting confused...<VBG>

The addressing in Mystic is the same if you use one base or many netmail bases, so there should be no advantage to trying to create 5 different netmail bases. Its the same code that addresses the messages no matter what. You're probably only making things more confusing for yourself by assuming Mystic is going to get confused. :)

When you are posting a message the address that is used will be selected based on the zone of your destination address. So if you send the message to 21:1/1 then Mystic will try to find your address that begins with 21. If it can't find any match then it will use the address assigned to the message base in the configuration for that base.

The MSGID has the correct address so that seems to imply Mystic is selecting the correct address for the origin.

The rest (routing, and VIA is done by the tosser which is HPT) and that is hard for me to help with since its not a part of Mystic.

--- Mystic BBS v1.12 A47 2020/10/31 (Windows/64)
* Origin: Sector 7 | Mystic WHQ (77:1/138)

The MSGID comes from Mystic and that part looks like its using the correctaddress at least.

I have to admit though that I do not test anymore with separate Netmail basesfor each network so its possible something could be addressed
wrong. I wouldprobably have to try to set up a test here.

I'm working with him to figure out what is wrong. I have the same setup as him and hpt uses the proper via line so i'm sure it's a configuration issue.

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

--- Mystic BBS/QWK Gate v1.12 A47 2020/10/31 (Linux/64)
* Origin: % disksh0p!bbs % bbs.diskshop.ca % SciNet ftn hq % (77:1/100)

Greetings g00r00!

Answering a msg of <Tuesday November 03 2020>, from you to me, about Re: Via line:

Ok a update.... We (another sysop with same setup) made some routing changes and believe we have fixed part of that fido via line issue.. except...
Mikes setup, mystic bbs /hpt/binkd/golded sends now correct via line to both my point and bbs from either his bbs or point...
My setup Mystic bbs /hpt/binkd/mystic bbs editor still sends bogus via line
My point /hpt/binkd/golded sends correct via lines

Mike switched his to mystic bbs /hpt/binkd/mystic bbs editor sends bad via lines....

We tried all combinations with a single netmail area and with individual netmail areas it made no difference on the above results.. I think that has to do with mystic's editor or something I am not sure how but its the only thing we add to break the via line. Perhaps there is a setting in cfg we could alter? perhaps a Bug? I am running the Pi version and Mike is running the linux version.


----
Regards,


Rick Smith (Nitro)

... HALF A CENTURY OLD BBSing GRANNY *&&*
--- GoldED+/LNX 1.1.5-b20180707
* Origin: ----> Abacus Sysop Point --->>>>bbs.abon.us:2323 (77:1/130.1)

We tried all combinations with a single netmail area and with individual netmail areas it made no difference on the above results.. I think that has todo with mystic's editor or something I am not sure how but its the only thingwe add to break the via line. Perhaps there is a setting in
cfg we couldalter? perhaps a Bug? I am running the Pi version and Mike
is running the linuxversion.

Mystic would only add the via lines if you were using it to process mail, hpt is the one adding via lines.

I did notice one thing in your configs that you should change, I think that will fix the issue.

Drop the no-route from all your statement. so:

route no-route hold

becomes

route hold

Also, all of you direct statements would only be needed for a single node, not a node you are routing mail through. Since you have 1:*, 77:* etc, you are using that node to route mail.

switch:

route direct

to

route crash (or hold depending on how you have things setup with that specific uplink)

That should fix your issue.

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

--- Mystic BBS/QWK Gate v1.12 A47 2020/10/31 (Linux/64)
* Origin: % disksh0p!bbs % bbs.diskshop.ca % SciNet ftn hq % (77:1/100)

Greetings Netsurge!

Wednesday November 04 2020 15:54, you wrote to me about an urgent matter!:

* Forwarded from area 'scimystic'

We tried all combinations with a single netmail area and with
individual netmail areas it made no difference on the above
results.. I think that has todo with mystic's editor or
something I am not sure how but its the only thingwe add to break
the via line. Perhaps there is a setting in cfg we couldalter?
perhaps a Bug? I am running the Pi version and Mike is running
the linuxversion.

Mystic would only add the via lines if you were using it to process
mail, hpt is the one adding via lines.

I did notice one thing in your configs that you should change, I think that will fix the issue.

Drop the no-route from all your statement. so:

route no-route hold

becomes

route hold

Also, all of you direct statements would only be needed for a single
node, not a node you are routing mail through. Since you have 1:*,
77:* etc, you are using that node to route mail.

Ok I will give this a try i guess... Since writing this post earlier I installed golded on my bbs machine and it works perfectly with the routing as is, so should I still change it? Just seems if I write the netmail logged on to my bbs is messes up the via line, if I write it using golded it works?

Sorry not trying to sound daft or anything just seems mystic to me is causing it not the routing? Or can the routing somehow affect mystic? I am just trying to match that in my head...




----
Regards,


Rick Smith (Nitro)

... BBSing and Computers
--- GoldED+/LNX 1.1.5-b20180707
* Origin: ----> Abacus Sysop Point --->>>>bbs.abon.us:2323 (77:1/130.1)

Greetings Netsurge!

Answering a msg of <Wednesday November 04 2020>, from you to me, about Re: Via line:

I think I fixed it, in mystic because I had setup the multiple netmail areas for different networks and they all had the same file name I think it was pulling my fido addy from the message base.. I was sitting here staring at it and it dawned on me that is the only way that addy can get associated with netmail, so I went back to one netmail area for all 5 networks and have a 0:0/000 addy for it and it all works fine... ( I think ) I will test further but I think that did do it...

Thank you for the time you have spent trying to help me sort this out!


----
Regards,


Rick Smith (Nitro)

... It was good BBSing with you Netsurge!
--- GoldED+/LNX 1.1.5-b20180707
* Origin: ----> Abacus Sysop Point --->>>>bbs.abon.us:2323 (77:1/130.1)

On 03 Nov 2020, g00r00 said the following...

The addressing in Mystic is the same if you use one base or many netmail bases, so there should be no advantage to trying to create 5 different g0> netmail bases.

I was just reading about this over on fsx. I have a netmail base setup for each network, I'll have to update my config.


Jay

... She had a photographic memory, but never developed it

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: Northern Realms (77:1/156)

Thank you for the time you have spent trying to help me sort this out!

I'm glad it's fixed.

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

--- Mystic BBS/QWK Gate v1.12 A47 2020/10/31 (Linux/64)
* Origin: % disksh0p!bbs % bbs.diskshop.ca % SciNet ftn hq % (77:1/100)