On 2/16/2023 5:32 PM, hg user wrote:
On Thu, Feb 16, 2023 at 9:57 PM joe a <joea-li...@j4computers.com
<mailto:joea-li...@j4computers.com>> wrote:
plugin: failed to parse plugin (from @INC): Can't locate
Mail/SpamAssassin/Plugin/SpamCop.pm:
lib/Mail/SpamAssassin/Plugin/SpamCop.pm: Permission denied at (eval 44)
line 1.
root can do anything. a restricted user can't: it's only allowed to do
what others allowed it.
it also runs with another environment, so it may miss PATHes or @INC
directories.
That throws me a curve. What is an @INC directory? SA specific?
I do not find any with the locate command, but if the are an actual
directory may need to escape the @ sign somehow. \ does not seem to do it.
You should locate the SpamCop.pm file and list the owner and ACL.
This I have done, with no change, even to the point of starting using _R
option at /usr/lib/perl5/vendor_perl/5.26.1/Mail
As user spamfilter run spamassassin with -D and see in the first lines
if you have similar errors.
Done that. It is impressively more verbose, but I did not detect any
more errors.
Also check permission of /var/mail/spamd/Cabinet.Missed-SPAM. I had
permission problems trying to sa-learn files owned by root.
That I found and fixed some time back.
Running with the -D option does produce more, after that list of
permission denied items
Feb 16 15:55:30.884 [10384] dbg: config: warning: no description set
for
STOX_REPLY_TYPE_WITHOUT_QUOTES
These are not permission errors but warnings about the rules having no
text descriptions. It's ok.
