public inbox for pmg-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: pmg-devel@lists.proxmox.com
Subject: [pmg-devel] [PATCH pmg-api 0/7] adapt to SpamAssassin 4.0.0
Date: Mon, 13 Mar 2023 22:23:43 +0100	[thread overview]
Message-ID: <20230313212351.111977-1-s.ivanov@proxmox.com> (raw)

SpamAssassin 4.0.0 was released back in December 2022 and seems to work
nicely for the greatest part.

This patchset adapts pmg-api where necessary (patch 1/7), updates the
templates for less diff (2/7), and enables the new features depending
on the spam section of pmg.conf (mostly only enabling modules which do
DNSBL lookups based on the rbl_checks setting)

for testing the ExtractText plugin I used the gtube test string in
a libreoffice document (saving it as .doc, .docx, .pdf, .odt, .rtf)
as it's still quite new functionality I added an explicit config-option
for it (also to provide some visibility)

pmg-api:
Stoiko Ivanov (7):
  ruledb: spam: adapt to spamassassin 4.0.0
  templates: sync spamassassin templates with 4.0.0 upstream
  templates: add template for spamassassin's v342.pre
  templates: add template for spamassassin's v400.pre
  config: add spam option for extract_text
  templates: enable DecodeShortUrls for SpamAssassin 4.0.0
  templates: enable DMARC plugin in v400.pre.in

 debian/control            |  9 +++++-
 src/Makefile              |  2 ++
 src/PMG/Config.pm         | 12 +++++++
 src/PMG/RuleDB/Spam.pm    | 10 +++---
 src/templates/init.pre.in | 26 ++++++++++++---
 src/templates/v310.pre.in | 18 +++++------
 src/templates/v320.pre.in |  5 +++
 src/templates/v342.pre.in | 39 ++++++++++++++++++++++
 src/templates/v400.pre.in | 68 +++++++++++++++++++++++++++++++++++++++
 9 files changed, 170 insertions(+), 19 deletions(-)
 create mode 100644 src/templates/v342.pre.in
 create mode 100644 src/templates/v400.pre.in

pmg-gui:
Stoiko Ivanov (1):
  spamdetector: add extract_text option

 js/SpamDetectorOptions.js | 2 ++
 1 file changed, 2 insertions(+)

-- 
2.30.2





             reply	other threads:[~2023-03-13 21:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-13 21:23 Stoiko Ivanov [this message]
2023-03-13 21:23 ` [pmg-devel] [PATCH pmg-api 1/7] ruledb: spam: adapt to spamassassin 4.0.0 Stoiko Ivanov
2023-03-13 21:23 ` [pmg-devel] [PATCH pmg-api 2/7] templates: sync spamassassin templates with 4.0.0 upstream Stoiko Ivanov
2023-03-13 21:23 ` [pmg-devel] [PATCH pmg-api 3/7] templates: add template for spamassassin's v342.pre Stoiko Ivanov
2023-03-13 21:23 ` [pmg-devel] [PATCH pmg-api 4/7] templates: add template for spamassassin's v400.pre Stoiko Ivanov
2023-03-13 21:23 ` [pmg-devel] [PATCH pmg-api 5/7] config: add spam option for extract_text Stoiko Ivanov
2023-03-13 21:23 ` [pmg-devel] [PATCH pmg-api 6/7] templates: enable DecodeShortUrls for SpamAssassin 4.0.0 Stoiko Ivanov
2023-03-13 21:23 ` [pmg-devel] [PATCH pmg-api 7/7] templates: enable DMARC plugin in v400.pre.in Stoiko Ivanov
2023-03-13 21:23 ` [pmg-devel] [PATCH pmg-gui 1/1] spamdetector: add extract_text option Stoiko Ivanov
2023-03-27 18:06   ` [pmg-devel] applied: " Thomas Lamprecht
2023-03-15 15:55 ` [pmg-devel] applied: [PATCH pmg-api 0/7] adapt to SpamAssassin 4.0.0 Thomas Lamprecht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230313212351.111977-1-s.ivanov@proxmox.com \
    --to=s.ivanov@proxmox.com \
    --cc=pmg-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal