One I have added a bunch of new message bases. I tried global adding one export and it crashed to cl each time. No particular reason I could see.
I was able to manually add each.

Thanks for letting me know. I did just try it here and seems to be working
for me, so there must be another piece of the puzzle.

2nd: the netmail origin line doesn’t contain the node number. This caused an issue with sbbs systems. I worked with rob and he changed something in sbbsecho. Not sure if that was left out intentionally or by accident.

Is the base type set to Echomail? Do you have a QWK network assigned to it?

--- Mystic BBS v1.12 A47 2020/09/25 (Windows/64)
* Origin: Sector 7 | Mystic WHQ (1:129/215)

This was a netmail, in a netmail echo. All echomail echos add the node to origin, netmails do not. I'll send you a netmail to try it to your
fidonet address.

Ahh okay I missed the part where it was a netmail, that is helpful.

This happens when you have no network address set for the Netmail base in A46+, but I've just changed it to properly add the address for all netmail bases (regardless of if an address is set or not) in the A47 prealpha which is available now.

Thanks for letting me know.

--- Mystic BBS v1.12 A47 2020/09/27 (Windows/64)
* Origin: Sector 7 | Mystic WHQ (1:129/215)

Hello g00r00!

Ahh okay I missed the part where it was a netmail, that is helpful.

This happens when you have no network address set for the Netmail base
in A46+, but I've just changed it to properly add the address for all netmail bases (regardless of if an address is set or not) in the A47 prealpha which is available now.

Thanks for letting me know.

sorry a little late to party but this bug but, this bug is also in the rpi build. any time frame for when A47 will be available for rpi??

also this seems to be affecting pass-through mail as well. ie mail from points is looping from point to hub... it seems to be using 1:1/0 for a node address again. or at least thats how sbbs is reporting it.

so the fix would be to seperate out each netmail area ?




Michael


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

Got it. Thanks man.

On 06:40 28/09 , g00r00 wrote:

also this seems to be affecting pass-through mail as well. ie mail from points is looping from point to hub... it seems to be using 1:1/0 for a node address again. or at least thats how sbbs is reporting it.

This is an origin line display issue, the addressing in the packet >headers/kludges are not affected by this. What you're describing there sounds >like an SBBS issue or something that different than this.

The good news is that you can fix this on your own!

The address not on the origin line happens when you have your Netmail base >assigned to Local network. Go into your NETMAIL base configuration and change >the address from Local 0:0/0 to any other network address and it should fix it.

In A46 it was changed to not display the address on the origin if you have the >base address set to Local. The change I have made to A47 was to revert back to
how it worked before A46 (where the address is still present even when its set >to Local).

--- Mystic BBS v1.12 A47 2020/09/27 (Windows/64)
* Origin: Sector 7 | Mystic WHQ (1:129/215)

--
yrNews Usenet Reader for iOS
http://appstore.com/yrNewsUsenetReader

--- Mystic BBS/NNTP v1.12 A47 2020/09/12 (Linux/64)
* Origin: The ByteXchange BBS | bbs.thebytexchange.com (1:19/37)

now for kicker.. even from node to node ie from 1:340/202 (mystic) to 1:340/203 (sbbs) both latest any mail that is not direct gets an invalid node address assigned to it (1:1/0) - this is very reminisent of the
sort of issues that were going on before

The default address (1:1/0) sounds like it could be related to the thing we're talking about here so its probably a good idea to get that resolved. If SBBS gets an address from the origin line, then it'd probably end up with some reasonable default like 1:1/0 if no address was there.

As far as the rest there are some many things that could be wrong there, including if someone is using old versions or has an ill-configured netmail route (also could be a bug too). Not sure where to begin so I think making sure the address is on the origin line is a good start.

I personally host a point system on SCINET, and they are able to send netmails throughout when we tested it. Netsurge confirmed all of the addressing in the netmails produced from Mystic match the same when they are generated by HPT (the Husky tosser) too. This was several months ago though.

--- Mystic BBS v1.12 A47 2020/09/27 (Windows/64)
* Origin: Sector 7 | Mystic WHQ (1:129/215)

The default address (1:1/0) sounds like it could be related to the
thing we're talking about here so its probably a good idea to get that resolved. If SBBS gets an address from the origin line, then it'd probably end up with some reasonable default like 1:1/0 if no address
was there.

any idea on when A47 for RPI will be available the setup was working in previons versions ..

As far as the rest there are some many things that could be wrong
there, including if someone is using old versions or has an
ill-configured netmail route (also could be a bug too). Not sure
where to begin so I think making sure the address is on the origin
line is a good start.

will tell him to try that - and report back

I personally host a point system on SCINET, and they are able to send netmails throughout when we tested it. Netsurge confirmed all of the addressing in the netmails produced from Mystic match the same when
they are generated by HPT (the Husky tosser) too. This was several
months ago though.

could/would you update to the latest A46 on that RPI see if it still
works for you. ???

yes when we brought the issue to you and Rob S.
This only seems to happen on the RPI version..

I am back to running on my desktop - my setup is different - linux64
- I do have my netmail areas seperated and my build works - I can only relay the info

Michael


--- GoldED+/LNX 1.1.5-b20180707
* Origin: Mike's Mansion - Portland, OR - mansion.dynv6.net:2323 (1:340/201.2)

The default address (1:1/0) sounds like it could be related to the thing we're talking about here so its probably a good idea to get tha resolved. If SBBS gets an address from the origin line, then it'd probably end up with some reasonable default like 1:1/0 if no address was there.

any idea on when A47 for RPI will be available the setup was working in previons versions ..

Just to reiterate in case there is confusion: They won't need A47 (just the final A46 release) but they have to assign an address that isn't 0:0/0 Local to the Netmail base for this to resolve itself.

I don't know when A47 will be done I don't even have a specific set of features I want to work on for this version at the moment! But if there is a signficant bug that requires updates, I will release prealpha builds for all OSes including Pi.

could/would you update to the latest A46 on that RPI see if it still
works for you. ???

I'll ask if they run on a Pi, I think they run on Linux not a Pi. There
isn't any Pi specific code in the tossing though so in theory it should be
the same as on any other Linux.

If it comes down to it I will set up a Pi point myself but lets get their Netmail area set up correctly first to see if that helps.

We'll get it sorted out :)

--- Mystic BBS v1.12 A47 2020/09/27 (Windows/64)
* Origin: Sector 7 | Mystic WHQ (1:129/215)

Ok I returned the netmail to separate areas ie each network has a set
node addy in netmail area (it used to work all as one) Mystic bbs for

There may still be some confusion here. The instructions I was giving were to solve the missing address on the origin line. There was not talk about trying to create multiple Netmail bases per network (?) so you lost me there! :)

The issue with the missing addressing on the origin line is because those people have their Netmail base address set as follows:

"Net Address: 0:0/0 (Local Network)"

That is why the addressing was not on the Origin line, because its set local. I've updated A47 to include the address.

I personally host a point system on SCINET, and they are able to send netmails throughout when we tested it. Netsurge confirmed all of the addressing in the netmails produced from Mystic match the same when they are generated by HPT (the Husky tosser) too. This was several

Echo mail works for all networks, only netmail has been affected. Let
me know if I can provide any other information...

Yes, I am speaking of Netmail here too. I believe there are also two FTN networks that are hubbed entirely by Mystic on a Pi and I haven't heard anything from them (yet). It could be unnoticed or that they haven't upgraded though.

What does the output of "fidopoll route" look like on both the systems you have?

We weren't able to find an issue with this over SciNet like I said, but we only tested Windows and Linux not Linux on a Pi (although that really shouldn't matter).

--- Mystic BBS v1.12 A47 2020/09/27 (Windows/64)
* Origin: Sector 7 | Mystic WHQ (1:129/215)

On 09-29-20 16:34, g00r00 wrote to Rick Smith <=-

Yes, I am speaking of Netmail here too. I believe there are also two
FTN networks that are hubbed entirely by Mystic on a Pi and I haven't heard anything from them (yet). It could be unnoticed or that they haven't upgraded though.

I'm one, but haven't got around to upgrading to A46 yet.


... Klingon bastard killed my son, doo-dah, doo-dah. 
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)