Migrating to ISPConfig - step by step (postfixadmin + Anti-Spam-Solution + roundcube)
I've installed ispConfig 220.127.116.11 an it's working great for me. Because I had to install it on an existing server environment I decided to take it step by step. The Webserver configuration worked fine and is up and running.
Now it's time to move the email-stuff. Existing environment:
- Postfixadmin is (still) in use
- Spamassassin up & running
- sieve up & running
- Roundcube (v 0.52)
This caused a major headache, but I was able to get the data from postfixadmin over to the ispconfig db. And here is my first question:
Postfixadmin used md5 password encryption whereas ispconfig used something else.
Modified Line 84: Encryption set to md5
My target is to preserve the user Passwords.
What I want to do now is to reconfigure / reinstall ISPConfig but this time with a mailserver. Is there anything else to make the md5-encryption work?
This is also a major problem. This is definitley caused by several features the users have in their webmailer (f.e. tag spam, setup filterrules within roundcube & stuff). Because this seems to be a hell lot of work to get this going I want to keep my current anti-spam & filtering solution in place and just use the user-administration of ispconfig. Therefore here is my second question:
Is there a major problem with this by modifying the postfix-configuration (main.cf) after the reinstall of ISPConfig? (I thought about excluding clamAV as a transport-pipe.)
The only thing that is still problematic is the feature that users are able to change their password from within the webmailer. I found the sql-command in the plugin-configuration file and wondered if it is possible to change this command, so it writes to the isp-db?
The Anti-Spam stuff I'm going to migrate on another shiny day. ;-)
I appreciate any suggestions.
Thanks. It worked out fine.
|All times are GMT +2. The time now is 06:51.|
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.