February 09, 2012, 11:26:22 AM *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: Work on Kolab2/Gentoo-2.2 has stopped. The project has been deprecated (see board Kolab2/Gentoo).
 
   Home   Help Search Login Register  
Pages: [1]
  Print  
Author Topic: Integrating Kolab with existing Postix setup  (Read 4039 times)
FuriousGeorge
Newbie
*

Karma: 0
Posts: 6


View Profile Email
« on: April 05, 2008, 12:11:35 AM »

I have multiple domains set up on this server, and not all need to use Kolab.  I'd like to experiment with it on a couple of domains without using a dedicated server.

I've been following the Gentoo endorsed installation docs, and I've emerged kolabd, but I haven't allowed it to take over my configs yet.

The reason is that I also followed the [url src="http://www.gentoo.org/doc/en/virt-mail-howto.xml"]Official Gentoo Postfix docs[/url], and the [url src="http://www.gentoo.org/doc/en/mailfilter-guide.xml"]Official Gentoo Mailfiltering docs[/url], and that's the paradigm I'm most familiar with for postfix administration.

Kolab's configs want to hose that, which in and of itself is not a problem, as long as I can rebuild them (which is another matter), without breaking kolab again.  For instance:

-I notice Kolab wants to use flat files for alias and transport maps in /etc/postfix/main.cf, rather than the mysql tables im currently using.  Can I change that?

-Also, I see that Kolab doesnt use courrier-imap...  does that mean I can't be using courrier-imap anymore?

-etc

Basically, I can't even wrap my mind around the full implications of a migration right now, as I'm not an expert when it comes to postfix administration, either.

I've read the warning, and I'm looking through the hundreds of template files.

Perhaps kolab, which I have yet to start using does things a better way, and eventually I will drink the kool-aid too, but for now I'd rather not put all my eggs in one basket.  I want to have my cake and eat it too, and try out kolab without relinquishing all control, or renting another server.  Is that possible?

Is there some sane path to doing this, or should I abandon all hope.

Postfix is the most important thing.  If I could get that working with Kolab while keeping the existing ability to add domains and users via rows in tables of my database, that would be a good start.
Logged
xehqter
Jr. Member
**

Karma: 1
Posts: 94


View Profile WWW
« Reply #1 on: April 05, 2008, 06:31:00 AM »

Short answer abandon all hope. Kolab isn’t designed to be a template allowing you to pick and choose different back ends / configurations. Each component is tightly integrated into another.  While you can tweak various aspects replacing back ends isn’t possible without rewriting the source.

If you want to try out kolab setup a virtual machine or rent a box. I recommend experimenting with kolab before taking the plunge, while I like kolab it isn’t without its own unique issues.
Logged

FuriousGeorge
Newbie
*

Karma: 0
Posts: 6


View Profile Email
« Reply #2 on: April 07, 2008, 11:02:42 PM »

Ive been thinking about it, and looking into it more.

i'm noticing most of the parts of the kolabd are already installed and running on my server.  From what I can tell so far, we are talking about a matter of switching from courier-imap to cyrus, and adding LDAP support.  The former seems trivial, and I'm sure the latter is more complicated, but not rocket science either.

I have a server hosting 3 less-than-mission-critical email domains.  I was thinking about backing up all the configs that kolabd wants to overwrite (obviously), and writing a simple shell script to stop a few services, start a few others and install the templates ive modified.

do you guys see any problem with that?

If I can't get it working within a few hours, I can restore my configs, switch imap servers back, turn off LDAP, and try to make more progress next time.

How does my plan sound to the experienced kolab user?
Logged
Gunnar Wrobel
Administrator
Sr. Member
*****

Karma: 2
Posts: 331


275141552 gunnarwrobel@yahoo.de gunnarwrobel
View Profile WWW Email
« Reply #3 on: April 08, 2008, 06:31:56 AM »

Ive been thinking about it, and looking into it more.

i'm noticing most of the parts of the kolabd are already installed and running on my server.  From what I can tell so far, we are talking about a matter of switching from courier-imap to cyrus, and adding LDAP support.  The former seems trivial, and I'm sure the latter is more complicated, but not rocket science either.

I have a server hosting 3 less-than-mission-critical email domains.  I was thinking about backing up all the configs that kolabd wants to overwrite (obviously), and writing a simple shell script to stop a few services, start a few others and install the templates ive modified.

do you guys see any problem with that?

If I can't get it working within a few hours, I can restore my configs, switch imap servers back, turn off LDAP, and try to make more progress next time.

How does my plan sound to the experienced kolab user?

Bad. At least if you want to do that on a production server. Chances are too high that you affect your other domains. If you do it on a separate machine that would be a different matter as you can always switch the domains back.

I don't know if you experienced no problems whatsoever when creating your current setup. But in general I feel e-mail/groupware servers are extremely complex and easy to brake.

A lot of what you plan there might be at least somewhat easier with Kolab2/Gentoo-2.2

Cheers,

Gunnar
Logged
xehqter
Jr. Member
**

Karma: 1
Posts: 94


View Profile WWW
« Reply #4 on: April 09, 2008, 05:49:03 AM »

While I admire your courage I don’t think you understand how tightly integrated/fragile each component is. Shoe horning dspam into kolab was a learning experience for me. 

Kolab isn’t just a bunch of backend configuration scripts, it’s a mesh of shell, perl, and php scripts held together by Popsicle sticks and duct tape. If each backend isn’t configured to kolab spec, expect problems from the scripts, one change can break your entire setup.  I’m amazed that Gunnar managed to get kolab running on Gentoo.

If you know what you’re doing you might get it to work however I would not trust it in a production setup.  If you’re really head strong on doing this try it on a local box first.  Find a spare system (or virtual machine), configure the box like your mail server, then try to migrate to kolab.  Its better to have a plan then loose a client because your testing a theory.

My 2 Cents
Jeremy
Logged

FuriousGeorge
Newbie
*

Karma: 0
Posts: 6


View Profile Email
« Reply #5 on: April 18, 2008, 02:44:55 AM »

You guys are right.

I bit the bullet and ponied up for another server.  I'm in the process of setting it up now, but as far as i can tell Kolab is already working (i can add users in the web manager), so I moved on to trying to get a web based client working. 

Naturally I went with the horde-kolab project, but I'm having some issues with that which you can read all about here http://forum.pardus.de/index.php/topic,212.0.html if you are interested

Thanks for the replies
Logged
xehqter
Jr. Member
**

Karma: 1
Posts: 94


View Profile WWW
« Reply #6 on: April 18, 2008, 04:51:01 AM »

Your kolab on gentoo adventure has only started.
Logged

Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!