The mailserver suite with the 'moo' – 🐮 + 🐋 = 💕
News and Infos
It´s finally time: Our new mailcow Demos are here and live for you to test!
A small but important update for or against the current SOGo Sieve/mail sending problems is here!
We received countless messages about this and implemented a fix within tis update, which hopefully solves the problem for everyone.
For those who are interested: It’s probably related to the IPv6 support introduced in SOGo 5.7.1 and the internal IPv6 connectivity of mailcow´s Docker containers, which triggered connectivity issues with SOGo.
Yeah… however, this bug should be fixed now.
It took long enough, but here it is finally: The new mailcow UI!
Currently it’s still exclusively in the nightly builds because we want to optimize the UI.
And that’s where you come in! Because we want to make the UI as user friendly as possible and improve not only the framework but also the usability.
So if there was one thing that always bothered you so far, please let us know!
Yeah, a August Update in September… kinda sus if you ask me!
This time there are even some changes regarding the Update sources! So stay curious.
Let’s start quite gently for the time being:
Stable changes (stable branch) OAuth clients and app passwords are now accepted again for Cal/CardDav connections. #4685 by @FreddleSpl0it SOGo has been updated to 5.7.1 (Complete changelog here) receives in mailcow stack container version: mailcow/sogo:1.
We’ve released an short update that improved the API and brings a new version of ClamAV (0.105.1).
Note: The update to ClamAV 0.105.1 is recommended by ClamAV as a security update (See ClamAV Update article)
Once again summarized what changes:
The schema of the domain section of the API has been adjusted and improved. Automatic GitHub actions for building the latest container versions has been set up (currently not used productively).
Happy new day to you!
Welcome to the new blog page.
Some of you may have already stumbled across the site on Twitter or on Telegram in the last update announcement, but now here again officially!
Built with the fast and beautiful Static Site Generator Hugo and the LoveIt Theme, this site can keep up with WordPress and even outperform it.
What changes for all blog readers? Well, actually nothing. The only thing that changes is the URL (at least for now) instead of mailcow.
It’s update time once again, a little later than before (I’ll get into that a bit later) but still packed with some changes:
TFA Changes 2FA is now also possible for mailbox users in the UI (previously this was reserved for administrators). Also, it is now possible to enable multiple 2FA options for an account. Note: Only one is used, which is selected by the user. There is a nice new menu at to select the available 2FA options.
Today we have put together a big fat update package for you again, which besides general container updates brings one big change:
Docker Compose v2 support!!!
But let’s start with the small stuff first:
Minor changes ClamAV is now using version 0.105 (the latest at release time). Postfix has been updated to version 3.5.6. netfilter, acme, dockerapi, olefy, watchdog, unbound and phpfpm have been updated to Alpine Linux 3.
Yesterday we received an important tip about a critical security vulnerability in mailcow (thanks again for that). It affects IMAPSYNC and gives access to administration rights in the mailcow UI and API.
It is strongly recommended to install the update as soon as possible to prevent exploitation.
As always please take a look at the GitHub Release: https://github.com/mailcow/mailcow-dockerized/releases/tag/2022-05d
The update does not remove any important functionality from mailcow or IMAPSYNC!
2022-05c It´s us again again!
This time we´ve published the 2022-05c Update which is a very small one.
It changed the API a bit again. This time for security reasons.
Head over to GitHub to see the full changelog: https://github.com/mailcow/mailcow-dockerized/releases/tag/2022-05c
2022-05b It´s us again!
Today we have a small API Fix Update which focus mainly on the UI.
As some of you reported the API Calls for Domains/Mailboxes don´t work anymore if there is no Tag set.