Univention Bugzilla – Bug 45581
inconsistent behavior of umc/users email field
Last modified: 2018-04-18 13:51:56 CEST
When a user without an entry in the "email" (contacts) field has a mailPrimaryAddress, the UMC shows the mailPrimaryAddress in the "email" field.
However when saving the user the email field is not saved.
It is only saved, when adding a 2nd address to "email". Then both addresses will be saved. When removing the 2nd address, the first remains in LDAP, even if it is still the same as the mailPrimaryAddress.
* the contacts field should not be shown as filled when if it's not, or
* it should be saved to LDAP
Does it cause any problem currently?
(In reply to Florian Best from comment #1)
> Does it cause any problem currently?
Yes: a customer is affected.
(In reply to Daniel Tröder from comment #2)
> (In reply to Florian Best from comment #1)
> > Does it cause any problem currently?
> Yes: a customer is affected.
Yes, UMC shows an mail address for the user but it isn't set. Thus, mail clients didn't find the contact information.
The customer needs a patch urgently
This is kind of a regression from Bug #41053 because the e-mail property has a default value of ['<mailPrimaryAddress>'] which is since then also evaluated when modifying the object.
This bug is worth another customer ticket.
On a fresh UCS 4.2-3 standalone mailserver one creates a new user without any e-mail attributes and adds the mailPrimaryAddress afterwards. What happened is the mailPrimaryAddress is shown in the contact tab without writing the value into the 'mail' attribute. This behavior is absolutely inconsistent.
Move to 4.3-0-errata. If a UCS 4.2 backport is needed, please clone this issue.
I have removed line
in the e-mail field definition.
OK e-mail does no longer use mailPimaryAddress as default