Hi Oswald, 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. Basically, my setup is: Exchange IMAP <=> mbsync <=> local IMAP (Dovecot) <=> MUA (Neomutt). I prefer hosting my own local IMAP server, but yeah, it's a bit annoying.
I'm not sure how comfortable I am sharing the config and more verbose logs via a public mailing list, though.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.
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 thsat branch?
Would it be better to use Davmail?probably not.
I've run into a bug with Davmail, but I'm not sure if it's related to mbsync. Basically, when syncing a shared inbox via my main account, the shared inbox's messages get copied into the main account. I'll share that config with you too. Best wishes, -- Dom Rodriguez GPG Fingerprint: EB0D 45E6 D0DC 1BA1 A2B5 FC24 72DC F123 1E54 BD43
signature.asc
Description: PGP signature
_______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
