[commit] (v1.0.5), (v1.0.6): backport: give the implicitly created imap account config the name of

2016-11-05 Thread Oswald Buddenhagen
commit d2ccc93584849a2981a5194c4d31b0c5617d3ee1 Author: Oswald Buddenhagen Date: Sun Apr 13 09:57:27 2008 + backport: give the implicitly created imap account config the name of the store. src/drv_imap.c |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/src

[commit] (v1.0.3), (v1.0.4), (v1.0.5), (v1.0.6): backport: less confusing uid ranges in debug

2016-11-05 Thread Oswald Buddenhagen
commit 534ccb326aa76c522b41729ea0c9ced931ec17f4 Author: Oswald Buddenhagen Date: Tue Jan 31 15:16:27 2006 + backport: less confusing uid ranges in debug src/sync.c |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/sync.c b/src/sync.c index 3722f01

[commit] (v1.0.4), (v1.0.5), (v1.0.6): backport: don't overlook 2nd and later single-letter options in last

2016-11-05 Thread Oswald Buddenhagen
commit e161af47bbe89ac4d6ac8a050f7e1f90a624d19e Author: Oswald Buddenhagen Date: Sat Feb 23 09:22:06 2008 + backport: don't overlook 2nd and later single-letter options in last argument. src/main.c |4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git

[commit] (v1.0.3), (v1.0.4), (v1.0.5), (v1.0.6): another attempt at working around glibc breakage.

2016-11-05 Thread Oswald Buddenhagen
commit b6c6299ea646ac07e6b6b4914fd64ba898d5febf Author: Oswald Buddenhagen Date: Mon Jul 31 05:31:17 2006 + another attempt at working around glibc breakage. src/drv_maildir.c |9 - 1 files changed, 4 insertions(+), 5 deletions(-) diff --git a/src/drv_maildir.c b/src

[commit] (v1.0.3), (v1.0.4), (v1.0.5), (v1.0.6): backport: compile fixes

2016-11-05 Thread Oswald Buddenhagen
commit 63c065a12738b0fc2531516a21dc56f8a367db28 Author: Oswald Buddenhagen Date: Tue Jan 31 15:15:00 2006 + backport: compile fixes configure.in |1 + src/drv_imap.c |4 2 files changed, 5 insertions(+), 0 deletions(-) diff --git a/configure.in b/configure.in index

[commit] (v1.0.4), (v1.0.5), (v1.0.6): backport: reverse-map to INBOX when encountered during listing.

2016-11-05 Thread Oswald Buddenhagen
commit 43f23fb1808acdfe5fe229cf9eb689324069e3dc Author: Oswald Buddenhagen Date: Sat Nov 18 13:17:31 2006 + backport: reverse-map to INBOX when encountered during listing. src/drv_maildir.c |6 -- 1 files changed, 4 insertions(+), 2 deletions(-) diff --git a/src

[commit] tag 'v1.0.2' re-created

2016-11-05 Thread Oswald Buddenhagen
The tag 'v1.0.2', previously at d7b8621, has been re-created at 3f1009a. -- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parall

Re: [commit] tag 'v1.0.2' re-created

2016-11-05 Thread Oswald Buddenhagen
On Sat, Nov 05, 2016 at 01:46:43PM +, Oswald Buddenhagen wrote: > The tag 'v1.0.2', previously at d7b8621, has been re-created at > 3f1009a. > the tag was wrong for a decade and nobody noticed. :D

branches renamed (Re: [commit] (v1.1.3): bump version)

2016-11-05 Thread Oswald Buddenhagen
something is evidently wrong with my post-receive hook - these mails refer to extant commits on living branches, so there should never have been notifications about them. :-/ anyway, as you may have noticed, i renamed all refs to something which ... requires less typing, mostly. if you have local

[commit] master: use a temporary for sanity

2016-11-05 Thread Oswald Buddenhagen
commit 5b0c8cfa6069ed7fe7957b45e0df4a2c097f8e1e Author: Oswald Buddenhagen Date: Sat Nov 5 18:16:43 2016 +0100 use a temporary for sanity src/sync.c | 23 --- 1 files changed, 12 insertions(+), 11 deletions(-) diff --git a/src/sync.c b/src/sync.c index f74f384

[commit] master: wrap message trashing into simple transactions

2016-11-05 Thread Oswald Buddenhagen
commit b63f169c5781b7bb886c0bd922945aeba5dd6da0 Author: Oswald Buddenhagen Date: Fri Nov 4 21:23:39 2016 +0100 wrap message trashing into simple transactions trashing many messages at once inevitably overtaxes m$ exchange, and the connection breaks. without any progress

[commit] master: pre-sort exception list passed to driver->load_box()

2016-11-05 Thread Oswald Buddenhagen
commit ae95490d5256372ad25ca1be5d7f7d1bfad051f6 Author: Oswald Buddenhagen Date: Fri Nov 4 21:09:02 2016 +0100 pre-sort exception list passed to driver->load_box() ... and use that to optimize the maildir driver somewhat. src/common.h |1 + src/drv_imap.c|

[commit] master: abstract growable arrays somewhat

2016-11-05 Thread Oswald Buddenhagen
commit 7b567164fff524b8d9ddbe09a8ffa78f66c6f8b5 Author: Oswald Buddenhagen Date: Fri Nov 4 21:48:58 2016 +0100 abstract growable arrays somewhat ... and sneak in a C99 requirement on the way. just because. configure.ac |4 +- src/common.h | 31

[commit] master: fix SubFolders style Maildir++

2016-11-05 Thread Oswald Buddenhagen
commit 0f24ca31b5fafe5228d0e99f460f1c823121b296 Author: Oswald Buddenhagen Date: Fri Nov 4 16:21:09 2016 +0100 fix SubFolders style Maildir++ turns out i misread the spec in a subtle way: while all other folders are physically nested under INBOX, the IMAP view puts them at the

[commit] branch 'wip/ignoreInboxCase' reset

2016-11-05 Thread Oswald Buddenhagen
The branch 'wip/ignoreInboxCase', previously at 6cc72b4, has been rewound by 57 revision(s) and subsequently fast-forwarded by 63 revision(s) to 4288064. -- Developer Access Program for Intel Xeon Phi Processors Access to

[commit] branch 'wip/inboxStrictness' reset

2016-11-05 Thread Oswald Buddenhagen
The branch 'wip/inboxStrictness', previously at 257f351, has been rewound by 58 revision(s) and subsequently fast-forwarded by 63 revision(s) to e2a3eec. -- Developer Access Program for Intel Xeon Phi Processors Access to

[commit] branch 'wip/placeholders' created

2016-11-05 Thread Oswald Buddenhagen
The branch 'wip/placeholders' has been created at 05db75c. -- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE.

[commit] branch 'wip/socket-debug' reset

2016-11-05 Thread Oswald Buddenhagen
The branch 'wip/socket-debug', previously at 7595196, has been rewound by 2 revision(s) and subsequently fast-forwarded by 86 revision(s) to 984a89c. -- Developer Access Program for Intel Xeon Phi Processors Access to Inte

[commit] branch 'wip/server-refactor' created

2016-11-05 Thread Oswald Buddenhagen
The branch 'wip/server-refactor' has been created at f06691c. -- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio X

[commit] master: wrap message trashing into simple transactions

2016-11-06 Thread Oswald Buddenhagen
commit b4d6e8fdedda0f65c7de9f7e2bfda17cfe372f76 Author: Oswald Buddenhagen Date: Fri Nov 4 21:23:39 2016 +0100 wrap message trashing into simple transactions trashing many messages at once inevitably overtaxes m$ exchange, and the connection breaks. without any progress

[commit] branch 'master' rewound

2016-11-06 Thread Oswald Buddenhagen
The branch 'master', previously at b63f169, has been rewound by 1 revision(s) to 5b0c8cf. -- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one yea

[commit] branch 'wip/placeholders' reset

2016-11-06 Thread Oswald Buddenhagen
The branch 'wip/placeholders', previously at 05db75c, has been rewound by 10 revision(s) and subsequently fast-forwarded by 10 revision(s) to 9a4d939. -- Developer Access Program for Intel Xeon Phi Processors Access to Int

[commit] branch 'wip/socket-debug' reset

2016-11-06 Thread Oswald Buddenhagen
The branch 'wip/socket-debug', previously at 984a89c, has been rewound by 4 revision(s) and subsequently fast-forwarded by 4 revision(s) to f51f919. -- Developer Access Program for Intel Xeon Phi Processors Access to Intel

[commit] branch 'master' rewound

2016-11-06 Thread Oswald Buddenhagen
The branch 'master', previously at b4d6e8f, has been rewound by 1 revision(s) to 5b0c8cf. -- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one yea

[commit] master: wrap message trashing into simple transactions

2016-11-06 Thread Oswald Buddenhagen
commit 2bba9b903c7a4f26bd30cf9aac19b9bfd458916c Author: Oswald Buddenhagen Date: Fri Nov 4 21:23:39 2016 +0100 wrap message trashing into simple transactions trashing many messages at once inevitably overtaxes m$ exchange, and the connection breaks. without any progress

[commit] branch 'wip/uidval-recovery' created

2016-11-06 Thread Oswald Buddenhagen
The branch 'wip/uidval-recovery' has been created at 9cd378d. -- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio X

[commit] branch 'wip/uidval-recovery' reset

2016-11-13 Thread Oswald Buddenhagen
The branch 'wip/uidval-recovery', previously at 9cd378d, has been rewound by 1 revision(s) and subsequently fast-forwarded by 10 revision(s) to 1335ca3. -- Developer Access Program for Intel Xeon Phi Processors Access to I

Re: [commit] branch 'wip/uidval-recovery' reset

2016-11-13 Thread Oswald Buddenhagen
On Sun, Nov 13, 2016 at 09:50:07PM +, Oswald Buddenhagen wrote: > The branch 'wip/uidval-recovery', previously at 9cd378d, has been > rewound by 1 revision(s) and subsequently fast-forwarded by 10 > revision(s) to 1335ca3. this is now mostly complete and just needs some

Re: Error: channel gmail: master [Gmail]/All Mail cannot be opened.

2016-11-15 Thread Oswald Buddenhagen
On Mon, Nov 14, 2016 at 11:58:51PM +0100, Felix E. Klee wrote: > Error: channel gmail: master [Gmail]/All Mail cannot be opened. > i can't see anything obviously wrong with the config and output up to here. try adding -Dmn to the command line, maybe that will reveal enough. --

Re: Failing to sync all mail in folder

2016-11-20 Thread Oswald Buddenhagen
On Tue, Nov 15, 2016 at 06:28:29PM +, Steve George wrote: > For testing I used MaxMessages 400, so I think that's why it's 'stuck' at > only > downloading 400 messages. Even if I put in 'MaxMessages 500' it won't > actually > download them, and removing it completely doesn't download all me

Re: `maxuid' issues in src/drv_imap.c

2016-11-20 Thread Oswald Buddenhagen
On Thu, Nov 17, 2016 at 11:19:28PM +0800, Casper Ti. Vector wrote: > When querying the imap mailbox for all messages with UID in [1,inf], > isync currently hardcodes the upper limit to 10, which can > actually be exceeded, which results in missing messages on the slave. > > This is not me

Re: `maxuid' issues in src/drv_imap.c

2016-11-24 Thread Oswald Buddenhagen
On Thu, Nov 24, 2016 at 08:12:29PM +0800, Casper Ti. Vector wrote: > On Sun, Nov 20, 2016 at 11:45:52AM +0100, Oswald Buddenhagen wrote: > > maybe mail me the output of a run with -Dn for a closer look. > > Done in private mail. > > > the 1e9 was just chosen to make

Re: Sasl: No worthy mechs found

2016-12-02 Thread Oswald Buddenhagen
On Fri, Dec 02, 2016 at 03:47:01AM +, david wen riccardi-zhu wrote: > Glad to hear! I'd made the same assumption. > Not sure if something is broken, > sounds like it. a -Dn dump from such a failing session would be interesting.

Re: empty line in output of -l

2016-12-02 Thread Oswald Buddenhagen
On Thu, Dec 01, 2016 at 11:35:16AM +0100, Peter P. wrote: > after some more research I think I can answer this for myself. It seems > the first block is the local (slave) folders, the second block the > remote (master) folders. > nah, this sounds totally wrong. the folder mapping must be somehow in

Re: different behavior between 1.2.1 and 1.1.2

2016-12-02 Thread Oswald Buddenhagen
On Thu, Dec 01, 2016 at 12:14:21PM +0100, Peter P. wrote: > I assume that the way the config options have changed, > yes, there is this item in the NEWS file: > > An IMAP Path/NAMESPACE rooted in INBOX won't be handled specially > > any more. This means that some Patterns may need adjustment. fr

[commit] branch '1.2' fast-forwarded

2016-12-03 Thread Oswald Buddenhagen
The branch '1.2', previously at 41308e4, has been fast-forwarded by 2 revision(s) to bc51d02. -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot

Re: Sasl: No worthy mechs found

2016-12-03 Thread Oswald Buddenhagen
On Fri, Dec 02, 2016 at 12:40:34PM +, david wen riccardi-zhu wrote: > Connection is now encrypted > * OK IMAP4 ready > >>> 1 CAPABILITY > * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS IDLE AUTH=PLAIN > 1 OK completed > Logging in... > IMAP error: authentication mechanism PLAIN is not

Re: Sasl: No worthy mechs found

2016-12-03 Thread Oswald Buddenhagen
On Sat, Dec 03, 2016 at 05:37:47PM +0100, Oswald Buddenhagen wrote: > peter's oringinal problem is probably actually expected behavior: > when the connection is not encrypted, > actually, nonsense, the -V log says it is encrypted. then the next guess would be that libsasl2-

[commit] 1.2: be more helpful when no SASL mechanisms are available

2016-12-03 Thread Oswald Buddenhagen
commit fdb03b91f2471ebc1ee715c78911c8a1085791d1 Author: Oswald Buddenhagen Date: Sat Dec 3 20:58:23 2016 +0100 be more helpful when no SASL mechanisms are available src/drv_imap.c |9 + 1 files changed, 9 insertions(+), 0 deletions(-) diff --git a/src/drv_imap.c b/src

[commit] 1.2: fix LOGIN in SASL builds

2016-12-03 Thread Oswald Buddenhagen
commit 2f91e22371fb2b7054e1576f6f85bde429cefec5 Author: Oswald Buddenhagen Date: Sat Dec 3 20:58:16 2016 +0100 fix LOGIN in SASL builds if AuthMechs includes more than just LOGIN and the server announces any AUTH= mechanism, we try SASL. but that can still fail to find any

[commit] 1.2: make * not match LOGIN even in non-SSL builds

2016-12-03 Thread Oswald Buddenhagen
commit 1b235d3d466afea7d41d60d12fb96c4a83b2671e Author: Oswald Buddenhagen Date: Sat Dec 3 20:00:38 2016 +0100 make * not match LOGIN even in non-SSL builds this is consistent with the plain text transmission warning below. src/drv_imap.c |2 ++ 1 files changed, 2 insertions

[commit] 1.2: inform user if LOGIN was skipped because of missing SSL

2016-12-03 Thread Oswald Buddenhagen
commit 1a707ab1563c8651e5ced0babf344baab6dad039 Author: Oswald Buddenhagen Date: Sat Dec 3 19:18:12 2016 +0100 inform user if LOGIN was skipped because of missing SSL 'AuthMechs *' technically includes LOGIN, so it is a bit unintuitive when it's still

Re: Sasl: No worthy mechs found

2016-12-04 Thread Oswald Buddenhagen
On Sun, Dec 04, 2016 at 04:21:54AM +0100, Peter P. wrote: > Oswald Buddenhagen [2016-12-03 18:03]: > > then the next guess would be that libsasl2-modules is not installed. > > At least, on my system, libsasl2-modules is installed. > yeah, while testing my fixes, i found that

[commit] 1.2: validate NAMESPACE response earlier

2016-12-04 Thread Oswald Buddenhagen
commit 03e25db3b8e5e938f1bb1009d747514b1315cae7 Author: Oswald Buddenhagen Date: Sun Dec 4 11:14:34 2016 +0100 validate NAMESPACE response earlier ... and don't silently fail later on. src/drv_imap.c | 37 ++--- 1 files changed, 26 inser

[commit] 1.2: accept NAMESPACE responses without hierarchy delimiter

2016-12-04 Thread Oswald Buddenhagen
commit ef0e7fdd3e921d612220a830436bb9862bca61ac Author: Oswald Buddenhagen Date: Sun Dec 4 11:23:47 2016 +0100 accept NAMESPACE responses without hierarchy delimiter RFC2342 states that the delimiter may be NIL, which some servers apparently actually make use of

Re: SSL connection error

2016-12-07 Thread Oswald Buddenhagen
On Tue, Dec 06, 2016 at 12:40:07PM +0100, Claus-Michael Schlesinger wrote: > Is there anything I can do on my side to fix this problem? > try pulling from git 1.2 or master branch - i fixed that error message somewhat recently. that won't fix the problem, but at least it should be better diagnosab

Re: SSL connection error

2016-12-08 Thread Oswald Buddenhagen
On Wed, Dec 07, 2016 at 12:11:35PM +0100, Claus-Michael Schlesinger wrote: > SSL error connecting mbox.uni-stuttgart.de (129.69.1.9:996): unable to get > local issuer certificate > > Connecting with openssl s_client still works fine. > this suggests that mbsync is for some reason using different

Re: SSL connection error

2016-12-08 Thread Oswald Buddenhagen
On Thu, Dec 08, 2016 at 03:56:32PM +0100, Claus-Michael Schlesinger wrote: > it seems that the authentication error might still be due to the ssl problem. > no, that's unrelated. ssl works at a different layer than the authentication. it appears that SASL PLAIN authentication isn't working with thi

[commit] 1.2: silence bogus [-Wmaybe-uninitialized] with -O0/-O1/-Os

2016-12-11 Thread Oswald Buddenhagen
commit 743968737c5e296fb5c7d0d2dc1de091cc84c0d7 Author: Oswald Buddenhagen Date: Sun Dec 11 12:09:36 2016 +0100 silence bogus [-Wmaybe-uninitialized] with -O0/-O1/-Os src/util.c |8 1 files changed, 8 insertions(+), 0 deletions(-) diff --git a/src/util.c b/src/util.c index

[commit] master: Merge branch '1.2'

2016-12-11 Thread Oswald Buddenhagen
Skipped 9 existing revision(s) on branch 'master'. commit ab955ffe6b66ccc87ac9364598f8681d8f415be9 Merge: 2bba9b9 7439687 Author: Oswald Buddenhagen Date: Sun Dec 11 12:52:46 2016 +0100 Merge branch '1.2' Conflicts: src/drv_imap.c s

[commit] branch 'wip/uidval-recovery' reset

2016-12-18 Thread Oswald Buddenhagen
The branch 'wip/uidval-recovery', previously at 1335ca3, has been rewound by 13 revision(s) and subsequently fast-forwarded by 26 revision(s) to b675aa1. -- Check out the vibrant tech community on one of the world's most

[commit] branch 'wip/uidval-recovery' reset

2016-12-18 Thread Oswald Buddenhagen
The branch 'wip/uidval-recovery', previously at b675aa1, has been rewound by 16 revision(s) and subsequently fast-forwarded by 15 revision(s) to 47440e7. -- Check out the vibrant tech community on one of the world's most

Re: Inbox-in-Path broken in commit ee8b835c ?

2016-12-19 Thread Oswald Buddenhagen
On Mon, Dec 19, 2016 at 05:13:20PM +0100, Aurelien Jarno wrote: > Does someone have an idea how to fix that? > pull git master and configure "SubFolders Maildir++". see manual for details. some background info can be found in the list archive (and the debian bug tracker).

Re: Incomplete journal entries

2016-12-25 Thread Oswald Buddenhagen
On Sat, Dec 24, 2016 at 03:18:46PM +0100, Yuri D'Elia wrote: > On Fri, Dec 23 2016, Evgeniy Berdnikov wrote: > >> Oswald is right, process completion (by exit() or interrupt by signal) > >> can only truncate data, but can not corrupt. Only system crash can > >> lead to data corruption. > > > >

[commit] master: print actually read TUID in debug message

2016-12-26 Thread Oswald Buddenhagen
commit 0c366552012b5f108f2371a3fca0c9f0c8fb Author: Oswald Buddenhagen Date: Sun Nov 13 22:20:55 2016 +0100 print actually read TUID in debug message src/sync.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/src/sync.c b/src/sync.c index 11f49d1..a8eaee4

[commit] master: mark string_list_t as packed

2016-12-26 Thread Oswald Buddenhagen
commit 879eb623bed4ef4b5dc1d430ca21d32cfcf59701 Author: Oswald Buddenhagen Date: Sun Nov 6 17:23:17 2016 +0100 mark string_list_t as packed otherwise we'll regularly over-allocate due to the struct's stride. src/common.h |2 +- 1 files changed, 1 insertions(+), 1

[commit] master: null-terminate lines read from state file & journal

2016-12-26 Thread Oswald Buddenhagen
commit 1330f43034c3240b442d66c6b4cff52d7d2d42ff Author: Oswald Buddenhagen Date: Sun Nov 13 22:19:40 2016 +0100 null-terminate lines read from state file & journal makes the subsequent code less convoluted. src/sync.c | 15 +-- 1 files changed, 9 insertions(+

[commit] master: make more use of shifted_bit()

2016-12-26 Thread Oswald Buddenhagen
commit 4db64967c9593ce4f70f62af81bf4ecf2858c16f Author: Oswald Buddenhagen Date: Sun Dec 18 21:52:06 2016 +0100 make more use of shifted_bit() technically, this introduces a redundant AND, but the compiler is smart enough to prove that (((A & M) ^ B) & M) == ((A

[commit] master: make more use of nfstrndup()

2016-12-26 Thread Oswald Buddenhagen
commit 3b615bba3ca3a3c66c9c6a2d3791a5af82d221c6 Author: Oswald Buddenhagen Date: Sun Nov 6 17:22:04 2016 +0100 make more use of nfstrndup() src/drv_imap.c| 20 +--- src/drv_maildir.c |8 +++- 2 files changed, 8 insertions(+), 20 deletions(-) diff --git a

[commit] master: document some additional uses for PipelineDepth

2016-12-26 Thread Oswald Buddenhagen
commit 22145f6674b823dd71443c38f07fa0f5bb0bebe1 Author: Oswald Buddenhagen Date: Sat Nov 12 14:15:57 2016 +0100 document some additional uses for PipelineDepth src/mbsync.1 |4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/src/mbsync.1 b/src/mbsync.1 index

[commit] 1.2: standardize on 'int' for message sizes

2016-12-29 Thread Oswald Buddenhagen
commit 67f4aeff1febc9bf750a927052c467fee15ba276 Author: Oswald Buddenhagen Date: Thu Dec 29 14:10:35 2016 +0100 standardize on 'int' for message sizes that's what the sources already assumed anyway. size_t is total overkill, as No Email Ever (TM) w

[commit] master: adjust return type of strnlen() replacement

2016-12-29 Thread Oswald Buddenhagen
commit 357dd5140558a044fe52a2d3ff7abb1153f9968a Author: Oswald Buddenhagen Date: Thu Dec 29 15:06:22 2016 +0100 adjust return type of strnlen() replacement it doesn't really matter, but it's nicer to stay consistent with the official prototype. src/util.c |2 +

[commit] master: make use of memchr() in strnlen() replacement after all

2016-12-29 Thread Oswald Buddenhagen
commit 3eea668052db201fe3d0453324a6b909e3568d38 Author: Oswald Buddenhagen Date: Thu Dec 29 15:08:26 2016 +0100 make use of memchr() in strnlen() replacement after all turns out the comment advising against it was bogus - unlike for memcmp(), the standard does indeed prescribe

[commit] master: make more use of strnlen()

2016-12-29 Thread Oswald Buddenhagen
commit 509a191474f9c872166d9345d0fd5c6b16cb36d8 Author: Oswald Buddenhagen Date: Thu Dec 29 14:34:30 2016 +0100 make more use of strnlen() includes adding the so far superfluous prototype for the replacemnt to common.h. src/common.h |3 +++ src/drv_imap.c |5

[commit] master: factor out copy_msg_convert()

2017-01-21 Thread Oswald Buddenhagen
commit 3dffd6882535d001d6dacfb4be71a40931d62f26 Author: Oswald Buddenhagen Date: Sat Nov 5 18:33:16 2016 +0100 factor out copy_msg_convert() src/sync.c | 135 +++ 1 files changed, 71 insertions(+), 64 deletions(-) diff --git a/src/sync.c

[commit] master: factor out app_cr

2017-01-21 Thread Oswald Buddenhagen
commit 1d3b36f89e716e28643154a319a489b4cdda23d4 Author: Oswald Buddenhagen Date: Sat Nov 5 18:33:47 2016 +0100 factor out app_cr src/sync.c |7 --- 1 files changed, 4 insertions(+), 3 deletions(-) diff --git a/src/sync.c b/src/sync.c index d1b3816..0ed73a7 100644 --- a/src

[commit] master: factor out copy_msg_bytes()

2017-01-21 Thread Oswald Buddenhagen
commit 951b7e77f8adb0ba41e51c3bf8222bf6cf5890dd Author: Oswald Buddenhagen Date: Sat Nov 5 18:32:49 2016 +0100 factor out copy_msg_bytes() src/sync.c | 64 ++-- 1 files changed, 32 insertions(+), 32 deletions(-) diff --git a/src/sync.c b

[commit] master: make fetching of partial UID ranges more flexible

2017-01-21 Thread Oswald Buddenhagen
commit 3d64f16702b14add905a45cf60124665cdd454b9 Author: Oswald Buddenhagen Date: Sun Dec 18 21:24:16 2016 +0100 make fetching of partial UID ranges more flexible instead of a single hard-coded branch, use a generic method to split ranges as needed. this is of course

[commit] master: don't fetch message size unless necessary

2017-01-21 Thread Oswald Buddenhagen
commit f9fe75602e36878d92c8476ba2a3dac524712e1c Author: Oswald Buddenhagen Date: Sun Dec 18 21:22:52 2016 +0100 don't fetch message size unless necessary when syncing flags but not re-newing non-fetched messages, there is no need to query the message size for all message

[commit] master: some reshuffling in maildir_scan() for clarity

2017-01-21 Thread Oswald Buddenhagen
commit ec4b21535fa61caed26c544c82f3e744febb3a15 Author: Oswald Buddenhagen Date: Sun Nov 6 17:26:39 2016 +0100 some reshuffling in maildir_scan() for clarity src/drv_maildir.c | 16 ++-- 1 files changed, 10 insertions(+), 6 deletions(-) diff --git a/src/drv_maildir.c b/src

[commit] master: implement Message-Id based UIDVALIDITY recovery

2017-01-21 Thread Oswald Buddenhagen
commit 77acc268123b8233843ca9bc3dcf90669efde08f Author: Oswald Buddenhagen Date: Sun Dec 18 20:50:20 2016 +0100 implement Message-Id based UIDVALIDITY recovery NEWS |2 + README| 10 src/driver.c |1 + src/driver.h |3 ++ src

[commit] branch 'wip/uidval-recovery' reset

2017-01-21 Thread Oswald Buddenhagen
The branch 'wip/uidval-recovery', previously at 47440e7, has been rewound by 11 revision(s) and subsequently fast-forwarded by 13 revision(s) to 224a783. -- Check out the vibrant tech community on one of the world's most e

[commit] branch 'wip/placeholders' reset

2017-01-22 Thread Oswald Buddenhagen
The branch 'wip/placeholders', previously at 9a4d939, has been rewound by 10 revision(s) and subsequently fast-forwarded by 33 revision(s) to 8d09ea4. -- Check out the vibrant tech community on one of the world's most enga

Re: Exit code to indicate sync changes

2017-01-23 Thread Oswald Buddenhagen
On Mon, Jan 23, 2017 at 12:34:53PM +0100, Yuri D'Elia wrote: > I'd be prepared to modify mbsync myself if there is consensus on the > behavior. > last time this came up i stipulated adding a (script) callback mechanism. this would allow reindexing specific folders, and could be used to emit desktop

Re: sync all channels with only INBOX

2017-01-26 Thread Oswald Buddenhagen
On Wed, Jan 25, 2017 at 12:00:05PM -0800, taequaiw wrote: > I was able to get mbsync channelname:INBOX to work. > Is there a way to do that for all channels, like mbsync -a :INBOX or > mbsync *:INBOX ? > not as such, but you could define a Group. ---

Re: Error severity and "unexpected BYE response"

2017-01-26 Thread Oswald Buddenhagen
On Wed, Jan 25, 2017 at 07:09:20PM -0800, Greg Hurrell wrote: > I have a Gmail sync that is currently failing with this `mbsync -V` debug > output: > > Synchronizing... > >>> 27 APPEND "[Gmail]/All Mail" {153284} > + go ahead > (1 in progress) >>> 28 APPEND "[Gmail]/All Mail" (\Seen) {630

Re: Error: incomplete journal entry

2017-01-31 Thread Oswald Buddenhagen
On Mon, Jan 30, 2017 at 10:10:51PM -0500, myglc2 wrote: > Seeing that the first of these is exactly the same as Peter P. > reported, I thought you might be interested. > Coincidence? > seems a bit unlikely. ^^ as before, the interesting question would be if anything unexpected happened before thi

Re: Problems with syncing mails with gmail

2017-02-01 Thread Oswald Buddenhagen
On Wed, Feb 01, 2017 at 09:38:38AM +0530, Tulasidhar Dronamraju wrote: > Error decompressing data from imap.gmail.com (74.125.130.109:993): (null) > try upgrading openssl and zlib. if that doesn't help, try the mbsync master branch from git. if that still does not work, use "DisableExtension COMPRE

Re: Problems with syncing mails with gmail

2017-02-04 Thread Oswald Buddenhagen
On Wed, Feb 01, 2017 at 10:32:16PM +0530, Tulasidhar Dronamraju wrote: > I tried upgrading openssl and zlib. That didnt help. > > With master branch from git https://git.code.sf.net/p/isync/isync > I get > "IMAP error: unexpected EOF from imap.gmail.com " both with and > without DisableExtension C

Re: How to not exclude IMAP INBOX

2017-02-04 Thread Oswald Buddenhagen
On Sat, Feb 04, 2017 at 02:33:52PM -0800, Nikolaus Rath wrote: > I thought this would give me a backup of all my IMAP folders. However, > it seems that INBOX itself is excluded - only the subfolders are copied: > judging by the command line + output, you're using a rather dated version (1.1.x, i g

Re: How to not exclude IMAP INBOX

2017-02-05 Thread Oswald Buddenhagen
On Sat, Feb 04, 2017 at 04:31:43PM -0800, Nikolaus Rath wrote: > I upgraded to 1.2.1, but the problem persists (I've not logged network > traffic, because it seems that mbsync sees the INBOX mailbox just fine - > but is then excluding it): > judging by the listing, the root cause is that INBOX liv

Re: explanation of status line

2017-02-09 Thread Oswald Buddenhagen
On Thu, Feb 09, 2017 at 11:31:17AM -0500, Peter P. wrote: > Hi amazing isync project! > > I have always been curious if there is an explanation for the status > line I am seeing when syncing mail, eg > M: +157/185 *216/216 #0/0 S: +0/302 *81/81 #0/0 > it's in the man page since 1.2.0. ;)

[commit] 1.2: don't arbitrarily limit UIDs to a billion, part 2

2017-02-15 Thread Oswald Buddenhagen
commit 2457b2baa329384294488b8eb9803a4c86788fad Author: Oswald Buddenhagen Date: Wed Feb 15 17:25:59 2017 +0100 don't arbitrarily limit UIDs to a billion, part 2 imap_find_new_msgs() had the same fixed limit as imap_load_box(). amends 815822d8. src/drv_imap.c | 2

[commit] 1.2: make -DN print also the sent data

2017-02-15 Thread Oswald Buddenhagen
commit 3ebb066aba7249bc85d4fd6adebe48eb543719a7 Author: Oswald Buddenhagen Date: Sat Jan 28 18:26:12 2017 +0100 make -DN print also the sent data src/drv_imap.c | 12 1 file changed, 12 insertions(+) diff --git a/src/drv_imap.c b/src/drv_imap.c index 1fa727f..3d66243 100644

[commit] 1.2: fix mislabeling of test

2017-02-15 Thread Oswald Buddenhagen
commit f62b3c7be96a194854073bca1478586f0f63d9dc Author: Oswald Buddenhagen Date: Wed Feb 15 11:45:52 2017 +0100 fix mislabeling of test src/run-tests.pl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/run-tests.pl b/src/run-tests.pl index 7c7d3fd..829791c 100755

Re: Nightmare with inbox case (Inbox / INBOX)

2017-02-17 Thread Oswald Buddenhagen
On Fri, Feb 17, 2017 at 11:03:19AM +0100, Florian Lombard wrote: > Gmail side, they are either Inbox/subfolder or INBOX/subfolder > I found what was the root cause of that: subfolders created with > thunderbird use INBOX, subfolders created with outlook 2016 use Inbox > accoring to the imap spec,

Re: Refiling issue: messages appear as unread again

2017-02-19 Thread Oswald Buddenhagen
On Sat, Feb 18, 2017 at 06:45:10PM +, Homan, Philipp wrote: > However, I noticed that upon refiling, the flags and the UID switch > their posisition, like so: > > from U=oldUID;2, 2,S > to 2,S, U=newUID > can you please paste the full, unmodified names? what i'm seeing so far is that you ne

Re: Fwd: Re: Refiling issue: messages appear as unread again

2017-02-20 Thread Oswald Buddenhagen
On Mon, Feb 20, 2017 at 05:29:55AM +, Homan, Philipp wrote: > Oswald Buddenhagen writes: > > can you please paste the full, unmodified names? what i'm seeing so > > far is that you need to use "FieldDelimiter ;", as that's clearly what > > you configu

Re: Fwd: Re: Refiling issue: messages appear as unread again

2017-02-21 Thread Oswald Buddenhagen
On Mon, Feb 20, 2017 at 04:46:50PM +, Homan, Philipp wrote: > /Archive/cur/'1487608528.de209b1bae3fa41e.L_LAPTOP:2,S,U=4367' > > had been refiled and synced under mbsync (after renaming the message > with the syntax you suggested) and it does show up as unread again. > yes, because that's sti

Re: Fwd: Re: Refiling issue: messages appear as unread again

2017-02-23 Thread Oswald Buddenhagen
On Tue, Feb 21, 2017 at 05:13:57PM +, Homan, Philipp wrote: > Oswald Buddenhagen writes: > >> /Archive/cur/'1487608528.de209b1bae3fa41e.L_LAPTOP:2,S,U=4367' > >> > >> had been refiled and synced under mbsync (after renaming the message > >> with

Re: [PATCH] Default SystemCertificates to no when CertificateFile exists

2017-02-23 Thread Oswald Buddenhagen
On Fri, Feb 17, 2017 at 03:37:11PM +0100, Yuri D'Elia wrote: > When a CertificateFile is provided, do not trust the system store by > default, since this is not the expected behavior for X.509 certificates. > > SystemCertificates can still be explicitly allowed/disallowed to restore > the previous

Re: [PATCH] Default SystemCertificates to no when CertificateFile exists

2017-02-23 Thread Oswald Buddenhagen
On Sat, Feb 18, 2017 at 10:39:14AM +0100, Yuri D'Elia wrote: > As for the second patch, I'd like to contribute extended exit status > codes. To avoid breaking old scripts, I'd add a new switch > (-e/--exit-code or something like it) that changes the meaning of the > exit status. > well, i'm still

Re: [PATCH] Default SystemCertificates to no when CertificateFile exists

2017-02-23 Thread Oswald Buddenhagen
On Thu, Feb 23, 2017 at 03:10:28PM +0100, Yuri D'Elia wrote: > On Thu, Feb 23 2017, Oswald Buddenhagen wrote: > > On Sat, Feb 18, 2017 at 10:39:14AM +0100, Yuri D'Elia wrote: > >> As for the second patch, I'd like to contribute extended exit status > >>

Re: [PATCH] Default SystemCertificates to no when CertificateFile exists

2017-02-24 Thread Oswald Buddenhagen
On Thu, Feb 23, 2017 at 07:09:51PM +0100, Yuri D'Elia wrote: > On Thu, Feb 23 2017, Oswald Buddenhagen wrote: > >> I see the use case when running as a daemon. > >> > >> You still need to specify the indexing status to the child process > >> though.

Re: [PATCH] Default SystemCertificates to no when CertificateFile exists

2017-02-25 Thread Oswald Buddenhagen
On Fri, Feb 24, 2017 at 12:11:47PM +0100, Yuri D'Elia wrote: > On Fri, Feb 24 2017, Oswald Buddenhagen wrote: > >> I'd like to know if, for instance, there's a transient failure (such as > >> connection error that I should not worry about). > >> >

Re: mbsync hanging

2017-02-27 Thread Oswald Buddenhagen
On Sun, Feb 26, 2017 at 10:22:12AM -0800, Mike Glover wrote: > I added the 'killall mbsync; sleep 5' as a workaround for this problem, > but I'd like to find a real solution. If there's other info I can > provide to help track this down, please let me know. > use the master branch. it has bette

Re: 'Connection reset by peer'

2017-03-02 Thread Oswald Buddenhagen
On Thu, Mar 02, 2017 at 06:43:22AM +, Jos van den Oever wrote: > propagating new messages > >>> 5 APPEND "INBOX" (\Seen \Deleted) "30-Jun-2016 08:40:53 +0200" {8355} > + send literal data > (1 in progress) >>> 6 APPEND "INBOX" (\Deleted) "30-Jun-2016 08:40:53 +0200" > {9806} > Socket error fro

Re: 'Connection reset by peer'

2017-03-02 Thread Oswald Buddenhagen
On Thu, Mar 02, 2017 at 03:23:50PM +, Jos van den Oever wrote: > My use case is actually to modify a subset of all my mails and > re-upload them. Perhaps isync is too heavy a tool for this and I > should script with some imap lib. > the only more lightweight solution i can think of would be u

Re: 'Connection reset by peer'

2017-03-04 Thread Oswald Buddenhagen
On Thu, Mar 02, 2017 at 09:05:00AM +0100, Oswald Buddenhagen wrote: > On Thu, Mar 02, 2017 at 06:43:22AM +, Jos van den Oever wrote: > > propagating new messages > > >>> 5 APPEND "INBOX" (\Seen \Deleted) "30-Jun-2016 08:40:53 +0200" {8355} >

Re: Mbsync, XOAUTH2, and Gmail

2017-03-05 Thread Oswald Buddenhagen
On Sun, Mar 05, 2017 at 10:13:00AM -0500, ben lamothe wrote: > I've noticed from the mbsync man page that mbsync has sasl support, and I > also understand that XOAUTH2 is a valid sasl auth mechanism, but I am > unclear how to configure mbsync to make use of that mechanism through sasl. > I can't fi

<    11   12   13   14   15   16   17   18   19   20   >