2022-06a

mailcow/mailcow-dockerized2022-06aJun 23, 2022by DerLinkman

AI Summary

Revision A of the June update making Docker Compose v2 mandatory and implementing hardening for IMAPSYNC.

Key Highlights

Docker Compose v2 is now required to run mailcow
IMAPSYNC Exploit hardening (hotfix)
Re-use DKIM key if available

Breaking Changes

Docker Compose v2 is now required

Full Release Notes

## What's Changed
* Translations update from Weblate by @milkmaker in https://github.com/mailcow/mailcow-dockerized/pull/4638
* hotfix imapsync (IMAPSYNC Exploit hardening) by @FreddleSpl0it in https://github.com/mailcow/mailcow-dockerized/pull/4629
* Docker-Compose v2 is now **required** to run mailcow. (Moved up, originally planned for December) by @DerLinkman
* [Web] Re-use DKIM key if available by @andryyy https://github.com/mailcow/mailcow-dockerized/commit/7ae7f25580dbab0e49ff0d208ba876be1485d468

---

#### About IMAPSYNC (SyncJobs)
It´s the second exploit in such a short time and we´re already thinking of a IMAPSYNC replacement in the near future. However with this update (2022-06a) an Administrator needs to set the SyncJob ACL whenever they create a new Mailbox user, which should be able to use the SyncJobs. **This don´t affect the Admin View of course, they can create SyncJobs like they normally could without a change**.

_**We advice you to update your mailcow in the near future. There will be a seperate CVE Number regarding this IMAPSYNC Exploit Hardening when it´s availble. We´ll create a Security Issue (like the last time) here on GitHub aswell.**_


**Full Changelog**: https://github.com/mailcow/mailcow-dockerized/compare/2022-06...2022-06a