1 |
Grant wrote: |
2 |
>>> Does anyone know of a good (or OK) webmail client in portage that |
3 |
>>> doesn't use PHP? I use squirrelmail now but I have PHP installed only |
4 |
>>> for that and I think PHP slows apache2 down a bit. |
5 |
>>> |
6 |
>>> - Grant |
7 |
>>> |
8 |
>> I don't think you'll find anything faster except maybe written in C, which |
9 |
>> is doubtful. The only other language you might find webmail written in is |
10 |
>> Perl/CGI and that is definitely not faster in my experience. PHP is about as |
11 |
>> good as you will get IMHO. |
12 |
> |
13 |
> I actually don't mean to speed up squirrelmail and PHP. The main |
14 |
> function of that system is to run a website in perl, and I thought I |
15 |
> might be bogging down apache2 a bit just by opening it up to PHP |
16 |
> interpretation (-D PHP). Is that the case? It would also be nice not |
17 |
> to be exposed to PHP exploits. It just seems kind of silly to |
18 |
> maintain and run PHP just for webmail. |
19 |
> |
20 |
> - Grant |
21 |
> |
22 |
|
23 |
Adding -D PHP makes your memory footprint larger, but unless you're |
24 |
actually using PHP that's the only side affect of loading it. If you're |
25 |
concerned about security, make sure you're using the sushosin USE |
26 |
variable and keeping PHP and Squirrelmail up to date. Regardless of |
27 |
which language or mail package you use you're going to have to keep them |
28 |
updated. |
29 |
|
30 |
One other thing to think about is whether or not finding a Perl webmail |
31 |
system is going to make your life any easier. Say you do find one and it |
32 |
installs a ton of Perl modules like all Perl applications. Some of those |
33 |
will be updates of Perl modules that your actual site depends on which |
34 |
may or may not break the site. Now you've got two applications to QA |
35 |
when you update any Perl module that is a dependency of both. |
36 |
|
37 |
kashani |