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

* Your Email Address
* Spam protection	Enter the letters below: ______ __ __ ___ ____ __ \| ____\| \/ \| \| \ \ / / \/ \| \| \|__ \| \ / \| \| \|\ \_/ /\| \ / \| \| __\| \| \|\/\| \|_ \| \| \ / \| \|\/\| \| \| \|____\| \| \| \| \|__\| \| \| \| \| \| \| \| \|______\|_\| \|_\|\____/ \|_\| \|_\| \|_\|
Comment	> 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. > >
Attachment
Watch this ticket