Spam control

In the last two weeks, I had less time to visit drupal.org and check for spam, but there are also less users checking for spam, lately.
It may take time, but spam is removed, if the spam isn't a project. In that case, only administrator users (not webmasters) can delete them.

I also now have a role that permits me to delete spam. I will react to spam reports posted on the Webmasters issue queue.

But I am new at this, and still learning the ropes. For instance, I haven't found a place where I can inspect "spam logs". If someone could tell me where to find it, I shall add inspecting those to my daily patrol tasks.

@gisle Posts flagged as spam are listed on https://www.drupal.org/admin/content/spam. Users normally don't report spam in the webmasters queue.

kiamlaluno, (re comment #4) found it, and just unpublished the first spam post.
Checked if the user had posted more spam (he had not). Also clicked "Mark as spammer".

@gisle Don't you see the link to block a user account? (On https://www.drupal.org/u/sahilkhan194, there are two links, after Status: block and Report as spammer.)
On https://www.drupal.org/user/3620388/admin-content, there is a link to delete (and report as spam) each of the user's post.

Yes, I've found the links. But new users may not know about the exact rules here, so just blocking them based on a single transgression seems a bit harsh.

I block those that has obvious and multiple spam posts attached to their account. Also: I never delete spam, as that don't let us see if the user has misbehaved before.

As webmaster, you are allowed to delete spam on sight, and immediately block spammers.
Administrator users can always check what you did, and restore what you deleted, if it wasn't spam.

Administrator users can always check what you did, and restore what you deleted, if it wasn't spam.

AFAIK, there is no "undelete" in Drupal core. Deleting something removes the node or comment from the database, and the only standard way to get it back is to roll back a DB backup. (Unless something like https://www.drupal.org/project/entity_soft_delete has been deployed on Drupal.org – but that project looks pretty stale.)

However, unpublishing is reversible.

Deleting spam without having permission to administer users has some snags.

Just visited a spam report (a pretty obvious one), a clicked link to block user account.
Plan was to proceed to the account and check for more spam, but because I just had blocked the user, I got a "403".

So unless I get the permission to administer users, I think I will leave blocking accounts to those with permission to administer users, and just focus on deleting the posts.

@gisle

Yeah, not having access to blocked accounts is a pain. I believe I have an issue in one of these queues about it from a couple years ago. Best to make sure you have their spam cleaned up totally and _then_ block them. Unfortunately, it's still an issue if you come across spam that hasn't been taken care of and find the user already blocked. Then there is no way to see if there is more, that I'm aware of.

I am closing this issue, since the original question was answered.