Hey mates,
I’ve been working on improving ns8-imapsync compatibility with Exchange servers, and I’d love to know if some of you have already hit similar issues.
The problem
When syncing from an Exchange server (in my case hosted at OVH), imapsync was simply refusing to connect. After digging into it, I added two flags that seem to help:
--addheader # tags messages to avoid re-syncing them
--automap # handles Exchange folder name differences automatically
While I was at it, I also cleaned up how optional arguments are passed in the shell script. Instead of passing empty strings when a variable is not set, I switched to a POSIX/ash-compatible pattern:
${VAR:+"${VAR}"} # quoted when set, nothing when empty
The full PR is here: fix: Exchange support, file age calculation and safe arg quoting by stephdl · Pull Request #102 · NethServer/ns8-imapsync · GitHub
Want to test?
Install the test build:
add-module ghcr.io/nethserver/imapsync:sdl-fixTimeStamp
Or update an existing instance:
api-cli run update-module --data '{"module_url":"ghcr.io/nethserver/imapsync:sdl-fixTimeStamp","instances":["imapsync1"],"force":true}'
My question
Have you ever had issues syncing with Exchange, whether hosted at OVH or elsewhere? Did it refuse to connect? Did the sync behave strangely?
Any feedback is welcome, even “never had a problem” is useful.