gVes

  • 15 May
  • Joined Jan 5, 2022
  • 4 discussions
  • 12 posts
  • 0 best answers
  • Post posted... wait what?
  • In New SSL issued every time server or ACME container is restarted - Help

    • gVes

        Moolevel 2
      • Post #1

      Dear Mailcow community.

      We are facing a very odd issue on our production server at work. We just made the switch from exchange last month, and so far so good, mailcow is faster, seems to be a lot more stable. Overall we are not looking back.

      We run about 8 domains on our server. But every time we restart the server or the ACME container, 8 new certificates are issued. Annoying thing is that sometimes ACME misses to issue one or two domains SSL.

      From what I have read online, this is unexpected behavior, and our certificates should only be renewed once they are close to expiring (after 3 months of being issued). So something is off.

      we are running the latest version of Mailcow, it was a fresh install on a fresh ubuntu machine. We did not touch any config files.

      Any ideas?
      Thanks.
      gVes

    • In iOS 18.4 stopping CalDAV and CardDAV access with password error

      • gVes

          Moolevel 2
        • Post #8

        Update: A user on Reddit figured out that by going into settings->mail->accounts->caldav account->advanced and in the user name deleting and re-adding the @ symbol fixed the issue.

        It worked for me!

      • In iOS 18.4 stopping CalDAV and CardDAV access with password error

        • gVes

            Moolevel 2
          • Post #7

          I have the same issue. Ever since iOS 18.4 update CalDav stopped working. Seems an iOS bug. Not sure what to do besides wait for 18.4.1?

        • In Draft mailbox on iOS EAS account not syncing.

          • gVes

              Moolevel 2
            • Post #6

            Oh, ok. Good to know. Thank you very much. Have a great day! đź‘Ť

          • In Draft mailbox on iOS EAS account not syncing.

            • gVes

                Moolevel 2
              • Post #4

              Hi esackbauer

              Thank you for the information. So if we want draft mailbox syncing should we switch to IMAP then since it isn’t likely to be an issue that will be solved soon?

              Thanks again.

              gVes

            • In Draft mailbox on iOS EAS account not syncing.

              • gVes

                  Moolevel 2
                • Post #2
                • Edited

                Ok, just a quick update. I did try reseting ActiveSync device cache. No difference.
                I also tried setting up the same account on BlueMail. In this app, draft mailbox syncs only one way - from WebUI or IMAP client to BlueMail, but not the other way around.

              • In Draft mailbox on iOS EAS account not syncing.

                • gVes

                    Moolevel 2
                  • Post #1

                  Hello folks.

                  We just setup a mailcow server at work. All seems to be working great, except one issue: when accounts are setup using Active Sync on iOS, our draft mailbox does not sync. If we setup the same account using IMAP, draft folder appears and is syncing with the server.

                  I have gone up and down all the settings but cannot find anything to remedy this.
                  Anything I have missed?

                  We are running the latest 2025-03a version of mailcow.

                  Thank you!

                  gVes

                  • Yes, you must use IMAP then. ActiveSync will never properly implement it.
                    SOGo will eventually remove ActiveSync totally in 2026.

                • In Fresh Installation - ACME-mailcow "Cannot match your IP against hostname"

                  Hi All.

                  My team and I have been battling to get mailcow running on our servers for the past few weeks.
                  Installation goes perfectly fine, but ACME-mailcow is unable to generate the certificates.
                  It detects our Public IP correctly, but then the A record DNS lookup reverts back to the VMs internal LAN IP.
                  Here are our logs, we have tried 8 times on fresh Ubuntu 22.04 installs. Any help would be greatly appreciated.

                  acme-mailcow-1 | 2024-04-15T06:58:11.088646840Z Mon Apr 15 09:58:11 EAT 2024 - Waiting for Docker API…
                  acme-mailcow-1 | 2024-04-15T06:58:11.111293170Z Mon Apr 15 09:58:11 EAT 2024 - Docker API OK
                  acme-mailcow-1 | 2024-04-15T06:58:11.127157703Z Mon Apr 15 09:58:11 EAT 2024 - Waiting for Postfix…
                  acme-mailcow-1 | 2024-04-15T06:58:11.145927392Z Mon Apr 15 09:58:11 EAT 2024 - Postfix OK
                  acme-mailcow-1 | 2024-04-15T06:58:11.160810560Z Mon Apr 15 09:58:11 EAT 2024 - Waiting for Dovecot…
                  acme-mailcow-1 | 2024-04-15T06:58:11.180074776Z Mon Apr 15 09:58:11 EAT 2024 - Dovecot OK
                  acme-mailcow-1 | 2024-04-15T06:58:11.271384324Z Mon Apr 15 09:58:11 EAT 2024 - Waiting for database…
                  acme-mailcow-1 | 2024-04-15T06:58:11.305947845Z Mon Apr 15 09:58:11 EAT 2024 - Database OK
                  acme-mailcow-1 | 2024-04-15T06:58:11.321035452Z Mon Apr 15 09:58:11 EAT 2024 - Waiting for Nginx…
                  acme-mailcow-1 | 2024-04-15T06:58:11.347624963Z Mon Apr 15 09:58:11 EAT 2024 - Nginx OK
                  acme-mailcow-1 | 2024-04-15T06:58:11.361708441Z Mon Apr 15 09:58:11 EAT 2024 - Waiting for resolver…
                  acme-mailcow-1 | 2024-04-15T06:58:11.479971547Z Mon Apr 15 09:58:11 EAT 2024 - Resolver OK
                  acme-mailcow-1 | 2024-04-15T06:58:11.493756001Z Mon Apr 15 09:58:11 EAT 2024 - Waiting for domain table…
                  acme-mailcow-1 | 2024-04-15T06:58:11.640666094Z OK
                  acme-mailcow-1 | 2024-04-15T06:58:11.654540698Z Mon Apr 15 09:58:11 EAT 2024 - Initializing, please wait…
                  acme-mailcow-1 | 2024-04-15T06:58:12.370569315Z Mon Apr 15 09:58:12 EAT 2024 - Using existing domain rsa key /var/lib/acme/acme/key.pem
                  acme-mailcow-1 | 2024-04-15T06:58:12.384939555Z Mon Apr 15 09:58:12 EAT 2024 - Using existing Lets Encrypt account key /var/lib/acme/acme/account.pem
                  acme-mailcow-1 | 2024-04-15T06:58:12.403864022Z Mon Apr 15 09:58:12 EAT 2024 - Detecting IP addresses…
                  acme-mailcow-1 | 2024-04-15T06:58:22.445191380Z Mon Apr 15 09:58:22 EAT 2024 - OK: 196.xxx.xx.xx, 0000:0000:0000:0000:0000:0000:0000:0000
                  acme-mailcow-1 | 2024-04-15T06:58:22.794571804Z Mon Apr 15 09:58:22 EAT 2024 - Found A record for mail.xyz.com: 10.10.1.109
                  acme-mailcow-1 | 2024-04-15T06:58:22.809034264Z Mon Apr 15 09:58:22 EAT 2024 - Cannot match your IP 196.xxx.xx.xx against hostname mail.xyz.com (DNS returned 10.10.1.109)
                  acme-mailcow-1 | 2024-04-15T06:58:22.829510734Z Mon Apr 15 09:58:22 EAT 2024 - Cannot validate any hostnames, skipping Let’s Encrypt for 1 hour.
                  acme-mailcow-1 | 2024-04-15T06:58:22.842764297Z Mon Apr 15 09:58:22 EAT 2024 - Use SKIP_LETS_ENCRYPT=y in mailcow.conf to skip it permanently.
                  acme-mailcow-1 | 2024-04-15T06:58:22.859996359Z OK

                  To add more info, our network is behind a CISCO router and which is NAT-ing our public IP to the VMs Internal IP.

                • In Issue with ACME getting SSL certificate.

                  Thank you. I’ll check it out and will post back the results!

                • In Issue with ACME getting SSL certificate.

                  Isn’t my ISP supposed to configure a rDNS for my IP. I don’t think this can be done on a domain control panel.

                  So I’ll ask for my provider to set up an PTR for my domain and see if it works.

                  Thanks.

                  • In Issue with ACME getting SSL certificate.

                    Hi all, I recently installed mailcow on a fresh Ubuntu 20.04 install. Everything went smooth. I am able to send and receive emails. very surprised by how simple it was really.

                    The only issue I have is that my sites do not seem to be encrypted. I’m a complete Linux noob so please go easy on me. From what I can see in the log files, acme-mailcow is not able to match my IP to my Hostname. I have setup my DNS correctly on my domain control panel which is pointing to the correct Public IP, MX records etc. (as I said I am able to send and receive emails with no issue). My only issue is my site is not secured.

                    I ran docker-compose logs acme-mailcow and these are the log files:

                    acme-mailcow_1 | Wed Jan 5 08:57:54 2022 - Waiting for Docker API…
                    acme-mailcow_1 | Wed Jan 5 08:57:54 2022 - Docker API OK
                    acme-mailcow_1 | Wed Jan 5 08:57:54 2022 - Waiting for Postfix…
                    acme-mailcow_1 | Wed Jan 5 08:57:54 2022 - Postfix OK
                    acme-mailcow_1 | Wed Jan 5 08:57:54 2022 - Waiting for Dovecot…
                    acme-mailcow_1 | Wed Jan 5 08:57:54 2022 - Dovecot OK
                    acme-mailcow_1 | Wed Jan 5 08:57:54 2022 - Waiting for database…
                    acme-mailcow_1 | Wed Jan 5 08:57:54 2022 - Database OK
                    acme-mailcow_1 | Wed Jan 5 08:57:54 2022 - Waiting for Nginx…
                    acme-mailcow_1 | Wed Jan 5 08:57:54 2022 - Nginx OK
                    acme-mailcow_1 | Wed Jan 5 08:57:54 2022 - Waiting for resolver…
                    acme-mailcow_1 | Wed Jan 5 08:57:55 2022 - Resolver OK
                    acme-mailcow_1 | Wed Jan 5 08:57:55 2022 - Waiting for domain table…
                    acme-mailcow_1 | OK
                    acme-mailcow_1 | Wed Jan 5 08:57:55 2022 - Initializing, please wait…
                    acme-mailcow_1 | Wed Jan 5 08:57:55 2022 - Using existing domain rsa key /var/lib/acme/acme/key.pem
                    acme-mailcow_1 | Wed Jan 5 08:57:55 2022 - Using existing Lets Encrypt account key /var/lib/acme/acme/account.pem
                    acme-mailcow_1 | Wed Jan 5 08:57:55 2022 - Detecting IP addresses…
                    acme-mailcow_1 | Wed Jan 5 08:58:06 2022 - OK: 197.156.88.132, 0000:0000:0000:0000:0000:0000:0000:0000
                    acme-mailcow_1 | Wed Jan 5 08:58:10 2022 - Found A record for autoconfig.setavicon.com: 10.10.1.12
                    acme-mailcow_1 | Wed Jan 5 08:58:10 2022 - Cannot match your IP 197.156.88.132 against hostname autoconfig.setavicon.com (DNS returned 10.10.1.12)
                    acme-mailcow_1 | Wed Jan 5 08:58:11 2022 - Found A record for mail.setavicon.com: 10.10.1.12
                    acme-mailcow_1 | Wed Jan 5 08:58:11 2022 - Cannot match your IP 197.156.88.132 against hostname mail.setavicon.com (DNS returned 10.10.1.12)
                    acme-mailcow_1 | Wed Jan 5 08:58:11 2022 - Cannot validate any hostnames, skipping Let’s Encrypt for 1 hour.
                    acme-mailcow_1 | Wed Jan 5 08:58:11 2022 - Use SKIP_LETS_ENCRYPT=y in mailcow.conf to skip it permanently.
                    acme-mailcow_1 | OK

                    Any input on how I can solve this would be so helpful.

                    Thanks guys.

                    gVes

                  • In Mailcow Clustering

                    Hi, I am also very interested in being to create a mailcow server cluster. Please keep us posted!