Can FMAIL support more than one net with the same zone? Right now, I've got
a mishmash of gecho and fastecho. Gecho isn't succeeding in sending stuff
out, but has stuff coming in. Fastecho is working both ways, but doesn't support League 10 and Araknet both being in zone 10.

--- shsbbs.net
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss) (Ports 22,23,110,21,119,8080) (ssh login 'bbs' pass 'shsbbs').


*** THE READER V4.50 [freeware]
---
* Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (1:340/1101)

Hi Martin,

On 2024-04-12 14:58:00, you wrote to All:

Can FMAIL support more than one net with the same zone?

The short answer is no, it doesn't support 5D addressing.

But depending on your role in the two nets: Are you just a downlink, or are you a Hub/*C. And do the nets have overlapping net numbers? You can probably set something up that works, where the two nets are in different groups, and if you are a Hub/*C, cook up a routing table for netmail routing to go right.

Right now, I've got a mishmash of gecho and fastecho. Gecho isn't succeeding in sending stuff out, but has stuff coming in. Fastecho is working both ways, but doesn't support League 10 and Araknet both
being in zone 10.

Maybe it should be fixed at the source and don't have two nets with the same zone number? ;-)
Maybe one can be changed or abolished?


Bye, Wilfred.

--- FMail-lnx64 2.3.2.1-B20240412
* Origin: FMail development HQ (2:280/464)

* In a message originally to Martin Kazmaier, Wilfred van Velzen said:

Hi Martin,

On 2024-04-12 14:58:00, you wrote to All:

Can FMAIL support more than one net with the same zone?

The short answer is no, it doesn't support 5D addressing.

But depending on your role in the two nets: Are you just a downlink, or
are you a Hub/*C. And do the nets have overlapping net numbers? You can probably set something up that works, where the two nets are in different groups, and if you are a Hub/*C, cook up a routing table for netmail
routing to go right.

I'm just a downlink. The net numbers are not overlapping.

Right now, I've got a mishmash of gecho and fastecho. Gecho isn't succeeding in sending stuff out, but has stuff coming in. Fastecho

is

working both ways, but doesn't support League 10 and Araknet both
being in zone 10.

Maybe it should be fixed at the source and don't have two nets with the
same zone number? ;-) Maybe one can be changed or abolished?

Nope. League 10 has been around since 2000, I think and Araknet has only
been around since 2020, but is really well established.

--- shsbbs.net
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss) (Ports 22,23,110,21,119,8080) (ssh login 'bbs' pass 'shsbbs').


---
* Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (1:340/1101)

Hello Martin,

On Saturday April 13 2024 11:40, you wrote to Wilfred van Velzen:

Maybe it should be fixed at the source and don't have two nets with
the same zone number? ;-) Maybe one can be changed or abolished?

Nope. League 10 has been around since 2000, I think and Araknet has
only been around since 2020, but is really well established.

Pardon me for saying so, but it is my not so humble opinion that as late in the game as 2020 it is not very smart to start an alternet with a zone number that is already in use. It is not a secret that most FTN software can not properly deal with duplicate zone numbers.

Having said that: I never understood the need for all these alternets in the first place...

Anyway, Fmail does not support it and in all likehood never will. It is just not worth the effort and making substantial changes to the config file will create backward compatibility problems with other software that interacts with Fmail. Wilfred had better spent his time on other things. Let those who created the problem of duplicate zone numbers sort it out among themselves.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20130111
* Origin: Michiel's laptop (2:280/464.5555)

Martin wrote (2024-04-12):

Can FMAIL support more than one net with the same zone? Right now, I've got a mishmash of gecho and fastecho. Gecho isn't succeeding in sending stuff out, but has stuff coming in. Fastecho is working both ways, but doesn't support League 10 and Araknet both being in zone 10.

What should work with most tossers is running a separate instance/configuration for one of the overlapping nets and export the mail to different outbound directories. For inbound you can use binkd's inbox node parameter and copy the incoming files with "exec" to a separate inbox. Or try a perl-hook script in binkd to sort incoming mail. You can also run to binkd instances on different ports with different binkd.cfg files.

Alternatively you can try a tosser that supports 5D, like Squish or Crashmail (though I'm not really sure, if they fully support the same zone number on different domains).

I would also recommend to use different session and packet passwords for each network.

Unfortunately there are several pitfalls and weird things can happen. A full 5D setup is possible, but it's not trivial.

---
* Origin: No REPLY kludge - no reply (2:280/464.47)

Hi Oli,

On 2024-04-16 11:06:20, you wrote to Martin Kazmaier:

I would also recommend to use different session and packet passwords
for each network.

That's always true! ;-)

You should always use diffent session, packet, etc passwords for all your links.


Bye, Wilfred.

--- FMail-lnx64 2.3.2.1-B20240412
* Origin: FMail development HQ (2:280/464)

Hello Wilfred,

On Tuesday April 16 2024 12:56, you wrote to Oli:

I would also recommend to use different session and packet
passwords for each network.

That's always true! ;-)

You should always use diffent session, packet, etc passwords for all
your links.

Different network != different link. Using different passwords for different networks is only possible if he does not get those networks from the same link. If het gets both networks fron the same link....

Anyway, I still think it is for those who created this problem by creating two networks with the same zone number to work it out among themselves.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20130111
* Origin: Michiel's laptop (2:280/464.5555)

Hi Michiel,

On 2024-04-16 15:47:51, you wrote to me:

I would also recommend to use different session and packet
passwords for each network.

That's always true! ;-)

You should always use diffent session, packet, etc passwords for all
your links.

MvdV> Different network != different link. Using different passwords for different
MvdV> networks is only possible if he does not get those networks from the same
MvdV> link. If het gets both networks fron the same link....

That is true.

MvdV> Anyway, I still think it is for those who created this problem by
MvdV> creating two networks with the same zone number to work it out among
MvdV> themselves.

That would be best. Or just wait for a bit. These networks tend to break down quickly all by themself... ;-)


Bye, Wilfred.

--- FMail-lnx64 2.3.2.1-B20240412
* Origin: FMail development HQ (2:280/464)

Hi Michiel,

On 2024-04-16 17:16:13, you wrote to me:

MvdV> Anyway, my point is that I advice against you putting time in it.
MvdV> Your time is better spent on other issues.

I don't intend to change FMail for this "issue". But we can support the op, with his setup. Within the limits of what is possible of course...

Bye, Wilfred.

--- FMail-lnx64 2.3.2.1-B20240412
* Origin: FMail development HQ (2:280/464)

Hello Wilfred,

On Tuesday April 16 2024 18:10, you wrote to me:

I don't intend to change FMail for this "issue". But we can support
the op, with his setup. Within the limits of what is possible of
course...

Sure, we can do that. But I think he already has enough clues to make it work for him...

Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20130111
* Origin: Michiel's laptop (2:280/464.5555)