G'day,I've got an old Cyrus 2.4.x install that I want to move to a more modern cyrus.
Reading through this : https://www.cyrusimap.org/3.0/imap/download/upgrade.html#upgrade-by-replicatingI have used unix sep, so in place is a no-no. (why it wasn't the default in the first place?!)
One of the things it says is to check with mbexamine as to the format of the emails.
Here's an example : Examining user/carl@XXXXXX... Mailbox Header Info: Path to mailbox: /var/spool/imap/domain/XXXXXXXX/user/carl Mailbox ACL: carl@XXXXXXX lrswipcda Unique ID: 44e86fb34ba0c00fUser Flags: $Label5 Junk NonJunk $Forwarded $MDNSent $label1 $label2 $label3 $
label4 Index Header Info: Generation Number: 4711 Minor Version: 12 Header Size: 128 bytes Record Size: 96 bytes Number of Messages: 10787 Mailbox Size: 950346472 bytes Last Append Date: (1631144700) Thu Sep 9 09:45:00 2021 UIDValidity: 1268826127 Last UID: 709480 Deleted: 0 Answered: 1114 Flagged: 1 Mailbox Options: POP3_NEW_UIDL Last POP3 Login: (0) Thu Jan 1 10:00:00 1970 Highest Mod Sequence: 1450920 Message Info: 000001> UID:00099225 INT_DATE:1385363079 SENTDATE:1385341200 SIZE:1758 > HDRSIZE:1556 LASTUPD :1385371111 SYSFLAGS:00000011 LINES:12> CACHEVER:3 GUID:df791095ea91d83e5aecdfc4cb3f3bcb98128cd1 MODSEQ:135015
> USERFLAGS: 00000000 00000000 00000000 00000000 and then it goes into each email The minor version is good! The doco says :If your old installation contains mailboxes or messages that are older than 2.4, they may not have GUID fields in their indexes (index version too old), or they may have their GUID field set to zero. 3.0 will not accept message replications without valid matching GUIDs, so you need to fix this on your old installation first.
Is the GUID field in the "Message Info" section the one that matters? Is it safe to assume that if the oldest messages I can find, have this, that the whole thing will be ok?
Thank you Carl
Attachment:
OpenPGP_0xCD6A3B668DA72C7C.asc
Description: OpenPGP public key
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature
<<< multipart/mixed; boundary="WHeMC1xE29cJChYYQ7koWv1jejNlFHm4P"; protected-headers="v1"; boundary="----------=_1631145064-612923-1"; charset="UTF-8": Unrecognized >>>
