Description of problem: To have better hands-on over spamming, i suggest every first post by a new forum-member being approved before. This will protect the forum against boring spam-messages in a most direct way. The first post by a new member most of the time indicates the right or wrong intentions. The amount of new members registering, on average level, is this low, i don't foresee much extra time to spend on managing. The way it is working now, also brings quite some steps to execute before everything is handled.
CC: (none) => maat-ml, marja11Assignee: mageia-webteam => forums-bugsSummary: Apporval first post into forum => Approval first post into forum
Done i think... let's test :)
Status: NEW => ASSIGNED
Just created a new account, parrot, and my first message was posted right away. https://forums.mageia.org/en/viewtopic.php?f=12&t=3229#p24642 Thx for the updates. I will reply back later in regard to the other messages.
Seems what maat changed is this in ACP: New member post limit: 1 New members are within the Newly Registered Users group until they reach this number of posts. You can use this group to keep them from using the PM system or to review their posts. A value of 0 disables this feature. This is not what is necessary, new posts (not members, as those cannot be verified without a post) should not be published without approval.
CC: (none) => doktor5000
FWIW, this issue still exists. From what I could find, most people ask exactly for the opposite, how to disable post approval. Seems this needs to be changed in ACP in forum permissions for all forums, and at the very least for the group "Newly registered users" we should probably change "Can Post without Approval" to no, for all forums. Current status can be seen in ACP > Permissions > PERMISSION MASKS > View forum-based permissions > select any forum > Misc tab > Can post without approval Seems this permission cannot be attached to the group, but only to a forum. And from what I've seen, it cannot be easily changed globally, but needs to be changed for every subforum under advanced permissions. Any objections to change this for all subforums?
CC: (none) => rverschelde, stormi
Given the recent experience, I think that this is essential. IIRC the Centos Forum is an example of a Forum that operates this way. A new user's posts must be approved before they are published.
The Forum troll is now polluting Bugzilla with its nonsense. See bug #17559
Hi there, I made 3-4 big changes on permissions: now a newcomer will go through moderation till he's considered by phpbb as regular user. forum team made a few tests today... let me know if there's something we did not expect. Cheers,
A regression, to me: I'm not sure it is good to have a time limit between posts for approved forums users. I'm anything but a fast writer, but do hit: "You cannot make another post so soon after your last."
(In reply to Marja van Waes from comment #8) > A regression, to me: > > I'm not sure it is good to have a time limit between posts for approved > forums users. > > I'm anything but a fast writer, but do hit: > > "You cannot make another post so soon after your last." That was actually an unrelated change by me, a day ago - I've set it to a higher threshold, but we can lower that again to the original value. It's originally used to prevent flooding. and it's currently set to 600 seconds. Which is pretty high. Set it back to 15 seconds.
(In reply to Florian Hubold from comment #9) > > That was actually an unrelated change by me, a day ago - I've set it to a > higher threshold, but we can lower that again to the original value. It's > originally used to prevent flooding. and it's currently set to 600 seconds. > Which is pretty high. > > Set it back to 15 seconds Thanks, Florian :-)
(In reply to Maat from comment #7) > Hi there, > > I made 3-4 big changes on permissions: now a newcomer will go through > moderation till he's considered by phpbb as regular user. > > forum team made a few tests today... let me know if there's something we did > not expect. > > Cheers, Closing as fixed, because any major regressions would have shown up, by now. For any smaller issue that might be related to the fix a new bug report can be opened, because reverting the changes isn't an option.
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED