Re: [SAtalk] Problem with spamd as non-root user

2003-06-18 Thread Kim Bisgaard
Hi Theo,

Tanks for your help! You where correct that it was due to old rule files 
from the prior installation of SA.

Regards,
Kim.
On Tue, Jun 17, 2003 at 02:45:26PM +0200, Kim Bisgaard wrote:
 

I am trying to run spamd a non-root user. I am using global SA 
filtering, and run both spamd and spamc as the same user.

The problem is that I get a log of errors in the log and I do not know 
what I have done to get them there (I am not a Perl expert!). First I 
get a lot of errors when I start spamd (Only the start and end shown 
here - there are a lot!):
   

You have a whole bunch of old (assuming you're running a newer version
of SA) config options.  My guess is that you have some ancient config
files hanging around somewhere.  Then you have a bunch of errors that
indicate old modules.
So I recommend going around, blow away any SA-related files, then
reinstall.
 

--
Kim Bisgaard
Oersted Science Data Center
Solar-Terrestrial Physics Division   Phone: +45 3915 7495 (direct)
Danish Meteorological Institute  Fax: +45 3915 7460 (division)
http://www.dmi.dk/solar-terrestrial/ -- Division homepage
http://www.dmi.dk/projects/oersted/  -- Oersted Satellite
http://www.dmi.dk/projects/wdcc1/-- WDC C1 for geo-magnetism
 These are our official Web addresses - ignore any change in the server name
 which may occur while browsing this site. Unfortunately, these pages are
 not reachable via links from the main institute pages - http://www.dmi.dk




---
This SF.Net email is sponsored by: INetU
Attention Web Developers  Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
___
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk


Re: [SAtalk] Problem with spamd as non-root user

2003-06-18 Thread Kim Bisgaard
Hi Michael,

Tanks for your help!

I took your advice and raised the port number, and it helped but not on 
the problems I reported in this thread. These problems seemed to be old 
rule files from the prior installation of SA.

The reason for running SA as a non-root was to have a home dir. with all 
the config files in one place, and not so much security.

regards,
Kim.
First, you will have to change the port spamd uses since only root
accounts can attach to port numbers  1024.
Second, check the rights to ALL the spamassassin files.  Spamd must be
able to read, and sometimes write to all the configs, databases, etc.
Third...  Oh, forget it.  Just run spamd as root and use iptables to
only allow access to port 783 from 127.0.0.1 and you're about as secure
as you're going to get.
My $0.02.

-Michael

 

Kim Bisgaard [EMAIL PROTECTED] 06/17/03 07:45AM 
   

Hi,

I am trying to run spamd a non-root user. I am using global SA 
filtering, and run both spamd and spamc as the same user.

The problem is that I get a log of errors in the log and I do not know

what I have done to get them there (I am not a Perl expert!). First I 
get a lot of errors when I start spamd (Only the start and end shown 
here - there are a lot!):
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in

SpamAssassin configuration, skipping: auto_report_threshold   30
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in
SpamAssassin configuration, skipping: spamphrase_highest_score 38220
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in
SpamAssassin configuration, skipping: spamphrase 38220 temple kiff
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in
SpamAssassin configuration, skipping: spamphrase 36580 kathmandu
temple
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in
SpamAssassin configuration, skipping: spamphrase 35770 million mails
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in
SpamAssassin configuration, skipping: spamphrase 35710 subject remove
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in
SpamAssassin configuration, skipping: spamphrase 33060 further
mailings
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in
SpamAssassin configuration, skipping: spamphrase 29530 seventh heaven
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in
SpamAssassin configuration, skipping: spamphrase 28870 profiled
companies
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in
SpamAssassin configuration, skipping: spamphrase 28270 removeyou com
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in
SpamAssassin configuration, skipping: spamphrase 28230 mailings please
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in
SpamAssassin configuration, skipping: spamphrase 26350 never receive
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in
SpamAssassin configuration, skipping: spamphrase 16553 click here
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in
SpamAssassin configuration, skipping: spamphrase 9903 removed from
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in
SpamAssassin configuration, skipping: spamphrase 9793 that you
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in
SpamAssassin configuration, skipping: spamphrase 9791 you not
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in
SpamAssassin configuration, skipping: spamphrase 8401 for your
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in
SpamAssassin configuration, skipping: spamphrase 8294 from our
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in
SpamAssassin configuration, skipping: spamphrase 8113 credit card
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in
SpamAssassin configuration, skipping: spamphrase 7509 the internet
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in
SpamAssassin configuration, skipping: spamphrase 7237 help you
Jun 16 14:16:43 postoffice spamd[7763]: Failed to run BALANCE_FOR_LONG
SpamAssassin test, skipping: ^I(Can't locate object method 
check_for_very_long_text via pack
age Mail::SpamAssassin::PerMsgStatus (perhaps you forgot to load 
Mail::SpamAssassin::PerMsgStatus?) at 
/usr/local/share/perl/5.6.1/Mail/SpamAssassin/PerMsgStatus
.pm line 2086. )
Jun 16 14:16:43 postoffice spamd[7763]: debug: running raw-body-text 
per-line regexp tests; score so far=0.8
Jun 16 14:16:43 postoffice spamd[7763]: debug: running uri tests; score

so far=0.4
Jun 16 14:16:43 postoffice spamd[7763]: debug: uri tests: Done uriRE
Jun 16 14:16:43 postoffice spamd[7763]: Bareword found where operator 
expected at /usr/share/spamassassin/20_uri_tests.cf, rule DAILY_PL,
line 
11, near 25FREEMEGS_U
RL_uri_test
Jun 16 14:16:43 postoffice spamd[7763]: ^I(Missing operator 

Re: [SAtalk] Problem with spamd as non-root user

2003-06-17 Thread Theo Van Dinter
On Tue, Jun 17, 2003 at 02:45:26PM +0200, Kim Bisgaard wrote:
 I am trying to run spamd a non-root user. I am using global SA 
 filtering, and run both spamd and spamc as the same user.
 
 The problem is that I get a log of errors in the log and I do not know 
 what I have done to get them there (I am not a Perl expert!). First I 
 get a lot of errors when I start spamd (Only the start and end shown 
 here - there are a lot!):

You have a whole bunch of old (assuming you're running a newer version
of SA) config options.  My guess is that you have some ancient config
files hanging around somewhere.  Then you have a bunch of errors that
indicate old modules.

So I recommend going around, blow away any SA-related files, then
reinstall.

-- 
Randomly Generated Tagline:
Always be sincere, even if you don't mean it.


pgp0.pgp
Description: PGP signature


Re: [SAtalk] Problem with spamd as non-root user

2003-06-17 Thread Michael Weber
First, you will have to change the port spamd uses since only root
accounts can attach to port numbers  1024.

Second, check the rights to ALL the spamassassin files.  Spamd must be
able to read, and sometimes write to all the configs, databases, etc.

Third...  Oh, forget it.  Just run spamd as root and use iptables to
only allow access to port 783 from 127.0.0.1 and you're about as secure
as you're going to get.

My $0.02.

-Michael

 Kim Bisgaard [EMAIL PROTECTED] 06/17/03 07:45AM 
Hi,

I am trying to run spamd a non-root user. I am using global SA 
filtering, and run both spamd and spamc as the same user.

The problem is that I get a log of errors in the log and I do not know

what I have done to get them there (I am not a Perl expert!). First I 
get a lot of errors when I start spamd (Only the start and end shown 
here - there are a lot!):
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in

SpamAssassin configuration, skipping: auto_report_threshold   30
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in

SpamAssassin configuration, skipping: spamphrase_highest_score 38220
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in

SpamAssassin configuration, skipping: spamphrase 38220 temple kiff
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in

SpamAssassin configuration, skipping: spamphrase 36580 kathmandu
temple
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in

SpamAssassin configuration, skipping: spamphrase 35770 million mails
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in

SpamAssassin configuration, skipping: spamphrase 35710 subject remove
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in

SpamAssassin configuration, skipping: spamphrase 33060 further
mailings
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in

SpamAssassin configuration, skipping: spamphrase 29530 seventh heaven
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in

SpamAssassin configuration, skipping: spamphrase 28870 profiled
companies
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in

SpamAssassin configuration, skipping: spamphrase 28270 removeyou com
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in

SpamAssassin configuration, skipping: spamphrase 28230 mailings please
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in

SpamAssassin configuration, skipping: spamphrase 26350 never receive
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in

SpamAssassin configuration, skipping: spamphrase 16553 click here
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in

SpamAssassin configuration, skipping: spamphrase 9903 removed from
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in

SpamAssassin configuration, skipping: spamphrase 9793 that you
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in

SpamAssassin configuration, skipping: spamphrase 9791 you not
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in

SpamAssassin configuration, skipping: spamphrase 8401 for your
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in

SpamAssassin configuration, skipping: spamphrase 8294 from our
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in

SpamAssassin configuration, skipping: spamphrase 8113 credit card
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in

SpamAssassin configuration, skipping: spamphrase 7509 the internet
Jun 16 14:16:43 postoffice spamd[7763]: debug: Failed to parse line in

SpamAssassin configuration, skipping: spamphrase 7237 help you
Jun 16 14:16:43 postoffice spamd[7763]: Failed to run BALANCE_FOR_LONG

SpamAssassin test, skipping: ^I(Can't locate object method 
check_for_very_long_text via pack
age Mail::SpamAssassin::PerMsgStatus (perhaps you forgot to load 
Mail::SpamAssassin::PerMsgStatus?) at 
/usr/local/share/perl/5.6.1/Mail/SpamAssassin/PerMsgStatus
.pm line 2086. )
Jun 16 14:16:43 postoffice spamd[7763]: debug: running raw-body-text 
per-line regexp tests; score so far=0.8
Jun 16 14:16:43 postoffice spamd[7763]: debug: running uri tests; score

so far=0.4
Jun 16 14:16:43 postoffice spamd[7763]: debug: uri tests: Done uriRE
Jun 16 14:16:43 postoffice spamd[7763]: Bareword found where operator 
expected at /usr/share/spamassassin/20_uri_tests.cf, rule DAILY_PL,
line 
11, near 25FREEMEGS_U
RL_uri_test
Jun 16 14:16:43 postoffice spamd[7763]: ^I(Missing operator before 
FREEMEGS_URL_uri_test?)
Jun 16 14:16:43 postoffice spamd[7763]: Bareword found where operator 
expected at /usr/share/spamassassin/20_uri_tests.cf, rule 
E_MAILPROMO_URL, line 172, near 25FR
EEMEGS_URL_uri_test
Jun 16 14:16:43 postoffice spamd[7763]: ^I(Missing operator before 
FREEMEGS_URL_uri_test?)
Jun 16 14:16:43 postoffice spamd[7763]: Failed to