Am 2022-05-13 19:03, schrieb Henrik K:
On Sun, May 02, 2021 at 10:36:37AM +0200, Giovanni Bechis wrote:
On Sat, May 01, 2021 at 12:54:41PM +0300, Henrik Krohns wrote:
>
> These kinds of changes just make you wonder what's the point of doing such
> plugins inside SA distribution.. if we ever do get 4.0 released, I really
> doubt if there are enough resources in the project to even release monthly
> updates after that..
>
I have no problem in working out-of-tree but distros will probably
never package an external plugin and, in some cases, it may be better
an outdated plugin then no plugin at all.
Releasing every some months could help, distro will ship outdated
packages
in any case but I do not think we can do much to improve that
situation.
Bumping up this discussion due to:
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7989
In current state the Esp.pm likely too vague for any users to use. It
should be clearly documented where the feed files are found, and what
format
they should be expected to be in. An external github page related to
the
plugin does not constitute as documentation.
Somewhat agree with Michael's comment that the module shouldn't be an
advertisement for Invaluement either. Then again, at this time
Invaluement
doesn't even seem to be providing the data, so what use is for the
module?
For the actual reply to Giovannis comment, "it may be better an
outdated
plugin then no plugin at all": Again, what use is the plugin as users
actually need knowledge and effort to setup the feed downloads and make
sure
they work. With the same effort they can download up-to-date module
from
Github into /etc/mail/spamassassin.
From my point of view, the Esp.pm plugin should not be a standard plugin
of SpamAssassin. Standard plugins should provide tools or language
extensions for the SA meta language. This plugin on the other hand
provides highly specialized functions. Since new functions have to be
programmed for each newly included ESP, the plugin needs a much faster
release cycle than SpamAssassin can provide. Therefore, the maintenance
of this plugin should be done outside SpamAssassin. Announcements about
new releases should definitely be made on the SpamAssassin user list.
The inclusion of new ESPs is certainly necessary, as there are dozens of
ESPs. For example, while I don't have a single spam mail from Maildome,
Mailup or Mdirector, other ESPs like ActiveCampaign, eC-messenger (was
eCircle), Klaviyo, Salesforce and Sparkpost are in my configuration. How
to do the configuration of new ESPs generically with standard
SpamAssassin means I will describe later when I have fully programmed
the changes needed for this.
Michael
