Store data encrypted in maildir
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-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Migrate from 2.2.13 to 2.4.17 disasters
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: > 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 shared states. > > Is it possible to dump all the context of a working cyrus install in a > database independent format so the it can be re-imported? > > Over the years I have found lots of packages that have complex internal > states that cannot be dumped in an independent format. > The user is left limited upgrade options. > > > > On 08/24/2015 04:49 PM, Giuseppe Ravasio (LU) wrote: > > 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 > > 4. Email flags (also for INBOX if imapsync isn't used properly) > > 5. Custom permissions > > > > Therefore I think that imapsync is not the best choice for corporate > > email servers or big installations. > > > > Giuseppe > > > > On 08/24/2015 01:44 PM, 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 environment where you can't have (or > >> shouldn't have) that information because of legal/privacy/ethical > >> reasons? Is there something I'm missing in the docs? > >> > >> Brian > >> > >> > >> *From:* Marcus Schopen > >> *Sent:* Aug 24, 2015 3:54 AM > >> *To:* mog...@fumlersoft.dk > >> *Cc:* info-cyrus@lists.andrew.cmu.edu > >> *Subject:* Re: Migrate from 2.2.13 to 2.4.17 disasters > >> > >> 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 problems. Good tool. > >> > >> Ciao! > >> > >> > >> > >> Cyrus Home Page: http://www.cyrusimap.org/ > >> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ > >> To Unsubscribe: > >> https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus > >> > >> > >> > >> > >> Cyrus Home Page: http://www.cyrusimap.org/ > >> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ > >> To Unsubscribe: > >> https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus > >> > > > > Cyrus Home Page: http://www.cyrusimap.org/ > > List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ > > To Unsubscribe: > > https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus > > > -- > Alvin Starr || voice: (905)513-7688 > Netvel Inc. || Cell: (416)806-0133 > al...@netvel.net || > > > > Cyrus Home Page: http://www.cyrusimap.org/ > List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ > To Unsubscribe: > https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus -- Bron Gondwana br...@fastmail.fm Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Migrate from 2.2.13 to 2.4.17 disasters
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 shared states. Is it possible to dump all the context of a working cyrus install in a database independent format so the it can be re-imported? Over the years I have found lots of packages that have complex internal states that cannot be dumped in an independent format. The user is left limited upgrade options. On 08/24/2015 04:49 PM, Giuseppe Ravasio (LU) wrote: > 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 > 4. Email flags (also for INBOX if imapsync isn't used properly) > 5. Custom permissions > > Therefore I think that imapsync is not the best choice for corporate > email servers or big installations. > > Giuseppe > > On 08/24/2015 01:44 PM, 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 environment where you can't have (or >> shouldn't have) that information because of legal/privacy/ethical >> reasons? Is there something I'm missing in the docs? >> >> Brian >> >> >> *From:* Marcus Schopen >> *Sent:* Aug 24, 2015 3:54 AM >> *To:* mog...@fumlersoft.dk >> *Cc:* info-cyrus@lists.andrew.cmu.edu >> *Subject:* Re: Migrate from 2.2.13 to 2.4.17 disasters >> >> 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 problems. Good tool. >> >> Ciao! >> >> >> >> Cyrus Home Page: http://www.cyrusimap.org/ >> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ >> To Unsubscribe: >> https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus >> >> >> >> >> Cyrus Home Page: http://www.cyrusimap.org/ >> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ >> To Unsubscribe: >> https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus >> > > Cyrus Home Page: http://www.cyrusimap.org/ > List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ > To Unsubscribe: > https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus -- Alvin Starr || voice: (905)513-7688 Netvel Inc. || Cell: (416)806-0133 al...@netvel.net || Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Migrate from 2.2.13 to 2.4.17 disasters
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 4. Email flags (also for INBOX if imapsync isn't used properly) 5. Custom permissions Therefore I think that imapsync is not the best choice for corporate email servers or big installations. Giuseppe On 08/24/2015 01:44 PM, 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 environment where you can't have (or > shouldn't have) that information because of legal/privacy/ethical > reasons? Is there something I'm missing in the docs? > > Brian > > > *From:* Marcus Schopen > *Sent:* Aug 24, 2015 3:54 AM > *To:* mog...@fumlersoft.dk > *Cc:* info-cyrus@lists.andrew.cmu.edu > *Subject:* Re: Migrate from 2.2.13 to 2.4.17 disasters > > 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 problems. Good tool. > > Ciao! > > > > Cyrus Home Page: http://www.cyrusimap.org/ > List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ > To Unsubscribe: > https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus > > > > > Cyrus Home Page: http://www.cyrusimap.org/ > List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ > To Unsubscribe: > https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus > Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Migrate from 2.2.13 to 2.4.17 disasters
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 cyrus or IMAP host by IMAP: in your imapd.conf set a cyrus admin user if not done til now: admins: cyrus and make sure it has a password / is available by cyrus auth subsys as other cyrus users. Use imapsync with --authuser1 /source host) --authuser2 (target host) instead of the mailbox account users: ---user[1|2] after experiments i have found that the following additional imapsync parameters could be helpful in a site migration scenario: --addheader -> this makes sure that the timestamps of the mail is the original one if all your copied messages are shown with a new timestamp / date from "today" in the target mailbox. imapsync uses the timestamps from the original mail headers instead which are "much closer" the original date. --usecache -> could speed up the migration significantly. --timeout -> set this higher if you get timeout problems. The nice thing is that you can restart the whole process anytime again later if the migration stops or connections breaks. You may use this script as a starting point. It is a bit more generic as it allows / accepts different account names on source / target site (may be simplified further): #!/bin/bash # # sync old imap account with new one # on syndicat.com mailhost # (c) 2015 Niels Dettenbach # # GPL licensed # usage="usage: imapsync_intrans " imapsync=`which imapsync` if [ $imapsync ] then if [ $5 ] then echo "start IMAP sync $2 <-> $4:" $imapsync \ --host1 $1 --authuser1 $2 --password1 $3 \ --host2 $6 --authuser2 $4 --password2 $5 \ --addheader --ssl1 --timeout 15 else echo $usage fi else echo "no imapsync found!" fi -- --- Niels Dettenbach Syndicat IT & Internet http://www.syndicat.com PGP: https://syndicat.com/pub_key.asc --- signature.asc Description: This is a digitally signed message part. Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Migrate from 2.2.13 to 2.4.17 disasters
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 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) that information because of legal/privacy/ethical reasons? Is there > something I'm missing in the docs? > > Brian > > > From: Marcus Schopen > Sent: Aug 24, 2015 3:54 AM > To: mog...@fumlersoft.dk > Cc: info-cyrus@lists.andrew.cmu.edu > Subject: Re: Migrate from 2.2.13 to 2.4.17 disasters > > 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 problems. Good tool. > > Ciao! > > > > Cyrus Home Page: http://www.cyrusimap.org/ > List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ > To Unsubscribe: > https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus > -- Mogens Melander +66 8701 33224 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Migrate from 2.2.13 to 2.4.17 disasters
> 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 access to any > account content usually - imapsync provides this authentication scheme (by > an > option "auth-user" or so) too... And also check the proxyservers option in imapd.conf which can be used to "...to proxy for other users..." Regards, Simon Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Migrate from 2.2.13 to 2.4.17 disasters
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 environment where you can't have (or shouldn't have) that information because of legal/privacy/ethical reasons? Is there something I'm missing in the docs? Brian I believe authuser is used. From man page: You may authenticate as one user (typically an admin user), but be authorized as someone else, which means you don’t need to know every user’s personal password. Specify --authuser1 "adminuser" to enable this on host1. In this case, --authmech1 PLAIN will be used by default since it is the only way to go for now. So don’t use --authmech1 SOMETHING with --authuser1 "adminuser", it will not work. Same behavior with the --authuser2 option. *From:* Marcus Schopen *Sent:* Aug 24, 2015 3:54 AM *To:* mog...@fumlersoft.dk *Cc:* info-cyrus@lists.andrew.cmu.edu *Subject:* Re: Migrate from 2.2.13 to 2.4.17 disasters 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 problems. Good tool. Ciao! Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus <> Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Migrate from 2.2.13 to 2.4.17 disasters
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 access to any account content usually - imapsync provides this authentication scheme (by an option "auth-user" or so) too... hth cheerioh, Niels. -- --- Niels Dettenbach Syndicat IT & Internet http://www.syndicat.com PGP: https://syndicat.com/pub_key.asc --- signature.asc Description: This is a digitally signed message part. Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Migrate from 2.2.13 to 2.4.17 disasters
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) that information because of legal/privacy/ethical reasons? Is there something I'm missing in the docs? Brian From: Marcus Schopen Sent: Aug 24, 2015 3:54 AM To: mog...@fumlersoft.dk Cc: info-cyrus@lists.andrew.cmu.edu Subject: Re: Migrate from 2.2.13 to 2.4.17 disasters 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 problems. Good tool. Ciao! Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus smime.p7s Description: S/MIME cryptographic signature Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Migrate from 2.2.13 to 2.4.17 disasters
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 can complete the migration ;-) KR Stefan On 08/24/15 09:51, Marcus Schopen wrote: > 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 problems. Good tool. > > Ciao! > > > > Cyrus Home Page: http://www.cyrusimap.org/ > List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ > To Unsubscribe: > https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Migrate from 2.2.13 to 2.4.17 disasters
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 problems. Good tool. Ciao! Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
