Mail Forwarding broken

[Daniel Hoffend]

I'm not sure what happens on the centos/rpm package version but the user 
type is included in the current 3.1.3 sql file.

https://git.kolab.org/kolab-wap/tree/doc/kolab_wap-3.1.sql?h=kolab-webadmin-3.1#n178
Did you enabled the Kolab 3.1:Updates Repo aswell? The predefined user 
types for mail forwarding were intruduced in one of the latest latest 
releases. Not sure if they made it into the "non-updates" repo.

As many bugs have been fixed in Updates it's recommended IMO to use 
Kolab3.1 and Kolab3.1:Updates

--
Daniel

------ Originalnachricht ------
Von: "Christian Tardif" <christian.tardif at servinfo.ca>
An: "Daniel Hoffend" <dh at dotlan.net>
Cc: "users at lists.kolab.org" <users at lists.kolab.org>
Gesendet: 11.12.2013 18:25:47
Betreff: Re: Mail Forwarding broken
>Then, something didn't work with the installation because I did a clean 
>install against a clean CentOS 6.4 installation, and I only have three 
>user types: Kolab user, Posix User, Mail-Enabled Posix user
>
>
>-- Christian...
>
>
>Quoting Daniel Hoffend <dh at dotlan.net>:
>
>>Yes.
>>
>>Afaik the mail forwarding user type and the corresponding 
>>virtual_alias_maps_forwarding.cf (or so) is shipped with a vanilla 
>>kolab 3.1. But it's possible that not all technical possibilities like 
>>catchall, etc are enabled per default via postfix on a vanilla 
>>installation.
>>
>>Maybe if you've upgraded it's possible that the upgrade didn't 
>>modified your kolab.user_types table.
>>
>>But overall: The mail forwarding feature (forwarding only ldap 
>>entries) is not a kolab feature. It's just a simple clever/correct 
>>usage of ldap attributes + postfix configuration. The kolab-web admin 
>>and it's predefined user_types just helps us/gives us an admin GUI to 
>>manage accounts instead of doing things manually with ldapadd on the 
>>cli
>>
>>--
>>Daniel Hoffend
>>
>>>Am 11.12.2013 um 05:10 schrieb Christian Tardif 
>>><christian.tardif at servinfo.ca>:
>>>
>>>That's really unclear to me... Is this something actually on the dev 
>>>side or if it is something we can already use? If so, where is that 
>>>hidden?
>>>
>>>Christian...
>>
>
>
>