Retro Guy:

When you rest from your latest bionic man upgrades, will you email
me instructions and that NoCem script blob and instructions? I need to
be on top of how to remove nasty or illegal messages from a RSLight
server and make sure they stay removed.

And I want to be sure my servers are honoring whatever NoCem messages
yours is sending, and how to automatically accept control messages
from arbitrary servers.

--
SugarBug | https://sybershock.com

Syber Shock wrote:

> Retro Guy:

> When you rest from your latest bionic man upgrades, will you email
> me instructions and that NoCem script blob and instructions? I need to
> be on top of how to remove nasty or illegal messages from a RSLight
> server and make sure they stay removed.

> And I want to be sure my servers are honoring whatever NoCem messages
> yours is sending, and how to automatically accept control messages
> from arbitrary servers.

Certainly! I will list some general steps here, and email you the scripts (there are 2). The scripts will work for rslight and inn2 servers, meaning they will send the proper message for either of these pieces of software to act upon them, the message format is the same for both.

First: set 'enable_nocem' => '1' in your $config_dir/rslight.inc.php.

NoCeM requires php-gnupg. Then, in the script nocem.php, it is expected that your GNUPGHOME is $config_dir.".gnupg for the web server user (probably www-data on Debian).

Then you will need to find the signing key of NoCeM messages you wish to honor. For example, mine is here: https://www.novabbs.com/hierarchy/nocem.txt . (You can find some more keys here: https://rosalind.home.xs4all.nl/nocemreg/nocemreg.html .

Add the keys you wish to honor to your keyring (in $config_dir.".gnupg).

Now you must know where to find NoCeM messages. news.lists.filters is a common place, but there can be others. For example, I post to news.lists.filters AND rocksolid.spam. Add this or these groups to your $config_dir/spoolnews/groups.txt . Then they will be polled from your remote server, but not listed in any of your sections, just that the server may now access the messages in these groups.

Once that is done, rslight will save all NoCeM messages to a folder as they arrive. Then, on the next run of cron, nocem.php will act upon the message(s). NoCeM messages are signed, so if the signature is good (per your gnupg), rslight will attemp to delete the message(s) listed in the NoCeM messages. You can view $spooldir/log/nocem.log to see what is happening. Watch for 'Bad signature' or 'Good signature' for the first clues of any issues.

Once the message is deleted (if found), nocem.php will move the NoCeM message to either a 'processed' or 'failed' subdirectory.

This is how acting on NoCeM messages works. Hopefully I didn't miss something important, but if so please let me know.

I'll send you the two scripts I use in a bit. I originally wrote them for just my own use, so I will set variables for options and get them to you by email.

--
Retro Guy