| Summary | Vacation and forward conflict in SunOne LDAP schema |
| Queue | Vacation |
| Queue Version | 3.0.1 |
| Type | Bug |
| State | Assigned |
| Priority | 1. Low |
| Owners | Ben Klang <ben (at) alkaloid (dot) net> |
| Requester | falon (at) csi (dot) it |
| Created | 05/09/2008 (2 days ago) |
| Due | |
| Updated | 05/09/2008 (2 days ago) |
| Assigned | 05/09/2008 (2 days ago) |
| Resolved | |
| Attachments | |
| Milestone | |
| Patch |
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.
Assigned to Ben Klang
Patch ⇒
Milestone ⇒
Queue ⇒ Vacation
Summary ⇒ Vacation and forward conflict in SunOne LDAP schema
Type ⇒ Bug
Priority ⇒ 1. Low
State ⇒ Unconfirmed
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