Re: Troubles syncing 'INBOX' directory

On Tue, Jun 17, 2014 at 05:55:18PM +0200, Bruno Gonzalez wrote: > On 14-06-17 17:40:14, Oswald Buddenhagen wrote: > > i meant > > Patterns * INBOX > > Not working either. > actually, Patterns INBOX* would be the correct config for you. but i don't think that would change anything. maybe you

[commit] isync_1_1_branch: bump version

commit 060430b23359d3cd8ad7b1531609c329ef22e9c4 Author: Oswald Buddenhagen Date: Sat Jun 28 14:27:04 2014 +0200 bump version configure.ac |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/configure.ac b/configure.ac index 3a9927d..5bccacf 100644 --- a/configure.ac

[commit] isync_1_1_branch: detect inconsistent state of highest assigned UID

commit 3d5539bb63b7f494f20357d7491d96228a432600 Author: Oswald Buddenhagen Date: Sat Jun 28 11:58:26 2014 +0200 detect inconsistent state of highest assigned UID the highest assigned UID must always be at least as high as the highest actually found UID, as otherwise we'd hand o

[commit] isync_1_1_branch: zero-terminate imap literals

commit 8513358e0a3f3d720b394251a018e46ed87ef262 Author: Oswald Buddenhagen Date: Sat Jun 28 11:04:41 2014 +0200 zero-terminate imap literals now that we properly support literals for strings, we must expect that the consumer code will use them as strings. amends fc77fe

Re: Isync 1.1.1 client->server update failure

Hi, Oswald. On Sat, Jun 28, 2014 at 11:38:54AM +0200, Oswald Buddenhagen wrote: > On Fri, Jun 27, 2014 at 12:41:49PM +0400, Evgeniy Berdnikov wrote: > > --- /var/mail/berd/.uidvalidity > > 1245525174 > > 400048 > >

Re: Isync 1.1.1 client->server update failure

On Fri, Jun 27, 2014 at 12:41:49PM +0400, Evgeniy Berdnikov wrote: > --- /var/mail/berd/.uidvalidity > 1245525174 > 400048 > > > --- /var/mail/berd/.mbsyncstate ---