I

ivarh

I do know that this works today using MS activesync but the xapsd plugin for dovecot have come a long way and I am looking forward to try to add it to the dovecot instance that is used by mailcow. Basically what is needed is to run a daemon (dovecot-xaps-daemon) built using go. It will listen for jobs on ::1 (IpV6) and is paired with a dovecot plugin that will let it know when a mail has been delivered to a user that ha a apple device that has enabled push notifications (dovecot-xaps-plugin). Anyone know how to add this plugin to the dovecot instance that mailcow is using and how to make that persistent during upgrades. I think I can place the daemon outside the docker container as the ipv6 address the plugin is connecting to is configurable
more information here: Push Comes to Dove’

Colin Cogle

Push Comes to Dove’

By adding a few things to your Dovecot IMAP server, you can have instant new mail notifications on your Apple devices.

This should allow for instant push notifications when a mail is deposited into dovecot instead of the periodiv testin that sogd is using today.

-Ivar

mlcwuser That hit the spot.. I guess this shows how important it is to read the documentation.
Thanks again and have a merry christmas

When you run a mailcow hosted email server through the email server test on this web site it warns about a couple of things:

Key exchange parametersclose
Verdict:
At least one of your mail servers supports insufficiently secure parameters for Diffie-Hellman key exchange.

Technical details:
Mail server (MX) Affected parameters Security level
mail.hosteng.au. DH-2048 insufficient
Test explanation:
We check if the public parameters used in Diffie-Hellman key exchange by your receiving mail servers (MX) are secure.

and this one:
Verdict:
At least one of your mail servers supports one or more ciphers that have a phase out status, because they are known to be fragile and are at risk of becoming insufficiently secure.

Technical details:
Mail server (MX) First found affected cipher Status
mail.hosteng.au. AES256-GCM-SHA384 phase out

I have tried to find information on how to reconfgure the chiper sets mailcow supports but not been able to fix these warnings.
If anyone is able to help I would be grateful.

I am running mailcow in a VM on my mac mini and it is working great. I am looking to simplify my setup and want to know if anyone have been able to run the mailcow docker containers straight under macos.

I have moved my email to a self-hosted Mailcow container on a Debian12 VM running on my Mac. It works like a charm; however, I miss one thing: I have set up my nameserver that serves my domains to accept rfc2136 updates, and my opnsense uses this to generate its certificates. Is there any way to configure the ACME container to use rfc2136/dns01 authentification instead of using the local webserver to let lets-encrypt validate ownership of the domain?