[Bug 7961] Spamassassin is ignoring additional own rules
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7961 --- Comment #12 from AXB --- (In reply to lsmod from comment #11) > Thanks. > > # spamassassin --lint > does not show any result - so this should be OK? > > Is the option -t for the debugging of rules? > > Is it generally better to put each word in one rule? Please use the mailinglist. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 7961] Spamassassin is ignoring additional own rules
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7961 --- Comment #11 from lsmod --- Thanks. # spamassassin --lint does not show any result - so this should be OK? Is the option -t for the debugging of rules? Is it generally better to put each word in one rule? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 7961] Spamassassin is ignoring additional own rules
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7961 Loren Wilton changed: What|Removed |Added CC||lwil...@earthlink.net --- Comment #10 from Loren Wilton --- This should be over on the users list, but: Have you run spamassassin --lint to make sure that the rules are correct? An error on one rule can often end up invalidating many other rules. It looks like your rule should hit. Since it doesn't it either isn't getting picked up as a rule for some reason, or there is something wrong with the rule neither of us understand. Try simplifying it. You don't need the parends, for a start. If you feel you do, you should use (?: instead of ( to make it a non-capturing group. I would start with a rule like header SEX Subject =~ /Sex/i If that doesn't hit, it is time to run SA with rules debug or rule file debug. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 7961] Spamassassin is ignoring additional own rules
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7961 Henrik Krohns changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |INVALID --- Comment #9 from Henrik Krohns --- Stop responding here please, use the mailinglist. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 7961] Spamassassin is ignoring additional own rules
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7961 lsmod changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID |--- --- Comment #8 from lsmod --- Sure? Today an email comes through: X-Spam-Threshold: 5 X-Spam-Score: 4.9 X-Spam-Score-Int: 49 X-Spam-Bar: X-Spam-Flag: NO X-Message-Age: 3 Subject: Sex oder Covid? This should be catched by the rule: header CONTAINS_SUB Subject =~ /(Sex|Potenz|Dating| Date |Finanz|Volksbank|FFP-2|M[aä]dchen|Bett|ficken|flirten|einsam|Rezept)/i score CONTAINS_SUB 5 describe CONTAINS_SUB Betreff enthält Spam-Wörter bit it isn't. So this own rule is still ignored. How it can be find out why? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 7961] Spamassassin is ignoring additional own rules
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7961 Henrik Krohns changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID CC||apa...@hege.li --- Comment #7 from Henrik Krohns --- Please ask for support in users mailing list. As you said, this is not a bug and SA project has no relation on how Debian does things. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 7961] Spamassassin is ignoring additional own rules
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7961 --- Comment #6 from lsmod --- I could find one solution for test now: Renaming /etc/spamassassin/sa-compile.pre to sa-compile.pre.bak deactivates loading the compiled rules. After restart of the Spamassassin the cf-files are used and the own rules are active. Sending an Test-Mail with the keywords leads to a corresponding Spam-Score: X-Spam-Threshold: 5 X-Spam-Score: 5.1 X-Spam-Score-Int: 51 X-Spam-Bar: + X-Spam-Flag: YES X-Message-Age: 2 Subject: My Madchen does have more sex and dating When the compiled ruleset shall be used, the question remains how own rules can be implemented that they are not overwritten by automatical updates? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 7961] Spamassassin is ignoring additional own rules
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7961 --- Comment #5 from lsmod --- Some own ideas to check: https://spamassassin.apache.org/full/3.2.x/doc/sa-compile.html No part of user_prefs or any files included from user_prefs can be built into the compiled set. This compiled set is then used by the Mail::SpamAssassin::Plugin::Rule2XSBody plugin to speed up SpamAssassin's operation, where possible, and when that plugin is loaded. It is not clear how own rules can be added? # spamassassin -D --lint 2>&1 | grep Rule2XSBody Mar 6 11:50:48.214 [123607] dbg: plugin: loading Mail::SpamAssassin::Plugin::Rule2XSBody from @INC Mar 6 11:50:49.293 [123607] dbg: plugin: Mail::SpamAssassin::Plugin::Rule2XSBody=HASH(0x55fec3febe90) implements 'finish_parsing_end', priority 0 Mar 6 11:50:50.043 [123607] dbg: plugin: Mail::SpamAssassin::Plugin::Rule2XSBody=HASH(0x55fec3febe90) implements 'check_start', priority 0 Mar 6 11:50:50.055 [123607] dbg: plugin: Mail::SpamAssassin::Plugin::Rule2XSBody=HASH(0x55fec3febe90) implements 'check_rules_at_priority', priority 0 Mar 6 11:50:50.056 [123607] dbg: plugin: Mail::SpamAssassin::Plugin::Rule2XSBody=HASH(0x55fec3febe90) implements 'run_body_fast_scan', priority 0 Mar 6 11:56:36.505 [124505] dbg: zoom: loading compiled ruleset from /var/lib/spamassassin/compiled/5.032/3.004006 Mar 6 11:56:36.507 [124505] dbg: zoom: using compiled ruleset in /var/lib/spamassassin/compiled/5.032/3.004006/Mail/SpamAssassin/CompiledRegexps/body_0.pm for Mail::SpamAssassin::CompiledRegexps::body_0 Mar 6 11:56:36.514 [124505] dbg: zoom: able to use 397/397 'body_0' compiled rules (100%) The compiled rules are used - so the rules loaded from the *.cf files are ignored? What is the way to add own rules to the compilation of the rules? How can be sa-compile deactivated for test purposes? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 7961] Spamassassin is ignoring additional own rules
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7961 --- Comment #4 from lsmod --- Here is what you want to check: drwxr-xr-x 4 root root 4,0K 27. Feb 12:57 spamassassin drwxr-xr-x 4 root root 4,0K 27. Feb 12:57 . drwxr-xr-x 164 root root 12K 26. Feb 07:36 .. -rw-r--r-- 1 root root 1,3K 19. Nov 2017 65_debian.cf -rw-r--r-- 1 root root 1,2K 30. Mai 2021 init.pre -rw-r--r-- 1 root root 3,3K 17. Feb 15:52 local.cf -rw-r--r-- 1 root root 3,3K 30. Mai 2021 local.cf.bak -rw-r--r-- 1 root root 2,9K 27. Apr 2018 local.cf.dpkg-old -rw-r--r-- 1 root root 2,4K 30. Okt 2016 local.cf.org -rw-r--r-- 1 root root 118 30. Okt 2016 sa-compile.pre drwxr-xr-x 2 root root 4,0K 30. Okt 2016 sa-update-hooks.d drwx-- 3 root root 4,0K 17. Feb 17:25 sa-update-keys -rw-r--r-- 1 root root 2,5K 30. Okt 2016 v310.pre -rw-r--r-- 1 root root 1,2K 30. Okt 2016 v312.pre -rw-r--r-- 1 root root 2,4K 30. Okt 2016 v320.pre -rw-r--r-- 1 root root 1,3K 30. Okt 2016 v330.pre -rw-r--r-- 1 root root 1020 30. Okt 2016 v340.pre -rw-r--r-- 1 root root 1,3K 30. Okt 2016 v341.pre -rw-r--r-- 1 root root 1,5K 30. Mai 2021 v342.pre -rw-r--r-- 1 root root 1,3K 30. Mai 2021 v343.pre -rw-r--r-- 1 root root 722 27. Feb 12:56 myrules.cf # This is the right place to customize your installation of SpamAssassin. # # See 'perldoc Mail::SpamAssassin::Conf' for details of what can be # tweaked. # # Only a small subset of options are listed below # ### header CONTAINS_SUB Subject =~ /(Sex|Potenz|Dating| Date |Finanz|Volksbank|FFP-2|M[aä]dchen|Bett|ficken|flirten|einsam|Rezept)/i score CONTAINS_SUB 5 describe CONTAINS_SUB Betreff enthält Spam-Wörter header CONTAINS_FROM From =~ /(Pillen|Erektion)/i score CONTAINS_FROM 5 describe CONTAINS_FROM Absender enthält Spam-Wörter There is no selinux installed or active on the server, only AppArmor, but not for SpamAssassin. How it can be checked if the compiled rules from sa-compile are used? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 7961] Spamassassin is ignoring additional own rules
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7961 --- Comment #3 from Benny Pedersen --- ls -l /etc ls -l /etc/spamassassin and lastly what is the content of myrules.cf ? is permissons on /etc/spamassassin allowin files to be read from spamd user ?, files must be owned by root, but not only with permission to be readed from root so set "chmod -R 0644 /etc/spamassassin" and chmod 0755 on the dir itself lastly all dirs and files set to root and group root if that still fails ensire selinux is disabled, if its works then its selinux problem to solve -- You are receiving this mail because: You are the assignee for the bug.
[Bug 7961] Spamassassin is ignoring additional own rules
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7961 lsmod changed: What|Removed |Added CC||fo...@home.decotrain.de --- Comment #2 from lsmod --- Thanks for your Tip! # spamassassin -D --lint 2>&1 | grep LOCAL_RULES_DIR Mar 5 17:35:25.045 [4145853] dbg: generic: Perl 5.032001, PREFIX=/usr, DEF_RULES_DIR=/usr/share/spamassassin, LOCAL_RULES_DIR=/etc/spamassassin, LOCAL_STATE_DIR=/var/lib/spamassassin So the directory is LOCAL_RULES_DIR=/etc/spamassassin This is not surprising and as stated in the bugreport at Debian the file with the own rules is read, but the rules are ignored: dbg: config: read file /etc/spamassassin/myrules.cf This is the main problem. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 7961] Spamassassin is ignoring additional own rules
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7961 Benny Pedersen changed: What|Removed |Added CC||m...@junc.eu --- Comment #1 from Benny Pedersen --- spamassassin -D --lint 2>&1 | grep LOCAL_RULES_DIR put rules in this dir -- You are receiving this mail because: You are the assignee for the bug.
