Re: Issues building 1.1.0 on FreeBSD

2014-01-02 Thread Chris Nehren
On Thu, Jan 02, 2014 at 21:13:15 +0100, Oswald Buddenhagen wrote: > On Sun, Dec 22, 2013 at 09:54:54PM -0500, Chris Nehren wrote: > On Wed, Dec 25, 2013 at 09:29:38PM +0100, Emanuel Haupt wrote: > > [compile on freebsd is teh FAIL] > > > fixed in isync_1_1_branch. presumably. Awesome! I'm about to

Re: Issues building 1.1.0 on FreeBSD

2014-01-02 Thread Oswald Buddenhagen
On Sun, Dec 22, 2013 at 09:54:54PM -0500, Chris Nehren wrote: On Wed, Dec 25, 2013 at 09:29:38PM +0100, Emanuel Haupt wrote: > [compile on freebsd is teh FAIL] > fixed in isync_1_1_branch. presumably. -- Rapidly troublesho

[commit] isync_1_1_branch: fix _POSIX_SYNCHRONIZED_IO usage

2014-01-02 Thread Oswald Buddenhagen
commit 6d2fd370a60de5cacaf8e60c117efe66c245dc16 Author: Oswald Buddenhagen Date: Thu Jan 2 19:36:45 2014 +0100 fix _POSIX_SYNCHRONIZED_IO usage it can be -1 for unsupported, or 0 for runtime detection (which we don't do). src/drv_maildir.c |2 +- src/sync.c|2

[commit] isync_1_1_branch: bump version

2014-01-02 Thread Oswald Buddenhagen
commit 813b4942db53688c9cbdcf62801076cb60126f7b Author: Oswald Buddenhagen Date: Thu Jan 2 21:08:57 2014 +0100 bump version configure.ac |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/configure.ac b/configure.ac index ed3e124..5f7c331 100644 --- a/configure.ac +

[commit] isync_1_1_branch: make date parsing portable, take 2

2014-01-02 Thread Oswald Buddenhagen
commit aee0fa3b68461fdc3208db8987752660810bddf3 Author: Oswald Buddenhagen Date: Thu Jan 2 20:50:42 2014 +0100 make date parsing portable, take 2 the global timezone variable is glibc-specific. so use timegm() instead of mktime() for the conversion. as that is specific to t

Re: Duplicate Exchange folders, password encryption & IMAP quick sync speed

2014-01-02 Thread Oswald Buddenhagen
On Thu, Jan 02, 2014 at 06:58:23PM +, Rob Stewart wrote: > On 2 January 2014 18:16, Oswald Buddenhagen wrote: > >> Done. It still takes a while.. about 30 seconds or so. Should I be > >> satisfied with this? > >> > > hmm, no, not really. something is wrong. > > try whether just --pull-new is e

Re: Duplicate Exchange folders, password encryption & IMAP quick sync speed

2014-01-02 Thread Chris Nehren
On Thu, Jan 02, 2014 at 19:16:47 +0100, Oswald Buddenhagen wrote: > depending on what you mean by command line. assuming you mean a text > console, i would expect any halfways decent MUA to support it - mutt and > pine (or whatever successors still exist) certainly do. Actually, mutt's poor handli

Re: Duplicate Exchange folders, password encryption & IMAP quick sync speed

2014-01-02 Thread Rob Stewart
On 2 January 2014 18:16, Oswald Buddenhagen wrote: > - >> * LIST (\HasNoChildren) "/" "Sent" >> * LIST (\HasNoChildren) "/" "Sent" >> * LIST (\HasNoChildren) "/" "Sent Mail" >> * LIST (\HasNoChildren) "/" "Sent Messages" > - > > clearly, the proxy is buggy or misconfigured. Ah, thanks. I

Re: Duplicate Exchange folders, password encryption & IMAP quick sync speed

2014-01-02 Thread Oswald Buddenhagen
On Thu, Jan 02, 2014 at 05:18:46PM +, Rob Stewart wrote: > On 2 January 2014 16:53, Oswald Buddenhagen wrote: > > On Mon, Dec 30, 2013 at 02:04:34PM +, Rob Stewart wrote: > >> 1. Duplicate folders on Exchange server. > >> > >> I am using davmail to sync with an Exchange server. For some re

Re: Duplicate Exchange folders, password encryption & IMAP quick sync speed

2014-01-02 Thread Rob Stewart
On 2 January 2014 16:53, Oswald Buddenhagen wrote: > On Mon, Dec 30, 2013 at 02:04:34PM +, Rob Stewart wrote: >> 1. Duplicate folders on Exchange server. >> >> I am using davmail to sync with an Exchange server. For some reason, >> there are two "Sent" folders on the server: >> > to analyze th

Re: Duplicate Exchange folders, password encryption & IMAP quick sync speed

2014-01-02 Thread Oswald Buddenhagen
On Mon, Dec 30, 2013 at 02:04:34PM +, Rob Stewart wrote: > 1. Duplicate folders on Exchange server. > > I am using davmail to sync with an Exchange server. For some reason, > there are two "Sent" folders on the server: > to analyze the problem the contents of the .mbsyncrc and the output of $