I'm experiencing the same error running a combination of spamassassin
and pyzor. I turned on debug logging for spamd (-D option) to get a
little more information.
The issue appears to be that pyzor is running as "nobody" (which is a
good thing, imo) and it is trying to create a .pyzor configuration file
in a directory that doesn't exist.
Nov 25 21:21:35 server spamd[26523]: pyzor: failure to parse response
"Traceback (most recent call last):"
Nov 25 21:21:35 server spamd[26523]: pyzor: failure to parse response "
File "/usr/bin/pyzor", line 408, in <module>"
Nov 25 21:21:35 server spamd[26523]: pyzor: failure to parse response "
main()"
Nov 25 21:21:35 server spamd[26523]: pyzor: failure to parse response "
File "/usr/bin/pyzor", line 131, in main"
Nov 25 21:21:35 server spamd[26523]: pyzor: failure to parse response "
config, options, args = load_configuration()"
Nov 25 21:21:35 server spamd[26523]: pyzor: failure to parse response "
File "/usr/bin/pyzor", line 107, in load_configuration"
Nov 25 21:21:35 server spamd[26523]: pyzor: failure to parse response "
os.mkdir(options.homedir)"
Nov 25 21:21:35 server spamd[26523]: pyzor: failure to parse response
"FileNotFoundError: [Errno 2] No such file or directory:
'/nonexistent/.pyzor'"
The user nobody has /nonexistent/ as its home directory.
I haven't yet found a way to specify the --homedir parameter in
spamassassin configuration, which could potentially work around this
problem. Still, it would be good if the default pyzor behavior wouldn't
make it fail when running as nobody.
spamassassin 3.4.2-1
pyzor 1:1.0.0.0-3
