Hello! I have a question. I have multiple Fido and other network addresses that receive mail. It looks as if each "secondary" netmail area only has an option for one Address (AKA).

For instance I have 3 fido addresses:

1:1/101, 1:267/310, 1:267/311

I would like to have FEUTIL run FEUTIL IMPORT -FORCE and see that there are 3 netmails addressed to all 3 of my addresses and import into my Fido Netmail.

Same idea with the other networks. I have the BBS and tosser setup correctly so the main address listed in the AKA used of the area. If a message to one of my other networks comes in, it will import that message into the netmail area for only the AKA listed, not another address from the same network.

Did that jumble make sense?

Thank you!

--- ProBoard v2.31
* Origin: ProBoard WHQ - SiliconUnderground - siliconu.com (1:267/310)

Hello Jason!

24 Jan 24 20:59, you wrote to all:

Hello! I have a question. I have multiple Fido and other network addresses that receive mail. It looks as if each "secondary" netmail
area only has an option for one Address (AKA).

For instance I have 3 fido addresses:

1:1/101, 1:267/310, 1:267/311

I would like to have FEUTIL run FEUTIL IMPORT -FORCE and see that
there are 3 netmails addressed to all 3 of my addresses and import
into my Fido Netmail.

Same idea with the other networks. I have the BBS and tosser setup correctly so the main address listed in the AKA used of the area. If
a message to one of my other networks comes in, it will import that message into the netmail area for only the AKA listed, not another
address from the same network.

Did that jumble make sense?

Thank you!

FastEcho currently will only do the AKA that is configured for the area. So if you have 3 addresses in a network, you need 3 netmail areas if you want them all imported to your BBS. Personally, I would just let the admin AKAs hang out in the FastEcho netmail directory and read them with GoldED or something similar.

Andrew

--- GoldED+/LNX 1.1.5-b20230826
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)

Andrew,

Thank you. I was thinking of having different areas, etc. I like \your idea of using GoldEd for the admin ones.

-Jasom

--- ProBoard v2.31
* Origin: ProBoard WHQ - SiliconUnderground - siliconu.com (1:267/310)

25 Jan 24 00:50, Andrew Leary wrote to Jason Bock:

Hello! I have a question. I have multiple Fido and other
network addresses that receive mail. It looks as if each
"secondary" netmail area only has an option for one Address
(AKA).

For instance I have 3 fido addresses:

1:1/101, 1:267/310, 1:267/311

I would like to have FEUTIL run FEUTIL IMPORT -FORCE and see that
there are 3 netmails addressed to all 3 of my addresses and
import into my Fido Netmail.

Same idea with the other networks. I have the BBS and tosser
setup correctly so the main address listed in the AKA used of the
area. If a message to one of my other networks comes in, it will
import that message into the netmail area for only the AKA
listed, not another address from the same network.

Did that jumble make sense?

Thank you!

FastEcho currently will only do the AKA that is configured for the
area. So if you have 3 addresses in a network, you need 3 netmail
areas if you want them all imported to your BBS. Personally, I would
just let the admin AKAs hang out in the FastEcho netmail directory and read them with GoldED or something similar.

It seems to be possible to create multiple netmail areas that point to the same msgbase. I just tried, those two last netmail areas do share the same squish base. :)

=== Cut ===
J NETMAIL 2:221/1.254
S NETMAIL_SQ 2:221/1.1530
S NETMAIL_SQ2 2:221/1.1531
=== Cut ===

'Tommi

--- FastEcho/2 1.46.1 Revival
* Origin: =========================>>>> (2:221/1)

26 Jan 24 20:00, Tommi Koivula wrote to Jason Bock:

FastEcho currently will only do the AKA that is configured for
the area. So if you have 3 addresses in a network, you need 3
netmail areas if you want them all imported to your BBS.
Personally, I would just let the admin AKAs hang out in the
FastEcho netmail directory and read them with GoldED or something
similar.

It seems to be possible to create multiple netmail areas that point to
the same msgbase. I just tried, those two last netmail areas do share
the same squish base. :)

=== Cut ===
J NETMAIL 2:221/1.254
S NETMAIL_SQ 2:221/1.1530
S NETMAIL_SQ2 2:221/1.1531
=== Cut ===

Importing to squish netmail seems not working, but for jam it does work!

=== Cut ===
J NETMAIL 2:221/1.254
J NETMAIL_1530 2:221/1.1530
J NETMAIL_1531 2:221/1.1531
=== Cut ===

=== Cut ===
D:\fastecho>grep NETMAIL areas.bbs
!D:\FASTECHO\NETMAIL\NETMAIL NETMAIL
!D:\FASTECHO\NETMAIL\JAM1 NETMAIL_1530
!D:\FASTECHO\NETMAIL\JAM1 NETMAIL_1531
=== Cut ===

'Tommi

--- FastEcho/2 1.46.1 Revival
* Origin: =========================>>>> (2:221/1.254)

Thank you! I had to create multiple areas like you showed in both ProBoard and FastEcho. Works fine, just extra "stuff". lol

Thank you!

--- ProBoard v2.31
* Origin: ProBoard WHQ - SiliconUnderground - siliconu.com (1:267/310)

What BBS software?

--- ProBoard v2.31
* Origin: ProBoard WHQ - SiliconUnderground - siliconu.com (1:267/310)

On 26.1.2024 14:27, Jason Bock wrote:

What BBS software?

https://en.wikipedia.org/wiki/Bulletin_board_system

--- Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:5.0) Aura/20220608 Interlink/52.9.8194
* Origin: 2a01:4f9:c011:1ec5:f1d0:2:221:10 (2:221/10)

On 26.1.2024 14:27, Jason Bock wrote:

What BBS software?

https://en.wikipedia.org/wiki/Bulletin_board_system

--- Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:5.0) Aura/20220608 Interlink/52.9.8194
* Origin: 2a01:4f9:c011:1ec5:f1d0:2:221:10 (2:221/10)

I meant, what BBS Software do you use?

--- ProBoard v2.31
* Origin: ProBoard WHQ - SiliconUnderground - siliconu.com (1:267/310)

26 Jan 24 16:49, Jason Bock wrote to Tommi Koivula:

@PID: ProBoard 2.31 J
@TID: FastEcho 1.46 43281

Some kludges missing...

What BBS software?

https://en.wikipedia.org/wiki/Bulletin_board_system

--- Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:5.0) Aura/20220608
Interlink/52.9.8194
* Origin: 2a01:4f9:c011:1ec5:f1d0:2:221:10 (2:221/10)

I meant, what BBS Software do you use?

Concord has been running here from the very first alpha version. It has a year 2020 bug, which will never be fixed. However, outbound messages can be fixed with pktdate.

--- ProBoard v2.31

When do we get the fidonet compatible OS/2 version of this? ;)

'Tommi

---
* Origin: * RBB * Lake Ylo * Finland * (2:221/360)

26 Jan 24 16:49, Jason Bock wrote to Tommi Koivula:

@PID: ProBoard 2.31 J
@TID: FastEcho 1.46 43281

Some kludges missing...

Yes, working through the code to fix that as well. I had tons of Y2K issues that were incorrectly implemented that I had to fix.

What BBS software?

https://en.wikipedia.org/wiki/Bulletin_board_system

--- Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:5.0) Aura/20220608
Interlink/52.9.8194
* Origin: 2a01:4f9:c011:1ec5:f1d0:2:221:10 (2:221/10)

I meant, what BBS Software do you use?

Concord has been running here from the very first alpha version. It has a year 2020 bug, which will never be fixed. However, outbound messages can be fixed with pktdate.

Very nice! Is there source code anywhere? Maybe someone can fix the issues.

--- ProBoard v2.31

When do we get the fidonet compatible OS/2 version of this? ;)

The current version (v2.30 is used on a couple ArcaOS (OS/2) systems now by Rick Smith and Sean Dennis)

I will eventually get around to getting an OS/2 version released. Having compiler limitation issues. (Borland C++ v3.1)

'Tommi

---
* Origin: * RBB * Lake Ylo * Finland * (2:221/360)

--- ProBoard v2.31
* Origin: ProBoard WHQ - SiliconUnderground - siliconu.com (1:267/310)