Hello everyone, (my first post here, so please bear with me if I make any mistake),

I have been using mailcow for 3 months and stress testing it. So far, amazing.
I used update.sh yesterday afternoon, so all components are upto day. I’m not using SOLR or IPV6.
So now before I move my mailboxes over, I was using iMapSync. Couple of questions:

  1. Where are the actual log files for iMapSync? In the WebU, the log files don’t appear until much much later, after the sync job is complete. I would like to see what is happening while happening. I checked all the docker running services logs by using the docker-compose logs command, but nothing seems to contain the logs for iMapSync.
  2. Is there a way to get the iMapSync to run immediatley? It seems to wait for quite a while.
  3. And, I noticed (or it seemed like this to me), that if I put five iMapSync schedules, they don’t seem to run in parallel. It goes down the list. If that’s default behaviour, is there a way to change that?

Thank you for everyone’s help in advance.

2 months later

This question is quite old, but maybe I’m able to answer at least the first question, because I had the same one 🙂

It looks like imapsync is called from GitHub Icon imapsync_cron.pl

GitHub Icon GitHub
mailcow-dockerized/data/Dockerfiles/dovecot/imapsync_cron.pl at 2fafb5b1ed4c4b44e4e2b79b452d31b3fe523ddc · mailcow/mailcow-dockerized
mailcow: dockerized - 🐮 + 🐋 = 💕. Contribute to mailcow/mailcow-dockerized development by creating an account on GitHub.
mailcow: dockerized - 🐮 + 🐋 = 💕. Contribute to mailcow/mailcow-dockerized development by creating an account on GitHub.
and the output is stored to the $stdout variable whose content is written to the database after the program is closed.

So IMHO you will not be able to access the output - except maybe via strace, which is not available in the container and has to be installed first.

Have something to say?

Join the community by quickly registering to participate in this discussion. We'd like to see you joining our great moo-community!

Update: Ok, you will be at least able to strace it from the root OS:

strace -s 10000 -p <PID of imapsync_cron.pl>

Important: Use the PID of imapsync_cron.pl, not imapsync itself.

2 years later

Again, this question is quite old, but I find that running cat /proc/$(pgrep perl)/fd/1 connects you to the stdout of the perl script that runs imapsync, so you can see what it’s doing.

Helped me discover that imapsync was trying to sync [Gmail]/All Mail/!

No one is typing