• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Installing spamassassin with PHP5 (CentOS package on RHEL4)

W

woodzie

Guest
Hi,

I have installed PHP5 on one Plesk RHEL4 server using the CentOS4 PHP5 packages. I've been running this for quite some time and everything appears to work correctly. However, when I try to install the SpamAssassin module, I get a "blacklist" error, due to a missing php-domxml dependency. I believe the package name was changed to php-xml in PHP5.

Is there any way to ingore certain dependencies when performing a module install?

I've tried running the commandline autoinstaller app, but there doesn't appear to be any commandline options that would help.

One solution I was thinking of is to download the psa-spamassassin RPM and install using RPM, ignoring the php-domxml dependency. Does anyone know how I can accomplish this?

Thanks in advance,
Darryl
 
Do you have php-xml (the PHP 5 version) installed? I believe it should provide php-domxml, so there should be no problem.
 
Installing spamassassin with PHP5 (CentOS package on RHEL4) [solved]

Hi,

I'm pretty sure I had the php-xml package installed, as many of the sites are using that functionality.

I ended up solving my problem by adding the Atomic Rocket Turtle Yum repository to my up2date sources, and doing a "up2date -u".

That pulled the more Plesk-compatible PHP5 packages from there, which replaced the CentOS4 ones. This went smoothly with no problems. In the process, I also upgrade Plesk from 8.0.0 to 8.1.0. The only hiccup there was that some domains started showing the Redhat Test Page. Once I added the DirectoryIndex in the vhost.conf for the affected domains, everything was fine.

Thanks for the reply.

Darryl
 
Back
Top