Hi all.

How do you handle write access to networks?
After automatic email verification new user have write access to local areas
on my BBS.

But how's it with networks?
I'm a little afraid about spam poster.

Cheers

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Omega BBS (21:3/128)

On 24 Nov 2020, Andy said the following...

Hi all.

How do you handle write access to networks?
After automatic email verification new user have write access to local areason my BBS.

But how's it with networks?
I'm a little afraid about spam poster.

Hi Andy,

I usually give all users read list post ACS for s10 and above for all networks. Some people would give read and list acs s10 but post s20 or something once their account is "verified" or something, but I like to offer anyone the ability to post right away.

What were you thinking about spam postings? Do you have an example?

Thanks!

---
|14Best regards,
|11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N

|07ÄÄ |08[|10eml|08] |15ml@erb.pw |07ÄÄ |08[|10web|08] |15www.erb.pw |07ÄÄÄ¿ |07ÄÄ |08[|09fsx|08] |1521:1/158 |07ÄÄ |08[|11tqw|08] |151337:1/101 |07ÂÄÄÙ |07ÄÄ |08[|12rtn|08] |1580:774/81 |07ÄÂ |08[|14fdn|08] |152:250/5 |07ÄÄÄÙ
|07ÄÄ |08[|10ark|08] |1510:104/2 |07ÄÙ

--- Mystic BBS v1.12 A47 2020/11/22 (OnePlus6T/arm32)
* Origin: phOnE In mY pOckEt BBS (21:1/158.6)

What were you thinking about spam postings? Do you have an example?

There are quite a few spam messages on Usenet.I don't want to encourage this, and that's why I'm thinking about how I can best prevent this on my
system.

Hence my question, how did other solve this.

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Omega BBS (21:3/128)

There are quite a few spam messages on Usenet.I don't want to encourage this,and that's why I'm thinking about how I can best prevent this on my system.

Well I guess you could raise the security level for the Post ACS so that although new users can read messages in the bases, until they are "validated" they cannot post?

You could do that on a per group or per base basis if you wanted more granularity of course.

I think that would be one way to lower the risk of people using your system to spam the echomail areas.

---
|14Best regards,
|11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N

|07ÄÄ |08[|10eml|08] |15ml@erb.pw |07ÄÄ |08[|10web|08] |15www.erb.pw |07ÄÄÄ¿ |07ÄÄ |08[|09fsx|08] |1521:1/158 |07ÄÄ |08[|11tqw|08] |151337:1/101 |07ÂÄÄÙ |07ÄÄ |08[|12rtn|08] |1580:774/81 |07ÄÂ |08[|14fdn|08] |152:250/5 |07ÄÄÄÙ
|07ÄÄ |08[|10ark|08] |1510:104/2 |07ÄÙ

--- Mystic BBS v1.12 A47 2020/11/22 (OnePlus6T/arm32)
* Origin: phOnE In mY pOckEt BBS (21:1/158.6)

On 11/24/2020 3:07 pm Andy said...

There are quite a few spam messages on Usenet.I don't want to encourage this, and that's why I'm thinking about how I can best prevent this on my system.

If somebody's going to spam USENET, they're not going to go through the effort of signing up on a BBS to do so. I'd leave the access same as your regular users.

--- ENiGMA 1/2 v0.0.12-beta (linux; x64; 12.19.1)
* Origin: cortex (21:2/128)

Well I guess you could raise the security level for the Post ACS so that although new users can read messages in the bases, until they are

Well, this is a practicable way I think. I'll tes this :)

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Omega BBS (21:3/128)

I'd leave the access same as your regular users.

Nearly the same as MeTaLoTiOn wrote.

This I will combine with email (self) verification.

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Omega BBS (21:3/128)

I have now changed the settings.
Thanks for your assistance.

Andy

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Omega BBS (21:3/128)

On 24 Nov 2020, MeaTLoTioN said the following...

Well I guess you could raise the security level for the Post ACS so that although new users can read messages in the bases, until they are "validated"they cannot post?

I'm kind of mean on my system. I require users to verify their email address before they're allowed to access anything.

Sure someone can create a new hotmail address and use that to verify their account, but at least they have to work for it to try and cause trouble.

Also would stop any automated bots, though I'm not aware of any that exist for BBSs.

Jay

... I want to be cremated as it is my last hope for a smoking hot body

--- Mystic BBS v1.12 A47 2020/11/17 (Windows/64)
* Origin: Northern Realms (21:3/110)

There are quite a few spam messages on Usenet.I don't want to encourage this, and that's why I'm thinking about how I can best prevent
this on my system.

In the halcyon days we used to let anyone at it. In those days most people were physically located not far from you and usually someone knew them or just a step removed. So it was probably a bit easier to vet. But we used to post a warning that if you abused it then that'd be it, no more for you.

Spec


*** THE READER V4.50 [freeware]
--- SuperBBS v1.17-3 (Eval)
* Origin: Scrawled in haste at The Lower Planes (21:3/101)

In the halcyon days we used to let anyone at it.

I remember this. In the late 80s I was running an up to 4 dial line BBS for a few years.

Networking and Internet... no chance :D

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Omega BBS (21:3/128)

How do you handle write access to networks?
After automatic email verification new user have write access to local areason my BBS.

But how's it with networks?
I'm a little afraid about spam poster.
Cheers

So I do what you do, and allow s10 users to access local message bases. My standard verified users are s20, so I set all FTNs to s20 so that they have to be validated to even see the FTNs.

Furthermore, I set some FTN message bases to s50; my extended access level. And a few FTN message bases to s255, the ones that are intended only for administators or etc etc.

I have a similar access level outline for my file areas, but... I think you get my basics.

Hope that helps, a little.



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Hope that helps, a little.

Yes indeed - it does.

Thanks Paulie

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Omega BBS (21:3/128)

Hello Andy!

On 24 Nov 2020, Andy said the following...

How do you handle write access to networks?

I have chosen four user flags:

ACS User Flags #1 (fa ... fz):

A: Disable local private posting
B: Disable local non-private posting
C: Disable netmail posting (ALL networks)
D: Disable echomail posting (ALL networks)

For local, private message areas ("e-mail, e.g. "Private Messages"):
Post ACS: !fa

For local discussions (e.g. "General Messages"):
Post ACS: s20&!fb

For netmail areas (e.g. "fsxNet Netmail"):
Post ACS: s20&!fc

For echomail areas (e.g. "FSX_BBS"):
Post ACS: s20&!fd

So if a user causes any trouble, posting can easily be disabled.

Best regards
Zip

--- Mystic BBS v1.12 A47 2020/11/23 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

Hello Zip

Looks somewhat more complicated in settings, but very effective, I think.

Thanks for detailed posting.

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Omega BBS (21:3/128)

Andy wrote:

Hi all.

How do you handle write access to networks?
After automatic email verification new user have write access to local areas on my BBS.

But how's it with networks?
I'm a little afraid about spam poster.

I don't have automatic verification, but I do let them have write access immediately to the local boards on my BBS. I find they'll see what they can access and post their spam before sending an email to the sysop to verify
their account. I've caught a number of potential spammers that way.
--- SBBSecho 3.11-Linux
* Origin: End Of The Line BBS - endofthelinebbs.com (21:2/101)

I don't have automatic verification, but I do let them have write access immediately to the local boards on my BBS. I find they'll see what they can access and post their spam before sending an email to the sysop to verify their account. I've caught a number of potential spammers that
way.

This is a very interesting idea (Y)

After all it is easy to delete local spam posts.

Thanks Nigel

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Omega BBS (21:3/128)

Hi there

I offer non-validated new users read only access to message bases

Once validated they gain post access to bases.

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

I offer non-validated new users read only access to message bases

That's in my settings too, write access is a little more different now.

But I'm still thinking about it, so it is not the end :)

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Omega BBS (21:3/128)

Hello Andy!

On 25 Nov 2020, Andy said the following...

Looks somewhat more complicated in settings, but very effective, I think. Thanks for detailed posting.

You're very welcome! :)

Best regards
Zip

--- Mystic BBS v1.12 A47 2020/11/23 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

How do I get my own node (not sure I am using the right reference)? I still
use /100.

Thank you for the awesome turorial on youtueb. Went pretty smooth.

Great Work!


°±²ÛNikadimusÛ²±°
°±²ÛThe Rats Nest BBS ²±°
°±²Ûratsnest.sytes.net:2323Û²±°

--- Mystic BBS v1.12 A45 2020/02/18 (Windows/64)
* Origin: Rats Nest BBS (21:1/999)

Hello Nikadimus,

How do I get my own node (not sure I am using the right reference)? I still use /100.

Grab the infopack..

http://bbs.nz/fsxinfo.zip

The is a text file in there called, FSXNET.TXT and there is a app section at the bottom of it that contains a Q&A of info Avon will need to get your node added.

So email or netmail that info to Avon, the info is all in the FSXNET.TXT along with other stuff youy may find interesting.

Ttyl :-),
Al

--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)