This content has been marked as final. Show 17 replies
[moved from a different forum]
Users in beehive can have multiple addresses, and each address of type MAILTO is used for email resolution.
So, if you have user "rodrigo" that you want to add a new email address to, you can use the modify_user command:
$ beectl modify_user
this sets Rodrigo's second business email address to "email@example.com"
You can have up to five business, five personal and five "other" addresses of each scheme, where scheme is one of:
mailto, tel, fax, ftp, http, https, im, imap, ldap, news, nntp, oraalert, oraassistantphone, oracallback, oraisdn, oramobile, oracarphone, orapager, orapostal, orapush, oraradio, orasms, oratelex, orattyttd, oravmail, pres, sip, urn, xmpp
$ beectl modify_user --help
for more details.
hope that helps,
That makes all sense!
Just getting used to the new concepts :D
is the syntax BUSINESS_2:MAILTO free or specified (apart the presence of :) ?
The format is not really free, but is made up of three parts; the TYPE (with an index), the SCHEME and the value.
The set of values available for type and scheme are listed here:
Does that answer your question?
the method outlined here is somewhat dissatisfying when it comes to the need to maintain a central repository of aliases (something like /var/adm/sendmail/aliases):
to change an alias like firstname.lastname@example.org, you would first have to seek for the current user who has this alias.
doesn't beehive offer a comparable central aliases database?
Isn't the addressbook not helping here? All the aliases should be visible through the addressbook, and you should be able to find them if you search by email address (alias in this case).
do you mean that the addressbook (you're actually referring to the GAL?) can / should be used to form aliases?
I don't have the local mail traffic in mind, but aliases that can be communicated as contacts to the public, and that finally point to employees.
It depends on what you want to do :
- for personal aliases just use the standard beehive behaviour
- for "functional aliases for the outside world", use groups (even with 1 person), so that you get a central management
thanks for that tip regarding public aliases.
We actually have some aliases pointing to the same group of people, so that a functional alias is reachable through several alternative spellings, like
email@example.com, firstname.lastname@example.org, email@example.com
(not our realworld example, but just for the purpose of having an example to discuss)
How can we implement several aliases pointing to the same distribution list (group), without doubling the group definition?
snmdla wrote: How can we implement several aliases pointing to the same distribution list (group), without doubling the group definition?A group is like a person it can have plenty of addresses as Richard mentioned above. What you are asking could also be used in OCS: create a distribution list and put people in it. So you have your group accounts_manager with address firstname.lastname@example.org containing Mr John Smith, so his inbox will get the email. However I'm not sure Zimbra will allow him to send email as email@example.com
thanks for the tip.
In a LDAP controlled setup, the question arises where to place the mail attribute that we use to use in user settings: neither posixGroup (currently not supported by beehive) nor groupofnames has such an attribute: we are probably forced to invent our own mail attribute.
Of course, and in production, you are 99% probable to be synced to an external directory, and in this case, you can't add email addresses via Beekeeper. If you have the ability to add several entries for the user's mail attribute in that directory, they end up mapped at random in Beehive, which means you never know, in Zimbra, which address you are sending as :o(
I haven't tried adding the other addresses as other that business_n though...
we were able to implement own attributes to reflect group mail adresses controlled in LDAP. Now there remains the question on how to implement aliases on group addresses (distlists) and team workspace addresses. If I understand you right, beehive allows only one group mail address (in contrast to user mail addresses).
Would it be a viable idea to implement aliases via external contact entries?
a test showed that I can define multiple group mail addresses in LDAP, and those addresses are synced into UDS and are reachable.
Only the first address will be listed in the GAL.