SpamAssassin auf aktuelle Version updaten

Postfix, QMail, Sendmail, Dovecot, Cyrus, Courier, Anti-Spam
fun4teen
Posts: 92
Joined: 2004-06-18 16:11

SpamAssassin auf aktuelle Version updaten

Post by fun4teen » 2006-10-26 13:49

Hi All,

auf meiner Suse 9 kiste läuft das alte SpamAssassin 2.64.

Inzwischen gibt es ja die 3.1.7 Version. Nun wollte ich das alte Updaten, allerdings will das nicht.

Ich ziehe mir die aktuelle Version .. baue aus der tar.gz Datei eine rpm .. und diese möchte ich dann via rpm -i installieren.

Allerdings bekomm ich dann immer diese Fehlermeldungen (auszug):
file /usr/share/spamassassin/50_scores.cf from install of perl-Mail-SpamAssassin-3.1.7-1 conflicts with file from package perl-spamassassin-2.64-3.2
file /usr/share/spamassassin/60_whitelist.cf from install of perl-Mail-SpamAssassin-3.1.7-1 conflicts with file from package perl-spamassassin-2.64-3.2
file /usr/share/spamassassin/user_prefs.template from install of perl-Mail-SpamAssassin-3.1.7-1 conflicts with file from package perl-spamassassin-2.64-3.2
Kann ich das nicht updaten? Er hat wohl probleme solange die alte Version auf dem Server läuft?

Danke

adjustman
Posts: 1132
Joined: 2003-03-26 23:29
Location: SA

Re: SpamAssassin auf aktuelle Version updaten

Post by adjustman » 2006-10-27 00:14

das sieht aber so aus, als ob bloss die *.cf Probleme machen.
Ist auch nicht verwunderlich. 2.64 => 3.1.7 sind Welten.
Kopier die doch manuell nach /usr/share/*
P.S. Warum löscht du nicht per Yast die 2.64 und kompilierst
mit perl Makefile.pl, make, make install?

fun4teen
Posts: 92
Joined: 2004-06-18 16:11

Re: SpamAssassin auf aktuelle Version updaten

Post by fun4teen » 2006-11-12 19:30

Hallo inzwischen läuft eigentlich SpamAss. echt gut, allerdings werden meine mail Logs noch ordentlich mit folgenden Einträgen zugemüllt:
Nov 12 19:16:03 pSERVER spamd[18282]: mkdir /XnirvanaX: Permission denied at /usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin.pm line 1530
Nov 12 19:16:03 pSERVER spamd[18282]: locker: safe_lock: cannot create tmp lockfile /XnirvanaX/.spamassassin/auto-whitelist.lock.pSERVER.pureserver.info.18282 for /XnirvanaX/.spamassassin/auto-whitelist.lock: No such file or directory
Nov 12 19:16:04 pSERVER spamd[18282]: mkdir /XnirvanaX: Permission denied at /usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin.pm line 1530
Nov 12 19:16:06 pSERVER spamd[18282]: mkdir /XnirvanaX: Permission denied at /usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin.pm line 1530
Nov 12 19:16:06 pSERVER spamd[18282]: locker: safe_lock: cannot create tmp lockfile /XnirvanaX/.spamassassin/auto-whitelist.lock.pSERVER.pureserver.info.18282 for /XnirvanaX/.spamassassin/auto-whitelist.lock: No such file or directory
Nov 12 19:16:47 pSERVER spamd[18282]: mkdir /XnirvanaX: Permission denied at /usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin.pm line 1530
Nov 12 19:16:50 pSERVER spamd[18282]: mkdir /XnirvanaX: Permission denied at /usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin.pm line 1530
Nov 12 19:16:50 pSERVER spamd[18282]: locker: safe_lock: cannot create tmp lockfile /XnirvanaX/.spamassassin/auto-whitelist.lock.pSERVER.pureserver.info.18282 for /XnirvanaX/.spamassassin/auto-whitelist.lock: No such file or directory
Nov 12 19:16:50 pSERVER spamd[18282]: bayes: locker: safe_lock: cannot create tmp lockfile /XnirvanaX/.spamassassin/bayes.lock.pSERVER.pureserver.info.18282 for /XnirvanaX/.spamassassin/bayes.lock: No such file or directory
Nov 12 19:16:58 pSERVER spamd[18282]: mkdir /XnirvanaX: Permission denied at /usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin.pm line 1530
Nov 12 19:17:01 pSERVER spamd[18282]: mkdir /XnirvanaX: Permission denied at /usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin.pm line 1530
Nov 12 19:17:01 pSERVER spamd[18282]: locker: safe_lock: cannot create tmp lockfile /XnirvanaX/.spamassassin/auto-whitelist.lock.pSERVER.pureserver.info.18282 for /XnirvanaX/.spamassassin/auto-whitelist.lock: No such file or directory
Nov 12 19:17:12 pSERVER spamd[18282]: mkdir /XnirvanaX: Permission denied at /usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin.pm line 1530
Nov 12 19:17:16 pSERVER spamd[18282]: mkdir /XnirvanaX: Permission denied at /usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin.pm line 1530
Nov 12 19:17:16 pSERVER spamd[18282]: locker: safe_lock: cannot create tmp lockfile /XnirvanaX/.spamassassin/auto-whitelist.lock.pSERVER.pureserver.info.18282 for /XnirvanaX/.spamassassin/auto-whitelist.lock: No such file or directory
Das sieht eigentlich klar nach irgendwelchen Rechte-Probleme bzw. Pfadprobleme aus.

Was soll den dieses XnirvanaX bedeuten? Habe hier im Forum schon danach gesucht, aber nichts entsprechendes finden können.

Danke

adjustman
Posts: 1132
Joined: 2003-03-26 23:29
Location: SA

Re: SpamAssassin auf aktuelle Version updaten

Post by adjustman » 2006-11-13 00:31

fun4teen wrote:Das sieht eigentlich klar nach irgendwelchen Rechte-Probleme bzw. Pfadprobleme aus.
ja
Was soll den dieses XnirvanaX bedeuten?
Ist eine "Eigenart" von Confixx btreffs der Mailboxen

der kleine tux
Posts: 97
Joined: 2005-10-29 04:12
Location: Planet Erde

Re: SpamAssassin auf aktuelle Version updaten

Post by der kleine tux » 2006-11-13 07:42

Morgen,
mit Option -x sollte die Warnung verschwinden
spamd -x
( --nouser-config )
und ohne

Code: Select all

-c, --create-prefs                 Create user preferences files
man spamd
gruss

fun4teen
Posts: 92
Joined: 2004-06-18 16:11

Re: SpamAssassin auf aktuelle Version updaten

Post by fun4teen » 2006-11-13 08:07

Der kleine Tux wrote:Morgen,
mit Option -x sollte die Warnung verschwinden
spamd -x
( --nouser-config )
und ohne

Code: Select all

-c, --create-prefs                 Create user preferences files
man spamd
gruss
Guten Morgen,
das werd ich gleich mal ausprobieren.

fun4teen
Posts: 92
Joined: 2004-06-18 16:11

Re: SpamAssassin auf aktuelle Version updaten

Post by fun4teen » 2006-11-13 08:53

Also irgendwie find ich in dem Script das Ausführen von Spamd nicht.

Kann mir da jemand kurz einen tipp nennen wo ich das -x hinzufügen muss?

Danke
#opyright (c) 1995-2002 SuSE Linux AG, Nuernberg, Germany.
# All rights reserved.
#
# Author: Christian Banik
#
# /etc/init.d/spamd
#
# and symbolic its link
#
# /usr/sbin/rcspamd
#
# LSB compliant service control script; see http://www.linuxbase.org/spec/
#
# System startup script for daemon spamd (written for SuSE Linux 8.0)
#
### BEGIN INIT INFO
# Provides: spamassassin daemon
# Required-Start: $remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Default-Start: 3 5
# Default-Stop: 0 1 2 6
# Description: Start spamd to allow filtering of incoming mail
# for spam.
#
### END INIT INFO
#
# Note on Required-Start: It does specify the init script ordering,
# not real dependencies. Depencies have to be handled by admin
# resp. the configuration tools (s)he uses.

# Source SuSE config (if still necessary, most info has been moved)
test -r /etc/rc.config && . /etc/rc.config

# Check for missing binaries (stale symlinks should not happen)
SPAMD_BIN=/usr/bin/spamd
test -x $SPAMD_BIN || exit 5

# Shell functions sourced from /etc/rc.status:
# rc_check check and set local and overall rc status
# rc_status check and set local and overall rc status
# rc_status -v ditto but be verbose in local rc status
# rc_status -v -r ditto and clear the local rc status
# rc_failed set local and overall rc status to failed
# rc_failed set local and overall rc status to
# rc_reset clear local rc status (overall remains)
# rc_exit exit appropriate to overall rc status
# rc_active checks whether a service is activated by symlinks
. /etc/rc.status

# First reset status of this service
rc_reset

# Return values acc. to LSB for all commands but status:
# 0 - success
# 1 - generic or unspecified error
# 2 - invalid or excess argument(s)
# 3 - unimplemented feature (e.g. "reload")
# 4 - insufficient privilege
# 5 - program is not installed
# 6 - program is not configured
# 7 - program is not running
#
# Note that starting an already running service, stopping
# or restarting a not-running service as well as the restart
# with force-reload (in case signalling is not supported) are
# considered a success.

case "$1" in
start)
echo -n "Starting spamassassin daemon (spamd)"
## Start daemon with startproc(8). If this fails
## the echo return value is set appropriate.

# NOTE: startproc returns 0, even if service is
# already running to match LSB spec.
startproc $SPAMD_BIN
touch /var/lock/spamd

# Remember status and be verbose
rc_status -v
;;
stop)
echo -n "Shutting down spamassassin daemon (spamd)"
## Stop daemon with killproc(8) and if this fails
## set echo the echo return value.

killproc $SPAMD_BIN
rm -f /var/lock/spamd

# Remember status and be verbose
rc_status -v
;;
restart)
## Stop the service and regardless of whether it was
## running or not, start it again.
$0 stop
$0 start

# Remember status and be quiet
rc_status
;;
status)
echo -n "Checking for spamassassin daemon (spamd): "
## Check status with checkproc(8), if process is running
## checkproc will return with exit status 0.

# Return value is slightly different for the status command:
# 0 - service running
# 1 - service dead, but /var/run/ pid file exists
# 2 - service dead, but /var/lock/ lock file exists
# 3 - service not running

# NOTE: checkproc returns LSB compliant status values.
checkproc $SPAMD_BIN
rc_status -v
;;
*)
echo "Usage: $0 {start|stop|restart|status|}"
exit 1
;;
esac
rc_exit
#EOF - Startscript

der kleine tux
Posts: 97
Joined: 2005-10-29 04:12
Location: Planet Erde

Re: SpamAssassin auf aktuelle Version updaten

Post by der kleine tux » 2006-11-13 09:06

unter Debian ist es in
/etc/default/spamassassin

Code: Select all

cat /etc/default/spamassassin
# /etc/default/spamassassin
# Duncan Findlay

# WARNING: please read README.spamd before using.
# There may be security risks.

# Change to one to enable spamd
ENABLED=0

# Options
# See man spamd for possible options. The -d option is automatically added.

# NOTE: version 3.0.x has switched to a "preforking" model, so you
# need to make sure --max-children is not set to anything higher than
# 5, unless you know what you're doing.

OPTIONS="--create-prefs --max-children 3 --helper-home-dir"

# Pid file
# Where should spamd write its PID to file? If you use the -u or
# --username option above, this needs to be writable by that user.
# Otherwise, the init script will not be able to shut spamd down.
PIDFILE="/var/run/spamd.pid"

# Set nice level of spamd
#NICE="--nicelevel 15"
gruss