Topic: Problem with spam-filter after upgrade to SME 7.2

[tiwang]

Hi out there
I have upgraded my SME Server 6.01 to 7.2 without many problems. My installtion of 6.01 was updated with Swerts-Knudsens spamassasin installer - and here my problems probably starts. The upgrade run through but I probably now have two spamsassin packages installed - when I here afterwards try to upgrade the server with "yum update" I get this error:

--> Processing Dependency: perl(Net::Daemon::Log) for package: perl-PlRPC
--> Processing Conflict: sme-spamfilter conflicts e-smith-spamassassin
--> Processing Dependency: perl(Net::Daemon) for package: perl-PlRPC
--> Processing Dependency: perl(Net::Daemon::Test) for package: perl-PlRPC
--> Restarting Dependency Resolution with new changes.
--> Populating transaction set with selected packages. Please wait.
---> Downloading header for perl-Net-Daemon to pack into transaction set.
perl-Net-Daemon-0.43-1.el 100% |=========================| 3.4 kB    00:00
---> Package perl-Net-Daemon.noarch 0:0.43-1.el4.rf set to be updated
--> Running transaction check
--> Processing Conflict: sme-spamfilter conflicts e-smith-spamassassin
--> Finished Dependency Resolution
Error: sme-spamfilter conflicts with e-smith-spamassassin
================================================================
No new rpms were installed. No additional commands are required.
================================================================

So - hmm - anyone out there with suggestions of how to correct this?

best regards /ti

[shell]

Hi tiwang,

I have a clean 7.2 system here and they only have smeserver-spamassassin and spamassassin installed.

Code: [Select]

rpm -qa *spam*
smeserver-spamassassin-1.4.0-16.el4.sme
spamassassin-3.2.3-44.el4

so you could try uninstalling the sme-spamfilter -

Code: [Select]

rpm -e sme-spamfilter
cheers, shell

[tiwang]

Hi Shell

looks as this solved the problem - I didn't dare just to remove it becuase i didn't know which of them was "the old one"

thanks a lot - ti

[tiwang]

BTW - it seems that I got more that one instance of the spamd forked:
sme1 qpsmtpd: Starting qpsmtpd succeeded
Dec  4 08:59:14 sme1 spamd: [3818] warn: server socket setup failed, retry 1: spamd: could not create INET socket on 127.0.0.1:783: Address already in use
Dec  4 08:59:15 sme1 spamd: [3818] warn: server socket setup failed, retry 2: spamd: could not create INET socket on 127.0.0.1:783: Address already in use
Dec  4 08:59:16 sme1 spamd: [3818] error: spamd: could not create INET socket on 127.0.0.1:783: Address already in use
Dec  4 08:59:16 sme1 spamd: spamd: could not create INET socket on 127.0.0.1:783: Address already in use
Dec  4 08:59:16 sme1 spamassassin: spamd startup failed
Dec  4 08:59:18 sme1 sqpsmtpd: Starting sqpsmtpd succeeded

but I have spamd running so there must be more start-up scripts for spamd (the logfile here is after reboot where I have removed the old installation of spam-assasin from Swert-Knudsen and run a full update. Your - or others - logfiles doesn't look similary - or?

best regards /ti