<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Arial; font-size: 12pt; color: #000000'>oki<br><br>I'm going to download and look'at Namespace structure code (hoops i need a new server)<br><br>In few days, i send a patch in forder file or in Namespace struct or in an other one<br><br><br>thank's for the answer<br><br><br>----- Mail Original -----<br>De: "Gunnar Wrobel" <wrobel@kolabsys.com><br>À: kolab-devel@kolab.org<br>Envoyé: Dimanche 31 Octobre 2010 22h02:34 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne<br>Objet: Re: [Kolab-devel] cyrus imap altnamespace<br><br>Hi Jean-Philippe,<br><br>Zitat von Jean-Philippe <jpisard@free.fr>:<br><br>> Hi<br>><br>><br>> the target :<br>> use horde with altnamespace<br>><br>> I have change severals functions in horde framework :<br>> just in the class Kolab_Folder<br>><br>> and I have add one general parameter :<br>> ['kolab']['imap']['altnamespace']<br>><br>><br>><br>> sample of one change in source code:<br>><br>> function setName($name)<br>> {<br>> global $conf;<br>> $check_inbox=true;<br>> if (isset($conf['kolab']['imap']['altnamespace'])) {<br>> if ($conf['kolab']['imap']['altnamespace']) $check_inbox=false;<br>> }<br>><br>><br>> $name = str_replace(':', '/', $name);<br>><br>> if ($check_inbox)<br>> {<br>> if (substr($name, 0, 5) != 'user/' && substr($name, 0, 7) !=<br>> 'shared.') {<br>> $name = 'INBOX/' . $name;<br>> }<br>> }<br>> $this->new_name = String::convertCharset($name,<br>> NLS::getCharset(), 'UTF7-IMAP');<br>> }<br><br>May I point you to upstream where some IMAP namespace support has <br>already been implemented: <br>http://git.horde.org/horde/-/browse/framework/Kolab_Storage/lib/Horde/Kolab/Storage/?sa=1<br><br>This will be part of Kolab Server 2.3 (which we hopefully release soon).<br><br>"altnamespace" is not in there yet but if in order to be included into <br>Kolab Storage it would need to fit the Namespace structure that is <br>available in the code already.<br><br>Maybe you can submit a full patch in a Kolab issue and we can continue <br>the discussion based on that?<br><br>Cheers,<br><br>Gunnar<br><br>><br>> _______________________________________________<br>> Kolab-devel mailing list<br>> Kolab-devel@kolab.org<br>> https://kolab.org/mailman/listinfo/kolab-devel<br>><br><br><br><br>--<br>Gunnar Wrobel<br>Developer, Kolab Systems AG<br><br>e: wrobel@kolabsys.com<br>t: +49 700 6245 0000<br>w: http://www.kolabsys.com<br><br>pgp: 9703 43BE<br><br>----------------------------------------------------------------<br>This message was sent using IMP, the Internet Messaging Program.<br><br>_______________________________________________<br>Kolab-devel mailing list<br>Kolab-devel@kolab.org<br>https://kolab.org/mailman/listinfo/kolab-devel<br></div></body></html>