Summary: | spamassassin | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Philippe ROUBACH <philippe.roubach> |
Component: | config dialog | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bugrprt21882, montel |
Priority: | NOR | ||
Version: | 5.7.1 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | https://commits.kde.org/kdepim-addons/70f99474e64b875bbf4f13920698f9c5a4d7c507 | Version Fixed In: | 17.12.3 |
Sentry Crash Report: |
Description
Philippe ROUBACH
2018-02-03 09:36:03 UTC
i forgot this : i choose spamassassin daemon What is the problem ? it creates a filter with regular expression with "(yes)|(YES)" so I don't understand the problem. in comment #1 i said i choose "spamassassin daemon" in this case it creates a filter with "yes" not "yes | YES" it's a regexp => search YES or yes so what is the problem ? it doesn't catch it ? well i mus explain more. With the assistant there is a step to choose spamassassin (perl) or spamssassin daemon then filters are created in case of spamassassin perl then a filter "X-Spam-flag = yes | YES" is created in case of spamassassin daemon a filter "X-Spam-Flag = yes" is created if you look message source you see ... X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on linux-58nc X-Spam-Flag: YES X-Spam-Level: ****** ... consequence: using spamc/spamd every message detected as spam is not treated as a spam Ok I understand it. Thanks for explanation *** Bug 389908 has been marked as a duplicate of this bug. *** Fixed in kdepim-addons 17.12.3 Git commit 70f99474e64b875bbf4f13920698f9c5a4d7c507 by Laurent Montel. Committed on 22/02/2018 at 05:49. Pushed by mlaurent into branch 'Applications/17.12'. Fix Bug 389820 - spamassassin FIXED-IN: 17.12.3 M +1 -1 kmail/plugins/common/kmail.antispamrc https://commits.kde.org/kdepim-addons/70f99474e64b875bbf4f13920698f9c5a4d7c507 |