Autocreate INBOX is a patch for Cyrus IMAP server that enables automatic creation of user mailboxes under some certain circumstances. It is intended for large installations where there is a strong possibility that not all users are going to use the mail service. Additionaly this patch will be useful for sites that couldn't afford or wouldn't like to have a per-user mechanism to create INBOXes. In such cases the best solution is to insert a user entry in a user database and let Cyrus create the mailboxes when it is necessary.
Autocreate patch enables the following situations when a user mailbox may be created.
Dec, 22 2009: Autocreate patch (version 0.10-0) released for cyrus 2.3.16.
Apr, 02 2009: Autocreate patch (version 0.10-0) released for cyrus 2.3.14.
Oct, 29 2008: Autocreate patch (version 0.10-0) released for cyrus 2.3.13.
Sep, 03 2007: Autocreate patch (version 0.10-0) released for cyrus 2.3.9.
Mar, 14 2007: Extra diff to the autocreate patch for building on FreeBSD 6.2 using the ports system. This diff is a diff to the patch and NOT the patch itself. The file to download is named: cyrus-imapd-2.3.8-autocreate-0.10-0-FreeBSD6.2.diff. Patch provided by Laimonas SLepcenka
Mar, 14 2007: Autocreate patch (version 0.10-0) released for cyrus 2.3.8.
Apr, 19 2006: Autocreate patch (version 0.9.4) released for cyrus 2.2.13.
Mar, 07 2006: Autocreate patch (version 0.10-0) released for cyrus 2.3.3.
Jan, 20 2006 New release of patch for Cyrus IMAPd 2.3.1 (version 0.10-0). This release is mostly a port to Cyrus IMAPd 2.3.1. Moreover, it contains a new configuration option (autocreate_users) to restrict the users whose mailboxes are automatically created. (For more information on this feature, please check imapd.conf (5) and README.autocreate for Cyrus 2.3.x
Oct, 19 2005 New release of patch for Cyrus IMAPd 2.2.12 (version 0.9.4) is out. This patch is a bug fix for a bug in mboxlist:mboxlist_autocreateinbox that causes segmentation fault in ltmpd if rcpt is in the form of & something. This bug was reported by Rob McMahon.
Jul, 16 2005 A bug in lmtpd.c:verify_user(), reported by Aaron Hope, that could potentially lead to a Cyrus segmentation fault has been fixed for Cyrus IMAPd 2.2.12. Upgrading the patch to version 0.9.3 for Cyrus IMAPd 2.2.12 is strongly recommended.
Feb, 16 2005 New releases of patches for Cyrus IMAPd 2.1.18 (version 0.9.3) and Cyrus IMAPd 2.2.12 (version 0.9.2) are out.
Jan, 19 2005: Bugfix release of patch for Cyrus IMAPd 2.2.10 is out. Please read the Changelog for more information on the changes.
Jan, 11 2005: New releases of the autocreate inbox patches for Cyrus IMAPd 2.1.17 (patch version 0.9.2) and Cyrus IMAPd 2.2.10 (patch version 0.9.0). Both versions contain the autosubscribe_all_sharedofolders new option and the autocreate sieve filter feature. Special thanks go to Simon Matter for his contribution in testing the patches and tracing some serious bugs.
Dec, 24 2004: New release of patch (version 0.9.1) for Cyrus IMAPd 2.1.17. It contains an one liner bug fix to the previous release. Oh, I almost forgot it. And merry Christmas to all!
Dec, 21 2004: New release of patch (version 0.9.0) for Cyrus IMAPd 2.1.17.
Nov, 24 2004: New release of patch cyrus-imapd-2.2.10-autocreate-0.1.diff for cyrus-imapd-2.2.10. This patch includes a small bugfix
Jul, 31 2004: There will be no release for the patches for cyrus imapd 2.2.8 since they are identical with the patches for cyrus-imapd-2.2.7. Just use those.
One may find detailed changelogs for Cyrus IMAPd 2.1.x,
Cyrus IMAPd 2.2.x and
Cyrus IMAPd 2.3.x
Before you download and install the autocreate patch read
README.autocreate for Cyrus IMAPd 2.1.x,
README.autocreate for Cyrus IMAPd 2.2.x or
README.autocreate for Cyrus IMAPd 2.3.x.
The patch may be downloaded from email.uoa.gr download site.
Virtual domains are supported by all versions of the patch for cyrus-imapd-2.2.1-BETA or later. However, it is not possible to declare different INBOX subfolders to be created or shared folders to be subscribed to for every domain. This is caused due to a limitation of Cyrus to define different per domain configuration files.
Things to be done are :
For contact information visit the contact page.