automatically create IMAP folders for new user

[xehqter]

Gunnar do you have any ideas/hacks that would allow me to automatically create IMAP folders when a kolab user is created?

[SteveB]

How about enabling the "autocreate" USE flag and configuring imapd.conf to create the needed folders?

// SteveB

[Gunnar Wrobel]

I know/heard about some imapd autocreate patches. Are these included in that cyrus-imapd release? In any case the necessary folders probably would not get annotations automatically. So this might actually require a good deal of hacking.

Which folders do you want to create automatically?

[xehqter]

It's for DSPAM, I got a chance to revisit it the past week. I was going to try Steve's suggestion this weekend
I like setting up a hierarchy with a spam folder in the root and two children folders; Block and Unblock.

Spam
-> Block
-> Unblock

So far I setup DSPAM in daemon (gateway) mode, postfix passes emails to dspam, if an email is marked as spam it uses a plussed address (user+spam@mydomain.com) to put the email in the Spam folder. I have a cron'd script which retrains misidentified spam and ham every few minutes, then moves it into the correct folder via cyrus deliver, rm, and cyrus reconstruct.

It would be a nice conclusion to the project if the folders were created automagically when a new user is created.

[Gunnar Wrobel]

When I updated cyrus imapd on friday I saw at least that it allows to activate the autocreate patches by using the "autocreate" use flag. So you should definitely turn that on and check how to configure it. but I guess it should be possible.

[xehqter]

I just had a peak at autocreate, while it does create folders I can't set permissions for those folders so i'm back to square one; finding where in the kolab's source cyrus mailboxes are created. For my nice dspam kolab setup i'd like to automatically create spam, block, unblock folders and give plused permission to the spam folder.

as i'm writing them I'm thinking a cron'd script to check for new users may be cleaner..  hmm.. something to sleep on..

[Gunnar Wrobel]

I didn't get a chance to look at your DSPAM solution yet, though I would like to. But at the moment there is just too much to do

But did you check the perl-kolab package and the kolabd proces?

What happens on Kolab when you create a new user is:

 - You add the user
 - The user gets written to LDAP
 - LDAP replicates the entry to kolabd listening on port 9999
 - kolabd will create and initialize the users mailbox in cyrus imap

The last step is not configurable but if you know perl a little bit you might be able to hack the code.

There might also be similar requests in the Kolab issue tracker. I don't know if somebody else did already suggest other solutions.

[xehqter]

thanks for the info, over the week I want to update the entry. That page just shows you how to shoe horn dspam into the loop, it doesn't mention training which is a big part of dspam.

I'm using Dspam in Global+Merged mode w/ mysql as the backend.
Meaning if I create a new user their automagically protected against spam by the global database until they have enough spam & ham for the merged database to kick in. I wrote a script to check the block/unblock folders, move the email to the appropriate location (inbox/spam folder), and to retrain the dspam global & merged definitions accordingly.

Long story short, depending on the user the Overall Accuracy is between 94.5% and 99.63%.

after dspam I want to try and get samba ldap (domain controller) working with kolab then modify webadmin so that i can manage all users from it... a pipe dream to keep me busy I suppose, if only I had time.

[Gunnar Wrobel]

thanks for the info, over the week I want to update the entry. That page just shows you how to shoe horn dspam into the loop, it doesn't mention training which is a big part of dspam.

I'm using Dspam in Global+Merged mode w/ mysql as the backend.
Meaning if I create a new user their automagically protected against spam by the global database until they have enough spam & ham for the merged database to kick in. I wrote a script to check the block/unblock folders, move the email to the appropriate location (inbox/spam folder), and to retrain the dspam global & merged definitions accordingly.

Long story short, depending on the user the Overall Accuracy is between 94.5% and 99.63%.

Sounds pretty good. And especially interesting in the light of the current spam wave washing over me

after dspam I want to try and get samba ldap (domain controller) working with kolab then modify webadmin so that i can manage all users from it... a pipe dream to keep me busy I suppose, if only I had time.

Samba integration is something many Kolab users are also interested in. There were already some discussions on the mailing list. If you get it to work that'd be great. And I don't mind if it only works on the Gentoo version

Don't work on the webadmin too early. It is the worst piece of software in the whole Kolab server and it still needs serious rewriting before it makes sense to push this thing any further.

In any case thanks for your efforts. People extending this is what makes the project move forward.

Cheers,

Gunnar