Just a thought, would there be room to display the Sysop field on this screen?

Ûßßßßßßßßßßßßßßßßßßßßßßßßßß EchoMail Nodes ßßßßßßßßßßßßßßßßßßßßßßßßßß
Û ID Active Description Network
Û ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
Û 1 Yes Agency HUB (Ori) 3:770/1

Best, Paul

--- E:avon@bbs.nz ------ W:bbs.nz ---
--- K:keybase.io/avon --------------

--- Mystic BBS v1.12 A43 2019/02/23 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Just a thought, would there be room to display the

Sysop field on thisAv> screen?Av>

Ûßßßßßßßßßßßßßßßßßßßßßßßßßß EchoMail Nodes ßßßßßßßßßßßßßßßßßßßßßß

ßßßßAv> Û ID Active DescriptionNetwork

Û ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

ÄÄÄAv> Û 1Yes Agency HUB (Ori)3:770/1
Well as you mentioned there isn't a lot of space in
80 columns maybe we canmove it back to one space
between everything³ ID Act Description
SysOp Name Network ³³
³
³1111 Yes 1234567890123456789012345 12345678901234567890 1111:1111/1111.0000
³SysOp name/Desc may get cut off in some cases b
ut it looks like we can fit itin there. I a
m also going to expand on the SysOp name to allow a
"@" inthere for cases like you're wher
e I have the Hub 21:1/100
but you prefer tobe reached at 21:1
/101 so I think I will add the option
to specify:"Avon@21:1
/101" as SysOp name and the autom
atic "Netmail SysOp" feat
ure willacknowledge that and send to 101 instead
.
--- Mystic BBS v1.12 A43 2019/02/17 (Linux/64)
* Origin: Sector 7 (21:1/108)

On 26 Feb 2019 at 06:02p, g00r00 pondered and said...

Well as you mentioned there isn't a lot of space in 80 columns maybe we ca move it back to one space between everything
SysOp name/Desc may get cut off in some cases but it looks like we can fit

Thank you, I think adding the info on this screen is helpful.

For info. I've used the 'description' field prior to the arrival of the dedicated 'sysop' field as a place to note both BBS name and sysop name. So I would have an entry like 'Agency BBS / Paul Hayton' in my description field.

That is still helpful to do because when you run a fidopoll search or list
the output just displays the description field, but perhaps you could add sysop to fidopoll results output? And if you did that I also wonder should 'description' be changed to 'BBS' to try and encourage clarity over use of
each data field?

in there. I am also going to expand on the SysOp name to allow a "@" in there for cases like you're where I have the Hub 21:1/100 but you prefer t be reached at 21:1/101 so I think I will add the option to specify: "Avon@21:1/101" as SysOp name and the automatic "Netmail SysOp" feature wi acknowledge that and send to 101 instead.

Thank you. I think this may address a wishlist item I had but had not mentioned.. I was looking for a way so that netmail sent to a HUB address
like 21:1/100 could be redirected to my netmail address of 21:1/101

I'm looking for lazy ways to avoid having to check two different netmail
boxes on two different Mystic systems. I could not figure out a way with the current netmail routing tools to create such a redirect. Your idea will help this but do you think there might be a way to put in a routing rule like I describe to catch anything sent to one netmail box but ideally be read in another?

Best, Paul

--- E:avon@bbs.nz ------ W:bbs.nz ---
--- K:keybase.io/avon --------------

--- Mystic BBS v1.12 A43 2019/02/23 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

list the output just displays the description field, but perhaps you
could add sysop to fidopoll results output? And if you did that I also wonder should 'description' be changed to 'BBS' to try and encourage clarity over use of each data field?

I think that can be done, sure. I am not sure I'll change it to BBS because
I am not sure I want that sort of clarity :) For example in my setup I don't use it for BBS name they will be labeled like:

[FSX] fsx HUB 1 Avon 21:1/100
[FIDONET] blah
[FIDONET] blah blah

Thank you. I think this may address a wishlist item I had but had not mentioned.. I was looking for a way so that netmail sent to a HUB address like 21:1/100 could be redirected to my netmail address of 21:1/101

Maybe we could also expand the tosser's forward function to redirect by
address in addition to user name. I agree it'd be helpful to have this
option available to both the client and server.

I'll have to look into the difficulty of that.

--- Mystic BBS v1.12 A43 2019/02/17 (Linux/64)
* Origin: Sector 7 (21:1/108)

On 26 Feb 2019 at 08:26p, g00r00 pondered and said...

I think that can be done, sure. I am not sure I'll change it to BBS because I am not sure I want that sort of clarity :) For example in my

Yep fair enough on that count...

mentioned.. I was looking for a way so that netmail sent to a HUB add like 21:1/100 could be redirected to my netmail address of 21:1/101

Maybe we could also expand the tosser's forward function to redirect by address in addition to user name. I agree it'd be helpful to have this option available to both the client and server.

I'll have to look into the difficulty of that.

Thank you :)

Best, Paul

--- E:avon@bbs.nz ------ W:bbs.nz ---
--- K:keybase.io/avon --------------

--- Mystic BBS v1.12 A43 2019/02/23 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)