[Tickets #6686] Re: Vacation and forward conflict in SunOne LDAP schema

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/6686
-----------------------------------------------------------------------
 Ticket             | 6686
 Updated By         | rostetter at mail.utexas.edu
 Summary            | Vacation and forward conflict in SunOne LDAP schema
 Queue              | Vacation
 Version            | 3.0.1
 Type               | Bug
 State              | Assigned
 Priority           | 1. Low
 Milestone          |
 Patch              |
 Owners             | Ben Klang
-----------------------------------------------------------------------


rostetter at mail.utexas.edu (2008-05-09 12:54) wrote:

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.