S
satch89450
Guest
I'm currently running PSA 7.0.3 and 7.0.4 on Red Hat 7.3 and Red Hat 9.0 boxes. I've been looking at what it would take to rebuild my servers to Fedora Core 2 or 3 and Plesk 7.5.1 and migrate accounts.
1. What migration tools exist?
2. Has Plesk modified their RPMs and published a repository that is accessible and usable to Yum? (I know that atomicrocketturtle has done something like this.)
3. What resource management/control tools has Plesk added to PSA? Do Web Apps still take over the server? Can incoming mail make even 1-GB RAM systems start thrashing?
4. Has Plesk fixed their QMail/SpamAssassin problem, where they send mail through SpamAssassin first and *then* find out there's no room for mail in the receipent's mailbox?
5. How about the "delete-spam" option -- does that work now?
6. Is there any way for SMTP-authenticated sessions to bypass blocklisting checks?
7. Is there any marker as to which SMTP-authenticated user submitted mail to the system, in case they are spamming through their account?
8. Indeed, has Plesk provided for a mail agent other than QMail, such as Exim or PostFix?
9. Is phpsuexec supported?
10. What spam tracing tools does Plesk provide with their bundled QMail?
11. Outbound mail rate limiting from Web sites?
12. Serialization of mail so that you don't have 30 connections to Yahoo at the same time, to the detriment of everyone else?
13. Plesk apparently bundles everything for a Web hosting appliance *except* Apache and PHP/Zend for Web sites. (They bundle PHP for thier own control panel.) Has Plesk isolated their changes in modules that conform to the Apache 2.0.x and 2.1.x API, so that any other modules supplied by Apache or any third party may be added and updated with impunity?
14. Has anyone successfully taken PSA 7.5.1 servers above the 300-domain mark in a commercial Web hosting environment?
The PHP 4.3.10 flap is making me consider this path.
1. What migration tools exist?
2. Has Plesk modified their RPMs and published a repository that is accessible and usable to Yum? (I know that atomicrocketturtle has done something like this.)
3. What resource management/control tools has Plesk added to PSA? Do Web Apps still take over the server? Can incoming mail make even 1-GB RAM systems start thrashing?
4. Has Plesk fixed their QMail/SpamAssassin problem, where they send mail through SpamAssassin first and *then* find out there's no room for mail in the receipent's mailbox?
5. How about the "delete-spam" option -- does that work now?
6. Is there any way for SMTP-authenticated sessions to bypass blocklisting checks?
7. Is there any marker as to which SMTP-authenticated user submitted mail to the system, in case they are spamming through their account?
8. Indeed, has Plesk provided for a mail agent other than QMail, such as Exim or PostFix?
9. Is phpsuexec supported?
10. What spam tracing tools does Plesk provide with their bundled QMail?
11. Outbound mail rate limiting from Web sites?
12. Serialization of mail so that you don't have 30 connections to Yahoo at the same time, to the detriment of everyone else?
13. Plesk apparently bundles everything for a Web hosting appliance *except* Apache and PHP/Zend for Web sites. (They bundle PHP for thier own control panel.) Has Plesk isolated their changes in modules that conform to the Apache 2.0.x and 2.1.x API, so that any other modules supplied by Apache or any third party may be added and updated with impunity?
14. Has anyone successfully taken PSA 7.5.1 servers above the 300-domain mark in a commercial Web hosting environment?
The PHP 4.3.10 flap is making me consider this path.