U
uniquegch

  • Joined Nov 10, 2023
  • 4 discussions
  • 28 posts
  • 0 best answers
  • Post posted... wait what?
  • mlcwuser yes I did and the best answer is only a link on what is new in the current version.

    [unknown] I used a different computer with Firefox as browser and made sure the cache is emptied and the login with the “new” URL works. But I still have an issue sending out e-mails. Did something change regarding Port 465 SMTP out SSL/TLS. Now those accounts do have MFA. Is there a thread to that issue? can you direct me to that SMTP Sending issue thanks

    • I have since today the issue not being able to login to the GUI using the administrator account. I am using also MFA, but it seems the login credentials are not correct. Also I am getting the error that I cannot send e-mails because of problem with SMTP. Sogo is disabled on m system, but I cannot login with another user, but of course only get the user options and no admin features. can I change that in the conf file?
      and I installed the newest version last week and everything was fine

      just used the helper script mailcow-reset-admin.sh but not able to login. it might also possible that failtoban is blocking my IP.

      [unknown]
      just used the helper script mailcow-reset-admin.sh but not able to login. it might also possible that failtoban is blocking my IP.

      • well the healtcheck is ok
        34bea2964d85:/# ./healthcheck.sh
        PING 1.1.1.1 (1.1.1.1): 56 data bytes

        — 1.1.1.1 ping statistics —
        3 packets transmitted, 3 packets received, 0% packet loss
        round-trip min/avg/max = 1.367/1.429/1.521 ms
        PING 8.8.8.8 (8.8.8.8): 56 data bytes

        — 8.8.8.8 ping statistics —
        3 packets transmitted, 3 packets received, 0% packet loss
        round-trip min/avg/max = 1.452/1.472/1.501 ms
        PING 9.9.9.9 (9.9.9.9): 56 data bytes

        — 9.9.9.9 ping statistics —
        3 packets transmitted, 3 packets received, 0% packet loss
        round-trip min/avg/max = 26.597/26.694/26.792 ms

      • thanks @DocFraggle did that and had to unblock another IP@ range.
        but still now looking into that again after 1 hour the container is still unhealthy. even that I restarted it. I will do the healthcheck again over the weekend.

      • but why is postfix affected by the non reachable url with dovecot?

      • I did some more digging and found out that “… Failed to connect to www.spamassassin.heinlein-support.de …” because that url was in an IP@ range which was blocked by fail2ban. unblocking that ip@ range allowed to be able to communicate with the url and dovecot is stable which also made postfix stable(?). does that make sense when dovecote cannot reach that url postfix is also not proper working.

      • I start having again major issues with postfix and dovecot. based on Watchdog they are going done at some point by -10 till 0 and try to come up. But that means I cannot use e-mail server with my mailboxes and other services for sending e-mails.

        normally I would stop the containers, do a pull and most often is a newer image available and fixes the issue, but now it is not working at all. What information I should check?

        here some postfix logs via docker compose logs. (seems a relation with the unhealthy unbound)
        postfix-mailcow-1 | Uptime: 4000 Threads: 9 Questions: 8447 Slow queries: 0 Opens: 66 Open tables: 59 Queries per second avg: 2.111
        postfix-mailcow-1 | Feb 2 10:48:03 84fb52519b2f syslog-ng[8]: syslog-ng starting up; version=‘3.28.1’
        postfix-mailcow-1 | Checking if ASN for your IP is listed for Spamhaus Bad ASN List…
        postfix-mailcow-1 | 2024-02-02 10:48:04,472 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
        postfix-mailcow-1 | 2024-02-02 10:48:04,473 INFO success: postfix entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
        postfix-mailcow-1 | 2024-02-02 10:48:04,473 INFO success: syslog-ng entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
        postfix-mailcow-1 | We couldn’t determine your AS… (maybe DNS/Network issue?) Response Code: 000
        postfix-mailcow-1 | Deactivating Spamhaus DNS Blocklists to be on the safe site!
        postfix-mailcow-1 | chown: cannot access ‘/usr/share/man/man1/mailq.1.gz’: No such file or directory
        postfix-mailcow-1 | Feb 2 10:48:12 84fb52519b2f postfix/postfix-script[362]: starting the Postfix mail system
        postfix-mailcow-1 | Feb 2 10:48:12 84fb52519b2f postfix/master[364]: daemon started – version 3.5.23, configuration /opt/postfix/conf
        postfix-mailcow-1 | Feb 2 10:48:38 84fb52519b2f postfix/master[364]: warning: process /usr/lib/postfix/sbin/smtpd pid 370 exit status 1

      • unbound-mailcow-1 | setup in directory /etc/unbound
        unbound-mailcow-1 | removing artifacts
        unbound-mailcow-1 | Setup success. Certificates created. Enable in unbound.conf file to use
        unbound-mailcow-1 | [1706863286] unbound[1:0] notice: init module 0: validator
        unbound-mailcow-1 | [1706863286] unbound[1:0] notice: init module 1: iterator
        unbound-mailcow-1 | [1706863286] unbound[1:0] info: start of service (unbound 1.17.1).
        unbound-mailcow-1 | [1706863293] unbound[1:0] info: generate keytag query _ta-4f66. NULL IN

        seems to look ok

      • as permanent situation the container unbound is always unhealthy. but it seems not to have an impact. Where can I find more details. because trying to use docker compose logs container name is not working

        • well based on watchguard (in the mailcow admin website - Logs) it is 5 of 5 aka fully healthy.
          Should Iook at /var/logs?

        • I am not sure for how long, but the container unbound (ver. 1.18) is always unhealthy. looking at the ports (netstat -tulpn) there is no listening on port 53, which is open in the UFW.

          at this point all the containers are up and running and healthy.

          • this is a little bit of a longer answer.

            well I did some looking around and came up with the following

            VPS: 5.10.0-26-amd64 #1 SMP Debian (bullseye) 5.10.197-1 (2023-09-29) x86_64 GNU/Linux
            Docker version 24.0.7
            Docker Compose version v2.18.1

            that VPS I am using only to run mailcow-dockerize

            I changed the setting of “… enable_ipv6: true …” to false (in the docker-compose.yml file around line 615).

            At this point watchdog shows me that postfix and dovecot are healthy, actually everything is healthy, except when I look with docker containter ps (kinda of see more details below)

            Current issue is also the container for unbound
            “… mailcow/unbound:1.18 ”/docker-entrypoint.…“ (unhealthy) …”

            after running docker container logs (ID unbound) I checked the firewall making sure the port 53 is not blocked / denied, rebootet the server (for $h!t and giggles) and when it was back online postfix and dovecot crapped out on me. and it makes sense because they cannot resolve DNS names (duh unbound not healthy).

            Now did some “hammer” tooling and ran.
            docker-compose kill
            docker-compose up -d

            NOTE: all containers have been created but not all have started like postfix, watchdog, acme, netfilter, clamd. and unbound caused an error.

            ok so killing seems at bit harsh. so lets be gentle and do
            docker-compose stop
            docker-compose up -d
            ah wonderful it shows all good and unbound heathly
            … hmm wait in docker container ps it shows container unbound unhealthy (WTF). But let me check, well watchdog shows everything healthy and all my mailboxes can be opened. So I guess after some much time x the $h!t will hit the fan again.

          • hello esackbauer,

            hmm ok and where do I find all those information?
            Thanks
            regards

            • and the problems are reoccuring and the ./update.sh “trick” does not work either.
              and I must assume I am the only one who seems to have that problem I will have to look for another mailserver solution.
              Thank you community for your outstanding help.
              You are all a blast.

              • one solution for the above described situation is running the update.sh script. I just executed it and for pretty much each container was an updated image available. I will keep an eye on that and see if the problem with the health status of dovecot and postfix is related with status of the current image.

              • how can fix the issue with dovecot and postfix, which seems to cause a connection refused from my mail client to the server mailboxes

              • and I am starting having the issues with Dovecot, postfix and also CertificateCheck.
                This leads to refusing the connection from my mailclient to the mailcow server.

              • Hello accolon, thanks for your posts. that is good information helping me understading this topic better.

              • Hello accolon, thanks for your reply and quick description. That applies for office files being an attachment coming in or send out? Would that also apply for “office” files generated with OpenOffice, Libreoffice?
                At this point I do not see the need for my setup (personally). please correct me if I am wrong. Always happy to learn something new (even for an old dog like me).