spamassassin vs. psa-spamassassin

manarak · Unread post by **manarak** » Wed Oct 19, 2005 5:42 am

I'd be very interested to know a solution for this problem.
Please tell me what to do, I am too inexperienced to take this decision on my own.

tabacco · Unread post by **tabacco** » Wed Oct 19, 2005 11:17 am

manarak wrote:I'd be very interested to know a solution for this problem.
Please tell me what to do, I am too inexperienced to take this decision on my own.

Yeesh... calm down. You only need to post once.

manarak · Unread post by **manarak** » Wed Oct 19, 2005 11:49 am

sorry - I guess I am a bit anxious

hegebutt · Unread post by **hegebutt** » Thu Oct 20, 2005 9:31 pm

I guess I'm a bit anxious too. So I decided to remove psa-spamassassin and then try updating spamassassin. That worked.

Then I installed psa-spamassassin. Here's what it said:

I will do the following:
[install: psa-spamassassin 7.5.4.rhel3.build75050824.12.i586]
Downloading Packages
Running test transaction:
Test transaction complete, Success!
psa-spamassassin 100 % done 1/1
[11232] error: persistent_udp: no such method at /usr/lib/perl5/vendor_perl/5.8.0/Mail/SpamAssassin/DnsResolver.pm line 99
[11296] error: persistent_udp: no such method at /usr/lib/perl5/vendor_perl/5.8.0/Mail/SpamAssassin/DnsResolver.pm line 99
Starting psa-spamassassin service: [ OK ]
Installed: psa-spamassassin 7.5.4.rhel3.build75050824.12.i586
Transaction(s) Complete

It seems to be working in Plesk. Just did this so I'm not sure if it's tagging mail yet.

Should I be worried about those errors?

tabacco · Unread post by **tabacco** » Thu Oct 20, 2005 10:42 pm

I got the same errors. We'll see, I guess

Unread post by **scott** » Fri Oct 21, 2005 7:48 am

those look harmless, psa-spamassassin doesnt really do anything with scanning. It just sets up config files.

manarak · Unread post by **manarak** » Fri Oct 21, 2005 9:40 am

what are the commands to remove psa-spamassassin and to update spamassassin (which version BTW, ART or PSA?)
sorry, still learning linux.

Unread post by **scott** » Fri Oct 21, 2005 9:47 am

spamassassin is the actual content anti-spam scanning engine, psa-spamassassin is just a front end for configuring spamassassin configuration files. You dont actually need psa-spamassassin if you are using qmail-scanner.

In order to update spamassassin, assuming you have the [atomic] archive, just run: yum update, no other special procedures are required.

hegebutt · Unread post by **hegebutt** » Sat Oct 22, 2005 10:47 am

Well, since I removed psa-spamassassin and then upgraded spamassassin (and then installed psa-spamassassin), it has not been marking spam. I removed them both again, and only installed spamassassin.

When I execute spamassassin --lint I get the following:

[2422] warn: dns: Net::DNS version is 0.31, but need 0.34 at /usr/lib/perl5/vendor_perl/5.8.0/Mail/SpamAssassin/Dns.pm line 589

Does this mean anything to anyone?

tabacco: Did you get SA working?

tabacco · Unread post by **tabacco** » Sat Oct 22, 2005 12:08 pm

Doesn't look like it's marking spam here either. I just tried downgrading to SA 3.0.4 and there were no errors this time. I'll keep you posted on how that works out.

hegebutt · Unread post by **hegebutt** » Sat Oct 22, 2005 1:15 pm

After I removed psa-spamassassin and spamassassin, I started to get blank emails. I checked the mail log an it said usr/local/psa/bin/psa-spamc does not exist, which is true.

I installed spamassassin and I still got the log error. Then I tried installing psa-spamassassin, and now I'm getting the conflict again, whereas before I was able to do this, with the errors noted in one of my previous posts.

I checked the sw-soft forums for the blank email issue, and found a post, but it didn't help.
http://forum.sw-soft.com/showthread.php ... blank+mail

Getting blank emails kind of sucks. And my clients agree. Any ideas?

Unread post by **scott** » Sat Oct 22, 2005 2:38 pm

Cant really give you guys any help here, I use qmail-scanner rather than psa-spamassassin

manarak · Unread post by **manarak** » Mon Oct 24, 2005 6:39 am

My problems became worse:

(I posted the following on the SW-Soft forum already, I cannot access the admin panel anymore, I would be very happy if someone could help me getting my plesk-box up and running again.)

I tried to upgrade my PSA 7.5.3 from ART to 7.5.4 through the updater.

The upgrade gave some errors:

quote:
--------------------------------------------------------------------------------
Preparing for packages installation...
----- begin of output -----
Installing /PSA_7.5.3/rpm_FedoraCore_2/opt/mail/perl-Text-Iconv-1.2-21.i586.rpm
Installing /PSA_7.5.3/rpm_FedoraCore_2/opt/mail/psa-spamassassin-7.5.3-fc2.build75050506.13.i586.rpm
error: Failed dependencies:
psa-spamassassin conflicts with spamassassin-3.1.0-1.rhfc2.art

----- end of output -----
===> Autoinstaller: stopped logging at Sun Oct 16 09:59:54 2005
--------------------------------------------------------------------------------

At this time, the errors in the Plesk panel began:

quote:
--------------------------------------------------------------------------------
The file loger.php is part of Plesk distribution. It cannot be run outside of Plesk environment.
--------------------------------------------------------------------------------
But somehow, the pages did still show after a reload of the page.

And I could not upgrade.

I then removed spamassassin through yum remove spamassassin.

Then I tried upgrading PSA to 7.5.4 through the updater.

Since then, I cannot login anymore to the control panel, the error message always says:

quote:
--------------------------------------------------------------------------------
The file constants.php3 is part of Plesk distribution. It cannot be run outside of Plesk environment.
--------------------------------------------------------------------------------

Can anyone help me getting these problems solved?
-> restore access to admin panel
-> upgrade Plesk to 7.5.4 proper?

Thank you

hegebutt · Unread post by **hegebutt** » Mon Oct 24, 2005 9:09 am

I've found the Plesk Updater to be buggy. And it doesn't work with 7.5.4 with a virtual dedicated server (Virtuozzo). Not sure if that's what you've got. I had similar problems when I tried to upgrade through the updater, after which I used yum.

I'm not the most experienced person here, so I'm not sure you should follow my advice, but you might want to remove psa through yum and then reinstall it.

There's probably some advice in the sw-soft forums. That's what I used when I ran into problems.

Unread post by **scott** » Mon Oct 24, 2005 9:25 am

Ive never seen that one before either, you might have to restore from a backup.