Hello All!

I had been asked to remove one of my downlinks from a specific echo due to rule violations, which I did. My question is can I keep him from resubscribing to that particular echo? I have used levels for like sysop specific etc would I have to do that? like set a write level on that echo that matches everyone but him or is there a simpler way?

Regards,

Rick

... A job is nice, but it interferes with BBSing.
--- GoldED+/LNX 1.1.5-b20180707
* Origin: Awesome Net- Oregon FTN Hub - www.awesomenet.us (1:105/81)

On 03 Apr 2024, Rick Smith said the following...

I had been asked to remove one of my downlinks from a specific echo due
to rule violations, which I did. My question is can I keep him from resubscribing to that particular echo? I have used levels for like
sysop specific etc would I have to do that? like set a write level on
that echo that matches everyone but him or is there a simpler way?

Check out the ReadOnly token:

3.5.16 ReadOnly
---------------
Syntax:
'ReadOnly <addressMask> <areaMask>'
Example:
'ReadOnly 2:5021/19.* tver.sysop*'
'ReadOnly 1:234/567 fidotest'
'ReadOnly 21:3/110.1 fsx_*'

Using this they could still see the echo with %LIST and re-subscribe, but it would be read only for them.

I just tested this out with a test point, the echo area isn't listed as read only in %LIST but any messages they try and post to that area will go into BAD:

FROM: 21:3/110.1
REASON: Sender not allowed to post in this area (access import)
AREANAME: FSX_TST

The affected node won't receive any bounceback messages.


Jay

... Did you know that dolphins are just gay sharks?

--- Mystic BBS v1.12 A49 2023/04/30 (Linux/64)
* Origin: Northern Realms (1:229/664)

Hello Rick!

04 Apr 24, Rick Smith wrote to Jay Harris:

I had been asked to remove one of my downlinks from a specific
echo due to rule violations, which I did. My question is can I
keep him from resubscribing to that particular echo? I have
used levels for like sysop specific etc would I have to do that?

Check out the ReadOnly token:

3.5.16 ReadOnly

Thanks Jay, I put that in this nodes link entry and it seem to accept
it, ran tparser and it didnt error so I will see whaat happens...

If you were asked to remove the link then you would still violate the rules.

The question "why lockout" is the key. If you have to lock out a group of users according to the echo rules then the group level system is your solution.

If your issue is just a single user with XAB violations then the simplest action would be disabling his areafix and take over manual control.

Regards

Kai

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

Hello Jay!

Thursday April 04 2024 08:57, you wrote to me:

* Forwarded from area 'FIDOSOFT.HUSKY'
On 03 Apr 2024, Rick Smith said the following...

3.5.16 ReadOnly
---------------
Syntax:
'ReadOnly <addressMask> <areaMask>'
Example:
'ReadOnly 2:5021/19.* tver.sysop*'
'ReadOnly 1:234/567 fidotest'
'ReadOnly 21:3/110.1 fsx_*'

Using this they could still see the echo with %LIST and re-subscribe,
but it would be read only for them.

Thanks this worked I did test as well... I hadnt thought of this option for a single link but right on.

Regards,

Rick

... Taglines - the "Magic: The Gathering" of BBSing!
--- GoldED+/LNX 1.1.5-b20180707
* Origin: Awesome Net- Oregon FTN Hub - www.awesomenet.us (1:105/81)