<?xml version="1.0" encoding="ISO-8859-1"?>
<?xml-stylesheet href="http://bugs.horde.org/themes/feed-rss.xsl" type="text/xsl"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
 <channel>
  <title>LDAP driver for SunOne Messaging</title>
  <pubDate>Fri, 08 Aug 2008 15:17:00 -0400</pubDate>
  <link>http://bugs.horde.org/ticket/6523</link>
  <atom:link rel="self" type="application/rss+xml" title="LDAP driver for SunOne Messaging" href="http://bugs.horde.org/ticket/6523/rss" />
  <description>LDAP driver for SunOne Messaging</description>

  
  
  <item>
   <title>I really would appreciate a LDAP driver for SunOne Messaging</title>
   <description>I really would appreciate a LDAP driver for SunOne Messaging.
The behavior requested differ on current LDAP driver as below:

forward with local copy must have following multivalued attribute:
maildeliveryoption: mailbox
maildeliveryoption: forward

forward with no local copy must have only the following mailveliveryoption attribute single value:
maildeliveryoption: forward


Without maildeliveryoption attribute set to &quot;forward&quot;, the forward mechanism doesn't work. It's not sufficient to set mailforwardingaddress attribute.

Thanks a lot.


</description>
   <pubDate>Tue, 25 Mar 2008 10:02:48 -0400</pubDate>
   <link>http://bugs.horde.org/ticket/6523#t44177</link>
  </item>
  <item>
   <title>Sure, but if you want it to be high priority you'll probably</title>
   <description>Sure, but if you want it to be high priority you'll probably need to sponsor its development.</description>
   <pubDate>Tue, 25 Mar 2008 10:57:34 -0400</pubDate>
   <link>http://bugs.horde.org/ticket/6523#t44179</link>
  </item>
  <item>
   <title>I have just refactored much of the old Exim-specific LDAP dr</title>
   <description>I have just refactored much of the old Exim-specific LDAP driver into a more generic LDAP driver supporting the following schemas:

* qmail-ldap (based on my own deployment)
* SunONE (as described in this ticket)
* Exim (as formerly implemented)
* Custom (in case one of the above do not fit)

I will be committing this updated driver shortly as it still requires a bit more testing.
</description>
   <pubDate>Fri, 02 May 2008 16:24:01 -0400</pubDate>
   <link>http://bugs.horde.org/ticket/6523#t45148</link>
  </item>
  <item>
   <title>This has been implemented with the rewritten LDAP driver.  P</title>
   <description>This has been implemented with the rewritten LDAP driver.  Please see http://lists.horde.org/archives/cvs/Week-of-Mon-20080505/078038.html</description>
   <pubDate>Mon, 05 May 2008 16:55:50 -0400</pubDate>
   <link>http://bugs.horde.org/ticket/6523#t45178</link>
  </item>
  <item>
   <title>I thank you very much for you effort.
I tried this patch, i</title>
   <description>I thank you very much for you effort.
I tried this patch, it is very useful.

There is again a bug that affect forward and vacation modules together.
Because they act on same multivalue attribute ('maildeliveryoption'), if I change setting on vacation I corrupt forward, If I change forward setting, vacation doesn't work more.

I think this is because ldap driver works on maildeliveryoption rewriting entire attribute, and not only his interesting value.
For instance, If I set forward on active vacation user, the forward driver remove 'autoreply' value of maildeliveryoption. 

A patch on this behavior should be very useful for all people that use vacation and forward together.

I thank you very much
Best Regards</description>
   <pubDate>Thu, 08 May 2008 05:20:51 -0400</pubDate>
   <link>http://bugs.horde.org/ticket/6523#t45195</link>
  </item>
  <item>
   <title>Unfortunately this problem is very specific to SunONE.  qmai</title>
   <description>Unfortunately this problem is very specific to SunONE.  qmail-ldap uses entirely different attributes to handle vacation messages and does not need nor use the mailDeliveryOption attribute at all.  From what I can tell Exim uses something different from both qmail-ldap and SunONE.

In addition this is really should be a new bug because the rewritten Forwards driver does work as advertised, it just conflicts with Vacation in your environment.  To be honest I'm not sure whether Forwards needs to be fixed, or Vaction, or both.  Please open a new ticket with this problem report and we'll track it separately.</description>
   <pubDate>Thu, 08 May 2008 13:51:05 -0400</pubDate>
   <link>http://bugs.horde.org/ticket/6523#t45199</link>
  </item>
  

 </channel>
</rss>
