My Kolab 2.4 experience on Centos 6

[Troy Carpenter]

On Wednesday, July 18, 2012 10:17:00 AM you wrote:
> Hi Troy,
> 
> On Tuesday, July 17, 2012 09:42:11 PM Troy Carpenter wrote:
> > After wasting my time with installing Kolab 2.4 in a Centos container under
> > Proxmox, I finally switched to installing under a full KVM version of
> > Centos. The install went as expected when following the instructions, with
> > the following additions:
> > 
> > 1. I had to manually create the localhost.pem file that was expected by
> > postfix to initiate TLS connections.
> > 
> 
> I've created ticket #886 for this issue[1].

The commands, which I don't think was included in the online docs:

cd etc/pki/tls/certs
make localhost.pem
cp localhost.pem ../private

Of course, if the config file is changed, the .pem file can be named anything.
 
> > 2. I had to configure postfix to use a smarthost and also handle the sasl
> > authentication for the smarthost (I had to do the authentication part in the
> > previous version of Kolab as well).
> > 
> 
> If you could summarize what you did, I'd be interested in including this 
> deployment scenario / change of configuration in the documentation.
> 
> For the sake of record keeping, I've created a ticket for this as well - 
> #887[2] - it is not an uncommon deployment scenario, after all.
>

In 2.3.4, setting a smarthost was done from the webadmin tool.  However, adding the part for sasl authentication was not:

1. Create a file called /etc/postfix/saslpass with the following content like this.  Change content as necessary:
echo "[smtp.provider.net]:587        username:password" > /etc/postfix/saslpass2

2. Make it a database:
postmap /etc/postfix/saslpass

3. Modify and reload postfix.  Add the following commands to the end of the postfix main.cf file (changing the smarthost to match step 1:
echo "# Postfix Relay Host
relayhost = [smtp.provider.net]:587
smtp_sasl_auth_enable = yes
smtp_tls_security_level = may
smtp_sasl_password_maps = hash:/etc/postfix/saslpass
smtp_sasl_mechanism_filter = plain, login
smtp_sasl_security_options = noanonymous" >> main.cf
/etc/init.d/postfix reload

 
> > The main problem I am having right now is with z-push.  When I point my
> > devices to the server, they are constantly telling me the password is wrong.
> > I have tried with an iPad and also just using a web browser on my PC.  With
> > the PC, I get the username/password dialog which also tells me the password
> > is incorrect.  I don't have any logs or debug information being generated. 
> > Like previous versions, I am using my email address as the username.
> 
> Z-Push requires you to login with your uid attribute value (the default is to 
> use the surname of a user). I know this is somewhat confusing, as Kolab 2.3 
> installations used the email address as the uid attribute value.

That's too bad.  My system is setup mainly for my family, so my uid is "carpenter", and every other user has the same with a number appended.  Very annoying. I did figure out how to unlock the fields in the new user screen and I did see that uid can be modified that way, but I never figured out where the uid was being automatically generated.  I will experiment with some custom UIDs to see what happens.

> > Logging in with IMAP works just fine, as does sending email.
> > 
> > The final problem I will need to deal with is transferring old emails from
> > my live 2.3 install to this one.  I have come across a tool called imapsync
> > that I plan to try.
> > 
> 
> Be careful with imapsync, we've heard of situations where misconfiguration 
> would have one end up with calendar items in mail folders or vice-versa ;-)
> 
> Offlineimap might be a utility to your liking as well.

I will try some others.  imapsync appears to have worked well for the two accounts I tested it on (over 12k emails in one account).  I really only have less than 20 users on the system. The different namespace structure threw me at first, but imapsync figured it out (by that I mean that 2.3.4 put all folders as subfolders of INBOX. 2.4 puts them outside of INBOX).