Active sync Front end
I have been getting requests to enable active sync on my cyrus mailserver. There are third party solutions like z-push but those dont seem to work on the default mail servers What can I use to enable activesync for cyrus Thanks Ram 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: Active sync Front end
On 5 November 2014 08:31, Ram r...@netcore.co.in wrote: I have been getting requests to enable active sync on my cyrus mailserver. There are third party solutions like z-push but those dont seem to work on the default mail servers What can I use to enable activesync for cyrus z-push works fine for me. 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
user rename and uidvalidity value
Hi, Can you please explain to me, why is a new value of uidvalidity generated when a user is renamed in cyrus_imapd? Rename: A001 rename user/a@bbb.cmailto:user/a@bbb.com user/x...@bbb.com Before rename: A001 select inbox * OK [CLOSED] Ok * 3 EXISTS * 0 RECENT * FLAGS (\Answered \Flagged \Draft \Deleted \Seen) * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen \*)] Ok * OK [UNSEEN 2] Ok * OK [UIDVALIDITY 1415092196] Ok * OK [UIDNEXT 4] Ok * OK [HIGHESTMODSEQ 5] Ok * OK [URLMECH INTERNAL] Ok A001 OK [READ-WRITE] Completed After rename: A001 select inbox * 3 EXISTS * 0 RECENT * FLAGS (\Answered \Flagged \Draft \Deleted \Seen) * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen \*)] Ok * OK [UNSEEN 2] Ok * OK [UIDVALIDITY 1415093437] Ok * OK [UIDNEXT 4] Ok * OK [HIGHESTMODSEQ 7] Ok * OK [URLMECH INTERNAL] Ok A001 OK [READ-WRITE] Completed Thank you in advance, Ondra This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you for understanding. 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: user rename and uidvalidity value
Hi partly diskussed in: https://bugzilla.mozilla.org/show_bug.cgi?id=365651#c4 snip --- ftp://ftp.rfc-editor.org/in-notes/rfc3501.txt 6.3.5. RENAME Command The value of the highest-used unique identifier of the old mailbox name MUST be preserved so that a new mailbox created with the same name will not reuse the identifiers of the former incarnation, UNLESS the new incarnation has a different unique identifier validity value. See the description of the UID command for more detail. If IMAP server returns same unique identifier validity value after rename, IMAP server MUST preserve highest-used unique identifier. snip --- the problem is, where to store the old highest-used unique identifier for the same mailboxname, if reused ?? the logical solution is to generate new uidvalidity for renamed mailbox, that guarantees, that in case of existing previous mailbox with the same name, that the change to other content is recognized .. Cheers Kleo On Wed, 5 Nov 2014, Hamada, Ondrej wrote: Hi, Can you please explain to me, why is a new value of uidvalidity generated when a user is renamed in cyrus_imapd? Rename: A001 rename user/a@bbb.cmailto:user/a@bbb.com user/x...@bbb.com Before rename: A001 select inbox * OK [CLOSED] Ok * 3 EXISTS * 0 RECENT * FLAGS (\Answered \Flagged \Draft \Deleted \Seen) * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen \*)] Ok * OK [UNSEEN 2] Ok * OK [UIDVALIDITY 1415092196] Ok * OK [UIDNEXT 4] Ok * OK [HIGHESTMODSEQ 5] Ok * OK [URLMECH INTERNAL] Ok A001 OK [READ-WRITE] Completed After rename: A001 select inbox * 3 EXISTS * 0 RECENT * FLAGS (\Answered \Flagged \Draft \Deleted \Seen) * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen \*)] Ok * OK [UNSEEN 2] Ok * OK [UIDVALIDITY 1415093437] Ok * OK [UIDNEXT 4] Ok * OK [HIGHESTMODSEQ 7] Ok * OK [URLMECH INTERNAL] Ok A001 OK [READ-WRITE] Completed Thank you in advance, Ondra This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you for understanding. -- _ | You have moved the mouse. # | Windows must be restarted for the changes to take effect. # | OK # ##/ ~~ ~~ ~~ ~~ ~~ ~~ ~~ Vladimir `KLEO' Klejch Kleo'at'netbox.cz ... ... ... ... 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: Active sync Front end
Am 05.11.2014 um 09:31 schrieb Ram: I have been getting requests to enable active sync on my cyrus mailserver. There are third party solutions like z-push but those dont seem to work on the default mail servers What can I use to enable activesync for cyrus Sogo and Horde/IMP can provide full Activesync support, also for calendars and contacts André 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: user rename and uidvalidity value
Yep, pretty much all that. Of course, we now (master branch) have tombstone records in mailboxes.db which do hold the old uidvalidity for a time. It's also not quite so hard a requirement as the RFC suggests - the RFC applies to what an authenticated user can see, and at least in theory, if you delete user B and then rename user A to user B, the password will be different, and the original user B will never be able to see those mailboxes - so it really doesn't matter that you reuse the UIDVALIDITY. So maybe renaming an entire user is a special case. But that would involve educating the Cyrus code about the fact that it's a user rename, right down to the low levels where the uidvalidity gets re-created. Bron. On Wed, Nov 5, 2014, at 10:00 PM, Vladimir Klejch wrote: Hi partly diskussed in: https://bugzilla.mozilla.org/show_bug.cgi?id=365651#c4 snip --- ftp://ftp.rfc-editor.org/in-notes/rfc3501.txt 6.3.5. RENAME Command The value of the highest-used unique identifier of the old mailbox name MUST be preserved so that a new mailbox created with the same name will not reuse the identifiers of the former incarnation, UNLESS the new incarnation has a different unique identifier validity value. See the description of the UID command for more detail. If IMAP server returns same unique identifier validity value after rename, IMAP server MUST preserve highest-used unique identifier. snip --- the problem is, where to store the old highest-used unique identifier for the same mailboxname, if reused ?? the logical solution is to generate new uidvalidity for renamed mailbox, that guarantees, that in case of existing previous mailbox with the same name, that the change to other content is recognized .. Cheers Kleo On Wed, 5 Nov 2014, Hamada, Ondrej wrote: Hi, Can you please explain to me, why is a new value of uidvalidity generated when a user is renamed in cyrus_imapd? Rename: A001 rename user/a@bbb.cmailto:user/a@bbb.com user/x...@bbb.com Before rename: A001 select inbox * OK [CLOSED] Ok * 3 EXISTS * 0 RECENT * FLAGS (\Answered \Flagged \Draft \Deleted \Seen) * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen \*)] Ok * OK [UNSEEN 2] Ok * OK [UIDVALIDITY 1415092196] Ok * OK [UIDNEXT 4] Ok * OK [HIGHESTMODSEQ 5] Ok * OK [URLMECH INTERNAL] Ok A001 OK [READ-WRITE] Completed After rename: A001 select inbox * 3 EXISTS * 0 RECENT * FLAGS (\Answered \Flagged \Draft \Deleted \Seen) * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen \*)] Ok * OK [UNSEEN 2] Ok * OK [UIDVALIDITY 1415093437] Ok * OK [UIDNEXT 4] Ok * OK [HIGHESTMODSEQ 7] Ok * OK [URLMECH INTERNAL] Ok A001 OK [READ-WRITE] Completed Thank you in advance, Ondra This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you for understanding. -- _ | You have moved the mouse. # | Windows must be restarted for the changes to take effect. # | OK # ##/ ~~ ~~ ~~ ~~ ~~ ~~ ~~ Vladimir `KLEO' KlejchKleo'at'netbox.cz ... ... ... ... 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: user rename and uidvalidity value
Thank you for clearing it up Let's imagine for a while that we handle the renaming of entire user and don't change the uidvalidity in such case - would it have any impact on replication (sync_client, sync_server)? Ondra -Original Message- From: info-cyrus-bounces+ondrej.hamada=acision@lists.andrew.cmu.edu [mailto:info-cyrus-bounces+ondrej.hamada=acision@lists.andrew.cmu.edu] On Behalf Of Bron Gondwana Sent: Wednesday, November 05, 2014 12:37 PM To: info-cyrus@lists.andrew.cmu.edu Subject: Re: user rename and uidvalidity value Yep, pretty much all that. Of course, we now (master branch) have tombstone records in mailboxes.db which do hold the old uidvalidity for a time. It's also not quite so hard a requirement as the RFC suggests - the RFC applies to what an authenticated user can see, and at least in theory, if you delete user B and then rename user A to user B, the password will be different, and the original user B will never be able to see those mailboxes - so it really doesn't matter that you reuse the UIDVALIDITY. So maybe renaming an entire user is a special case. But that would involve educating the Cyrus code about the fact that it's a user rename, right down to the low levels where the uidvalidity gets re-created. Bron. On Wed, Nov 5, 2014, at 10:00 PM, Vladimir Klejch wrote: Hi partly diskussed in: https://bugzilla.mozilla.org/show_bug.cgi?id=365651#c4 snip --- ftp://ftp.rfc-editor.org/in-notes/rfc3501.txt 6.3.5. RENAME Command The value of the highest-used unique identifier of the old mailbox name MUST be preserved so that a new mailbox created with the same name will not reuse the identifiers of the former incarnation, UNLESS the new incarnation has a different unique identifier validity value. See the description of the UID command for more detail. If IMAP server returns same unique identifier validity value after rename, IMAP server MUST preserve highest-used unique identifier. snip --- the problem is, where to store the old highest-used unique identifier for the same mailboxname, if reused ?? the logical solution is to generate new uidvalidity for renamed mailbox, that guarantees, that in case of existing previous mailbox with the same name, that the change to other content is recognized .. Cheers Kleo On Wed, 5 Nov 2014, Hamada, Ondrej wrote: Hi, Can you please explain to me, why is a new value of uidvalidity generated when a user is renamed in cyrus_imapd? Rename: A001 rename user/a@bbb.cmailto:user/a@bbb.com user/x...@bbb.com Before rename: A001 select inbox * OK [CLOSED] Ok * 3 EXISTS * 0 RECENT * FLAGS (\Answered \Flagged \Draft \Deleted \Seen) * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen \*)] Ok * OK [UNSEEN 2] Ok * OK [UIDVALIDITY 1415092196] Ok * OK [UIDNEXT 4] Ok * OK [HIGHESTMODSEQ 5] Ok * OK [URLMECH INTERNAL] Ok A001 OK [READ-WRITE] Completed After rename: A001 select inbox * 3 EXISTS * 0 RECENT * FLAGS (\Answered \Flagged \Draft \Deleted \Seen) * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen \*)] Ok * OK [UNSEEN 2] Ok * OK [UIDVALIDITY 1415093437] Ok * OK [UIDNEXT 4] Ok * OK [HIGHESTMODSEQ 7] Ok * OK [URLMECH INTERNAL] Ok A001 OK [READ-WRITE] Completed Thank you in advance, Ondra This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you for understanding. -- _ | You have moved the mouse. # | Windows must be restarted for the changes to take effect. # | OK # ##/ ~~ Vladimir `KLEO' Klejch Kleo'at'netbox.cz 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 This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to,
