Hello David!

22 Oct 24 08:04, you wrote to all:

I am hgaving a ton on issues with mail routing and apparently, as per
the book *it's my config*.

I have setup everything as a normal person would do, checked the docs
and I have 3 node addresses

FSX: 21:3/188
Fido: 3:633/2744.188
Micronet: 618:500/67

[...]

Post a log file sample and what your config setup is. Without that information no one will be able to help.




Vorlon


--- GoldED+/LNX 1.1.5-b20240302
* Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (21:1/195)

Hello Vorlon!

23 Oct 24 11:18, you wrote to me:

Hello David!

22 Oct 24 08:04, you wrote to all:

I am hgaving a ton on issues with mail routing and apparently, as
per the book *it's my config*.

I have setup everything as a normal person would do, checked the
docs and I have 3 node addresses

FSX: 21:3/188
Fido: 3:633/2744.188
Micronet: 618:500/67

[...]

Post a log file sample and what your config setup is. Without that information no one will be able to help.

I finally got it sorted out making some bad blood in the process ...

I think I'm going to try EleBBS too, not ditching mystic but I've heard its BinkD implementation is buggy -- not said by me --

I couln't find a good source of info or answer to my question on editing menus and translating them, but I'll leave that for another thread.


David


--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: SkyNet BBS | Colombia | bbs.skynetbbs.com:20023 (21:3/188)

David Gonzalez wrote to Vorlon <=-

I am hgaving a ton on issues with mail routing and apparently, as
per the book *it's my config*.

I have setup everything as a normal person would do, checked the
docs and I have 3 node addresses

FSX: 21:3/188
Fido: 3:633/2744.188
Micronet: 618:500/67

[...]

Post a log file sample and what your config setup is. Without that information no one will be able to help.

I finally got it sorted out making some bad blood in the process ...

So..... was it indeed your config, or something else? It's usually good
to provide the solution to problems, so that the next person may not
have to go through the same thing.



... Gone crazy, be back later, please leave message.
=== MultiMail/Linux v0.52
--- SBBSecho 3.20-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (21:2/138)

Hello Gamgee!

24 Oct 24 07:52, you wrote to me:

David Gonzalez wrote to Vorlon <=-

I am hgaving a ton on issues with mail routing and apparently,
as per the book *it's my config*.

I have setup everything as a normal person would do, checked the
docs and I have 3 node addresses

FSX: 21:3/188
Fido: 3:633/2744.188
Micronet: 618:500/67

[...]

Post a log file sample and what your config setup is. Without
that information no one will be able to help.

I finally got it sorted out making some bad blood in the process
...

So..... was it indeed your config, or something else? It's usually
good to provide the solution to problems, so that the next person may
not have to go through the same thing.

Apparently but not my mistake but mystic's, it was sending my fiodomail with my fsx AKA and also I had an issue with Golded, I accidentally added a domain @fidonet.org (5D) and @fidonet to try to see if mail went through but it ended up being worse.

I removed all of those from Golded and have not tried net/echo from mystic yet.

Thanks


David


--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: SkyNet BBS | Colombia | bbs.skynetbbs.com:20023 (21:3/188)

Hello Gamgee!

24 Oct 24 07:52, you wrote to me:

Apparently but not my mistake but mystic's, it was sending my fiodomail with my fsx AKA and also I had an issue with Golded, I accidentally added a domain @fidonet.org (5D) and @fidonet to try to see if mail went through but it ended up being worse.

I removed all of those from Golded and have not tried net/echo from mystic yet.

Thanks

David

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: SkyNet BBS | Colombia | bbs.skynetbbs.com:20023 (21:3/188)

I would also consciously keep in mind, none of the people assisting are doing this as "their job" (i.e. they are NOT being paid).

I have ran BBSs since the early 90's, and the community is like a brother-hood. While at (MANY) times there are moments of frustration, try to keep in mind that everyone wants to help.

(my 2 cents) take it or leave it.

-StingRay

A-Net Online

Hello StingRay!

24 Oct 24 12:54, you wrote to me:

I removed all of those from Golded and have not tried net/echo from
mystic yet.

Thanks

David

I would also consciously keep in mind, none of the people assisting
are doing this as "their job" (i.e. they are NOT being paid).

Yup, that's what community support means, and don't get me wrong I won't trash or ask for support as somebody suggested, that's why I started looking for solutions myself.

I have ran BBSs since the early 90's, and the community is like a brother-hood. While at (MANY) times there are moments of frustration,
try to keep in mind that everyone wants to help.

Even me, that's why I wrote about GoldED and how to fix some of the stuff I had going on.

(my 2 cents) take it or leave it.

That's how it is, indeed, don't worry thick skin.

-StingRay

A-Net Online
--- SBBSecho 3.14-Win32
* Origin: A-NET ONLINE - a-net-online.lol (21:3/189)

David


--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: SkyNet BBS | Colombia | bbs.skynetbbs.com:20023 (21:3/188)

David Gonzalez wrote to Gamgee <=-

I am hgaving a ton on issues with mail routing and apparently,
as per the book *it's my config*.

I have setup everything as a normal person would do, checked the
docs and I have 3 node addresses

FSX: 21:3/188
Fido: 3:633/2744.188
Micronet: 618:500/67

Post a log file sample and what your config setup is. Without
that information no one will be able to help.

I finally got it sorted out making some bad blood in the process
...

So..... was it indeed your config, or something else? It's usually
good to provide the solution to problems, so that the next person may
not have to go through the same thing.

Apparently but not my mistake but mystic's, it was sending my fiodomail with my fsx AKA and also I had an issue with Golded, I accidentally
added a domain @fidonet.org (5D) and @fidonet to try to see if mail
went through but it ended up being worse.

Well, I'd have to say that Mystic was only doing what you configured it
to do... If it was sending Fido mail with the FSX AKA, it must have
been because you configured it that way. There is no other explanation.

Not sure how Golded would have affected that, and wondering why you'd
even want to use that when just starting out. But that's your choice,
and that's OK. Again config problems, though...

I removed all of those from Golded and have not tried net/echo from
mystic yet.

I see. Well, good luck and hope it works. Thanks for the update.



... Apathy Error: Strike any key...or none, for that matter.
=== MultiMail/Linux v0.52
--- SBBSecho 3.20-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (21:2/138)

Hello Gamgee!

24 Oct 24 21:18, you wrote to me:

David Gonzalez wrote to Gamgee <=-

I am hgaving a ton on issues with mail routing and apparently,
as per the book *it's my config*.

I have setup everything as a normal person would do, checked
the docs and I have 3 node addresses

FSX: 21:3/188
Fido: 3:633/2744.188
Micronet: 618:500/67

Post a log file sample and what your config setup is. Without
that information no one will be able to help.

I finally got it sorted out making some bad blood in the process
...

So..... was it indeed your config, or something else? It's
usually good to provide the solution to problems, so that the
next person may not have to go through the same thing.

Apparently but not my mistake but mystic's, it was sending my
fiodomail with my fsx AKA and also I had an issue with Golded, I
accidentally added a domain @fidonet.org (5D) and @fidonet to try
to see if mail went through but it ended up being worse.

Well, I'd have to say that Mystic was only doing what you configured
it to do... If it was sending Fido mail with the FSX AKA, it must
have been because you configured it that way. There is no other explanation.

No, I think it was something to do with my uplink too, I was presenting all my AKAs and it would reject mail, then I had to create separate events to poll with 1 AKA first, then the other, but yeah I get what you say and respect it.

Not sure how Golded would have affected that, and wondering why you'd
even want to use that when just starting out. But that's your choice,
and that's OK. Again config problems, though...

That was my setup back in the 90s, FD+Fastecho+RA+GoldED.

I removed all of those from Golded and have not tried net/echo
from mystic yet.

I see. Well, good luck and hope it works. Thanks for the update.

... Apathy Error: Strike any key...or none, for that matter.
=== MultiMail/Linux v0.52
--- SBBSecho 3.20-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL *
(21:2/138)

David


--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: SkyNet BBS | Colombia | bbs.skynetbbs.com:20023 (21:3/188)

Re: Mail routing issues
By: David Gonzalez to Gamgee on Thu Oct 24 2024 09:35 pm

Howdy,

No, I think it was something to do with my uplink too, I was presenting all my AKAs and it would reject mail, then I had to create separate events to poll with 1 AKA first, then the other, but yeah I get what you say and respect it.

Nope, I dont think you are correct there.

The suggestion to "hide AKAs" and poll individually was to ensure that presenting multiple AKAs wasnt affecting how I process your mail - since I process mail on the fly as it is received, based on the authenticated AKAs.

As I explained to you via email/netmail - I wanted to illiminate if this code was the cause of the incorrect processing of mail (it wasnt). Its the first time I had a point address point being presented and that part of the code hasnt been tested. (I have other users collect mail from multiple networks, and they present all AKAs at the same time.)

So, upon review your tosser (mystic) was packing messages with your FSXnet AKA when the message was destined to fidonet.

Here is an example, a fidonet netmail packet 0cfcde35.pkt, received by you in mail bundle fd8af604.mo8, which your system sent at 21 Oct 2024 21:56:27 -0500:

00000000 bc 00 b8 0a e8 07 09 00 15 00 15 00 38 00 19 00 |............8...| 00000010 00 00 02 00 03 00 79 02 fe 00 xx xx xx xx xx xx |......y...xxxxxx| 00000020 xx xx 15 00 03 00 00 00 00 01 fe 00 01 00 15 00 |xx..............| 00000030 03 00 00 00 00 00 00 00 00 00 02 00 bc 00 00 00 |................| 00000040 03 00 5c 00 03 01 00 00 32 31 20 4f 63 74 20 32 |..\.....21 Oct 2| 00000050 34 20 20 32 31 3a 35 35 3a 32 39 00 61 64 6d 69 |4 21:55:29.admi|

This packet is from 0x0015:0x0003/0x00bc (21:3/188) to 0x0003:0x0279/0x0ab8 (3:633/2744) - and during that session you only presented your fido AKA.

You can refer to the respective FTS document to understand the format of the packet.

My system rejected the packet, because the source address, is not in the same domain as the target address (the domain was set to fidonet, because that's the address you authenticated with during the session). The INTL kludge was also incorrect.

As I explained, you had configuration problem, which I think you might have fixed.


...ëîåï
--- SBBSecho 3.20-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

David Gonzalez wrote to Gamgee <=-

So..... was it indeed your config, or something else? It's
usually good to provide the solution to problems, so that the
next person may not have to go through the same thing.

Apparently but not my mistake but mystic's, it was sending my
fiodomail with my fsx AKA and also I had an issue with Golded, I
accidentally added a domain @fidonet.org (5D) and @fidonet to try
to see if mail went through but it ended up being worse.

Well, I'd have to say that Mystic was only doing what you configured
it to do... If it was sending Fido mail with the FSX AKA, it must
have been because you configured it that way. There is no other explanation.

No, I think it was something to do with my uplink too, I was presenting all my AKAs and it would reject mail, then I had to create separate
events to poll with 1 AKA first, then the other, but yeah I get what
you say and respect it.

I just read the post in this area from your uplink, and I strongly
disagree with your claim. It clearly was your mis-configuration that
caused the issues. Everyone else (including me) has multiple network
AKAs, and don't have any problems with that.

It's OK to admit that you had something mis-configured. Nobody here
thinks less of you for that, as we've all done similar things. But continually trying to blame others for your own mistakes gives an
entirely different impression...

Not sure how Golded would have affected that, and wondering why you'd
even want to use that when just starting out. But that's your choice,
and that's OK. Again config problems, though...

That was my setup back in the 90s, FD+Fastecho+RA+GoldED.

OK, but this isn't the 90's, and you're not using ANY of that software
now. You're using Mystic. At least in the beginning, when trying to
get set up, keep things simple. That helps to avoid mis-configuration.
:-)

Good luck with things, and hope you stick around!


... He does the work of 3 Men...Moe, Larry & Curly
=== MultiMail/Linux v0.52
--- SBBSecho 3.20-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (21:2/138)

On Fri, Oct 25 02:35:20 -0500, you wrote:

No, I think it was something to do with my uplink too, I was presenting all my AKAs and it would reject mail, then I had to create separate
events to poll with 1 AKA first, then the other, but yeah I get what you say and respect it.

For the record, and future reference:

If you and your uplink have more than one matching zone number (ie: you are both in multiple, similar networks, whether linked via those networks or not) binkp's standard is to take the FIRST aka that matches.

For example, if you both have a Fidonet zone 1 address, and you both have a FSX zone 21 address.. if the zone 1 address is listed first, when you poll your FSX uplink it will try to negotiate with the zone 1 address.

Sometimes this gets in the way of doing what you want to do, however.. with Mystic you can do a couple things:

1) Use the "Hide AKAs" option to only poll your uplink with the AKA you want it to poll with. This way your uplink's binkp server won't see your other AKAs.

2) Setup the same (it must be the same) binkp session password to your uplink for every zone you both have. This way the first matching zone number that makes the negotiation will pass as secure.

Note: Don't do both of the above options at the same time. One or the other.. or you will probably have a slew of other issues.

HTH

Regards,
Nick

... Take my advice, I don't use it anyway.
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:128.0) Gecko/20100101 Thunderb
* Origin: The Pharcyde ~ telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

Hello Accession!

25 Oct 24 17:00, you wrote to me:

Now for anyone watchin, this is a *great* response, someone willing to help.

On Fri, Oct 25 02:35:20 -0500, you wrote:

No, I think it was something to do with my uplink too, I was
presenting all my AKAs and it would reject mail, then I had to
create separate events to poll with 1 AKA first, then the other,
but yeah I get what you say and respect it.

For the record, and future reference:

If you and your uplink have more than one matching zone number (ie:
you are both in multiple, similar networks, whether linked via those networks or not) binkp's standard is to take the FIRST aka that
matches.

For example, if you both have a Fidonet zone 1 address, and you both
have a FSX zone 21 address.. if the zone 1 address is listed first,
when you poll your FSX uplink it will try to negotiate with the zone 1 address.

Sometimes this gets in the way of doing what you want to do, however.. with Mystic you can do a couple things:
1) Use the "Hide AKAs" option to only poll your uplink with the AKA
you want it to poll with. This way your uplink's binkp server won't
see your other AKAs.

OK, I will have to do that because during my *own* digging, I turned it on and off to see if things worked, until *I* found that a combination of things helped me solve the issue.

2) Setup the same (it must be the same) binkp session password to your uplink for every zone you both have. This way the first matching zone number that makes the negotiation will pass as secure.

I do have this setup this exact same way, all passwords are the same for my uplink.

Note: Don't do both of the above options at the same time. One or the other.. or you will probably have a slew of other issues.

I will check and might have to change some of my setting and lean for option one, I checked and I *do* have the Hide AKAs ON for both links to Deon, might the same session password for both be disturbing my polls.

I do have some issue when I *mis poll force*, first attempt which poll my uplink simultaneously using both AKAs, fails, when I issue the command a second time it goes trhough and I think that's exactly what you wisely mentioned.

HTH

Regards,
Nick

Thanks a million Nick

David


--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: SkyNet BBS | Colombia | bbs.skynetbbs.com:20023 (21:3/188)

On Sat, Oct 26 02:12:40 -0500, you wrote:

Now for anyone watchin, this is a *great* response, someone willing to help.

I replied to you multiple times when you had questions earlier about Mystic and/or Golded, but you only replied once. Maybe, whatever issues you were having caused you to miss some messages?

OK, I will have to do that because during my *own* digging, I turned it
on and off to see if things worked, until *I* found that a combination
of things helped me solve the issue.

I do have this setup this exact same way, all passwords are the same for my uplink.

This is generally just a safe precaution to do, depending on what software you're connecting to. Some are more strict than others when it comes to this.

I will check and might have to change some of my setting and lean for option one, I checked and I *do* have the Hide AKAs ON for both links to Deon, might the same session password for both be disturbing my polls.

See below. It sounds like you're using Deon for two networks, so when using "mis poll force" it will poll him twice at the exact same time, which could very well cause an issue when trying to authenticate.

I do have some issue when I *mis poll force*, first attempt which poll
my uplink simultaneously using both AKAs, fails, when I issue the
command a second time it goes trhough and I think that's exactly what
you wisely mentioned.

You can try different methods as well, like try /not/ using "mis poll force", if you can. Try setting up separate timed events (which you can stagger 10 minutes apart of something) for each network callout, and use "mis poll <node>" instead. This will separate the polls so that no confusion can be made as to which node number you're using, or connecting to.

Early on, I always had issues with the "force" option as well, but then again, when I have Mystic running, it polls my hub for 4-5 networks. So running "force" would basically connect to myself and try to authenticate 4-5 times, at the same time.. which never worked well. Creating a separate poll for each network is what worked for me.

I imagine the "force" option works much better if you had /different/ uplinks. For example, you had 3 networks, 3 separate uplinks. "mis poll force" would connect to all three of them at the same time and get your mail for each network. I just don't think it works as well when you have 2 or more networks with the same uplink.

Thanks a million Nick

No problem! Enjoy the hobby!

Regards,
Nick

... Take my advice, I don't use it anyway.
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:128.0) Gecko/20100101 Thunderb
* Origin: The Pharcyde ~ telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

Hello Accession!

26 Oct 24 08:23, you wrote to me:

On Sat, Oct 26 02:12:40 -0500, you wrote:

Now for anyone watchin, this is a *great* response, someone
willing to help.

I replied to you multiple times when you had questions earlier about Mystic and/or Golded, but you only replied once. Maybe, whatever
issues you were having caused you to miss some messages?

OK, I will have to do that because during my *own* digging, I
turned it on and off to see if things worked, until *I* found
that a combination of things helped me solve the issue.

I do have this setup this exact same way, all passwords are the
same for my uplink.

This is generally just a safe precaution to do, depending on what
software you're connecting to. Some are more strict than others when
it comes to this.

I will check and might have to change some of my setting and lean
for option one, I checked and I *do* have the Hide AKAs ON for
both links to Deon, might the same session password for both be
disturbing my polls.

See below. It sounds like you're using Deon for two networks, so when using "mis poll force" it will poll him twice at the exact same time, which could very well cause an issue when trying to authenticate.

I do have some issue when I *mis poll force*, first attempt which
poll my uplink simultaneously using both AKAs, fails, when I
issue the command a second time it goes trhough and I think
that's exactly what you wisely mentioned.

You can try different methods as well, like try /not/ using "mis poll force", if you can. Try setting up separate timed events (which you
can stagger 10 minutes apart of something) for each network callout,
and use "mis poll <node>" instead. This will separate the polls so
that no confusion can be made as to which node number you're using, or connecting to.

Early on, I always had issues with the "force" option as well, but
then again, when I have Mystic running, it polls my hub for 4-5
networks. So running "force" would basically connect to myself and try
to authenticate 4-5 times, at the same time.. which never worked well. Creating a separate poll for each network is what worked for me.

I imagine the "force" option works much better if you had /different/ uplinks. For example, you had 3 networks, 3 separate uplinks. "mis
poll force" would connect to all three of them at the same time and
get your mail for each network. I just don't think it works as well
when you have 2 or more networks with the same uplink.

I run mis server, so when it *poll force*, it does as you say, I will change my events to poll Deon's exacat uplink address to avoid having to poll multiple times to get it done.

*Thanks a million Nick--again*

No problem! Enjoy the hobby!

Regards,
Nick

... Take my advice, I don't use it anyway.
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:128.0) Gecko/20100101 Thunderb
* Origin: The Pharcyde ~ telnet://bbs.pharcyde.org (Wisconsin)
(21:1/200)

David


--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: SkyNet BBS | Colombia | bbs.skynetbbs.com:20023 (21:3/188)