ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    MailCow in Production Datacenter

    Scheduled Pinned Locked Moved IT Discussion
    mailcowemailsmtpdocker
    59 Posts 11 Posters 6.0k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • scottalanmillerS
      scottalanmiller @gtech
      last edited by

      @gtech said in MailCow in Production Datacenter:

      Are you using only the global settings AS/AV? Or are you using other installed tools. Still find spam emails counts are high with just those settings.

      No third party tools, just PyRazr and such that are included and recommended in the Zimbra guides. We find it comparable to the spam we get on O365 or GSuite.

      1 Reply Last reply Reply Quote 0
      • D
        dave_c @scottalanmiller
        last edited by

        @scottalanmiller
        He has a business to run. Mailcow is a community based project; the project lead used to work full time on it but no longer. He is using mailcow in his hosting business
        Regarding the reliable process: I agree, at least in part
        Regarding the update break: It happened once and there were at least 2 ways of solving it. It wasn't a big problem but was a problem

        scottalanmillerS 1 Reply Last reply Reply Quote 0
        • D
          dave_c @gtech
          last edited by

          @gtech
          Why do you need a proxy?

          scottalanmillerS 1 Reply Last reply Reply Quote 0
          • scottalanmillerS
            scottalanmiller @dave_c
            last edited by

            @dave_c said in MailCow in Production Datacenter:

            @gtech
            Why do you need a proxy?

            Why wouldn't you? You don't want to just assign public IPs to your email web interface in most cases.

            D 1 Reply Last reply Reply Quote 1
            • D
              dave_c @scottalanmiller
              last edited by

              @scottalanmiller
              I do not use a proxy for mailcow as it comes with the same nginx that I would use as a proxy. I have access to nginx.conf to make almost any adjustment I need

              scottalanmillerS 1 Reply Last reply Reply Quote 0
              • scottalanmillerS
                scottalanmiller @dave_c
                last edited by

                @dave_c said in MailCow in Production Datacenter:

                He has a business to run. Mailcow is a community based project; the project lead used to work full time on it but no longer. He is using mailcow in his hosting business

                He does, and there is nothing wrong with that. But no matter what the legitimate reason, it reflects very poorly on a product when it comes to considering whether we want to use it in production or not. Not that we are looking for support from the developer, but it is just "another piece of concern" along with the deployment methodology. That he isn't full time and has a hosting business with no full time people is a concern for people looking to use that, for sure!

                1 Reply Last reply Reply Quote 0
                • scottalanmillerS
                  scottalanmiller @dave_c
                  last edited by

                  @dave_c said in MailCow in Production Datacenter:

                  I do not use a proxy for mailcow as it comes with the same nginx that I would use as a proxy.

                  I'm assuming you aren't running in a datacenter. We want it behind the same nginx proxy that all of our interfaces are behind. They all share one. That MailCow comes with one doesn't help us in any way.

                  1 Reply Last reply Reply Quote 0
                  • scottalanmillerS
                    scottalanmiller
                    last edited by

                    Not to say that it is bad that it has its own Nginx, but that seems like just extra complexity that doesn't need to be there, that adds more places for things to break.

                    D 1 Reply Last reply Reply Quote 0
                    • D
                      dave_c @scottalanmiller
                      last edited by dave_c

                      @scottalanmiller
                      I am running it on rented servers and I understand why you want it to be behind you proxy

                      @scottalanmiller said in MailCow in Production Datacenter:

                      but that seems like just extra complexity that doesn't need to be there, that adds more places for things to break.

                      How would you serve the PHP code of the control panel if you are not including a web server within mailcow?

                      scottalanmillerS 2 Replies Last reply Reply Quote 0
                      • scottalanmillerS
                        scottalanmiller @dave_c
                        last edited by

                        @dave_c said in MailCow in Production Datacenter:

                        How would you serve the PHP code of the control panel if you are not including a web server within mailcow?

                        Same way that MailCow does... run it in its own instance that only does that. I don't know what they use, but I would guess Apache. The Docker instance in MailCow that runs the PHP code for the web server is called sogo-mailcow. The Nginx instance in MailCow that we are talking about is called nginx-mailcow and is a reverse proxy that does not run PHP.

                        1 Reply Last reply Reply Quote 0
                        • scottalanmillerS
                          scottalanmiller @dave_c
                          last edited by

                          @dave_c said in MailCow in Production Datacenter:

                          I am running it on rented servers and I understand why you want it to be behind you proxy

                          If they just had it as an "on/off" option, I think including it is great. But it seems like bypassing it is cumbersome and might break future updates. That's a big problem here, sure I can get in under the hood and try to alter things, but will that work reliably as they deploy anew?

                          1 Reply Last reply Reply Quote 0
                          • stacksofplatesS
                            stacksofplates
                            last edited by

                            What does your current docker-compose.yml file look like?

                            scottalanmillerS C 2 Replies Last reply Reply Quote 0
                            • scottalanmillerS
                              scottalanmiller @stacksofplates
                              last edited by

                              @stacksofplates said in MailCow in Production Datacenter:

                              What does your current docker-compose.yml file look like?

                              I'll let you know once it installs. I've already started a fresh ground-up install.

                              1 Reply Last reply Reply Quote 0
                              • C
                                Curtis @stacksofplates
                                last edited by

                                @stacksofplates @scottalanmiller

                                https://github.com/mailcow/mailcow-dockerized/blob/master/docker-compose.yml

                                stacksofplatesS 1 Reply Last reply Reply Quote 0
                                • stacksofplatesS
                                  stacksofplates @Curtis
                                  last edited by

                                  @Curtis said in MailCow in Production Datacenter:

                                  @stacksofplates @scottalanmiller

                                  https://github.com/mailcow/mailcow-dockerized/blob/master/docker-compose.yml

                                  Yeah I know there's a default, I didn't know if he had changed it at all.

                                  scottalanmillerS 1 Reply Last reply Reply Quote 0
                                  • scottalanmillerS
                                    scottalanmiller @stacksofplates
                                    last edited by

                                    @stacksofplates said in MailCow in Production Datacenter:

                                    @Curtis said in MailCow in Production Datacenter:

                                    @stacksofplates @scottalanmiller

                                    https://github.com/mailcow/mailcow-dockerized/blob/master/docker-compose.yml

                                    Yeah I know there's a default, I didn't know if he had changed it at all.

                                    I had not, the default didn't work so I wasn't looking to modify it yet.

                                    stacksofplatesS 1 Reply Last reply Reply Quote 0
                                    • stacksofplatesS
                                      stacksofplates @scottalanmiller
                                      last edited by

                                      @scottalanmiller said in MailCow in Production Datacenter:

                                      @stacksofplates said in MailCow in Production Datacenter:

                                      @Curtis said in MailCow in Production Datacenter:

                                      @stacksofplates @scottalanmiller

                                      https://github.com/mailcow/mailcow-dockerized/blob/master/docker-compose.yml

                                      Yeah I know there's a default, I didn't know if he had changed it at all.

                                      I had not, the default didn't work so I wasn't looking to modify it yet.

                                      ok. Let me spin up a system with docker and compose. I've been using podman so I don't have the tools on my laptop.

                                      1 Reply Last reply Reply Quote 0
                                      • stacksofplatesS
                                        stacksofplates
                                        last edited by

                                        I was able to proxy through NGINX after running docker-compose up -d. I didn't use HTTPS because I'm lazy but it passed HTTP fine.

                                        1 Reply Last reply Reply Quote 1
                                        • stacksofplatesS
                                          stacksofplates
                                          last edited by stacksofplates

                                          It's just a simple config to test (again because I'm lazy):

                                          nginxconf.png

                                          mailcow.png

                                          1 Reply Last reply Reply Quote 1
                                          • scottalanmillerS
                                            scottalanmiller
                                            last edited by

                                            Great, glad to hear that that works. I'll be testing it more once I see if it comes up at all. The first time it didn't at all, so you are two steps farther than we got 🙂

                                            C scottalanmillerS 2 Replies Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 2 / 3
                                            • First post
                                              Last post