bokysan/docker-postfix
1
1
Fork 0
mirror of https://github.com/bokysan/docker-postfix.git synced 2024-11-10 08:55:39 +08:00
Code Issues Projects Releases Packages Wiki Activity
docker-postfix/Dockerfile

57 lines
2.1 KiB
Text
Raw Normal View History

Swiched from alpine:edge to alpine:latest. Fixed some typos.
2018-11-13 19:05:58 +08:00
FROM alpine:latest
Initial support for DKIM and testing This commit brings two important features: - **DKIM support** It's now possible to configure this postfix image to sign messages using DKIM by simply generating the keys and providing them in the approprate folder. This should bring us one step closer to directly sending out emails without relying on a 3rd-party proxy. - **test support** A nice and handy script, conviniently called `test.sh` has been provided, builds the image, spins it up and tries to send out an email. You'll need `docker-compose` to run it, though.
2019-02-19 17:49:55 +08:00
LABEL maintaner="Bojan Cekrlic - https://github.com/bokysan/docker-postfix/"
Postfix, initial release
2016-03-18 07:06:12 +08:00
NEW FEATURE: A new feature has been added -- it's now posible to specify a RELAY hosts's username and password, if your remote host requires authentication. NEW FEATURE: The possibility to execute third party scripts. This should make extending this image easier. REFACTORING: Dockerfile now starts with run.sh instead of suprevisor. This makes it much easier to see any errors that might creep into the code. Also note that the script now relies on POSIX-compliant commands only so the executor has been changed from /bin/bash to /bin/sh.
2017-11-02 21:16:52 +08:00
# See README.md for details
Postfix, initial release
2016-03-18 07:06:12 +08:00
Major update, better support for handling TLS connections. This update includes a few features that make it easier to work with relay hosts. The configuration now uses built-in (Alpine) TLS certificates and allows the user to specify how the Postfix should establish a TLS connection. Configure it using `RELAYHOST_TLS_LEVEL`, if needed. Another configuration option was added, `MESSAGE_SIZE_LIMIT`, which enables you to reject messages exceeding certain limits. Especially useful with relay servers, to prevent messages getting stuck in Postfix queue. Use the `INBOUND_DEBUGGING` parameter to enable additional postfix logs for incoming messages when things go south. Use `TZ` parameter to set the timezone of the container (especially useful for logs and dates in the messages). *Notice that `ALLOWED_SENDER_DOMAINS` is now a neccessary parameter.* Turns out that due to Postfix anti-spam configuration there's no way to start it properly without specifying the domains it will relay email for. This commit also includes a few samples of running the container: - standalone - in [docker-compose](https://docs.docker.com/compose/) Further work: add a working Kubernetes / Helm chart example.
2019-01-02 17:10:17 +08:00
# Set the timezone for the container, if needed.
ENV TZ=
Minor edits for easier understanding. The Dockerfile has been reformatted a bit to make it more clear and easy to understand. README.md has been updated with the postfix's user account details.
2018-07-27 22:42:35 +08:00
# Postfix myhostname
ENV HOSTNAME=
# Host that relays your msgs
ENV RELAYHOST=
# An (optional) username for the relay server
ENV RELAYHOST_USERNAME=
# An (optional) login password for the relay server
ENV RELAYHOST_PASSWORD=
Major update, better support for handling TLS connections. This update includes a few features that make it easier to work with relay hosts. The configuration now uses built-in (Alpine) TLS certificates and allows the user to specify how the Postfix should establish a TLS connection. Configure it using `RELAYHOST_TLS_LEVEL`, if needed. Another configuration option was added, `MESSAGE_SIZE_LIMIT`, which enables you to reject messages exceeding certain limits. Especially useful with relay servers, to prevent messages getting stuck in Postfix queue. Use the `INBOUND_DEBUGGING` parameter to enable additional postfix logs for incoming messages when things go south. Use `TZ` parameter to set the timezone of the container (especially useful for logs and dates in the messages). *Notice that `ALLOWED_SENDER_DOMAINS` is now a neccessary parameter.* Turns out that due to Postfix anti-spam configuration there's no way to start it properly without specifying the domains it will relay email for. This commit also includes a few samples of running the container: - standalone - in [docker-compose](https://docs.docker.com/compose/) Further work: add a working Kubernetes / Helm chart example.
2019-01-02 17:10:17 +08:00
# Define relay host TLS connection level. See http://www.postfix.org/postconf.5.html#smtp_tls_security_level for details.
# By default, the permissive level ("may") is used, if not defined.
ENV RELAYHOST_TLS_LEVEL=
Minor edits for easier understanding. The Dockerfile has been reformatted a bit to make it more clear and easy to understand. README.md has been updated with the postfix's user account details.
2018-07-27 22:42:35 +08:00
# Allow domains from per Network ( default 127.0.0.0/8,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16 )
ENV MYNETWORKS=127.0.0.0/8,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16
# Allow any sender domains
ENV ALLOWED_SENDER_DOMAINS=
Major update, better support for handling TLS connections. This update includes a few features that make it easier to work with relay hosts. The configuration now uses built-in (Alpine) TLS certificates and allows the user to specify how the Postfix should establish a TLS connection. Configure it using `RELAYHOST_TLS_LEVEL`, if needed. Another configuration option was added, `MESSAGE_SIZE_LIMIT`, which enables you to reject messages exceeding certain limits. Especially useful with relay servers, to prevent messages getting stuck in Postfix queue. Use the `INBOUND_DEBUGGING` parameter to enable additional postfix logs for incoming messages when things go south. Use `TZ` parameter to set the timezone of the container (especially useful for logs and dates in the messages). *Notice that `ALLOWED_SENDER_DOMAINS` is now a neccessary parameter.* Turns out that due to Postfix anti-spam configuration there's no way to start it properly without specifying the domains it will relay email for. This commit also includes a few samples of running the container: - standalone - in [docker-compose](https://docs.docker.com/compose/) Further work: add a working Kubernetes / Helm chart example.
2019-01-02 17:10:17 +08:00
# Attachments size. 0 means unlimited. Usually needs to be set if your relay host has an attachment size limit
ENV MESSAGE_SIZE_LIMIT=
# Enable additional debugging for connections to postfix
ENV INBOUND_DEBUGGING=
Postfix, initial release
2016-03-18 07:06:12 +08:00
Major update, better support for handling TLS connections. This update includes a few features that make it easier to work with relay hosts. The configuration now uses built-in (Alpine) TLS certificates and allows the user to specify how the Postfix should establish a TLS connection. Configure it using `RELAYHOST_TLS_LEVEL`, if needed. Another configuration option was added, `MESSAGE_SIZE_LIMIT`, which enables you to reject messages exceeding certain limits. Especially useful with relay servers, to prevent messages getting stuck in Postfix queue. Use the `INBOUND_DEBUGGING` parameter to enable additional postfix logs for incoming messages when things go south. Use `TZ` parameter to set the timezone of the container (especially useful for logs and dates in the messages). *Notice that `ALLOWED_SENDER_DOMAINS` is now a neccessary parameter.* Turns out that due to Postfix anti-spam configuration there's no way to start it properly without specifying the domains it will relay email for. This commit also includes a few samples of running the container: - standalone - in [docker-compose](https://docs.docker.com/compose/) Further work: add a working Kubernetes / Helm chart example.
2019-01-02 17:10:17 +08:00
# Install supervisor, postfix
More resillient builds It turns out that builds cannot be predictable - different accounts were assigned by different build systems. Consequentially we install each tool separately.
2019-02-19 19:08:13 +08:00
# Install postfix first to get the first account (101)
# Install opendkim second to get the second account (102)
Minor edits for easier understanding. The Dockerfile has been reformatted a bit to make it more clear and easy to understand. README.md has been updated with the postfix's user account details.
2018-07-27 22:42:35 +08:00
RUN true && \
Fix for #12 where Alpine 3.9 split cyrus-sasl into multiple packages: https://bugs.alpinelinux.org/issues/9987
2019-05-13 19:28:55 +08:00
apk add --no-cache --upgrade cyrus-sasl cyrus-sasl-plain cyrus-sasl-login && \
apk add --no-cache postfix && \
More resillient builds It turns out that builds cannot be predictable - different accounts were assigned by different build systems. Consequentially we install each tool separately.
2019-02-19 19:08:13 +08:00
apk add --no-cache opendkim && \
apk add --no-cache ca-certificates tzdata supervisor rsyslog && \
Minor edits for easier understanding. The Dockerfile has been reformatted a bit to make it more clear and easy to understand. README.md has been updated with the postfix's user account details.
2018-07-27 22:42:35 +08:00
apk add --no-cache --upgrade musl musl-utils && \
(rm "/tmp/"* 2>/dev/null || true) && (rm -rf /var/cache/apk/* 2>/dev/null || true)
Postfix, initial release
2016-03-18 07:06:12 +08:00
Minor edits for easier understanding. The Dockerfile has been reformatted a bit to make it more clear and easy to understand. README.md has been updated with the postfix's user account details.
2018-07-27 22:42:35 +08:00
# Set up configuration
COPY supervisord.conf /etc/supervisord.conf
COPY rsyslog.conf /etc/rsyslog.conf
Initial support for DKIM and testing This commit brings two important features: - **DKIM support** It's now possible to configure this postfix image to sign messages using DKIM by simply generating the keys and providing them in the approprate folder. This should bring us one step closer to directly sending out emails without relying on a 3rd-party proxy. - **test support** A nice and handy script, conviniently called `test.sh` has been provided, builds the image, spins it up and tries to send out an email. You'll need `docker-compose` to run it, though.
2019-02-19 17:49:55 +08:00
COPY opendkim.conf /etc/opendkim/opendkim.conf
Added HEADER_CHECKS configuration option (#15) * Added HEADER_CHECKS configuration option
2019-10-03 15:01:53 +08:00
COPY header_checks /etc/header_checks
Minor edits for easier understanding. The Dockerfile has been reformatted a bit to make it more clear and easy to understand. README.md has been updated with the postfix's user account details.
2018-07-27 22:42:35 +08:00
COPY run.sh /run.sh
Initial support for DKIM and testing This commit brings two important features: - **DKIM support** It's now possible to configure this postfix image to sign messages using DKIM by simply generating the keys and providing them in the approprate folder. This should bring us one step closer to directly sending out emails without relying on a 3rd-party proxy. - **test support** A nice and handy script, conviniently called `test.sh` has been provided, builds the image, spins it up and tries to send out an email. You'll need `docker-compose` to run it, though.
2019-02-19 17:49:55 +08:00
COPY opendkim.sh /opendkim.sh
RUN chmod +x /run.sh /opendkim.sh
Postfix, initial release
2016-03-18 07:06:12 +08:00
Initial support for DKIM and testing This commit brings two important features: - **DKIM support** It's now possible to configure this postfix image to sign messages using DKIM by simply generating the keys and providing them in the approprate folder. This should bring us one step closer to directly sending out emails without relying on a 3rd-party proxy. - **test support** A nice and handy script, conviniently called `test.sh` has been provided, builds the image, spins it up and tries to send out an email. You'll need `docker-compose` to run it, though.
2019-02-19 17:49:55 +08:00
# Set up volumes
VOLUME [ "/var/spool/postfix", "/etc/postfix", "/etc/opendkim/keys" ]
Postfix, initial release
2016-03-18 07:06:12 +08:00
Minor edits for easier understanding. The Dockerfile has been reformatted a bit to make it more clear and easy to understand. README.md has been updated with the postfix's user account details.
2018-07-27 22:42:35 +08:00
# Run supervisord
USER root
WORKDIR /tmp
EXPOSE 587
Initial support for DKIM and testing This commit brings two important features: - **DKIM support** It's now possible to configure this postfix image to sign messages using DKIM by simply generating the keys and providing them in the approprate folder. This should bring us one step closer to directly sending out emails without relying on a 3rd-party proxy. - **test support** A nice and handy script, conviniently called `test.sh` has been provided, builds the image, spins it up and tries to send out an email. You'll need `docker-compose` to run it, though.
2019-02-19 17:49:55 +08:00
CMD ["/bin/sh", "-c", "/run.sh"]
Reference in a new issue Copy permalink