Facilitating installation and update of anti-spam filter

[Grant Taylor]

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.bin>