Re: v3.0: IMAP hierarchy flexibility

2016-06-08 Thread Bron Gondwana via Cyrus-devel
On Thu, Jun 9, 2016, at 01:34, Thomas Jarosch via Cyrus-devel wrote: > Hi Bron, > > given the switch to UUIDs for the folder structure in the backend of v3.0*, > I'm wondering if the following folder structure can be supported: > > - Inbox/folder_below_inbox > - folder_next_to_inbox > - user/smi

Re: v3.0

2016-05-24 Thread qyb via Cyrus-devel
On Tue, May 24, 2016 at 9:12 AM, Nicola Nye via Cyrus-devel < cyrus-devel@lists.andrew.cmu.edu> wrote: > Thanks for this feedback! I've updated the docs to reflect it. > > Please let us know if you notice anything else. > >Nicola > > It's ok now.

Re: v3.0

2016-05-23 Thread Nicola Nye via Cyrus-devel
Thanks for this feedback! I've updated the docs to reflect it. Please let us know if you notice anything else. Nicola - Original message - From: "qyb via Cyrus-devel" To: cyrus-devel@lists.andrew.cmu.edu Subject: Re: v3.0 Date: Fri, 20 May 2016 00:01:08 +0800 we

Re: v3.0

2016-05-19 Thread qyb via Cyrus-devel
website doc error: https://cyrusimap.org/imap/developer/basicserver.html 7. Configuring Cyrus... I need create /etc/imapd.conf and create directory first, then run "sudo -u cyrus ./tools/mkimap"

Re: v3.0

2016-05-19 Thread qyb via Cyrus-devel
The libical2's default configure will put dynamic-library in /usr/local/lib/x86_64-linux-gnu directory. I rebuild it with "cmake -DCMAKE_INSTALL_PREFIX=/usr/local -DCMAKE_INSTALL_LIBDIR=/usr/local/lib", then it's ok now! Thanks. On Thu, May 19, 2016 at 1:24 PM, Anatoli wrote: > > > It works well

Re: v3.0

2016-05-19 Thread Ken Murchison via Cyrus-devel
pped with cyrus-imap and everything works as expected? Regards, Anatoli -Original Message- From: Anatoli [mailto:m...@anatoli.ws <mailto:m...@anatoli.ws>] Sent: Tuesday, April 19, 2016 03:39 To: cyrus-devel@list

Re: v3.0

2016-05-19 Thread Ken Murchison via Cyrus-devel
s as expected? Regards, Anatoli -Original Message- From: Anatoli [mailto:m...@anatoli.ws <mailto:m...@anatoli.ws>] Sent: Tuesday, April 19, 2016 03:39 To: cyrus-devel@lists.andrew.cmu.edu <mailto:cyrus-devel@lists.andrew.cmu.edu> Subject:

Re: v3.0

2016-05-18 Thread qyb via Cyrus-devel
t; iSchedule draft, but is it required? And should it be OpenDKIM only or any >> other DKIM package works too? >> >> >> And then there is an old warning (also happens in 2.5.7): >> >> configure: WARNING: Parts of com_err distribuion were found, but not >> compile_e

Re: v3.0

2016-05-18 Thread qyb via Cyrus-devel
_err from included sources. > > What should be installed/changed to avoid it? Or maybe the warning itself > should be converted to a notice as compile_et is shipped with cyrus-imap > and > everything works as expected? > > Regards, > Anatoli > > > -Original Message

RE: v3.0

2016-05-16 Thread Anatoli via Cyrus-devel
Sent: Tuesday, May 17, 2016 01:16 To: cyrus-devel@lists.andrew.cmu.edu Subject: Re: v3.0 I made a patch (configure.ac.patch, attached) [...] Please apply the fixes as you see fit. Thanks, those look good to me. I'll push it up, but I'll split it into separate commits for each piec

Re: v3.0

2016-05-16 Thread ellie timoney via Cyrus-devel
sage. >> >> Changed the type of message when com_err is absent or incomplete >> (lacking compile_et): from warning to notice, as this is the most >> common situation I believe (no or incomplete com_err) and it doesn't >> affect in anything the result of the bu

Re: v3.0

2016-05-16 Thread ellie timoney via Cyrus-devel
pport?") > introduced with my previous patch for --disable-squat option fix. This > typo doesn't affect anything (it's just a comment for config.h.in), > but seizing the opportunity of fixing Makefile.am, here it is. > > > With all this applied, I see no warning/errors for the

RE: v3.0

2016-05-16 Thread Anatoli via Cyrus-devel
out all of them, not allowing to continue to the make stage until all requirements are satisfied. Please apply the fixes as you see fit. Regards, Anatoli -Original Message- From: Cyrus-devel [mailto:cyrus-devel-bounces+me=anatoli...@lists.andrew.cmu.edu] On Behalf Of ellie timoney

Re: v3.0

2016-05-15 Thread ellie timoney via Cyrus-devel
yacc checking should be placed in the configure again, > inside the enable-sieve block. > > Regards, > Anatoli > > > -Original Message- > From: Ken Murchison [mailto:mu...@andrew.cmu.edu] > Sent: Wednesday, May 11, 2016 15:44 > To: Anatoli; cyrus-

RE: v3.0

2016-05-13 Thread Anatoli via Cyrus-devel
nt: Wednesday, May 11, 2016 15:44 To: Anatoli; cyrus-devel@lists.andrew.cmu.edu Subject: Re: v3.0 On 05/09/2016 02:57 AM, Anatoli via Cyrus-devel wrote: > Hi all, > > I'm testing v3.0.0 beta2. Here goes the feedback, this time for the build > process. > > 1. --disable-sq

Re: v3.0

2016-05-12 Thread ellie timoney via Cyrus-devel
not > compile_et. > configure: WARNING: Will build com_err from included sources. > > What should be installed/changed to avoid it? Or maybe the warning itself > should be converted to a notice as compile_et is shipped with cyrus-imap > and > everything works as expected? >

Re: v3.0

2016-05-11 Thread Ken Murchison via Cyrus-devel
the warning itself should be converted to a notice as compile_et is shipped with cyrus-imap and everything works as expected? Regards, Anatoli -Original Message- From: Anatoli [mailto:m...@anatoli.ws] Sent: Tuesday, April 19, 2016 03:39 To: cyrus-devel@lists.andrew.cmu.edu Subject: RE: v3

Re: v3.0

2016-05-10 Thread Ken Murchison via Cyrus-devel
toli.ws] Sent: Tuesday, April 19, 2016 03:39 To: cyrus-devel@lists.andrew.cmu.edu Subject: RE: v3.0 Hi Ellie, Thanks for the link! This is the information I was looking for. Great, there's a new beta! I'll test it these days and if it behaves reasonably well, I'll try to deploy it

RE: v3.0

2016-05-09 Thread Anatoli via Cyrus-devel
elf should be converted to a notice as compile_et is shipped with cyrus-imap and everything works as expected? Regards, Anatoli -Original Message- From: Anatoli [mailto:m...@anatoli.ws] Sent: Tuesday, April 19, 2016 03:39 To: cyrus-devel@lists.andrew.cmu.edu Subject: RE: v3.0 Hi Ellie, Thanks

RE: v3.0

2016-04-21 Thread Anatoli via Cyrus-devel
, April 21, 2016 12:34 To: Anatoli Cc: cyrus-devel@lists.andrew.cmu.edu Subject: RE: v3.0 On Wed, 20 Apr 2016, Anatoli via Cyrus-devel wrote: > The T199 actually mentions exactly this behavior. Why do you think that this > is not a bug? How is it supposed the specialuse flag should be set f

RE: v3.0

2016-04-21 Thread Leena Heino via Cyrus-devel
On Wed, 20 Apr 2016, Anatoli via Cyrus-devel wrote: The T199 actually mentions exactly this behavior. Why do you think that this is not a bug? How is it supposed the specialuse flag should be set from cyradm? OR, what does the specialuse property from getmd mean if it's not the same as SPECIAL-U

RE: v3.0

2016-04-20 Thread Anatoli via Cyrus-devel
y from getmd mean if it's not the same as SPECIAL-USE extension flag accessible via IMAP? Regards, Anatoli -Original Message- From: Cyrus-devel [mailto:cyrus-devel-bounces+me=anatoli...@lists.andrew.cmu.edu] On Behalf Of Leena Heino via Cyrus-devel Sent: Wednesday, April 20, 201

Re: v3.0

2016-04-20 Thread Leena Heino via Cyrus-devel
On Mon, 18 Apr 2016, ellie timoney via Cyrus-devel wrote: I'm personally interested in resolving the "specialuse flags not working from cyradm" (T199, 198, 191, 121; looks like still pending) issue Are these still issues? Or are they stale tasks that have been fixed but not closed? We've had

RE: v3.0

2016-04-19 Thread Anatoli via Cyrus-devel
up to each server implementation (section 3)). Regards, Anatoli -Original Message- From: Cyrus-devel [mailto:cyrus-devel-bounces+me=anatoli...@lists.andrew.cmu.edu] On Behalf Of ellie timoney via Cyrus-devel Sent: Sunday, April 17, 2016 22:37 To: cyrus-devel@lists.andrew.cmu.edu Subject

Re: v3.0

2016-04-17 Thread ellie timoney via Cyrus-devel
Hi Anatoli, > I'm quite interested in this release and I'd > like to help with testing, simple problems investigation and fixing, and > similar tasks, That would be greatly appreciated :) > but at least some insight to the current state of the > master is needed for that, i.e. how close it is to