https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8004
Bug ID: 8004 Summary: seteuid to 0 failed: Operation not permitted Product: Spamassassin Version: SVN Trunk (Latest Devel Version) Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P2 Component: spamassassin Assignee: dev@spamassassin.apache.org Reporter: marcel.even...@gmail.com Target Milestone: Undefined I built a test rpm of spamassassin-4.0.0 svn1901614 in order to test the SpamAssassin 4.0 branch with amavis-2.12.2-1. Now I'm seeing this warning when restarting Amavis: Jun 4 06:39:04 el8p18 amavis[3566886]: _WARN: util: seteuid to 0 failed: Operation not permitted at /usr/share/perl5/vendor_perl/Mail/SpamAssassin/Util.pm line 1888. Jun 4 06:39:04 el8p18 amavis[3566886]: _WARN: util: POSIX::setgid 981 failed: Operation not permitted Jun 4 06:39:04 el8p18 amavis[3566886]: _WARN: util: failed to set gid 981: Operation not permitted Jun 4 06:39:04 el8p18 amavis[3566886]: _WARN: util: failed to set effective gid 981 985: Operation not permitted gid 981 is the amavis group. Even with this warning Amavis and SpamAssassin 4 seem to be working fine together. I don't see this error when downgrading back to spamassassin 3.4.6-1. I'm not sure if this is a bug in SpamAssassin 4 or Amavis. -- You are receiving this mail because: You are the assignee for the bug.