cyrus-imapd36: Updated MESSAGE and TODO files

[Matthias Petermann <mp%petermann-it.de@localhost>]

Module Name:	pkgsrc-wip
Committed By:	Matthias Petermann <mp%petermann-it.de@localhost>
Pushed By:	mp
Date:		Sat Feb 18 06:06:50 2023 +0100
Changeset:	16a959cf3200767f94c4d87d85c343b63e39d389

Modified Files:
	cyrus-imapd36/MESSAGE
	cyrus-imapd36/TODO

Log Message:
cyrus-imapd36: Updated MESSAGE and TODO files

Signed-off-by: Matthias Petermann <mp%petermann-it.de@localhost>

To see a diff of this commit:
https://wip.pkgsrc.org/cgi-bin/gitweb.cgi?p=pkgsrc-wip.git;a=commitdiff;h=16a959cf3200767f94c4d87d85c343b63e39d389

Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.

diffstat:
 cyrus-imapd36/MESSAGE | 16 ++++++++++++++++
 cyrus-imapd36/TODO    | 42 +++++++++---------------------------------
 2 files changed, 25 insertions(+), 33 deletions(-)

diffs:
diff --git a/cyrus-imapd36/MESSAGE b/cyrus-imapd36/MESSAGE
index fa139efedc..0fb3e36068 100644
--- a/cyrus-imapd36/MESSAGE
+++ b/cyrus-imapd36/MESSAGE
@@ -9,4 +9,20 @@ for more detailed instructions on setting up or upgrading the environment
 before starting the Cyrus IMAP server.  In particular, several services
 may need to be added to /etc/services.
 
+For users upgrading from 3.0.x < 3.6.0:
+
+In version 3.6 mailboxes and user metadata directories are now organized
+on disk by UUID rather then by mailbox name. Compatibility with existing
+layouts by mailbox name is maintained by the IMAP server. In addition to
+that, tooling is provided to support migrations. 
+
+Optionally the default can be changed back to mailbox name by adding to
+imapd.conf:
+
+	mailbox_legacy_dirs: yes
+
+Please refer the 3.6.0 release notes for further details about migrations:
+
+	https://www.cyrusimap.org/imap/download/release-notes/3.6/x/3.6.0.html
+
 ===========================================================================
diff --git a/cyrus-imapd36/TODO b/cyrus-imapd36/TODO
index 70a8ec6490..8d0f88a400 100644
--- a/cyrus-imapd36/TODO
+++ b/cyrus-imapd36/TODO
@@ -1,49 +1,25 @@
-Warning: this pkg is currently under construction. It was created as a
-copy of mail/cyrus-imap24. It cannot currently be expected that it can
-be built, let alone that it will work as expected. I plan to keep the
+Warning: this pkg is currently under construction. I plan to keep the
 pkg up to date here so that the progress is transparent. I am open to
-suggestions or active support.
+suggestions and active support.
 
 Done:
 
-- Make it build the most basic way
+- Updated to 3.6 (used 3.0 pkg from wip as base)
 
-- Make it install
+- Performed basic testing (installation on NetBSD 10.0_BETA,
+  configured a IMAP server with saslauthd ldap, created a mailbox,
+  configured the mailbox and caldav calendar in Thunderbird
 
-- Update PLIST (take care of ldap / http options)
-
-- Evaluation of the patches of the existing Cyrus-imap-pkgs and
-  their applicability for cyrus-imap 3
-
-- Review and adjustment of scripts / provided files (configuration
-  examples, man pages)
-
-- Performed first integration tests (client connection to IMAP,
-  authenticated via saslauthd with ldap)
-
-- Integrated documentation from source package into the package
+Next steps:
 
-- Possibly create further patches for cyrus-imap 3 (especially with
-  regard to the newly added functions CalDAV / CardDAV), if necessary
+- watch log files for suspious messages, clarify
 
-Next steps:
+- more testing, i.e. migrate my "production" 3.0.17 install to 3.6.1 
 
 - regenerate documentation at build time using Sphinx
 
 Bugs:
 
-- The way how the Dav-Patch is integrated. It is not a security patch
-  nor a patch that would be necessary to ensure the build.
-  In principle, it eliminates a functional deficiency, which may
-  not be a deficiency at all, but simply an implementation gap.
-  pkgsrc is therefore not the right place to deal with this problem,
-  I'm almost sure of that. Without this patch, the CalDAV / CardDAV
-  functionality cannot be used meaningfully for me, and in my
-  experience it will also be for most other users who want to
-  maintain a shared calendar, for example. I will definitely keep
-  an eye on what is going on upstream. In the meantime, I would like
-  to keep the patch here if there are no important reasons why.
-
 - Kerberos support, PostgreSQL and MySQL are currently not tested
 
 For questions, tips or offers of help you can contact me at mp%petermann-it.de@localhost