如何快速的搭建电子邮局（邮箱，企业邮箱，个性化域名邮箱）？注意：不太适合windows操作系统
前提条件
- 一个属于你自己的玉米（域名），可以花几十块钱购买玉米，或者申请免费的域名（不好申请）
- 一台云服务器（最低配置1g内存,单核cpu,1兆带宽）,本人使用的oracle免费主机
- 防火墙（如果未开启忽略）至少放行25,465，993端口，放行命令参考
- RedHat/Centos系列linux
systemctl status firewalld #查看状态 firewall-cmd --zone=public --add-port=25/tcp --permanent firewall-cmd --zone=public --add-port=465/tcp --permanent firewall-cmd --zone=public --add-port=993/tcp --permanent - ubuntu 等使用ufw防火墙的linux
ufw status ufw allow 25 ufw allow 465 ufw allow 993
- 除了系统自身的防火墙，还需要云主机厂商的安全策略里需要放行上面三个端口
正式开始
首先登录自己域名厂商管理面板，添加如下几个记录
| Type | Name | Content | |
|---|---|---|---|
| A | 云主机ip地址 | ||
| MX | @ | mail.域名 | (Priority: 10) |
| PTR | ip地址的倒序.in-addr.arpa | ||
| TXT | @ | v=spf1 a mx ~all | |
| TXT | mail._domainkey | 服务启动运行命令后得到 |
登录到自己的云服务器，在适当的目录创建三个文件，docker-compose.yml mail.env ssl.conf 具体内容如下：
-
docker-compose.yml 域名替换自己的域名
version: "3" services: mgx: container_name: mgx image: hotpot/mgx:ssl-ml environment: - EMAIL=me@域名 ports: - "80:80" - "443:443" volumes: - ./data/mgx/config:/ssl-conf.d - ./data/mgx/pub-data:/data - ./data/mgx/cert:/etc/letsencrypt restart: always mail: image: ghcr.io/docker-mailserver/docker-mailserver:latest container_name: mail hostname: mail.域名 env_file: mail.env ports: - "25:25" # SMTP (explicit TLS => STARTTLS, Authentication is DISABLED => use port 465/587 instead) - "465:465" # ESMTP (implicit TLS) - "993:993" # IMAP4 (implicit TLS) volumes: - ./data/dms/mail-data/:/var/mail/ - ./data/dms/mail-state/:/var/mail-state/ - ./data/dms/mail-logs/:/var/log/mail/ - ./data/dms/config/:/tmp/docker-mailserver/ - ./data/mgx/cert/:/etc/letsencrypt/:ro - /etc/localtime:/etc/localtime:ro restart: always stop_grace_period: 1m cap_add: - NET_ADMIN healthcheck: test: "ss --listening --tcp | grep -P 'LISTEN.+:smtp' || exit 1" timeout: 3s retries: 0 -
mail.env 修改：
POSTMASTER_ADDRESS=postmaster@域名ENABLE_FAIL2BAN=1如果服务器配置高一点话可以打开：ENABLE_CLAMAV=1ENABLE_RSPAMD=1# ----------------------------------------------- # --- Mailserver Environment Variables ---------- # ----------------------------------------------- # DOCUMENTATION FOR THESE VARIABLES IS FOUND UNDER # https://docker-mailserver.github.io/docker-mailserver/latest/config/environment/ # ----------------------------------------------- # --- General Section --------------------------- # ----------------------------------------------- # empty => uses the `hostname` command to get the mail server's canonical hostname # => Specify a fully-qualified domainname to serve mail for. This is used for many of the config features so if you can't set your hostname (e.g. you're in a container platform that doesn't let you) specify it in this environment variable. OVERRIDE_HOSTNAME= # REMOVED in version v11.0.0! Use LOG_LEVEL instead. DMS_DEBUG=0 # Set the log level for DMS. # This is mostly relevant for container startup scripts and change detection event feedback. # # Valid values (in order of increasing verbosity) are: `error`, `warn`, `info`, `debug` and `trace`. # The default log level is `info`. LOG_LEVEL=info # critical => Only show critical messages # error => Only show erroneous output # **warn** => Show warnings # info => Normal informational output # debug => Also show debug messages SUPERVISOR_LOGLEVEL= # 0 => mail state in default directories # 1 => consolidate all states into a single directory (`/var/mail-state`) to allow persistence using docker volumes ONE_DIR=1 # Support for deployment where these defaults are not compatible (eg: some NAS appliances): # /var/mail vmail User ID (default: 5000) DMS_VMAIL_UID= # /var/mail vmail Group ID (default: 5000) DMS_VMAIL_GID= # **empty** => use FILE # LDAP => use LDAP authentication # OIDC => use OIDC authentication (not yet implemented) # FILE => use local files (this is used as the default) ACCOUNT_PROVISIONER= # empty => postmaster@domain.com # => Specify the postmaster address POSTMASTER_ADDRESS=postmaster@域名 # Check for updates on container start and then once a day # If an update is available, a mail is sent to POSTMASTER_ADDRESS # 0 => Update check disabled # 1 => Update check enabled ENABLE_UPDATE_CHECK=1 # Customize the update check interval. # Number + Suffix. Suffix must be 's' for seconds, 'm' for minutes, 'h' for hours or 'd' for days. UPDATE_CHECK_INTERVAL=1d # Set different options for mynetworks option (can be overwrite in postfix-main.cf) # **WARNING**: Adding the docker network's gateway to the list of trusted hosts, e.g. using the `network` or # `connected-networks` option, can create an open relay # https://github.com/docker-mailserver/docker-mailserver/issues/1405#issuecomment-590106498 # The same can happen for rootless podman. To prevent this, set the value to "none" or configure slirp4netns # https://github.com/docker-mailserver/docker-mailserver/issues/2377 # # none => Explicitly force authentication # container => Container IP address only # host => Add docker container network (ipv4 only) # network => Add all docker container networks (ipv4 only) # connected-networks => Add all connected docker networks (ipv4 only) PERMIT_DOCKER=none # Set the timezone. If this variable is unset, the container runtime will try to detect the time using # `/etc/localtime`, which you can alternatively mount into the container. The value of this variable # must follow the pattern `AREA/ZONE`, i.e. of you want to use Germany's time zone, use `Europe/Berlin`. # You can lookup all available timezones here: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones#List TZ= # In case you network interface differs from 'eth0', e.g. when you are using HostNetworking in Kubernetes, # you can set NETWORK_INTERFACE to whatever interface you want. This interface will then be used. # - **empty** => eth0 NETWORK_INTERFACE= # empty => modern # modern => Enables TLSv1.2 and modern ciphers only. (default) # intermediate => Enables TLSv1, TLSv1.1 and TLSv1.2 and broad compatibility ciphers. TLS_LEVEL= # Configures the handling of creating mails with forged sender addresses. # # **0** => (not recommended) Mail address spoofing allowed. Any logged in user may create email messages with a forged sender address (see also https://en.wikipedia.org/wiki/Email_spoofing). # 1 => Mail spoofing denied. Each user may only send with his own or his alias addresses. Addresses with extension delimiters(http://www.postfix.org/postconf.5.html#recipient_delimiter) are not able to send messages. SPOOF_PROTECTION= # Enables the Sender Rewriting Scheme. SRS is needed if your mail server acts as forwarder. See [postsrsd](https://github.com/roehling/postsrsd/blob/master/README.md#sender-rewriting-scheme-crash-course) for further explanation. # - **0** => Disabled # - 1 => Enabled ENABLE_SRS=0 # Enables the OpenDKIM service. # **1** => Enabled # 0 => Disabled ENABLE_OPENDKIM=1 # Enables the OpenDMARC service. # **1** => Enabled # 0 => Disabled ENABLE_OPENDMARC=1 # Enabled `policyd-spf` in Postfix's configuration. You will likely want to set this # to `0` in case you're using Rspamd (`ENABLE_RSPAMD=1`). # # - 0 => Disabled # - **1** => Enabled ENABLE_POLICYD_SPF=1 # 1 => Enables POP3 service # empty => disables POP3 ENABLE_POP3= # Enables ClamAV, and anti-virus scanner. # 1 => Enabled # **0** => Disabled ENABLE_CLAMAV=0 # Enables Rspamd # **0** => Disabled # 1 => Enabled ENABLE_RSPAMD=1 # When `ENABLE_RSPAMD=1`, an internal Redis instance is enabled implicitly. # This setting provides an opt-out to allow using an external instance instead. # 0 => Disabled # 1 => Enabled ENABLE_RSPAMD_REDIS= # When enabled, # # 1. the "[autolearning][rspamd-autolearn]" feature is turned on; # 2. the Bayes classifier will be trained when moving mails from or to the Junk folder (with the help of Sieve scripts). # # **0** => disabled # 1 => enabled RSPAMD_LEARN=0 # This settings controls whether checks should be performed on emails coming # from authenticated users (i.e. most likely outgoing emails). The default value # is `0` in order to align better with SpamAssassin. We recommend reading # through https://rspamd.com/doc/tutorials/scanning_outbound.html though to # decide for yourself whether you need and want this feature. RSPAMD_CHECK_AUTHENTICATED=0 # Controls whether the Rspamd Greylisting module is enabled. # This module can further assist in avoiding spam emails by greylisting # e-mails with a certain spam score. # # **0** => disabled # 1 => enabled RSPAMD_GREYLISTING=0 # Can be used to enable or disable the Hfilter group module. # # - 0 => Disabled # - **1** => Enabled RSPAMD_HFILTER=1 # Can be used to control the score when the HFILTER_HOSTNAME_UNKNOWN symbol applies. A higher score is more punishing. Setting it to 15 is equivalent to rejecting the email when the check fails. # # Default: 6 RSPAMD_HFILTER_HOSTNAME_UNKNOWN_SCORE=6 # Amavis content filter (used for ClamAV & SpamAssassin) # 0 => Disabled # 1 => Enabled ENABLE_AMAVIS=1 # -1/-2/-3 => Only show errors # **0** => Show warnings # 1/2 => Show default informational output # 3/4/5 => log debug information (very verbose) AMAVIS_LOGLEVEL=0 # This enables DNS block lists in Postscreen. # Note: Emails will be rejected, if they don't pass the block list checks! # **0** => DNS block lists are disabled # 1 => DNS block lists are enabled ENABLE_DNSBL=0 # If you enable Fail2Ban, don't forget to add the following lines to your `compose.yaml`: # cap_add: # - NET_ADMIN # Otherwise, `nftables` won't be able to ban IPs. ENABLE_FAIL2BAN=1 # Fail2Ban blocktype # drop => drop packet (send NO reply) # reject => reject packet (send ICMP unreachable) FAIL2BAN_BLOCKTYPE=drop # 1 => Enables Managesieve on port 4190 # empty => disables Managesieve ENABLE_MANAGESIEVE= # **enforce** => Allow other tests to complete. Reject attempts to deliver mail with a 550 SMTP reply, and log the helo/sender/recipient information. Repeat this test the next time the client connects. # drop => Drop the connection immediately with a 521 SMTP reply. Repeat this test the next time the client connects. # ignore => Ignore the failure of this test. Allow other tests to complete. Repeat this test the next time the client connects. This option is useful for testing and collecting statistics without blocking mail. POSTSCREEN_ACTION=enforce # empty => all daemons start # 1 => only launch postfix smtp SMTP_ONLY= # Please read [the SSL page in the documentation](https://docker-mailserver.github.io/docker-mailserver/latest/config/security/ssl) for more information. # # empty => SSL disabled # letsencrypt => Enables Let's Encrypt certificates # custom => Enables custom certificates # manual => Let's you manually specify locations of your SSL certificates for non-standard cases # self-signed => Enables self-signed certificates SSL_TYPE=letsencrypt # These are only supported with `SSL_TYPE=manual`. # Provide the path to your cert and key files that you've mounted access to within the container. SSL_CERT_PATH= SSL_KEY_PATH= # Optional: A 2nd certificate can be supported as fallback (dual cert support), eg ECDSA with an RSA fallback. # Useful for additional compatibility with older MTA and MUA (eg pre-2015). SSL_ALT_CERT_PATH= SSL_ALT_KEY_PATH= # Set how many days a virusmail will stay on the server before being deleted # empty => 7 days VIRUSMAILS_DELETE_DELAY= # Configure Postfix `virtual_transport` to deliver mail to a different LMTP client (default is a dovecot socket). # Provide any valid URI. Examples: # # empty => `lmtp:unix:/var/run/dovecot/lmtp` (default, configured in Postfix main.cf) # `lmtp:unix:private/dovecot-lmtp` (use socket) # `lmtps:inet:<host>:<port>` (secure lmtp with starttls) # `lmtp:<kopano-host>:2003` (use kopano as mailstore) POSTFIX_DAGENT= # Set the mailbox size limit for all users. If set to zero, the size will be unlimited (default). # # empty => 0 POSTFIX_MAILBOX_SIZE_LIMIT= # See https://docker-mailserver.github.io/docker-mailserver/edge/config/user-management/accounts/#notes # 0 => Dovecot quota is disabled # 1 => Dovecot quota is enabled ENABLE_QUOTAS=1 # Set the message size limit for all users. If set to zero, the size will be unlimited (not recommended!) # # empty => 10240000 (~10 MB) POSTFIX_MESSAGE_SIZE_LIMIT= # Mails larger than this limit won't be scanned. # ClamAV must be enabled (ENABLE_CLAMAV=1) for this. # # empty => 25M (25 MB) CLAMAV_MESSAGE_SIZE_LIMIT= # Enables regular pflogsumm mail reports. # This is a new option. The old REPORT options are still supported for backwards compatibility. If this is not set and reports are enabled with the old options, logrotate will be used. # # not set => No report # daily_cron => Daily report for the previous day # logrotate => Full report based on the mail log when it is rotated PFLOGSUMM_TRIGGER= # Recipient address for pflogsumm reports. # # not set => Use REPORT_RECIPIENT or POSTMASTER_ADDRESS # => Specify the recipient address(es) PFLOGSUMM_RECIPIENT= # Sender address (`FROM`) for pflogsumm reports if pflogsumm reports are enabled. # # not set => Use REPORT_SENDER # => Specify the sender address PFLOGSUMM_SENDER= # Interval for logwatch report. # # none => No report is generated # daily => Send a daily report # weekly => Send a report every week LOGWATCH_INTERVAL= # Recipient address for logwatch reports if they are enabled. # # not set => Use REPORT_RECIPIENT or POSTMASTER_ADDRESS # => Specify the recipient address(es) LOGWATCH_RECIPIENT= # Sender address (`FROM`) for logwatch reports if logwatch reports are enabled. # # not set => Use REPORT_SENDER # => Specify the sender address LOGWATCH_SENDER= # Defines who receives reports if they are enabled. # **empty** => ${POSTMASTER_ADDRESS} # => Specify the recipient address REPORT_RECIPIENT= # Defines who sends reports if they are enabled. # **empty** => mailserver-report@${DOMAINNAME} # => Specify the sender address REPORT_SENDER= # Changes the interval in which log files are rotated # **weekly** => Rotate log files weekly # daily => Rotate log files daily # monthly => Rotate log files monthly # # Note: This Variable actually controls logrotate inside the container # and rotates the log files depending on this setting. The main log output is # still available in its entirety via `docker logs mail` (Or your # respective container name). If you want to control logrotation for # the Docker-generated logfile see: # https://docs.docker.com/config/containers/logging/configure/ # # Note: This variable can also determine the interval for Postfix's log summary reports, see [`PFLOGSUMM_TRIGGER`](#pflogsumm_trigger). LOGROTATE_INTERVAL=weekly # If enabled, employs `reject_unknown_client_hostname` to sender restrictions in Postfix's configuration. # # - **0** => Disabled # - 1 => Enabled POSTFIX_REJECT_UNKNOWN_CLIENT_HOSTNAME=0 # Choose TCP/IP protocols for postfix to use # **all** => All possible protocols. # ipv4 => Use only IPv4 traffic. Most likely you want this behind Docker. # ipv6 => Use only IPv6 traffic. # # Note: More details at http://www.postfix.org/postconf.5.html#inet_protocols POSTFIX_INET_PROTOCOLS=all # Choose TCP/IP protocols for dovecot to use # **all** => Listen on all interfaces # ipv4 => Listen only on IPv4 interfaces. Most likely you want this behind Docker. # ipv6 => Listen only on IPv6 interfaces. # # Note: More information at https://dovecot.org/doc/dovecot-example.conf DOVECOT_INET_PROTOCOLS=all # ----------------------------------------------- # --- SpamAssassin Section ---------------------- # ----------------------------------------------- ENABLE_SPAMASSASSIN=0 # deliver spam messages in the inbox (eventually tagged using SA_SPAM_SUBJECT) SPAMASSASSIN_SPAM_TO_INBOX=1 # KAM is a 3rd party SpamAssassin ruleset, provided by the McGrail Foundation. # If SpamAssassin is enabled, KAM can be used in addition to the default ruleset. # - **0** => KAM disabled # - 1 => KAM enabled # # Note: only has an effect if `ENABLE_SPAMASSASSIN=1` ENABLE_SPAMASSASSIN_KAM=0 # spam messages will be moved in the Junk folder (SPAMASSASSIN_SPAM_TO_INBOX=1 required) MOVE_SPAM_TO_JUNK=1 # spam messages wil be marked as read MARK_SPAM_AS_READ=0 # add spam info headers if at, or above that level: SA_TAG=2.0 # add 'spam detected' headers at that level SA_TAG2=6.31 # triggers spam evasive actions SA_KILL=10.0 # add tag to subject if spam detected SA_SPAM_SUBJECT=***SPAM***** # ----------------------------------------------- # --- Fetchmail Section ------------------------- # ----------------------------------------------- ENABLE_FETCHMAIL=0 # The interval to fetch mail in seconds FETCHMAIL_POLL=300 # Use multiple fetchmail instances (1 per poll entry in fetchmail.cf) # Supports multiple IMAP IDLE connections when a server is used across multiple poll entries # https://otremba.net/wiki/Fetchmail_(Debian)#Immediate_Download_via_IMAP_IDLE FETCHMAIL_PARALLEL=0 # Enable or disable `getmail`. # # - **0** => Disabled # - 1 => Enabled ENABLE_GETMAIL=0 # The number of minutes for the interval. Min: 1; Max: 30. GETMAIL_POLL=5 # ----------------------------------------------- # --- LDAP Section ------------------------------ # ----------------------------------------------- # A second container for the ldap service is necessary (i.e. https://hub.docker.com/r/bitnami/openldap/) # empty => no # yes => LDAP over TLS enabled for Postfix LDAP_START_TLS= # empty => mail.example.com # Specify the `<dns-name>` / `<ip-address>` where the LDAP server is reachable via a URI like: `ldaps://mail.example.com`. # Note: You must include the desired URI scheme (`ldap://`, `ldaps://`, `ldapi://`). LDAP_SERVER_HOST= # empty => ou=people,dc=domain,dc=com # => e.g. LDAP_SEARCH_BASE=dc=mydomain,dc=local LDAP_SEARCH_BASE= # empty => cn=admin,dc=domain,dc=com # => take a look at examples of SASL_LDAP_BIND_DN LDAP_BIND_DN= # empty** => admin # => Specify the password to bind against ldap LDAP_BIND_PW= # e.g. `"(&(mail=%s)(mailEnabled=TRUE))"` # => Specify how ldap should be asked for users LDAP_QUERY_FILTER_USER= # e.g. `"(&(mailGroupMember=%s)(mailEnabled=TRUE))"` # => Specify how ldap should be asked for groups LDAP_QUERY_FILTER_GROUP= # e.g. `"(&(mailAlias=%s)(mailEnabled=TRUE))"` # => Specify how ldap should be asked for aliases LDAP_QUERY_FILTER_ALIAS= # e.g. `"(&(|(mail=*@%s)(mailalias=*@%s)(mailGroupMember=*@%s))(mailEnabled=TRUE))"` # => Specify how ldap should be asked for domains LDAP_QUERY_FILTER_DOMAIN= # ----------------------------------------------- # --- Dovecot Section --------------------------- # ----------------------------------------------- # empty => no # yes => LDAP over TLS enabled for Dovecot DOVECOT_TLS= # e.g. `"(&(objectClass=PostfixBookMailAccount)(uniqueIdentifier=%n))"` DOVECOT_USER_FILTER= # e.g. `"(&(objectClass=PostfixBookMailAccount)(uniqueIdentifier=%n))"` DOVECOT_PASS_FILTER= # Define the mailbox format to be used # default is maildir, supported values are: sdbox, mdbox, maildir DOVECOT_MAILBOX_FORMAT=maildir # empty => no # yes => Allow bind authentication for LDAP # https://wiki.dovecot.org/AuthDatabase/LDAP/AuthBinds DOVECOT_AUTH_BIND= # ----------------------------------------------- # --- Postgrey Section -------------------------- # ----------------------------------------------- ENABLE_POSTGREY=0 # greylist for N seconds POSTGREY_DELAY=300 # delete entries older than N days since the last time that they have been seen POSTGREY_MAX_AGE=35 # response when a mail is greylisted POSTGREY_TEXT="Delayed by Postgrey" # whitelist host after N successful deliveries (N=0 to disable whitelisting) POSTGREY_AUTO_WHITELIST_CLIENTS=5 # ----------------------------------------------- # --- SASL Section ------------------------------ # ----------------------------------------------- ENABLE_SASLAUTHD=0 # empty => pam # `ldap` => authenticate against ldap server # `shadow` => authenticate against local user db # `mysql` => authenticate against mysql db # `rimap` => authenticate against imap server # Note: can be a list of mechanisms like pam ldap shadow SASLAUTHD_MECHANISMS= # empty => None # e.g. with SASLAUTHD_MECHANISMS rimap you need to specify the ip-address/servername of the imap server ==> xxx.xxx.xxx.xxx SASLAUTHD_MECH_OPTIONS= # empty => Use value of LDAP_SERVER_HOST # Note: You must include the desired URI scheme (`ldap://`, `ldaps://`, `ldapi://`). SASLAUTHD_LDAP_SERVER= # empty => Use value of LDAP_BIND_DN # specify an object with privileges to search the directory tree # e.g. active directory: SASLAUTHD_LDAP_BIND_DN=cn=Administrator,cn=Users,dc=mydomain,dc=net # e.g. openldap: SASLAUTHD_LDAP_BIND_DN=cn=admin,dc=mydomain,dc=net SASLAUTHD_LDAP_BIND_DN= # empty => Use value of LDAP_BIND_PW SASLAUTHD_LDAP_PASSWORD= # empty => Use value of LDAP_SEARCH_BASE # specify the search base SASLAUTHD_LDAP_SEARCH_BASE= # empty => default filter `(&(uniqueIdentifier=%u)(mailEnabled=TRUE))` # e.g. for active directory: `(&(sAMAccountName=%U)(objectClass=person))` # e.g. for openldap: `(&(uid=%U)(objectClass=person))` SASLAUTHD_LDAP_FILTER= # empty => no # yes => LDAP over TLS enabled for SASL # If set to yes, the protocol in SASLAUTHD_LDAP_SERVER must be ldap:// or missing. SASLAUTHD_LDAP_START_TLS= # empty => no # yes => Require and verify server certificate # If yes you must/could specify SASLAUTHD_LDAP_TLS_CACERT_FILE or SASLAUTHD_LDAP_TLS_CACERT_DIR. SASLAUTHD_LDAP_TLS_CHECK_PEER= # File containing CA (Certificate Authority) certificate(s). # empty => Nothing is added to the configuration # Any value => Fills the `ldap_tls_cacert_file` option SASLAUTHD_LDAP_TLS_CACERT_FILE= # Path to directory with CA (Certificate Authority) certificates. # empty => Nothing is added to the configuration # Any value => Fills the `ldap_tls_cacert_dir` option SASLAUTHD_LDAP_TLS_CACERT_DIR= # Specify what password attribute to use for password verification. # empty => Nothing is added to the configuration but the documentation says it is `userPassword` by default. # Any value => Fills the `ldap_password_attr` option SASLAUTHD_LDAP_PASSWORD_ATTR= # empty => `bind` will be used as a default value # `fastbind` => The fastbind method is used # `custom` => The custom method uses userPassword attribute to verify the password SASLAUTHD_LDAP_AUTH_METHOD= # Specify the authentication mechanism for SASL bind # empty => Nothing is added to the configuration # Any value => Fills the `ldap_mech` option SASLAUTHD_LDAP_MECH= # ----------------------------------------------- # --- SRS Section ------------------------------- # ----------------------------------------------- # envelope_sender => Rewrite only envelope sender address (default) # header_sender => Rewrite only header sender (not recommended) # envelope_sender,header_sender => Rewrite both senders # An email has an "envelope" sender (indicating the sending server) and a # "header" sender (indicating who sent it). More strict SPF policies may require # you to replace both instead of just the envelope sender. SRS_SENDER_CLASSES=envelope_sender # empty => Envelope sender will be rewritten for all domains # provide comma separated list of domains to exclude from rewriting SRS_EXCLUDE_DOMAINS= # empty => generated when the image is built # provide a secret to use in base64 # you may specify multiple keys, comma separated. the first one is used for # signing and the remaining will be used for verification. this is how you # rotate and expire keys SRS_SECRET= # ----------------------------------------------- # --- Default Relay Host Section ---------------- # ----------------------------------------------- # Setup relaying all mail through a default relay host # # empty => don't configure default relay host # default host and optional port to relay all mail through DEFAULT_RELAY_HOST= # ----------------------------------------------- # --- Multi-Domain Relay Section ---------------- # ----------------------------------------------- # Setup relaying for multiple domains based on the domain name of the sender # optionally uses usernames and passwords in postfix-sasl-password.cf and relay host mappings in postfix-relaymap.cf # # empty => don't configure relay host # default host to relay mail through RELAY_HOST= # empty => 25 # default port to relay mail RELAY_PORT=25 # empty => no default # default relay username (if no specific entry exists in postfix-sasl-password.cf) RELAY_USER= # empty => no default # password for default relay user RELAY_PASSWORD= -
ssl.conf 域名部分替换自己的域名
server { listen 443 ssl; server_name mail.域名; ssl_certificate /etc/letsencrypt/live/mail.域名/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/mail.域名/privkey.pem; ssl_session_timeout 5m; ssl_ciphers ECDHE-RSA-AES128-GCM-SHA256:ECDHE:ECDH:AES:HIGH:!NULL:!aNULL:!MD5:!ADH:!RC4; ssl_protocols TLSv1 TLSv1.1 TLSv1.2; ssl_prefer_server_ciphers on; ssl_dhparam /etc/letsencrypt/dhparams/dhparam.pem; error_page 500 502 503 504 404 403 /error.html; #error_page 404 /error.html; location = /error.html { root html; } #只允许 get,post,head方式的请求，其他的不安全也没有用到，不接受 if ($request_method !~ ^(GET|HEAD|POST)$) { return 404; } location / { root html; } } -
启动服务器
docker compose up, 稍等片刻之后另一个ssh窗口登录服务器执行如下命令：#新增用户： docker exec -ti mail setup email add me@域名 # 生成DKIM： docker exec -ti mail setup config dkim # 生成的记录值复制到域名解析name为mail._domainkey这个的值
至此如果不出意外的可以成功接发邮件了，通过客户端登录测试吧（pc端outlook或者其他，手机客户端outlook或者自带的）smtp,imap服务器地址都是mail.域名，用户名/密码 me@域名/密码
有什么问题可以联系我：
- https://123456.blog
- me@mgl.pub
3225
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
