We are going for an upgrade of the entire OS.
We are going to have some downtimes.
We will return to normal operations soon.
The admin--
Gab Virebent
--
https://contact.virebent.art
https://www.virebent.art
https://news.tcpreset.net
https://jabber.tcpreset.net
https://virebent.noblogs.org/
https://infosec.exchange/@virebent
Best of luck on the upgrade.
https://contact.virebent.artThe admin
Gab Virebent
--
https://contact.virebent.art--
The Doctor wrote:
Best of luck on the upgrade.Thanks for the support.
There were some rough patches, but fortunately, it wasn't necessary
to use any files from the backup or the snapshot.
It is now fully operational, and the update went as planned.
On Mon, 31 Aug 2026 18:19:03 +0200
Gabx <victor@virebent.tcpreset> wrote:
The Doctor wrote:I blinked and I missed it! Good job on the successful update.
Nigel Reed wrote:
On Mon, 31 Aug 2026 18:19:03 +0200
Gabx <victor@virebent.tcpreset> wrote:
The Doctor wrote:I blinked and I missed it! Good job on the successful update.
Thanks,
i adopted *infybofh* new [Cleanfeed-NG](https://github.com/infybofh/cleanfeed-ng)
it looks promising, which naturally prompted me to examine [Postfilter-NG](https://github.com/infybofh/postfilter-ng],
another of his projects.
From there, integrating NoCeM became a logical step.
https://news.tcpreset.net/nocem_stats.html
Postfilter-NG is still undergoing an audit, but the architecture is
ready, observable, and documented
On Mon, 31 Aug 2026 20:46:28 +0000
"Gabx"<usenet@tcpreset.invalid> wrote:
https://news.tcpreset.net/nocem_stats.htmlI already have NoCeM configured, whether it's done properly I am not
exactly sure. I am planning to move to cleanfeed-NG this weekend since
I'll have some free time. I've not looked at postfilter-NG - I never
knew it existed.
I do have a feeling that cleanfeed may have dumped some legitimate
posts so maybe cleanfeed-NG will be better. Did you use stock or did
you tweak it?
Nigel Reed wrote:
On Mon, 31 Aug 2026 20:46:28 +0000
"Gabx"<usenet@tcpreset.invalid>-a wrote:
https://news.tcpreset.net/nocem_stats.htmlI already have NoCeM configured, whether it's done properly I am not
exactly sure. I am planning to move to cleanfeed-NG this weekend since
I'll have some free time. I've not looked at postfilter-NG - I never
knew it existed.
You could check whether NoCeM notices are arriving, whether their
signatures validate against the trusted issuer keys, and whether the referenced Message-IDs are actually being processed.
Logs are more important than the statistics page alone.
I do have a feeling that cleanfeed may have dumped some legitimate
posts so maybe cleanfeed-NG will be better. Did you use stock or did
you tweak it?
For Cleanfeed-NG, i started from the stock version and adapted the local configuration and policies, without modifying its core.
I am monitoring rejection data carefully because false positives are
also my-a main concern.
Postfilter-NG is currently running in audit mode, so I can observe its decisions before allowing it to reject anything.
I would be interested to hear how your Cleanfeed-NG migration goes and
to compare results.
Best regards--
Gabx
For Cleanfeed-NG, i started from the stock version and adapted the local configuration and policies, without modifying its core.
I am monitoring rejection data carefully because false positives are
also my-a main concern.
I would be interested to hear how your Cleanfeed-NG migration goes and
to compare results.
Hi Gabx,
For Cleanfeed-NG, i started from the stock version and adapted the
local configuration and policies, without modifying its core.
Same for me.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 74 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 123:48:38 |
| Calls: | 1,194 |
| Files: | 1,352 |
| Messages: | 290,603 |