Recipient policy not updating new users

6854933580_2c8b688306_z

Important By default, the primary recipient email address is used as a globally unique identifier involving authentication (allowing login by email address), the user’s mailbox name, mail delivery configuration, access control and the storage of user profiles.

It is therefore very important that no two entries share a single primary recipient email address. The first item in the list will be used as the attribute to use for primary recipient email addresses.

If you are getting any reports of email delivery problems, setting this preference to "user sending message" may resolve the issue.

Once this preference is set, the name of the user sending the message will appear in the From field and that user's email address will be used if the message recipient replies to the message.

The secondary email address attribute (alias by default) is set to the value(s) returned by the recipient policy as well.

Furthermore, the recipient policy allows these automatically recipient email addresses to be globally unique.

If the number of parent domain name spaces hosted is relatively static, we recommend considering the use of configured lookup tables per parent domain name space.

recipient policy not updating new users-38recipient policy not updating new users-15recipient policy not updating new users-22

At times this may not be ideal, especially when dealing with recipient mail servers that employ aggressive spam filters or whitelists.The recipient policy aids deployments in achieving a level of consistency throughout their recipient database by applying a naming convention, avoiding the need for Kolab Groupware administrators to need to understand and consistently apply naming convention rules.Consistency is important when considering global address book listings and searches in different contexts, and when anticipating what a valid recipient address for a given user may be – noted that most email users do not have access to your global address book to verify a recipient address is valid, and it is likely that most communications will take place with those users. This is considered inadequate, as many users will experience this inappropriate, inconsiderate and/or awkward – it is the user’s native tongue after all and transliteration is used in every-day life.In these cases, setting a custom SMTP server allows you to send system notifications from your own mail server instead.By default, even if a user has upload or download notifications for a folder, they will not receive notifications about their own activity in those folders.The primary email address attribute value is, by default, used to determine a user’s mailbox name.

You must have an account to comment. Please register or login here!