date:20051110





Anyone?

Jeffrey Duncan wrote:

  
Okay, so I see that I have two versions of PerMsgStatus.pm (below)
Would this be causing the following issues?

Failed to run __ENV_AND_HDR_FROM_MATCH SpamAssassin test,
skipping:__(Can't locate object metho
d "check_for_matching_env_and_hdr_from" via package
"Mail::SpamAssassin::PerMsgStatus" at
/usr/lib/perl5/site_perl/5.8.5/Mail/SpamAs
sassin/PerMsgStatus.pm line 2312, GEN12 line 83._) 


How do I remove one of them to get rid of the issues?
  
Jeffrey Duncan wrote:
  

Thanks, 

What do you mean resolve? Here is the output ...


[EMAIL PROTECTED] log]# locate PerMsgStatus.pm
/usr/lib/perl5/site_perl/5.8.6/Mail/SpamAssassin/PerMsgStatus.pm
/usr/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/PerMsgStatus.pm
/usr/src/redhat/BUILD/Mail-SpamAssassin-3.1.0/lib/Mail/SpamAssassin/PerMsgStatus.pm
/usr/src/redhat/BUILD/Mail-SpamAssassin-3.1.0/blib/lib/Mail/SpamAssassin/PerMsgStatus.pm
/downloads/qmailrocks/perlmods/rpms/newmods/Mail-SpamAssassin-3.1.0/lib/Mail/SpamAssassin/PerMsgStatus.pm
/downloads/qmailrocks/perlmods/rpms/newmods/Mail-SpamAssassin-3.1.0/blib/lib/Mail/SpamAssassin/PerMsgStatus.pm
[EMAIL PROTECTED] log]# 

Justin Mason wrote:

  -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Jeffrey Duncan writes:
  
  
Hello.  I am getting the following in my logs and wonder if anyone can 
help with the problem:

Nov  9 12:56:01 server spamd[1845]: Failed to run 
__ENV_AND_HDR_FROM_MATCH SpamAssassin test, skipping:__(Can't locate 
object method "check_for_matching_env_and_hdr_from" via package 
"Mail::SpamAssassin::PerMsgStatus" at 
/usr/lib/perl5/site_perl/5.8.5/Mail/SpamAss
assin/PerMsgStatus.pm line 2312, GEN3 line 144._)

Nov  9 12:56:01 server spamd[1845]: Failed to run USER_IN_DEF_SPF_WL 
SpamAssassin test, skipping:__(Can't locate object method "chec
k_for_def_spf_whitelist_from" via package 
"Mail::SpamAssassin::PerMsgStatus" at 
/usr/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/Per
MsgStatus.pm line 2312, GEN3 line 144._)

Nov  9 12:56:01 server spamd[1845]: Failed to run USER_IN_SPF_WHITELIST 
SpamAssassin test, skipping:__(Can't locate object method "c
heck_for_spf_whitelist_from" via package 
"Mail::SpamAssassin::PerMsgStatus" at 
/usr/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/PerM
sgStatus.pm line 2312, GEN3 line 144._)

Version is : SpamAssassin version 3.0.2 running on Perl version 5.8.6
I am using Fedora Core 4 and qmail

I have search for days on this and can't seem to find what's wrong.  Any 
help would be greatly appreciated!

  
  
Run "locate spamd", "locate PerMsgStatus.pm", and resolve the two.  there
should only be one set of SpamAssassin perl modules in your system, and
this almost definitely is not the case, as it's picking up modules that do
not match the rules.

- --j.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Exmh CVS

iD8DBQFDcmEsMJF5cimLx9ARAkDKAJ9FVZuWLhicYL4VH0sd/KSQDzWgdgCfdbkz
jje1pi73zTGyMEthQEBmELg=
=TKzI
-END PGP SIGNATURE-

Re: Can't locate object method

Jeffrey Duncan wrote:
 Okay, so I see that I have two versions of PerMsgStatus.pm (below)
 
 How do I remove one of them to get rid of the issues?
 
 Jeffrey Duncan wrote:
 
 Thanks, 

 What do you mean resolve?  Here is the output ...

  
 [EMAIL PROTECTED] log]# locate PerMsgStatus.pm
 /usr/lib/perl5/site_perl/5.8.6/Mail/SpamAssassin/PerMsgStatus.pm
 /usr/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/PerMsgStatus.pm
 /usr/src/redhat/BUILD/Mail-SpamAssassin-3.1.0/lib/Mail/SpamAssassin/PerMsgStatus.pm
 /usr/src/redhat/BUILD/Mail-SpamAssassin-3.1.0/blib/lib/Mail/SpamAssassin/PerMsgStatus.pm
 /downloads/qmailrocks/perlmods/rpms/newmods/Mail-SpamAssassin-3.1.0/lib/Mail/SpamAssassin/PerMsgStatus.pm
 /downloads/qmailrocks/perlmods/rpms/newmods/Mail-SpamAssassin-3.1.0/blib/lib/Mail/SpamAssassin/PerMsgStatus.pm


I'd assume you installed an older version of SA while you were using perl 5.8.5.
Later you upgraded to 5.8.6 and then installed 3.1.0 sometime afterward.

The 3.1.0 installation did not see the outdated site_perl directory, thus never
removed it.

I'd suggest blowing away the old copy entirely with rm -rf:

rm -rf /usr/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/

then try your SA. If that doesn't fix things, rm -rf both of them and re-install
SA 3.1.0.


While you're at it double-check for duplicate spamd and spamc scripts. That's
less likely but it is possible that one is in /usr/bin and another is in
/usr/local/bin..

Re: Can't locate object method

Thanks,

>From my mail headers I think I am running 3.0.2 - also,

spamc -V
SpamAssassin Client version 3.0.2

I think what happened is that I did a yum update and it broke things.
I tried to rename the 5.8.5 PerMsgStatus and spamd didn't load. I
thinik I have some mix ups here. Should I uninstall SA and start from
scratch? COuld you give me a few pointers on how to get rid of it
gracefully?

Thanks for your help!

Matt Kettler wrote:
Jeffrey Duncan wrote:

Matt Kettler wrote:

Jeffrey Duncan wrote:

Okay, so I see that I have two versions of PerMsgStatus.pm (below)

How do I remove one of them to get rid of the issues?

Jeffrey Duncan wrote:

Thanks,

What do you mean resolve? Here is the output ...

[EMAIL PROTECTED] log]# locate PerMsgStatus.pm
/usr/lib/perl5/site_perl/5.8.6/Mail/SpamAssassin/PerMsgStatus.pm
/usr/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/PerMsgStatus.pm
/usr/src/redhat/BUILD/Mail-SpamAssassin-3.1.0/lib/Mail/SpamAssassin/PerMsgStatus.pm
/usr/src/redhat/BUILD/Mail-SpamAssassin-3.1.0/blib/lib/Mail/SpamAssassin/PerMsgStatus.pm
/downloads/qmailrocks/perlmods/rpms/newmods/Mail-SpamAssassin-3.1.0/lib/Mail/SpamAssassin/PerMsgStatus.pm
/downloads/qmailrocks/perlmods/rpms/newmods/Mail-SpamAssassin-3.1.0/blib/lib/Mail/SpamAssassin/PerMsgStatus.pm

I'd assume you installed an older version of SA while you were using perl 5.8.5.
Later you upgraded to 5.8.6 and then installed 3.1.0 sometime afterward.

The 3.1.0 installation did not see the outdated site_perl directory, thus never
removed it.

I'd suggest blowing away the old copy entirely with rm -rf:

rm -rf /usr/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/

then try your SA. If that doesn't fix things, rm -rf both of them and re-install
SA 3.1.0.

While you're at it double-check for duplicate spamd and spamc scripts. That's
less likely but it is possible that one is in /usr/bin and another is in
/usr/local/bin..

Re: Can't locate object method

Jeffrey Duncan wrote:
 Thanks,
 
From my mail headers I think I am running 3.0.2 - also,
 
 spamc -V
 SpamAssassin Client version 3.0.2
 
 I think what happened is that I did a yum update and it broke things.  I
 tried to rename the 5.8.5 PerMsgStatus and spamd didn't load.  I thinik
 I have some mix ups here.  Should I uninstall SA and start from
 scratch? 

Probably...

 COuld you give me a few pointers on how to get rid of it
 gracefully?
 

I'd first try to use yum remove. At least this will gracefully remove as much
as yum understands.

After that I'd check and see if rpm -qa thinks there's still some kind of SA
package installed and I'd rpm -e any that are left over.

From there, do an updatedb and locate to see what's left over that couldn't be
removed by your package manager and wipe the leftovers out with rm. While this
might sound un-graceful, it's pretty much all you've got.

Suggested locate searches:
locate spamassassin
locate spamc
locate spamd
locate sa-learn
locate SpamAssassin

Make sure you hit pretty much everything in /usr. (ie: /usr/share/spamassassin/,
/usr/lib/perl5/site_perl/*/SpamAssassin, /usr/bin/, /usr/local/bin, etc.)


After you've cleaned out all the SA residue, then try to re-install SA.

Re: Can't locate object method





Thanks! Do I need to remove the 5.8.5 and 5.8.6
perl libraries too?

Matt Kettler wrote:

  Jeffrey Duncan wrote:
  
  
Thanks,

From my mail headers I think I am running 3.0.2 - also,

spamc -V
SpamAssassin Client version 3.0.2

I think what happened is that I did a yum update and it broke things.  I
tried to rename the 5.8.5 PerMsgStatus and spamd didn't load.  I thinik
I have some mix ups here.  Should I uninstall SA and start from
scratch? 

  
  
Probably...

  
  
COuld you give me a few pointers on how to get rid of it
gracefully?


  
  
I'd first try to use "yum remove". At least this will gracefully remove as much
as yum understands.

After that I'd check and see if rpm -qa thinks there's still some kind of SA
package installed and I'd rpm -e any that are left over.

From there, do an updatedb and locate to see what's left over that couldn't be
removed by your package manager and wipe the leftovers out with rm. While this
might sound un-graceful, it's pretty much all you've got.

Suggested locate searches:
locate spamassassin
locate spamc
locate spamd
locate sa-learn
locate SpamAssassin

Make sure you hit pretty much everything in /usr. (ie: /usr/share/spamassassin/,
/usr/lib/perl5/site_perl/*/SpamAssassin, /usr/bin/, /usr/local/bin, etc.)


After you've cleaned out all the SA residue, then try to re-install SA.

Re: Spam, Block: Good to know my representative is spamming..

2005-11-10 Thread Evan Platt


At 12:52 PM 11/9/2005, you wrote:


Woops, should have gone to Spam-L, the anti-spam list.

But.. Good fodder to set up filters for. :)

Evan



Just received quite a rude reply off list, which I did reply to, but 
I'm pretty confident the return address was false.


It was from a Not Here as the name.

The reply was simply (and quoted my Received the below crap in my 
inbox comment:


So did I - from some idiot, who doesn't know how to post to a LIST!!!

Well, not here - first off, my post was intended for SPAM-L, a 
anti-spam list. SPAM-L comes right after SpamAssassin in my address 
book. Honest mistake. I posted the above apology minutes after 
realizing my mistake.


Second off, I'm guessin you were commenting that I was the idiot.

I believe YOU are the idiot (nameless, nonetheless) because you 
DIDN'T receive the spam from me. If you knew how to read, I ONLY 
included the headers.


I cannot locate who this person is, searching on a number of headers, 
but I have their IP information from the e-mail.


Granted, I'm taking it with a very small grain of salt, based on the 
fact that the person doesn't even have the guts to use their name.


Perhaps a simple IQ test prior to allowing people to join this list 
would eliminate these types of people from joining?

Re: HUGE bayes DB (non-sitewide) advice?

2005-11-10 Thread email builder

  Just a follow-up to my own brain-lapse:
  
  If you define a custom user scores query like this:
  
  user_scores_sql_custom_querySELECT preference, value FROM
  spamassassin_settings WHERE username = _USERNAME_ OR username = '!GLOBAL'
 OR
  username = CONCAT('@', _DOMAIN_) ORDER BY username ASC
  
  Then you can easily decide to use bayes on a per-domain basis for one or
 more
  of your domains (and still have per-user bayes for all other domains).  A
  sample insert row into the settings table, then, would be:
  
  INSERT INTO spamassassin_settings (username, preference, value) VALUES
  ('@example.com', 'bayes_sql_override_username', 'example.com');
  
  So everyone in the example.com domain shares all bayes information which
 is
  placed under the username example.com.
 
 is that in the FAQ?  because it certainly sounds like a cool tip for
 Bayes/SQL users.

I don't think so.  One other thing to note about this setup is:

I think I caught the idea of using !GLOBAL from someone's how-to a while back
(IIRC, the manual suggests @GLOBAL), this way the global settings can be
ordered in the query to always override any per-domain settings.
 
 (there should really be a section of the FAQ dedicated to that stuff.)

Would be nice.




__ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com

Re: How to verify SA options being used by spamc from remote host

2005-11-10 Thread Geoff Varney

 Matthew.van.Eerde at hbinc.com writes:

 
 Geoff Varney wrote:
  I start spamd with a -u spamd user.
 ...
  bayes_path /root/.spamassassin
 
 The short answer is, you can tell if bayes is being used because (almost) 
every message will hit a BAYES_XX
 rule for some value of XX.  The exceptions will be messages with blank 
bodies, or which are unsuitable for
 bayes-checking for some other reason.  But even a Bayes-neutral text should 
fire BAYES_50.
 
 That said, there are at least two problems with your bayes_path.
 
 First, it ends in a directory name.  Read the documentation for bayes_path 
to understand why this is
 wrong... it's not really a path, despite the name.  It's a path and a 
filename prefix.  So
 /root/.spamassassin/bayes is more likely to be what you want.
 
 Second, the spamd user likely doesn't have write access 
to /root/.spamassassin/ -- if it does, that's a
 problem.  Make a directory like /etc/mail/spamassassin/bayes/, chown it to 
the spamd user, and set
 bayes_path to /etc/mail/spamassassin/bayes/bayes (note the double bayes 
there)
 

Awesome Matthew!  I was heading down the right path yesterday with this being 
at least in part a permissions issue.  So many things in Linux end up being 
permissions, but not always easy to spot for near-novice Linux users like me.

I did as you suggested and created the new bayes path.  I copied over the 
other (improperly named) database files and renamed them to bayes_? and 
now in the maillog I am seeing bayes_ entries when mail is scanned.

Thanks a lot for your help.  I will monitor and make sure this is working.

Geoff

Help starting service





I installed SA 3.1.0 using the CPAN install
Mail::SpamAssassin method and all went well with no errors. 

I cannot however get the service started. I am using Qmail from the
qmailrocks install. I have removed all my old SA 3.0.2 files and
started fresh. What can I do at this point to make the SA work with
qmail 

J

Re: Help starting service

2005-11-10 Thread Theo Van Dinter

FWIW, it's generally bad form to post HTML-only messages to mailing lists.


On Thu, Nov 10, 2005 at 02:33:37PM -0500, Jeffrey Duncan wrote:

-- 
Randomly Generated Tagline:
If we can't keep this sort of thing out of the kernel, we might as well
 pack it up and go run Solaris. - Larry McVoy


pgpWfM2CVuyJt.pgp
Description: PGP signature

RE: Help starting service

From: Jeffrey Duncan [mailto:[EMAIL PROTECTED]
 
 I installed SA 3.1.0 using the CPAN install Mail::SpamAssassin
 method and all went well with no errors.  
 
 I cannot however get the service started.  I am using Qmail from the
 qmailrocks install.  I have removed all my old SA 3.0.2 files and
 started fresh.  What can I do at this point to make the SA work with
 qmail 

Details please!

How are you trying to start the service?  Do you get any error
messages?  Have you checked the log files?

Bowie

Re: Help starting service

2005-11-10 Thread Mathieu CHATEAU





Hello Jeffrey,

what is your platform ?

You need to install sa-spamd daemon.
qmail-scanner use spamc which then communicate with spamassassin daemon.

cheers,
Mathieu CHATEAU

Thursday, November 10, 2005, 8:33:37 PM, you wrote:

--
Best regards,
Mathieu  mailto:[EMAIL PROTECTED]

Re: Help starting service

Hello.  I am running FC4.  I can start the service on the command line 
by just typing spamd and it all works fine.  Must be something very 
simple - been at this all day !


I have tried to start the service the following ways ...

# service spamassassin start
spamassassin: unrecognized service

and

# /etc/rc.d/init.d/spamassassin start
-bash: /etc/rc.d/init.d/spamassassin: No such file or directory

Thanks for the help.

Jeff



Mathieu CHATEAU wrote:


Hello Jeffrey,


what is your platform ?


You need to install sa-spamd daemon.

qmail-scanner  use spamc which then communicate with spamassassin daemon.


cheers,

Mathieu CHATEAU


Thursday, November 10, 2005, 8:33:37 PM, you wrote:


--

Best regards,

 Mathieumailto:[EMAIL PROTECTED]

Re: Help starting service

Jeffrey Duncan wrote:
 Hello.  I am running FC4.  I can start the service on the command line
 by just typing spamd and it all works fine.  Must be something very
 simple - been at this all day !
 
 I have tried to start the service the following ways ...
 
 # service spamassassin start
 spamassassin: unrecognized service
 
 and
 
 # /etc/rc.d/init.d/spamassassin start
 -bash: /etc/rc.d/init.d/spamassassin: No such file or directory
 

look in /etc/rc.d/init.d and see if theres a spamd service instead of a
spamassassin service.


Also, when you re-installed, how did you re-install?

Re: Help starting service

I installed using cpan Mail::SpamAssassin as listed on SA site.  It's 
working, but it won't start as a service.


neither service is listed in that directory.

Matt Kettler wrote:

Jeffrey Duncan wrote:
  

Hello.  I am running FC4.  I can start the service on the command line
by just typing spamd and it all works fine.  Must be something very
simple - been at this all day !

I have tried to start the service the following ways ...

# service spamassassin start
spamassassin: unrecognized service

and

# /etc/rc.d/init.d/spamassassin start
-bash: /etc/rc.d/init.d/spamassassin: No such file or directory




look in /etc/rc.d/init.d and see if theres a spamd service instead of a
spamassassin service.


Also, when you re-installed, how did you re-install?

Re: Help starting service

Jeffrey Duncan wrote:
 I installed using cpan Mail::SpamAssassin as listed on SA site.  It's
 working, but it won't start as a service.
 
 neither service is listed in that directory.

Ok, if you installed from CPAN, you essentially installed from source.

The source will NOT install a service script.

Service scripts are distribution specific. ie: they differ between Redhat Linux,
suse Linux, Solaris, and freebsd. There is no universal common format for them
that applies to all *nix oses.

The SA source does come with several service scripts you can use, but it doesn't
automatically install them.

Find the redhat-rc-script.sh (probably in /root/.cpan/ somewhere) and copy it
to /etc/rc.d/init.d/spamassassin. That should let you treat SA as a redhatish
service.

RE: Help starting service

From: Jeffrey Duncan [mailto:[EMAIL PROTECTED]
 
 I installed using cpan Mail::SpamAssassin as listed on SA site.  It's 
 working, but it won't start as a service.
 
 neither service is listed in that directory.

I install the same way and I've got an /etc/rc.d/init.d/spamd file to
do the startup.  It's possible I may have written it myself.

Try putting the file listed below into /etc/rc.d/init.d/spamd (or
spamassassin, whichever you prefer).

Bowie




#!/bin/bash
# chkconfig: 2345 30 70
# Description: Daemon for email spam checking
# Startup file for spamd
#

export LC_ALL=C

# source function library
. /etc/init.d/functions

RETVAL=0

start() {
echo -n $Starting SpamAssassin daemon: 
/usr/bin/spamd -d -m 8 --max-conn-per-child=50 -r
/var/run/spamd/spamd.pid
echo
return 0
}

stop() {
echo -n $Stopping SpamAssassin daemon: 
kill `cat /var/run/spamd/spamd.pid`
echo
return 0
}

reload(){
stop
start
}

restart(){
stop
start
}


case $1 in
  start)
start
;;
  stop)
stop
;;
  restart)
restart
;;
  reload)
reload
;;
  *)
echo $Usage: $0 {start|stop|restart|reload}
RETVAL=1
esac

exit $RETVAL

Re: Help starting service


I get the following after creating the script, chmod +x ..

Starting SpamAssassin daemon: [16717] warn: Option r requires an argument
/etc/init.d/spamd: line 17: /var/run/spamd/spamd.pid: No such file or 
directory






Bowie Bailey wrote:

From: Jeffrey Duncan [mailto:[EMAIL PROTECTED]
  
I installed using cpan Mail::SpamAssassin as listed on SA site.  It's 
working, but it won't start as a service.


neither service is listed in that directory.



I install the same way and I've got an /etc/rc.d/init.d/spamd file to
do the startup.  It's possible I may have written it myself.

Try putting the file listed below into /etc/rc.d/init.d/spamd (or
spamassassin, whichever you prefer).

Bowie




#!/bin/bash
# chkconfig: 2345 30 70
# Description: Daemon for email spam checking
# Startup file for spamd
#

export LC_ALL=C

# source function library
. /etc/init.d/functions

RETVAL=0

start() {
echo -n $Starting SpamAssassin daemon: 
/usr/bin/spamd -d -m 8 --max-conn-per-child=50 -r
/var/run/spamd/spamd.pid
echo
return 0
}

stop() {
echo -n $Stopping SpamAssassin daemon: 
kill `cat /var/run/spamd/spamd.pid`
echo
return 0
}

reload(){
stop
start
}

restart(){
stop
start
}


case $1 in
  start)
start
;;
  stop)
stop
;;
  restart)
restart
;;
  reload)
reload
;;
  *)
echo $Usage: $0 {start|stop|restart|reload}
RETVAL=1
esac

exit $RETVAL

RE: Help starting service

From: Jeffrey Duncan [mailto:[EMAIL PROTECTED]
 
 I get the following after creating the script, chmod +x ..
 
 Starting SpamAssassin daemon: [16717] warn: Option r requires an
 argument /etc/init.d/spamd: line 17: /var/run/spamd/spamd.pid: No
 such file or directory

Right... The following should be one line:

  /usr/bin/spamd -d -m 8 --max-conn-per-child=50 -r
/var/run/spamd/spamd.pid

That second line is actually the argument to '-r'.

Bowie

Re: Help starting service


Great I am almost there!  A cpuple more things ...
How do I get it to start on boot?  The same way with chkconfig spamd on ?

and

The STOP fails ..

# service spamd start
Starting SpamAssassin daemon:
# service spamd stop
Stopping SpamAssassin daemon: cat: /var/run/spamd/spamd.pid: No such 
file or directory
kill: usage: kill [-s sigspec | -n signum | -sigspec] [pid | job]... or 
kill -l [sigspec]


Bowie Bailey wrote:

From: Jeffrey Duncan [mailto:[EMAIL PROTECTED]
  

I get the following after creating the script, chmod +x ..

Starting SpamAssassin daemon: [16717] warn: Option r requires an
argument /etc/init.d/spamd: line 17: /var/run/spamd/spamd.pid: No
such file or directory



Right... The following should be one line:

  /usr/bin/spamd -d -m 8 --max-conn-per-child=50 -r
/var/run/spamd/spamd.pid

That second line is actually the argument to '-r'.

Bowie

RE: Help starting service

From: Jeffrey Duncan [mailto:[EMAIL PROTECTED]
 
 Great I am almost there!  A cpuple more things ...
 How do I get it to start on boot?  The same way with 
 chkconfig spamd on ?
 
 and
 
 The STOP fails ..
 
 # service spamd start
 Starting SpamAssassin daemon:
 # service spamd stop
 Stopping SpamAssassin daemon: cat: /var/run/spamd/spamd.pid: No such 
 file or directory
 kill: usage: kill [-s sigspec | -n signum | -sigspec] [pid | 
 job]... or 
 kill -l [sigspec]

The script tries to record the pid in /var/run/spamd/spamd.pid.  If
the directory doesn't exist (or isn't writable), it fails.

What you need to do is create the directory and chown it to the user
spamd runs as.

For example (assuming your spamd user is 'spamscan'):

mkdir /var/run/spamd
chown spamscan /var/run/spamd

The chkconfig information is already in the file.  To get it to run at
startup, simply do this:

chkconfig --add spamd

This will cause it to start in runlevels 2-5.  To change the runlevel
settings, take a look at the man page for chkconfig.  It's very easy
to use.

Bowie

Re: Help starting service