Autor: Bill Hacker Data: A: Jerry Stuckle CC: exim-users, Marc Perkel Assumpte: Re: [exim] Exim and SpamAssassin
Jerry Stuckle wrote:
> Hi, Bill,
>
> Thanks for the suggestion, but that's not it. The MySQL calls are
> working fine.
*SNIP*
> So, I'm back to my previous question. Is there any way to get a
> debug trace for the process created to handle the message coming out
> of SpamAssassin?
Exim can only log what it handles, so even enhancement
with 'warn', 'message' and 'log_write' won't see what goes on between
the hand-off to SA and the return - only before and after.
Exim *can* log the setup and results of all SQL calls - even to the
point of showing the pwd in the log - that you may be doing already.
But the problem seems to be in the SA area.
SA does have configurable logging, but I have never paid much attention
to it.
'Cheap and cheerful' way I go about it is to point everything in
installed ports and packages to syslogd, crank up their debug levels,
edit /etc/syslog.conf to send *everything loose* to /var/log/console.log
Then use 'multitail' to watch ~/console.log and several others at once,
see which is most helpful....
*BEWARE* - if you get disconnected from an ssh session, 'multitail'
will live on, and within a day or less can consume all the CPU
available. Always do a 'top' and make sure it is dead before going away!