On Thu, Oct 19, 2017 at 04:15:43PM +0000, Peter J. Philipp wrote: > Hi! > > Thanks, I won't lie. I did look at that page, but I was in a panic and > didn't look at it carefully enough. I did run the commands to lint the > config files but there was no output. But I should have been trying to > convert my databases from berkeley db but I realise now they aren't even > in bdb format: > > mercury$ for i in *.db; do hexdump -C $i | head -1; done > 00000000 a1 02 8b 0d 74 77 6f 73 6b 69 70 20 66 69 6c 65 |....twoskip > file| > 00000000 a1 02 8b 0d 74 77 6f 73 6b 69 70 20 66 69 6c 65 |....twoskip > file| > 00000000 a1 02 8b 0d 74 77 6f 73 6b 69 70 20 66 69 6c 65 |....twoskip > file| > 00000000 a1 02 8b 0d 74 77 6f 73 6b 69 70 20 66 69 6c 65 |....twoskip > file| > 00000000 a1 02 8b 0d 74 77 6f 73 6b 69 70 20 66 69 6c 65 |....twoskip > file| > > What I'm going to do what I had planned, was, to copy my imap stuff over > to another computer and upgrade that in all peace and taking my time. > Then perhaps I can go back to the major version 3. > > What I foolishly did was I did a pkg_add -u and expected everything to > still function without informing myself earlier. > > Thanks Antoine for the link again,
No problem. Keep me posted :-) > > -peter > > > On 10/19/17 17:55, Antoine Jacoutot wrote: > > On Mon, Oct 16, 2017 at 12:27:59PM +0000, Peter J. Philipp wrote: > >> Hi, > >> > >> I got these messages with the new 6.2 cyrus imapd: > >> > >> Oct 14 11:03:26 mercury imaps[55561]: client id sessionid=<CENSOR>: > >> "name" "Thunderbird" "version" "52.2.1" > >> Oct 14 11:03:26 mercury imaps[55561]: Fatal error: Internal error: > >> assertion failed: imap/message.c: 4286: !message_need(m, M_RECORD) > >> Oct 14 11:03:26 mercury master[70566]: process type:SERVICE name:imaps > >> path:/usr/local/cyrus/libexec/imapd age:0.542s pid:55561 exited, status 75 > >> > >> > >> I didnt know what to do with this, so I ran "reconstruct -O -V max" as > >> _cyrus user, but that had the same failure in an assert failure. > >> > >> So I decided to downgrade after upgrading to a new version wasn't > >> possible. I put the 6.1 /usr/ports/mail/cyrus_imapd in the 6.2 tree > >> (after backign up the 6.2 cyrus_imapd) and made install after > >> pkg_delete'ing the 6.2 cyrus_imapd. It worked I, I made sure that that > >> I ran the reconstruct again and it did mention there was a diff version > >> and probably fixed it. Either way I have my important mail running > >> again and wanted to share. > >> > >> If I want to go back to cyrus imapd version 3.x.x what should I look > >> for? or wait for? > >> > >> If anyone has had the same problems perhaps they took greater care than > >> me to get this going otherwise the downgrade seems to have worked for me. > > Hi. > > > > I can't reproduce the issue. > > Did you properly convert your old DBs in case they were of type Berkeley? > > https://cyrusimap.org/imap/download/upgrade.html > > > -- Antoine
