iRedMail — iRedMail on existing server using other existing MySQL host

Re: iRedMail on existing server using other existing MySQL host

2009-09-25T07:02:05Z

Updated.

We have a simple way to make iRedMail not to install AMP related binary packages, and it's simplier now.
http://code.google.com/p/iredmail/wiki/ … ation_Tips

Re: iRedMail on existing server using other existing MySQL host

2009-09-25T06:54:40Z

After review the Installation_Tips wiki page, i found it is out of date.

I will update it now.

Re: iRedMail on existing server using other existing MySQL host

2009-09-25T06:52:26Z

Fixed:
http://code.google.com/p/iredmail/sourc … ;repo=wiki

Thanks for your report

Re: iRedMail on existing server using other existing MySQL host

2009-09-25T06:41:14Z

Excellent Thanks.

FYI, the link here: http://code.google.com/p/iredmail/wiki/Installation
That says: Tip: You can use exist MySQL database server to store virtual domains/users.
Does not point to the Tips page. That was the missing link for me

Re: iRedMail on existing server using other existing MySQL host

2009-09-25T06:14:46Z

Reference:

- How to Use Exist MySQL Server
http://code.google.com/p/iredmail/wiki/ … ation_Tips

WARNING WARNING WARNING WARNING:
Backup all data on your exist server before you try to deploy iRedMail on it.

iRedMail on existing server using other existing MySQL host

2009-09-25T05:11:42Z

I have iRedMail working great on my own personal domain. It's been doing its job there for months with no problem. Reduced my spam by... loads.

I'm now looking to use it at my work. I want to deploy it on a server that also has existing server services running on it (many of them are custom), and I just wanted to double-check that it will not impact existing features.

Also, I'd like to use an existing MySQL server, that's not on the localhost. Having a quick look, I found conf/mysql in the install heirarchy. Is that all I need to change to use the other server? From what I can glean in scripts/config, I would have to change MYSQL_FRESH_INSTALLATION to "NO" and modify the MYSQL_SERVER.

I've also seen that regardless, functions/mysql.sh will try to restart the mysql daemon on the localhost (which doesn't bother me, because it doesn't have one).