Hey there

Learning as I go with this one.

In the config for links I had set up nodes using link names like

101
102
103
.
.
.
1202

I now see this may not be ideal in that an areafix reply ends up being sent
to the link name (which may not be at all what the receiving node is
expecting)

7 Mar:14:2021:13:36:33 pkt: /hub/echomail/in/temp/0826a421.tos [21:2/1202]
L Mar:14:2021:13:36:33 Netmail from 21:2/1202 to 21:1/100.0
8 Mar:14:2021:13:36:33 Process command: %HELP
8 Mar:14:2021:13:36:33 AreaFix: HELP sent to 1202
L Mar:14:2021:13:36:34 Wrote Netmail: 21:1/100.0 -> 21:2/1202.0
8 Mar:14:2021:13:36:34 areafix: Successfully done for 21:2/1202

So I'm thinking ... well I could call the link 'Sysop' but then I'm picking only one link can have that name i.e. each link needs to be unique.

I could use the FTN address for the link name, and tell folks to ensure their end will map netmail sent to their AKA to their sysop netmail inbox..

I could use the persons name 'joe blogs' but what if

1) there's more than one 'joe blogs'

or

2) you're feeding 'job blogs' assorted zones/nets - how does that end up working when you have different rules for what you configure to feed Fido vs fsxNet etc.

Some top tips would be welcome from seasoned users of HPT :)

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

Hello Paul,

I now see this may not be ideal in that an areafix reply ends up being sent to the link name (which may not be at all what the receiving node
is expecting)

Yes, I have always put the name of the sysop there.

So I'm thinking ... well I could call the link 'Sysop' but then I'm picking only one link can have that name i.e. each link needs to be unique.

I don't think the name needs to be unique although I think all my links do have a unique name. If you call all your links Sysop then netmail to them will be sent to Sysop. That would work OK for me. Mystic nodes would need a forward setup for that.

I could use the FTN address for the link name, and tell folks to
ensure their end will map netmail sent to their AKA to their sysop
netmail inbox..

Yes, simpler to use their name but a lot of typing.. :)

2) you're feeding 'job blogs' assorted zones/nets - how does that end
up working when you have different rules for what you configure to
feed Fido vs fsxNet etc.

If you send both fidonet and fsxnet to the same node they need a link setup for each AKA. They can connect fidonet with their fidonet AKA and fsxnet with their fsxnet AKA. I have a few of those setup here.

Some top tips would be welcome from seasoned users of HPT :)

That's how I do it here.. :)

Ttyl :-),
Al

--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

On 13 Mar 2021 at 08:05p, Alan Ianson pondered and said...

So I'm thinking ... well I could call the link 'Sysop' but then I'm picking only one link can have that name i.e. each link needs to be unique.

I don't think the name needs to be unique although I think all my links
do have a unique name. If you call all your links Sysop then netmail to

Thanks Al I'll try that option and shift to sysop names. I can see I have
some Fido and othernets set up already in the links file for sysops that I
feed both networks to so I guess that will be the best way to solve this.

If you send both fidonet and fsxnet to the same node they need a link setup for each AKA. They can connect fidonet with their fidonet AKA and fsxnet with their fsxnet AKA. I have a few of those setup here.

will do. Hopefully this will sort things.

Thanks for the reply. :)

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

Hello Paul!

14 Mar 21, Paul Hayton wrote to All:

In the config for links I had set up nodes using link names like

Mar:14:2021:13:36:33 AreaFix: HELP sent to 1202 L
Mar:14:2021:13:36:34 Wrote Netmail: 21:1/100.0 -> 21:2/1202.0 8

So I'm thinking ... well I could call the link 'Sysop' but then I'm picking only one link can have that name i.e. each link needs to be unique.

That's why you shouldn't bloat your network layout. There is no need for northern and southern nets if both connect to the same INA. Keep it simple.

For easy identification you could use link names like sysop_name.zone

I could use the FTN address for the link name, and tell folks to
ensure their end will map netmail sent to their AKA to their sysop
netmail inbox..

1) there's more than one 'joe blogs'

joe_blogs_two.21

2) you're feeding 'job blogs' assorted zones/nets - how does that end
up working when you have different rules for what you configure to
feed Fido vs fsxNet etc.

Use what's most usable for you. joe.fido, joe.fsx, fido.foe, fsx.joe...

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

On 14 Mar 2021 at 01:56p, Kai Richter pondered and said...

That's why you shouldn't bloat your network layout. There is no need for northern and southern nets if both connect to the same INA. Keep it simple.

?? OK thanks...

For easy identification you could use link names like sysop_name.zone

I've opted for sysop names... seems to be OK.

Thanks for the reply.

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)