I'm not an expert (by any strech of the imagination) on SA debug output.
However, one line there looks more curious to me than others:

> > debug: using "/root/.spamassassin/user_prefs" for user prefs file

> > Failed to parse line in SpamAssassin configuration, skipping: N_"

I don't see anything else that seems to me to be a failure, although someone
else that knows more might spot something odd.

But what I see from the above makes me think that one of the SA
configuration or rules files has a problem, possibly the mentioned
user_prefs file.  I don't know if SA reads all the config files and then
parses them in a batch, or if it parses them one at a time.  If it does them
one at a time, that error is almost surely in the user_prefs file.

I'd scan that file for some token that starts with, or maybe consists
completely of either "N_" or maybe "n_".  I suspect that a line got mangled
and there is a newline in the middle of what should be a single line.  Or if
this is an upgrade to 3.0 (sorry, I've forgotten what got you into this)
maybe you have some option in there that is no longer valid in 3.0.

        Loren

Reply via email to