Send inn-workers mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/inn-workers
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-workers digest..."
Today's Topics:
1. Re: Facilitating installation and update of anti-spam filter
(The Doctor)
2. Re: Facilitating installation and update of anti-spam filter
(Grant Taylor)
----------------------------------------------------------------------
Message: 1
Date: Sun, 10 Jul 2022 16:24:33 -0600
From: The Doctor <[email protected]>
To: Jesse Rehmer <[email protected]>
Cc: [email protected]
Subject: Re: Facilitating installation and update of anti-spam filter
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
On Sun, Jul 10, 2022 at 03:37:46PM -0500, Jesse Rehmer wrote:
>
> > On Jul 10, 2022, at 1:34 PM, Julien ??LIE <[email protected]> wrote:
> >
> > Local patches should indeed be retained, I agree.
> >
> > Note that you would have the same problem if distributions provided
> > inn2-cleanfeed packages... Any update would erase local changes (unless
> > done in cleanfeed.local).
>
> Until an integrated filter that is regularly maintained and battle-tested is
> introduced with INN, I???d rather not have anything mess with pyClean.
> I???ve found some of its filters too aggressive and have disabled several,
> which it doesn???t provide an easy way to do via config files. Cleanfeed has
> config options for disabling each of its checks, if I recall correctly. In
> my case filter_innd.py is heavily modified. Overall pyClean does it???s job,
> but I find the PHN/FSL filters reject a fair amount of ???valid??? articles.
> I put quotes around valid because admittedly the articles I???m referring to
> are often part of flame wars and such, but they are not what I consider spam.
>
> I can???t get pyClean to work with Python 3.8/3.9 and had to revert to using
> Python 2.7. It loads and reports it is hooked into INN but never does any
> filtering or logging. Looking at the Github repo it has had a few updates in
> the last couple years, but the majority of the code is 7 years old. Another
> hurdle for me was Steve???s repo has zero installation instructions. When I
> first came across it I had no idea how to properly install and configure. It
> wasn???t until I stumbled upon a fork whose maintainer took the time to
> provide a basic install guide that it was clear what to do.
>
> If such filtering packages are going to be distributed with INN hopefully
> they get more love and maintenance. I don???t know if this would improve
> performance, but I???d like the filter to run as an external process. During
> busy times innd with pyClean is using ~40-60% more CPU than another innd
> process handing the same feed with no filtering. I lack the skills to dive
> into whether this is due to pyClean code, the Python hook, or a combination
> but it uses quite a bit more CPU than Cleanfeed. My server isn???t that busy
> compared to others, but I could see it being unusable for those handling just
> a small fraction of binary groups. I only carry a few that are sporadic, but
> I can tell when binary articles are coming in by how much one of my spool
> machine???s CPU usage spikes. Having the filter run as a separate process
> would at least give me a better idea where to place blame and investigate for
> improvement.
>
I tried a Python 2.7 programme with Python 3. Incompatible.
You need to rewrite the whole module.
> Whatever is decided, let???s please not introduce another ???Cleanfeed???
> into the world, where multiple iterations by various maintainers are strewn
> amongst the Internet, and for a beginner is confusing to understand what is
> the newest version, where to get it, who maintains it, etc.
>
> > Nonetheless, we have configuration files for which news admins should give
> > better care. How could they notably know there are moderating rules to
> > change? (the fido7.* line in moderators should for instance point to
> > @fido7.org and no longer @fido7.ru - I bet most news admins did not do the
> > change)
> > Same thing for control.ctl when a rule (and sometimes its associated key)
> > change...
> >
> > Which in fact raises the question of how to ease the administration of a
> > news server and inform admins of changes they should have a look at?
>
> Good question, this has been a point of struggle for me after putting down
> INN/Diablo/NNTP for some years and picking things up again. This area of
> administration is a mess across the entirety of Usenet. INN???s maintainers
> have seemingly been the only entity attempting to keep the usefulness of
> control messages alive. A common method to update, or notify of updates, to
> the control.ctl or filters would be a good start. I try to keep this stuff
> up-to-date, but it can be confusing what is ???up-to-date??? and where is the
> proper place to look for changes.
Thanks to Julien and Russ, INN rocks!
>
> Regards,
>
> Jesse Rehmer
> --
> inn-workers mailing list
> [email protected]
> https://lists.isc.org/mailman/listinfo/inn-workers
--
Member - Liberal International This is [email protected] Ici [email protected]
Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising!
Look at Psalms 14 and 53 on Atheism https://www.empire.kred/ROOTNK?t=94a1f39b
Which truth is the correct one? -unknown Beware https://mindspring.com
------------------------------
Message: 2
Date: Sun, 10 Jul 2022 22:03:11 -0600
From: Grant Taylor <[email protected]>
To: [email protected]
Subject: Re: Facilitating installation and update of anti-spam filter
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
On 7/10/22 12:34 PM, Julien ?LIE wrote:
> Hi Grant,
Hi,
> Local patches should indeed be retained, I agree.
:-)
> Note that you would have the same problem if distributions provided
> inn2-cleanfeed packages... Any update would erase local changes (unless
> done in cleanfeed.local).
Maybe ~> probably.
> Unfortunately I am not aware of such a mailing-list...
That sounds like something that could be rectified.
> I agree that "constant" polling from installed instances should be
> avoided (I had in mind once a week or even a month).? They do not change
> often.
:-/
> Nonetheless, we have configuration files for which news admins should
> give better care.? How could they notably know there are moderating
> rules to change? (the fido7.* line in moderators should for instance
> point to @fido7.org and no longer @fido7.ru - I bet most news admins did
> not do the change)
> Same thing for control.ctl when a rule (and sometimes its associated
> key) change...
Agreed.
> Which in fact raises the question of how to ease the administration of a
> news server and inform admins of changes they should have a look at?
I don't know. If INN supports include file directive(s) and (re)setting
values multiple times, I could see how the configuration files could be
addressed. E.g. have default in <file>, which has something like
"include <file>.local" as it's last line. Then any INN / distro
provided settings that the admin wants to overwrite could be placed in
the <file>.local file.
There might be an opportunity for some minor refactoring to make
supporting updates easier.
--
Grant. . . .
unix || die
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4017 bytes
Desc: S/MIME Cryptographic Signature
URL:
<https://lists.isc.org/pipermail/inn-workers/attachments/20220710/4a17300e/attachment-0001.bin>
------------------------------
Subject: Digest Footer
_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers
------------------------------
End of inn-workers Digest, Vol 142, Issue 5
*******************************************
