Tickets :: [#4130] mail attribute being set incorrectly

6.0.0-beta1

9/21/25

Summary	mail attribute being set incorrectly
Queue	Horde Framework Packages
Queue Version	HEAD
Type	Bug
State	Resolved
Priority	1. Low
Owners	ben (at)
Requester	bklang (at) horde (dot) org
Created	07/08/2006 (7015 days ago)
Due
Updated	08/14/2006 (6978 days ago)
Assigned	07/08/2006 (7015 days ago)
Resolved	08/14/2006 (6978 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	Yes

08/14/2006 01:38:04 AM	ben	State ⇒ Resolved

08/14/2006 01:37:42 AM	ben	Comment #4	Reply to this comment
Agreed. Committed, thanks!

07/23/2006 04:41:20 AM	Ben Klang	Comment #3	Reply to this comment
I know that LDAP will return an error if you try to create or modify an object and pass an attribute with a null or empty value. That might have been the original motivation for putting a space in the field. However, unless the 'mail' attribute is required by one of the dependant objectclasses (which it doesn't appear to be) it shouldn't be set with bogus data. In my opinion it shouldn't be set with bogus data at all if it can be avoided.

07/08/2006 05:22:44 AM	ben	Comment #2 Assigned to ben State ⇒ Assigned	Reply to this comment
I seem to remember there being a good reason to insert an empty value here. I don't remember what it was though, so I'm holding off on this one until I get a chance to look into it more deeply.

07/08/2006 03:18:28 AM	Ben Klang	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ mail attribute being set incorrectly Queue ⇒ Horde Framework Packages New Attachment: group-dont-set-empty-mail-attr.patch State ⇒ Unconfirmed	Reply to this comment
The LDAP Group driver sets the mail attribute unnecessarily. It should only be set when there is actual data. This patch corrects the issue.