On Fri, Mar 17, 2023 at 05:34:37AM -0400, Michael Grant via users wrote: > On Fri, Mar 17, 2023 at 11:26:21AM +0200, Henrik K wrote: > > On Fri, Mar 17, 2023 at 04:52:41AM -0400, Michael Grant via users wrote: > > > Is there a recommended way of installing a spamassassin plugin on > > > debian (or ubuntu) such that the plugin gets updated via say apt? I'm > > > guessing no because I don't see many spamassassin plugins when I do an > > > "apt search". > > > > > > Up to now, I have been manually putting things in /etc/spamassassin/ > > > but I feel like there has to be a better way to manage these. > > > > > > What do people do to keep things up to date easily? > > > > There is no automated handling of third party plugins. It's up the > > maintainers to provide or not provide any support. Which usually just means > > monitoring some github repo etc. > > What about CPAN? Do people use that? It seems like there's quite a > few modules in CPAN already. I will admit that if I see a debian > package, I go for that, I rarely if ever install stuff from CPAN but I > could be convinced to use it more if this created some order out of > the chaos.
Again, it's up to the plugin developer to publish it in CPAN or not, some can be found there. But it really isn't any different or more safe than wgetting some Plugin.pm file manually from Github. It's not recommended to automate either way, since you could just be downloading some incompatible or worst case, a malicious file. Always audit and test updates manually.
