• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Squirrelmail?

R

Ronny

Guest
I have seen a bunch of threads but not a single one telling you how to install it or where to access. I have installed ART squirrelmail, but still can't access it with webmail.domain.com or domain.com/webmail or domain.com/squirrelmail
 
It's webmail.domain.com but it'll not work if you're running Plesk7.5.3 (that's an assumption as Horde location changed in Plesk753) ... if not Plesk753 ensure you've restarted apache first.
 
In Plesk 7.1.x, you could simply pop it into /home/httpd/vhosts/webmail/httpdocs and it would like a champ. I'm running Plesk 7.5.3, and this is no longer the case. With that said, it's still possible to get it working...

You'll need to download the latest Squrrelmail from their site (v1.4.4 I think) and expand it somewhere on your machine (say /usr/local/webmail/squirrelmail-1.4.4). Lock down permissions on the file as restrictive as you can get away with (see the install guide for SM for more info). Also create a directory for data and attachments (these would be writable by the WebServer), so you could use (/usr/local/webmail/squirrelmail-tmp/data and attach). Set permissions on those properly too.

Once you have squirrelmail out there, use the configure script to set your Squirrelmail installation up. See the SM docs for that too, it's pretty easy.

Now edit your httpd.include file (think it's /etc/httpd/conf/httpd.include) and look for the 'webmail' Virtual Hosts on 80 and 443. You'll see an alias in each one for /horde and /imp... Just create a new alias called squirrelmail (or whatever you want), and configure it to point at the path you deployed to above.

Once all that is done, restart httpd (/etc/init.d/httpd restart) and try hitting squirrelmail...

That's all off the top, so please forgive any typo'd paths. If you're having issues, I can fill in the gaps when I get back to the house (and my machine).

Joe
 
Nevermind that previous post. Works fine until Plesk rebuilds the httpd.include file (adding a new domain, etc). Then it gets scrubbed...

Back to the drawing board. I'll let you know if I come up with anything...

Joe
 
Alright, I think I have it this time... It's a bit of an extreme fix I'm sure, but it works (so far)...

I ended up writing a 'wrapper' script for websrvmng in /usr/local/psa/admin/sbin... The wrapper calls the original websrvmng (renamed to websrvmng.plesk), and then calls a script I wrote to parse httpd.include and put my entries back in.

Man, I wish Plesk would refer to editable templates... This would be so much easier!

Joe
 
my squirrelmail rpm places a config file in /etc/httpd/conf.d/squirrelmail.conf, which sets the following:

Alias /webmail /usr/share/squirrelmail

In order to replace horde with squirrelmail you I believe you would add an Alias:

Alias /horde /usr/share/squirrelmail

This was in fact the old behavior of the rpm when perlboy first created the package. If your system has this file, and it's not parsing it for some reason, then I'd say the problem is elsewhere in your configs, its probably not an internal issue with apache itself.
 
In my situation, I have some users who prefer Horde while others prefer Squirrelmail. I wanted to provide both with a pretty little page to let them choose :)...

It's all good. Works so far!

Joe
 
Back
Top