Sat, 05 Jul 2008 19:00:33 -0400 http://bugs.horde.org/ticket/6686 Vacation and forward conflict in SunOne LDAP schema I would like to explain a problem that affect all people that use forward and vacation modules together with LDAP driver. In SunOne schema vacation and forward mechanism use the same attribute "maildeliveryoption". So, if a user set vacation lose forward setting, and vice versa. Because if I set a module I change maildeliveryoption not only on interested value, but rewriting all its values. Let me explain with an example: Let be that attribute which contains the vacation status and forward status is the same: maildeliveryoption. A user set a forward: ldap driver set maildeliveryoption adding "forward" value. Then the same user also set vacation: ldap vacation driver instead to *add* "autoreply" value to maildeliveryoption, *replace* it with "autoreply" value. So user lose the "forward" value previously set. See also http://bugs.horde.org/ticket/6523 I know that this should be a particular condition of SunOne, but all environments that use same multivalued attribute to set vacation and forward could be affected. It is also true that these LDAP drivers should only modify single value of multivalued attribute, instead of replacing attribute at all, without preserve other values. What do you think? A fix to this behavior should be very appreciate. I thank you very much Best Regards Fri, 09 May 2008 03:12:15 -0400 http://bugs.horde.org/ticket/6686#t45201 This isn't totally unique to LDAP. If you use the .forward setup for vacation and forwards, they also overwrite eachother since they use the same .forward file and don't really know about each other (as well as any other uses of the .forward file). To fix this, you would need "intellegent" parsing of the contents of the field/file/etc so as to "update" it intellegently rather than simply replacing or removing the contents. Doing such work reliably may be problematic depending on the contents of the field and how it can be updated by other sources, etc. Maybe it is better to focus on Ingo for such advanced settings, rather than continuing such complex work on Sork? IMHO, in order to implement the requested feature, we would need to know all possible values of maildeliveryoption and what the syntax of the contents is. Then build something which understands that syntax and knows the options, and can manipulate them in a safe way. Doing that for LDAP is probably much easier than for a .forward file, but you still never know if some other software might use the maildeliveryoption in a non-standard way or something. Fri, 09 May 2008 12:54:13 -0400 http://bugs.horde.org/ticket/6686#t45210 I would try to explain better about LDAP. I don't think it is necessary to know all possible values of attribute used by forward/vacation. It's only necessary that driver acts only on values related to working mechanism. For instance, If vacation module set attribute maildeliveryoption to "autoreply", when I unset vacation, driver should only delete value "autoreplay" of maildeliveryoption, leaving other values unchanged. "ldap_mod_del" permits deletion of single attribute value, I suppose. At the same, I could add value to attribute leaving its other values unchanged. I apologize if I don't explain better. Thank again Regards Tue, 13 May 2008 08:17:21 -0400 http://bugs.horde.org/ticket/6686#t45257