Skip to content

Add mailcow subdomain sample config #756

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 3 commits into from
Closed

Add mailcow subdomain sample config #756

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
1c66922
Add mailcow subdomain sample config
petarvnikolov Mar 16, 2025
25b2f2f
Merge branch 'master' into master
petarvnikolov May 31, 2025
3f85e9a
Fix comment position to match rest of proxy-confs
petarvnikolov May 31, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
74 changes: 74 additions & 0 deletions mailcow.subdomain.conf.sample
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,74 @@
## Version 2025/03/16
# make sure that your mailcow container is named mailcow
# make sure that you are aqquainted with the mailcow documentation (https://docs.mailcow.email/)
# make sure you have read the most important entries in the "Get Started" section, "Post Installation Tasks -> Reverse Proxy -> Overview" and "Post Installation Tasks -> Reverse Proxy -> Nginx" sections
# make sure that your dns is configured as per your domain requirements and the mailcow documentation
# make sure to set up a mechanism to copy your SSL certificate after each renewal to /data/assets/ssl/ directory for mailcow to use (see mailcow documentation in "Post Installation Tasks -> Reverse Proxy -> Overview")

server {
listen 443 ssl;
listen [::]:443 ssl;

server_name mailcow.* autoconfig.* autodiscover.*; # modify these names to match your domain/mailcow configuration

include /config/nginx/ssl.conf;

client_max_body_size 0;

# enable for ldap auth (requires ldap-location.conf in the location block)
#include /config/nginx/ldap-server.conf;

# enable for Authelia (requires authelia-location.conf in the location block)
#include /config/nginx/authelia-server.conf;

# enable for Authentik (requires authentik-location.conf in the location block)
#include /config/nginx/authentik-server.conf;

location / {
# enable the next two lines for http auth
#auth_basic "Restricted";
#auth_basic_user_file /config/nginx/.htpasswd;

# enable for ldap auth (requires ldap-server.conf in the server block)
#include /config/nginx/ldap-location.conf;

# enable for Authelia (requires authelia-server.conf in the server block)
#include /config/nginx/authelia-location.conf;

# enable for Authentik (requires authentik-server.conf in the server block)
#include /config/nginx/authentik-location.conf;

include /config/nginx/resolver.conf;
set $upstream_app mailcow;
set $upstream_port 8080;
set $upstream_proto http;
proxy_pass $upstream_proto://$upstream_app:$upstream_port;

proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
Comment on lines +48 to +51
Copy link
Member

@Roxedus Roxedus May 23, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These are redundant, they should exist in proxy.conf

Copy link
Contributor Author

@petarvnikolov petarvnikolov May 31, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The issue was that when i tried to overwrite values for proxy_buffers and etc., nginx detected duplicated directives in the same context. That is why I removed the proxy.conf include and wrote all the necessary directives manually in the location blocks. Would a more accurate solution be to define the proxy.conf include in the server block of the proxy-conf and overwrite the necessary directives in the location blocks?

Copy link
Contributor Author

@petarvnikolov petarvnikolov May 31, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

*The specific values for proxy_buffers, proxy_buffer_size, proxy_busy_buffers_size, proxy_connection_timeout, proxy_send_timeout and proxy_read_timeout are required as per the mailcow-dockerized documentation regarding reverse proxies.

proxy_buffer_size 128k;
proxy_buffers 64 512k;
proxy_busy_buffers_size 512k;
}

location /Microsoft-Server-ActiveSync {
include /config/nginx/resolver.conf;
set $upstream_app mailcow;
set $upstream_port 8080;
set $upstream_proto http;
proxy_pass $upstream_proto://$upstream_app:$upstream_port;

proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_connect_timeout 75;
proxy_send_timeout 3650;
proxy_read_timeout 3650;
proxy_buffers 64 512k;

client_body_buffer_size 512k;
}
}