Simple postfix relay host ("postfix null client") for your Docker containers. Based on Debian (default), Ubuntu and Alpine Linux. Feel free to pick your favourite distro.
RELAYHOST
, RELAYHOST_USERNAME
and RELAYHOST_PASSWORD
POSTFIX_smtp_tls_security_level
XOAUTH2_CLIENT_ID
, XOAUTH2_SECRET
, XOAUTH2_INITIAL_ACCESS_TOKEN
, XOAUTH2_INITIAL_REFRESH_TOKEN
and XOAUTH2_TOKEN_ENDPOINT
MASQUERADED_DOMAINS
SMTP_HEADER_CHECKS
POSTFIX_myhostname
POSTFIX_mynetworks
POSTFIX_message_size_limit
SKIP_ROOT_SPOOL_CHOWN
ANONYMIZE_EMAILS
This image allows you to run POSTFIX internally inside your docker cloud/swarm installation to centralise outgoing email sending. The embedded postfix enables you to either send messages directly or relay them to your company's main server.
This is a server side POSTFIX image, geared towards emails that need to be sent from your applications. That's why this postfix configuration does not support username / password login or similar client-side security features.
IF YOU WANT TO SET UP AND MANAGE A POSTFIX INSTALLATION FOR END USERS, THIS IMAGE IS NOT FOR YOU. If you need it to manage your application's outgoing queue, read on.
To run the container, do the following:
docker run --rm --name postfix -e "ALLOWED_SENDER_DOMAINS=example.com" -p 1587:587 boky/postfix
or
helm repo add bokysan https://bokysan.github.io/docker-postfix/ helm upgrade --install --set persistence.enabled=false --set config.general.ALLOW_EMPTY_SENDER_DOMAINS=yes mail bokysan/mail
You can also find this image at ArtifactHub.
You can now send emails by using localhost:1587
(on Docker) as your SMTP server address. Note that if you haven't configured your domain
to allow sending from this IP/server/nameblock, your emails will most likely be regarded as spam.
All standard caveats of configuring the SMTP server apply:
If you don't know what any of the above means, get some help. Google is your friend. It's also worth noting that it's pretty difficult to host a SMTP server on a dynamic IP address.
Please note that the image uses the submission (587) port by default. Port 25 is not exposed on purpose, as it's regularly blocked by ISPs, already occupied by other services, and in general should only be used for server-to-server communication.
Several potentially "surprising" changes went into this issue and hence warrant a version upgrade:
v
and without v
prefix.
As seen in PR #141 some tools rely on version not
having the prefix. I've seen both in the wild, so the image
now includes both. This should work and should hopefully provide most compatibility.master
branch now builds images called edge
.
latest
images are built from the last tag. We've had several issues with people using the latest
tag
and reporting problems. You can now rely on latest
being the latest stable release.linux/386
, linux/amd64
, linux/arm/v5
, linux/arm/v6
, linux/arm/v7
, linux/arm64
, linux/arm64/v8
, linux/mips64le
,
linux/ppc64le
and linux/s390x
.smtpd_tls_security_level
is now set to may
. If you encounter
issues, try setting it to none
explicitly (see #160).There's a potentially breaking change introduced now in v3.0.0
: Oracle has changed the license of BerkleyDB to AGPL-3.0, making it
unsuitable to link to packages with GPL-incompatible licenses. As a result Alpine (on which this image is based)
has deprecated BerkleyDB throughout the image:
Support for Postfix
hash
andbtree
databases has been removed.lmdb
is the recommended replacement. Before upgrading, all tables in/etc/postfix/main.cf
usinghash
andbtree
must be changed to a supported alternative. See the Postfix lookup table documentation for more information.
While this should not affect most of the users (/etc/postfix/main.cf
is managed by this image), there might be use cases where
people have their own configuration which relies on hash
and btree
databases. To avoid braking live systems, the version of this
image has been updated to v3.0.0
.
Available for all your favourite architectures. Run in your server cluster. Run it on your Raspberry Pi 4. Run it on your ancient Pentium or an old Beaglebone. The following architectures are supported: linux/386
, linux/amd64
, linux/arm/v6
, linux/arm/v7
, linux/arm64
and linux/ppc64le
.
TZ
= The timezone for the image, e.g. Europe/Amsterdam
FORCE_COLOR
= Set to 1
to force color output (otherwise auto-detected)INBOUND_DEBUGGING
= Set to 1
to enable detailed debugging in the logsALLOWED_SENDER_DOMAINS
= domains which are allowed to send email via this serverALLOW_EMPTY_SENDER_DOMAINS
= if value is set (i.e: true
), ALLOWED_SENDER_DOMAINS
can be unsetLOG_FORMAT
= Set your log format (JSON or plain)Enable additional debugging for any connection coming from POSTFIX_mynetworks
. Set to a non-empty string (usually 1
or yes
) to enable debugging.
ALLOWED_SENDER_DOMAINS
and ALLOW_EMPTY_SENDER_DOMAINS
Due to in-built spam protection in Postfix you will need to specify sender domains -- the domains you are using to send your emails from, otherwise Postfix will refuse to start.
Example:
docker run --rm --name postfix -e "ALLOWED_SENDER_DOMAINS=example.com example.org" -p 1587:587 boky/postfix
If you want to set the restrictions on the recipient and not on the sender (anyone can send mails but just to a single domain
for instance), set ALLOW_EMPTY_SENDER_DOMAINS
to a non-empty value (e.g. true
) and ALLOWED_SENDER_DOMAINS
to an empty
string. Then extend this image through custom scripts to configure Postfix further.
The image will by default output logs in human-readable (plain
) format. If you are deploying the image to Kubernetes, it might
be worth changing the output format to json
as it's more easily parsable by tools such as Prometheus.
To change the log format, set the (unsurprisingly named) variable LOG_FORMAT=json
.
RELAYHOST
= Host that relays your messagesSASL_RELAYHOST
= (optional) Relay Host referenced in the sasl_passwd
file. Defaults to the value of RELAYHOST
RELAYHOST_USERNAME
= An (optional) username for the relay serverRELAYHOST_PASSWORD
= An (optional) login password for the relay serverRELAYHOST_PASSWORD_FILE
= An (optional) file containing the login password for the relay server. Mutually exclusive with the previous option.POSTFIX_smtp_tls_security_level
= Relay host TLS connection levelXOAUTH2_CLIENT_ID
= OAuth2 client id used when configured as a relayhost.XOAUTH2_SECRET
= OAuth2 secret used when configured as a relayhost.XOAUTH2_INITIAL_ACCESS_TOKEN
= Initial OAuth2 access token.XOAUTH2_INITIAL_REFRESH_TOKEN
= Initial OAuth2 refresh token.XOAUTH2_TOKEN_ENDPOINT
= Token endpoint provided four your XOAUTH App , GMail use : https://accounts.google.com/o/oauth2/tokenSMTPD_SASL_USERS
= Users allow to send mail (ex: user1:pass1,user2:pass2,...). Warning: Users need to be specified with a domain, as explained
on ticket [#192]. This image will automatically add a domain if one is not provided and will
issue a notice when that happens.MASQUERADED_DOMAINS
= domains where you want to masquerade internal hostsSMTP_HEADER_CHECKS
= Set to 1
to enable header checks of to a location of the file for header checksPOSTFIX_myhostname
= Set the name of this postfix serverPOSTFIX_mynetworks
= Allow sending mails only from specific networks ( default 127.0.0.0/8,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16
)POSTFIX_message_size_limit
= The maximum size of the message, in bytes, by default it's unlimitedPOSTFIX_<any_postfix_setting>
= provide any additional postfix settingRELAYHOST
, RELAYHOST_USERNAME
and RELAYHOST_PASSWORD
Postfix will try to deliver emails directly to the target server. If you are behind a firewall, or inside a corporation you will most likely have a dedicated outgoing mail server. By setting this option, you will instruct postfix to relay (hence the name) all incoming emails to the target server for actual delivery.
Example:
docker run --rm --name postfix -e RELAYHOST=192.168.115.215 -p 1587:587 boky/postfix
You may optionally specifiy a relay port, e.g.:
docker run --rm --name postfix -e RELAYHOST=192.168.115.215:587 -p 1587:587 boky/postfix
Or an IPv6 address, e.g.:
docker run --rm --name postfix -e
AI小说写作助手,一站式润色、改写、扩写
蛙蛙写作—国内先进的AI写作平台,涵盖小说、学术、社交媒体等多场景。提供续写、改写、润色等功能,助力创作者高效优化写作流程。界面简洁,功能全面,适合各类写作者提升内容品质和工作效率。
字节跳动发布的AI编程神器IDE
Trae是一种自适应的集成开发环境(IDE),通过自动化和多元协作改变开发流程。利用Trae,团队能够更快速、精确地编写和部署代码,从而提高编程效率和项目交付速度。Trae具备上下文感知和代码自动完成功能,是提升开发效率的理想工具。
全能AI智能助手,随时解答生活与工作的多样问题
问小白,由元石科技研发的AI智能助手,快速准确地解答各种生活和工作问题,包括但不限于搜索、规划和社交互动,帮助用户在日常生活中提高效率,轻松管理个人事务。
实时语音翻译/同声传译工具
Transly是一个多场景的AI大语言模型驱动的同声传译、专业翻译助手,它拥有超精准的音频识别翻译能力,几乎零延迟的使用体验和支持多国语言可以让你带它走遍全球,无论你是留学生、商务人士、韩剧美剧爱好者,还是出国游玩、多国会议、跨国追星等等,都可以满足你所有需要同传的场景需求,线上线下通用,扫除语言障碍,让全世界的语言交流不再有国界。