Re: Changelog, LDAP features
Thomas Luzat [EMAIL PROTECTED] wrote: a) Fetching Sieve-scripts from LDAP (would guess not) b) Fetching Quota settings from LDAP (same) It's probably best to write some LDAP-Cyrus gateway for that, right? For the university of Constance I wrote a little Daemon program which synchronizes OpenLDAP with Cyrus databases (and mailboxes) - because they did not want to compile the postfix and cyrus things themselves (lack of support). It uses the rather simple openldap-replication-mechanism to accomplish this. For the staff there, the postfix/cyrus server is completely in the LDAP tree including passwords, quotas, forwards and autoreplies (via a special autoreply program, also written by myself because most of them lying around send out too many autoreplies (to lists, errors, ...) and could not take the autoreply message via LDAP. Here we use the standard autoreply-LDAP-attributes.). Mailboxes get created automatically when an LDAP entry comes in and it gets deactivated when it is removed. So the user support personnel can just create an LDAP entry to make a valid postfix-alias and cyrus mailbox available immediately. Works like a charm but it is not very elegant (I must admit it). I did not find any other solutions than to write it on my own. If there are other solutions, let me know. I packaged the whole system to a package named priscilla - Pascal
Re: Changelog, LDAP features
Thomas Luzat [EMAIL PROTECTED] wrote: a) Fetching Sieve-scripts from LDAP (would guess not) b) Fetching Quota settings from LDAP (same) It's probably best to write some LDAP-Cyrus gateway for that, right? For the university of Constance I wrote a little Daemon program which synchronizes OpenLDAP with Cyrus databases (and mailboxes) - because they did not want to compile the postfix and cyrus things themselves (lack of support). If there are other solutions, let me know. The University of Athens is doing some cool work here http://email.uoa.gr/projects/cyrusmaster/ I packaged the whole system to a package named priscilla - What is the license of your package, can it be downloaded somewhere? Simon Pascal
Re: Changelog, LDAP features
Simon Matter [EMAIL PROTECTED] wrote: The University of Athens is doing some cool work here http://email.uoa.gr/projects/cyrusmaster/ I'll take a look at it! What is the license of your package, can it be downloaded somewhere? Yes it will be next week. Had enough time to test it, it works in production for approx 15000 users since 6 months now - the daemon logs activity via syslog. It is not a click here to install-Package though, you will have to read readme-Files and edit some configurations with a text editor... See it as a glue between cyrus and OpenLDAP. Pascal
Re: Changelog, LDAP features
Thomas Luzat wrote: Hello! 1) Is there any 'readable' changelog (better than the CVS entries) for Cyrus IMAP available? Are you looking for a log listing changes between releases (doc/changes.html) or changes between source file versions (CVS logs)? 2) Is there a list of planned featues and features which is being worked on? Not really. The cyrus-devel list or the Cyrus Wiki would be the most obvious places for this type of thing to exist. 3) Are there any plans to allow some further integration of LDAP? I am thinking about: a) Fetching Sieve-scripts from LDAP (would guess not) No, but I don't see why it couldn't exist. I don't know if you'd want integration with timsieved or not (probably not). b) Fetching Quota settings from LDAP (same) This would be fairly trivial once the quota stuff gets changed to use the cyrusdb interface. Then all that would need to be done would be to write a cyrusdb_ldap backend. In fact the cyrusdb_ldap backend could be written any time. -- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key--http://www.oceana.com/~ken/ksm.pgp
Re: Changelog, LDAP features
On Wed, 19 Nov 2003, Ken Murchison wrote: 2) Is there a list of planned featues and features which is being worked on? Not really. The cyrus-devel list or the Cyrus Wiki would be the most obvious places for this type of thing to exist. Generally if someone suggests a feature that we want to implement sometime, we throw it in our bugzilla so we don't forget. However, currently I think we're heading into a mostly-maintenance period (after 2.2 gets a stable release -- possibly by the end of the year, certainly by the end of January). 3) Are there any plans to allow some further integration of LDAP? I am thinking about: a) Fetching Sieve-scripts from LDAP (would guess not) No, but I don't see why it couldn't exist. I don't know if you'd want integration with timsieved or not (probably not). There's no plans for this. There's no real strong reasons against it, except for performance -- currently we mmap the bytecode directly from disk, as opposed to having to download it for each delivery (even from a local replica, this is a lose). b) Fetching Quota settings from LDAP (same) This would be fairly trivial once the quota stuff gets changed to use the cyrusdb interface. Then all that would need to be done would be to write a cyrusdb_ldap backend. In fact the cyrusdb_ldap backend could be written any time. Again, no plans, and no reasons against except for performance. Quotas get updated surprisingly frequently (every delivery, APPEND, COPY, and EXPUNGE), so having them in LDAP may not be desirable from a performance standpoint (LDAP directories don't tend to be designed around near-continuous updates). -Rob -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456 Research Systems Programmer * /usr/contributed Gatekeeper
Re: Changelog, LDAP features
On Wed, 19 Nov 2003, Rob Siemborski wrote: On Wed, 19 Nov 2003, Ken Murchison wrote: b) Fetching Quota settings from LDAP (same) This would be fairly trivial once the quota stuff gets changed to use the cyrusdb interface. Then all that would need to be done would be to write a cyrusdb_ldap backend. In fact the cyrusdb_ldap backend could be written any time. Quotas get updated surprisingly frequently (every delivery, APPEND, COPY, Nah, I think what is in question is the maximum quota, not the current quota state... i.e. that which is set by sq in cyradm. I have a script (modified from someone else) that fetches the quotas from LDAP and apply any changes using the perl interface, but that's suboptimal at best. I imagine a lot of people have similar kludges in their setups. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh
Re: Changelog, LDAP features
On Wed, 19 Nov 2003, Henrique de Moraes Holschuh wrote: Nah, I think what is in question is the maximum quota, not the current quota state... i.e. that which is set by sq in cyradm. I have a script (modified from someone else) that fetches the quotas from LDAP and apply any changes using the perl interface, but that's suboptimal at best. I imagine a lot of people have similar kludges in their setups. That is, of course, different. -Rob -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456 Research Systems Programmer * /usr/contributed Gatekeeper
OT: Re: Changelog, LDAP features
On Wed, 2003-11-19 at 17:48, Rob Siemborski wrote: On Wed, 19 Nov 2003, Ken Murchison wrote: 2) Is there a list of planned featues and features which is being worked on? Not really. The cyrus-devel list or the Cyrus Wiki would be the most obvious places for this type of thing to exist. Generally if someone suggests a feature that we want to implement sometime, we throw it in our bugzilla so we don't forget. However, currently I think we're heading into a mostly-maintenance period (after 2.2 gets a stable release -- possibly by the end of the year, certainly by the end of January). 3) Are there any plans to allow some further integration of LDAP? I am thinking about: a) Fetching Sieve-scripts from LDAP (would guess not) No, but I don't see why it couldn't exist. I don't know if you'd want integration with timsieved or not (probably not). There's no plans for this. There's no real strong reasons against it, except for performance -- currently we mmap the bytecode directly from disk, as opposed to having to download it for each delivery (even from a local replica, this is a lose). b) Fetching Quota settings from LDAP (same) This would be fairly trivial once the quota stuff gets changed to use the cyrusdb interface. Then all that would need to be done would be to write a cyrusdb_ldap backend. In fact the cyrusdb_ldap backend could be written any time. Sorry, it is a little bit off topic but I decided to ask since you have mentioned about near future plans. Do you plan to include a document as to how to implement Cyrus 2.2 virtual domains feature into postfix ? This has been written in the todo list. Murat
Changelog, LDAP features
Hello! 1) Is there any 'readable' changelog (better than the CVS entries) for Cyrus IMAP available? 2) Is there a list of planned featues and features which is being worked on? 3) Are there any plans to allow some further integration of LDAP? I am thinking about: a) Fetching Sieve-scripts from LDAP (would guess not) b) Fetching Quota settings from LDAP (same) It's probably best to write some LDAP-Cyrus gateway for that, right? Thanks! Thomas signature.asc Description: This is a digitally signed message part
