Ok fixed the symbolic link error, I updated the spamd script with the 3.0.5 one, but backed up the old one. Restored the old one and no errors. It still shows 3.0.5 in the logs but not in the email headers. Any idea where to look to see what Im pumping into spamc? I am running qmail with qmail-scanner on Fedora core 2.
Robert -----Original Message----- From: Robert Bartlett [mailto:[EMAIL PROTECTED] Sent: Thursday, January 12, 2006 3:04 PM To: 'Matt Kettler' Cc: 'users@spamassassin.apache.org' Subject: RE: AWL and Auto Learn Bayes Looks like it was erroring out trying to access the pid file? It was pointed to the wrong file. So now when I stop and restart it, it nows shows this in the maillog: Jan 12 15:01:35 milkyway spamd[17235]: server started on port 783/tcp (running version 3.0.5) Jan 12 15:01:35 milkyway spamd[17235]: server successfully spawned child process, pid 17240 Jan 12 15:01:35 milkyway spamd[17235]: server successfully spawned child process, pid 17241 Jan 12 15:01:35 milkyway spamd[17235]: server successfully spawned child process, pid 17242 Jan 12 15:01:35 milkyway spamd[17235]: server successfully spawned child process, pid 17243 Jan 12 15:01:35 milkyway spamd[17235]: server successfully spawned child process, pid 17244 Jan 12 15:01:35 milkyway spamd[17235]: Can't write to PID file: Too many levels of symbolic links I look in the directory for the pid file and its highlighted red, so now the link is not working? And it still shows as 3.0.1 in the header of emails. Robert -----Original Message----- From: Matt Kettler [mailto:[EMAIL PROTECTED] Sent: Thursday, January 12, 2006 2:42 PM To: Robert Bartlett Cc: users@spamassassin.apache.org Subject: Re: AWL and Auto Learn Bayes Robert Bartlett wrote: > Hello, > Thanks for the help. It seems to be painless, but in the headers it > still shows 3.0.1, but when I startup SA in debug mode it says 3.0.5. > I vagually remember a file I had to edit to show the proper version in > the email headers? No, there shouldn't be. SA adds the headers based on the version number that's really running. Maybe Im thinking of something else? I tried restarting SA, still > shows 3.0.1. Or does it really matter? I just want to make sure 3.0.5 > is running. > How are you calling SA? Are you using a MTA integration tool, or a script that pipes stuff into spamc?
