Because of the sudden end-of-life of Fedora Core 4, I'm moving my mail
server from FC4 to a CentOS 4.4 box.
FC4 uses DB4 4.3.27.
CentOS 4.4 uses DB4 4.2.52.
What's the best way for me to downgrade the Cyrus DBs for this migration?
Thanks.
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
C
Simon Matter wrote:
Because of the sudden end-of-life of Fedora Core 4, I'm moving my mail
server from FC4 to a CentOS 4.4 box.
FC4 uses DB4 4.3.27.
CentOS 4.4 uses DB4 4.2.52.
What's the best way for me to downgrade the Cyrus DBs for this migration?
Convert all BerkeleyDBs on the FC4 box
Simon Matter wrote:
>>
>> Simon Matter wrote:
Because of the sudden end-of-life of Fedora Core 4, I'm moving my mail
server from FC4 to a CentOS 4.4 box.
FC4 uses DB4 4.3.27.
CentOS 4.4 uses DB4 4.2.52.
What's the best way for me to downgrade the Cyrus DBs
Simon Matter wrote:
I finally got a window of scheduled downtime to test this, and I'm
having problems. Here's what I did:
# /etc/init.d/cyrus-imapd stop
# db_checkpoint -v -1 -h /var/lib/imap/db
# db_recover -v -h /var/lib/imap/db
# rm db/*
# /usr/lib/cyrus-imapd/cvt_cyrusdb /var/lib/imap/del
We're running Cyrus IMAPD 2.2.3 from Fedora Core 2 and we're
having problems with timsieved in terms of it parsing scripts into
bytecode.
When using sieveshell on the following trivial script, we're getting
the following error:
# more testsieve
redirect "[EMAIL PROTECTED]";
# sieveshell --user=
I'm in the process of testing the upgrade from a CentOS 6 box running
2.3.16 to a CentOS 8 box running 3.0.7.
The upgrade has been less troublesome than expected, but I'm seeing a
strange problem with newly received mail being marked as "read" even
though they have not been opened by the clien
