On Sat, Aug 23, 2008 at 10:40:13 +0200, Oswald Buddenhagen wrote:
> On Fri, Aug 01, 2008 at 10:13:54AM +0200, Tino Keitel wrote:
> > mbsync stumbled over a file in this maildir that was zero sized.
> > Mbsync should better report that error, though.
> >
> does this patch help?
I just had an empty
On Fri, Aug 01, 2008 at 10:13:54AM +0200, Tino Keitel wrote:
> mbsync stumbled over a file in this maildir that was zero sized.
> Mbsync should better report that error, though.
>
does this patch help?
--
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
--
Confusion, chaos, pa
On Thu, Jul 31, 2008 at 23:35:17 +0200, Oswald Buddenhagen wrote:
> On Thu, Jul 31, 2008 at 10:57:23AM +0200, Tino Keitel wrote:
> > Any hints what I should try next?
> >
> strace, valgrind ...
I tried strace, and saw that mbsync stumbled over a file in this
maildir that was zero sized. This for
On Thu, Jul 31, 2008 at 10:57:23AM +0200, Tino Keitel wrote:
> Any hints what I should try next?
>
strace, valgrind ...
> The same configuration worked before.
>
hmm, what is the exact last version which worked?
is debian applying any patches nowawadays? does it work with upstream
built from sour
Hi,
[now with the correct, compressed attachment]
my mbsync always exists with error code 1 for a certain mailbox, but no
error is shown. mbsync -V doesn't show any possible error condition
either. I attached the mbsync -V 2>&1 output. Any hints what I should
try next?
The sync happens over a SS
