https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8031
Sidney Markowitz <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|REOPENED |RESOLVED --- Comment #24 from Sidney Markowitz <[email protected]> --- I have not got as far as getting the exact same error as Giovanni, but I have got to a point where I'm going to close it again as WONTFIX. I can summarize the problem as this: When spamd is run as root, it will setuid to switch to either the user in the -u option or to user nobody. If the uid it switches to does not have read access to the modules in the perl lib directories and the SpamAssassin modules, then of course any subsequent require of the modules will fail. Whether or not that is sufficient to cause a specific test to fail depends on the test. But it is still wrong. In my logs, even when the test got a pass, the logs still had permission denied warnings that just didn't happen to cause a die that failed the test. Changing that one require that you see did not really fix anything, just allowed a PASS result. The bottom line is that it is not valid to run spamd as root and have perl lib or SpamAssassin modules in directories that are not accessible to the user that spamd will run as. That will not work when run in production and so doesn't have to work when running tests. Put SpamAssassin in a world-accessible directory tree and the test should run even if run as root. But better, only run the root tests as root. -- You are receiving this mail because: You are the assignee for the bug.
