aliases of various types

[Gavin McCullagh]

Hi Gunnar,

On Tue, 06 Jul 2010, Gunnar Wrobel wrote:

> I think it would be great if you could also paste your summary into
> a wiki page ;)

Done:

https://wiki.kolab.org/index.php/Managing_Email_aliases

> I don't have anything new to add to your summary but I guess Thomas
> might still have the one or the other suggestion. 

I'm looking to set our standard operating procedures, so any extra ways to
deal with these things are very welcome.

> You focus solely on the web admin however. This might be too restrictive.
> There is nothing that would prevent you from also using the postfix
> aliases file on the Kolab server.

I'd really rather not use the aliases file if I can avoid it.  We found it
scaled very badly on our last Kolab install (our aliases file is 985 lines
long and is 65KB).  It's way too easy to make mistakes and too difficult to
find things.  We also need to give people ssh access which we may not want
to.

> Of course the Kolab web admin is limited in its abilities but it
> would be hard to support a large amount of the possible use cases
> with this tool. So for anything which is not directly possible via
> the web admin it is quite okay to use the server configuration
> templates and files.

One of the main things we're missing is a simple way to forward a local
alias to a remote account.  Would it be possible to implement local aliases
for address book entries in the same way as you do for normal users?  The
two alternatives I can see 
 - create the account and set a sieve forward on it 
 - create an addressbook entry and a distribution list against the local
   name

are both rather messy.  We'll probably go with the former as having
hundreds of distribution lists doesn't look like it'll work well in the web
interface (you can't search the distribution lists) but it's pain that you
have to login as the user to do it.

Gavin