Tracey Gates wrote:
OK. Sorry, I'm a novice at all of this admin stuff. I replaced the old
files back and restarted spamd again. I did a find for spamd and here
is my results:
[EMAIL PROTECTED] /]# find ./ -name spamd
find: ./proc/9832/fd: No such file or directory
./etc/rc.d/init.d/spamd
./usr/bin/spamd
./usr/src/redhat/BUILD/Mail-SpamAssassin-3.0.2/spamd
./usr/src/redhat/BUILD/Mail-SpamAssassin-3.0.2/spamd/spamd
./usr/src/redhat/BUILD/Mail-SpamAssassin-3.0.2/blib/script/spamd
./usr/src/redhat/BUILD/Mail-SpamAssassin-3.1.1/spamd
./usr/src/redhat/BUILD/Mail-SpamAssassin-3.1.1/spamd/spamd
./usr/src/redhat/BUILD/Mail-SpamAssassin-3.1.1/blib/script/spamd
./home/administrator/Mail-SpamAssassin-3.0.2/spamd
./home/administrator/Mail-SpamAssassin-3.0.2/spamd/spamd
./home/administrator/Mail-SpamAssassin-3.0.2/blib/script/spamd
Am I looking for the correct file? I don't see what it might be picking
up the wrong version.
Ah, wait! I just went back and re-read the original email. You said:
>I'm running on a RedHat ES 3.0 using CommuniGatePro and CGPSA. The
>CGPSA.conf file points to the correct directories for my SA
>installation. Any suggestions would be a great help.
This link: http://www.tffenterprises.com/cgpsa/
says:
>The filter works efficiently, by directly using the SpamAssassin API.
>It does not rely on a daemon process such as spamd or on the execution
>of shell scripts (as the usual process for utilizing SpamAssassin with
>CommuniGate servers does). It can safely be used with multiple
>CommuniGate Pro enqueuer threads.
So... basically, your not using spamd. Looking for another copy of it
is pointless. It seems you have 2 copies of the SpamAssassin API laying
around.
-Jim
