Is there a way I can store cyrus imap mails encrypted. This may not be
a fully secure system
but I just need something so that a root logged in user cant trivially
read the files
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyr
All the databases are dumpable or convertable to flat format, which is
basically the same as dumping them!
Also - every version with skiplist is forwards compatible - you can convert to
skiplist and it will upgrade automatically.
Bron.
On Tue, Aug 25, 2015, at 07:14, Alvin Starr wrote:
> upgra
upgrading works best when the databases are the same.
If you end up having to destroy the databases and recreate information
using reconstruct then you lose information also.
Last migration I did I used imapsync but it was not a complex migration
so I was not that concerned about things like sha
I think that the key difference between using imapsync and upgrading
cyrus is the amount of states that will be lost.
I almost sure that with imapsync you cannot recreate:
1. Subscribed folders
2. Seen states for shared folders (also for INBOX if imapsync isn't used
properly)
3. Shared seen states
Am Montag, 24. August 2015, 16:29:55 schrieb Mogens Melander:
> It should be possible, using the cyrus admin account. But I'm
> sure there will be something about this in the imapsync docs.
cyrus <-> imapsync mini HOWTO
===
To migrate your postboxes from one to another cy
It should be possible, using the cyrus admin account. But I'm
sure there will be something about this in the imapsync docs.
On Mon, August 24, 2015 13:44, bs...@vsvinc.com wrote:
> Apologizes for the thread diversion here but I've been seeing a lot of
> discussion about using imapsync to migrate
> Am Montag, 24. August 2015, 07:44:42 schrieb bs...@vsvinc.com:
>> From what I have read in the documentation, you must have each user's
>> password.
> This is incorrect for cyrus.
>
>> Is there something I'm missing in the docs?
> It seem so.
>
> You can use a single cyrus admin user instead too
On 08/24/2015 08:44 AM, bs...@vsvinc.com wrote:
Apologizes for the thread diversion here but I've been seeing a lot
of discussion about using imapsync to migrate servers. From what I have
read in the documentation, you must have each user's password. How is
this possible in a business enviro
Am Montag, 24. August 2015, 07:44:42 schrieb bs...@vsvinc.com:
> From what I have read in the documentation, you must have each user's
> password.
This is incorrect for cyrus.
> Is there something I'm missing in the docs?
It seem so.
You can use a single cyrus admin user instead too which have
Apologizes for the thread diversion here but I've been seeing a lot of
discussion about using imapsync to migrate servers. From what I have read in
the documentation, you must have each user's password. How is this possible in
a business environment where you can't have (or shouldn't have) t
Yeah, that would have been my next move. But thankfully it won't be
necessary, Bron's suggestion worked: after I removed all old Berkeley
databases Cyrus worked fine. Thanks a lot Bron!
Now just need to figure out why on the new machine sendmail suddenly
doesn't seem to read userdb anymore and I c
Am Sonntag, den 23.08.2015, 20:36 +0200 schrieb Mogens Melander:
> For a task like this, I would use imapsync, a well documented,
> well supported and open source tool.
>
> https://github.com/imapsync/imapsync
I've used imapsync to migrate an internal server from 2.1.18 to 2.4.17
without any prob
12 matches
Mail list logo
