On Mon, Oct 14, 2024 at 03:16:36PM +0100, Dom (shymega) Rodriguez wrote:
On 23.09.2024 10:34, Oswald Buddenhagen via isync-devel wrote:
On Sun, Sep 22, 2024 at 06:09:06PM +0200, Dom (shymega) Rodriguez wrote:
As well as that, I find OWA has the dates in the wrong order after
syncing. I have `CopyArrivalDates` set as true.
you mean, the pull causes the server to re-stamp the messages? that's
just weird ...
It happens after a fresh sync. I have to re-stamp the messages.
i still don't understand what _exactly_ the problem is.
try the formal "what did i do / what did i expect / what did actually
happen" format, for each weirdness separately, in as far as possible.
Basically, my setup is:
Exchange IMAP <=> mbsync <=> local IMAP (Dovecot) <=> MUA (Neomutt).
that's just fine. the rewrite from isync to mbsync was done with such a
configuration explicitly in mind.
mail them to me privately.
Which logs do you need? I.e, in terms of `-D` flags. I have to be
careful with providing raw email data, though.
the -D log won't reveal anything personal that the -V log you already
sent didn't. only -DN would take it to the next level.
the log should be from a single (small) channel:box, as otherwise i'll
completely drown in noise. and make sure that it actually includes
propagation of fresh affected messages. ideally, blow away the copy _and
the corresponding sync state_ of a small folder and re-sync it from
scratch.
in the previous log, we see this:
IMAP command 'NAMESPACE' returned an error: User is authenticated but not
connected.
which is just weird.
to debug this, we need the -Dn log from that channel.
I've tried the `wip/exchange-workarounds-1.5` branch on NixOS, which
produced a segfault. I can get a backtrace if needed.
won't hurt, and valgrind'ing would be even better. just make sure the
build has debug symbols, as otherwise the traces will be completely
useless.
however, the branch isn't really expected to work, as it's untested; i
had no access to exchange for half a decade. and even in the best case,
it contains some rather egregious hacks.
I had to rebase it, but the segfaults
prevent it from working so far.
Which Exchange version were you targeting on that branch?
none, as i didn't write it.
check the list archive (or maybe the bug tracker - i don't remember) -
maybe you'll find something.
but i don't think you'd find anything particularly interesting, as it
will be ancient by now anyway.
_______________________________________________
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
