Insular email distribution - mail server as Docker images

Mailu

Last update: Jan 4, 2023

Related tags

Communication letsencrypt docker mail docker-compose email imap smtp dkim webmail pop3 mailserver dmarc fetchmail

Overview

Mailu is a simple yet full-featured mail server as a set of Docker images. It is free software (both as in free beer and as in free speech), open to suggestions and external contributions. The project aims at providing people with an easily setup, easily maintained and full-featured mail server while not shipping proprietary software nor unrelated features often found in popular groupware.

Most of the documentation is available on our Website, you can also try our demo server before setting up your own, and come talk to us on Matrix.

Features

Main features include:

Standard email server, IMAP and IMAP+, SMTP and Submission
Advanced email features, aliases, domain aliases, custom routing
Web access, multiple Webmails and administration interface
User features, aliases, auto-reply, auto-forward, fetched accounts
Admin features, global admins, announcements, per-domain delegation, quotas
Security, enforced TLS, Letsencrypt!, outgoing DKIM, anti-virus scanner
Antispam, auto-learn, greylisting, DMARC and SPF
Freedom, all FOSS components, no tracker included

Contributing

Mailu is free software, open to suggestions and contributions. All components are free software and compatible with the MIT license. All specific configuration files, Dockerfiles and code are placed under the MIT license.

Comments

Arm32v6/7 or Arm64v8 for docker?

Is it possible to use an arm machine for mailu? I've looked through the tags and there doesn't seem to be a specific arm tag, and I can't see if a manifest has been made.

If not, are there build docker instructions so I could build the images myself?
status/wip

opened by psyciknz 240
Adding support for arm64 images
What type of PR?

Enhancement & bug-fix (fix #1200)

What does this PR do?

This PR adds support for arm64 architecture, thanks to Travis multi-platform capabilities. Tests are done on both amd64 and arm64 architectures, and manifest(s) are created with the same image naming than current naming, so that the PR is transparent for the existing users, and no change is needed on the setup/flavor side.

Related issue(s)

Fix #1200

Prerequistes

[X] In case of feature or enhancement: documentation updated accordingly

[X] Unless it's docs or a minor change: add changelog entry file.

type/enhancement
opened by ofthesun9 70
Discussion about project management

Hi to everyone. First of I want to apologize for not being as reactive as I would like: my work and personal life have taken a turn where I cannot spend more than a couple hours per week on my projects, and I still have a few of them running.

Mailu remains one the most depending projects and I would like to give it a proper care, and that probably means giving the community more credit for its contributions. I can count at least 5 people providing more meaningful contributions than I have in the past month and that I would like to empower somehow in the project.

I have invited main contributors to the team, as team members, so they can review pull requests with automated merge coming along the way, and manage issues. I hope this will help Mailu live even when I cannot connect for multiple weeks. I will also make sure that I am privately available to main contributors and that we can properly discuss strategies.

Finally, we have discussed financing the development in a previous issue (#508). I have decided to setup a Patreon (https://www.patreon.com/kaiyou). The idea is that I might keep small amounts to keep the project going (pay for Github fees, maybe a demo server again as it expired) and will redistribute the rest to contributors.

Any comment is welcome :)
type/discussion

opened by kaiyou 65
Switch to a base image containing base tools and the podop and socrate libs

What type of PR?

enhancement of build process

What does this PR do?

Changes build.hcl to build core images using a base image. Also adds a "assets" base image for the admin container.
type/enhancement

opened by ghostwheel42 55
Implement #2510: oletools integration
What type of PR?

Feature

What does this PR do?

OLETools now flags documents with macros and rejects suspicious ones. We also block executable file extensions by default (but don't perform inspection in archives: you can tell users to zip-up whatever needs sending).

Related issue(s)

closes #2510

closes #2511

Prerequisites

Before we can consider review and merge, please make sure the following list is done and checked. If an entry in not applicable, you can check it or remove it from the list.

[ ] In case of feature or enhancement: documentation updated accordingly

[x] Unless it's docs or a minor change: add changelog entry file.

priority/p2 type/feature
opened by nextgens 53
Nginx Reverse Proxy error
SOLUTION: https://github.com/linuxserver/reverse-proxy-confs/pull/154

TO-DO:

[x] Reverse-proxy

[x] Fix login fail to webmail, seems to be a 301 nginx error

Im using this image: https://hub.docker.com/r/linuxserver/letsencrypt/

And im trying to create a mailu.subfolder.conf or even better a mailu.subdomain.conf, but first i am trying to do it with a subfolder, because of the wiki https://mailu.io/1.7/reverse.html

Now my problem, i have 0 idea of how to create a reverse proxy and the wiki its confusing for me, because i have tried almost every issue open or close here talking about reverse proxy and i have nothing only this page showing:

I would like to get help and create a mailu.subfolder.conf and add it to https://github.com/linuxserver/reverse-proxy-confs to avoid getting the same errors.

i have tried too to edit a pre-configured reverse-proxy i took as example adminer:

# adminer does not require a base url setting, but the container needs to be named adminer location /adminer { return 301 $scheme://$host/adminer/; } location ^~ /adminer/ { # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable the next two lines for ldap auth, also customize and enable ldap.conf in the default conf #auth_request /auth; #error_page 401 =200 /login; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app adminer; set $upstream_port 8080; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port;

And did this (i have tried first to get working atleast /admin and them make works /webmail, but i couldnt 😢 ):

# adminer does not require a base url setting, but the container needs to be named adminer location /admin{ return 301 $scheme://$host/admin/; } location ^~ /admin/ { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app front; set $upstream_port 8080; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port/admin; }

Got same error

And i dont know what to test more, because i have trying this 4 days, if someone could help me would be amazing, because i dont want to rent another VPS to only host Mailu.

I creating the files at:

Proxy-confs folder: /nginx/proxy-confs

Nginx Folder: /nginx/
opened by vinanrra 49
Resolve HOST to ADDRESS only if ADDRESS is not already set
What type of PR?

bug-fix

What does this PR do?

~Makes the rsolving from hosts to ips at startup configurable~

I rewrote the pull request after #940 was merged. Now it resolves HOSTs to ADDRESSes only of ADDRESSes are not already set. So on kubernetes we can jsut set the address and have working service discovery.

Related issue(s)

closes #1113

Prerequistes

~Minor change, backward compatible~ Changelog will be added
opened by micw 49
ClamAV using all my disk space

Hi, ClamAV keep's using all my disk space, and there is no option in the .env to limit it. It seems to be the temp files e.g. /home/core/mailu/filters/clamav-0033b19aa8a68887f57a9126f168010d.tmp

Anyone know how to limit the disk usage? Seen as though I have 1gb memory.

Thank you, Jamie
priority/p0 type/security type/bug

opened by jbonnett92 49
Rework the anti-spoofing rule
What type of PR?

Feature

What does this PR do?

We shouldn't assume that Mailu is the only MTA allowed to send emails on behalf of the domains it hosts. We should also ensure that it's non-trivial for email-spoofing of hosted domains to happen

Previously we were preventing any spoofing of the envelope from; Now we are preventing spoofing of both the envelope from and the header from unless some form of authentication passes (is a RELAYHOST, SPF, DKIM, ARC)

Related issue(s)

close #2475

Prerequisites

Before we can consider review and merge, please make sure the following list is done and checked. If an entry in not applicable, you can check it or remove it from the list.

[x] In case of feature or enhancement: documentation updated accordingly

[x] Unless it's docs or a minor change: add changelog entry file.

type/feature
opened by nextgens 48
Allow specific users to send email from any address
Before switching to Mailu I had postfix set up so that my admin user [email protected] could impersonate / send email as any other user.

This was extremely useful for sending email programmatically from multiple sources, e.g. from a web app that needs to send email from *@mydomain.dev and several other domains like *@admin.mydomain.dev/*@someotherdomain.dev.

I suspect I can add something into overrides/postfix.conf to get this behavior back, but I'm not sure how to do it since I only want a specific user to be able to impersonate others, not all users. Ideally there would be a UI page to configure the permitted sender addresses for each user, with sqlite-style wildcard support.

smtpd_client_restrictions = permit_mynetworks, check_sender_access ${podop}senderaccess, reject_non_fqdn_sender, reject_unknown_sender_domain, reject_unknown_recipient_domain, reject_unverified_recipient, permit smtpd_relay_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination

For now, given I'm the only one using the server and I need this behavior back ASAP, can I just remove the check_sender_access ${podop}senderaccess, line? Or is there a better long-term fix?

I also cant just use RELAYNETS with some whitelisted IPs becuase the servers doing the sending have dynamic IP addresses that often change, I need it to be whitelisted on a per-user basis not a per-sender-ip basis.

Useful links:

https://github.com/Mailu/Mailu/blob/master/core/postfix/conf/main.cf

http://www.postfix.org/ADDRESS_VERIFICATION_README.html

http://www.postfix.org/postconf.5.html#check_sender_access

type/enhancement backlog
opened by pirate 46
Upgrade Snappymail to 2.21 and merge the webmail containers
What type of PR?

enhancement

What does this PR do?

Upgrade Snappymail to 2.21 and merge the webmail containers. This will make the CI faster and should simplify things going forward (hardening but also allow running more than one webmail at the time, ...).

enable APCu

add new test to ensure we redirect to SSO and have disabled the admin panel

add all the packaged dictionaries for spell checking

harden the configuration of the webmails a bit (more to come in a separate PR)

turn off deprecation warnings (php8.1 is too new)

turn off error reporting (log them instead)

return HTTP302 when we should

gpg-verify the signature of the webmails we ship

upgrade to snappymail 2.21, switch to the new json config format

use socrates as it's meant to so that helm users can do their thing

run the HTTPd and PHP as different users

redirect the PHP errors to stderr

Related issue(s)

closes #2466

closes #948

closes #2250

Prerequisites

Before we can consider review and merge, please make sure the following list is done and checked. If an entry in not applicable, you can check it or remove it from the list.

[ ] In case of feature or enhancement: documentation updated accordingly

[x] Unless it's docs or a minor change: add changelog entry file.

priority/p2 type/security type/enhancement
opened by nextgens 44
Modify the healtchecks to make them disapear from the logs.
What type of PR?

enhancement

What does this PR do?

Modify the healtchecks to make them disapear from the logs. This is not perfect...

dovecot now complains about waitpid/finding a new process

postfix is still regularly pinging rspamd / his milter and that generates a few lines worth of logs each time.

Related issue(s)

Prerequisites

Before we can consider review and merge, please make sure the following list is done and checked. If an entry in not applicable, you can check it or remove it from the list.

[ ] In case of feature or enhancement: documentation updated accordingly

[x] Unless it's docs or a minor change: add changelog entry file.

priority/p2 type/enhancement
opened by nextgens 2
The IP you're using to send mail is not authorized to 550-5.7.1 send email directly to our servers.

I failed to send an email to gmail. Is there a solution to this problem?

host alt1.gmail-smtp-in.l.google.com[142.250.141.26] said: 550-5.7.1 [47.98.50.1] The IP you're using to send mail is not authorized to 550-5.7.1 send email directly to our servers. Please use the SMTP relay at your 550-5.7.1 service provider instead. Learn more at 550 5.7.1 https://support.google.com/mail/?p=NotAuthorizedError j15-20020a056a00234f00b0057a8accf94dsi11536503pfj.261 - gsmtp (in reply to end of DATA command)

opened by liusijun 1
is:issue is:open how to send mail to @msn.com by mailu
Environment & Version

Environment

[ ] docker-compose

[ ] kubernetes

[ ] docker swarm

Version

Version: master

Description

Replication Steps

Observed behaviour

Expected behaviour

Logs
opened by killghost 2
autodetect SUBNET
What type of PR?

enhancement

What does this PR do?

autodetect SUBNET; switch to unbound for name resolution.

The idea here is to reduce the number of tricky questions we ask the user during setup and minimize the opportunities for missconfiguration: "smart defaults". If you get it wrong you turn your instance into an open-relay.

Related issue(s)

Prerequisites

Before we can consider review and merge, please make sure the following list is done and checked. If an entry in not applicable, you can check it or remove it from the list.

[ ] In case of feature or enhancement: documentation updated accordingly

[x] Unless it's docs or a minor change: add changelog entry file.

priority/p2 type/enhancement
opened by nextgens 5
Issues with email server.

Please answer the following questions relating to customer service email communications triggered through a CRM platform.

Issues are being faced with:

• SMTP provider & the email gateway server limits • How can these limits be changed i.e. increasing daily limits? • How can we minimise bounce backs for legitimate customer service communications, sent via email for our own customers

Thank you
status/response_needed

opened by X24D83FF0 2

Releases(1.9.45)

1.9.45(Dec 30, 2022)
This is a new automatic release of Mailu. The new version can be seen in the tag name. The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images docker-compose pull && docker-compose up -d. The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.

To check what was changed:

Go to https://github.com/Mailu/Mailu/tree/master/towncrier/newsfragments

Change the branch to the tag of this release.

Read the news fragment files to check what was changed.

The release notes of the original release can be accessed via menu item 'Release notes' on mailu.io.
Source code(tar.gz)
Source code(zip)
1.9.44(Dec 27, 2022)
This is a new automatic release of Mailu. The new version can be seen in the tag name. The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images docker-compose pull && docker-compose up -d. The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.

To check what was changed:

Go to https://github.com/Mailu/Mailu/tree/master/towncrier/newsfragments

Change the branch to the tag of this release.

Read the news fragment files to check what was changed.

The release notes of the original release can be accessed via menu item 'Release notes' on mailu.io.
Source code(tar.gz)
Source code(zip)
1.9.43(Nov 30, 2022)
This is a new automatic release of Mailu. The new version can be seen in the tag name. The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images docker-compose pull && docker-compose up -d. The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.

To check what was changed:

Go to https://github.com/Mailu/Mailu/tree/master/towncrier/newsfragments

Change the branch to the tag of this release.

Read the news fragment files to check what was changed.

The release notes of the original release can be accessed via menu item 'Release notes' on mailu.io.
Source code(tar.gz)
Source code(zip)
1.9.42(Nov 24, 2022)
This is a new automatic release of Mailu. The new version can be seen in the tag name. The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images docker-compose pull && docker-compose up -d. The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.

To check what was changed:

Go to https://github.com/Mailu/Mailu/tree/master/towncrier/newsfragments

Change the branch to the tag of this release.

Read the news fragment files to check what was changed.

The release notes of the original release can be accessed via menu item 'Release notes' on mailu.io.
Source code(tar.gz)
Source code(zip)
1.9.41(Nov 23, 2022)
This is a new automatic release of Mailu. The new version can be seen in the tag name. The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images docker-compose pull && docker-compose up -d. The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.

To check what was changed:

Go to https://github.com/Mailu/Mailu/tree/master/towncrier/newsfragments

Change the branch to the tag of this release.

Read the news fragment files to check what was changed.

The release notes of the original release can be accessed via menu item 'Release notes' on mailu.io.
Source code(tar.gz)
Source code(zip)
1.9.40(Nov 9, 2022)
This is a new automatic release of Mailu. The new version can be seen in the tag name. The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images docker-compose pull && docker-compose up -d. The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.

To check what was changed:

Go to https://github.com/Mailu/Mailu/tree/master/towncrier/newsfragments

Change the branch to the tag of this release.

Read the news fragment files to check what was changed.

The release notes of the original release can be accessed via menu item 'Release notes' on mailu.io.
Source code(tar.gz)
Source code(zip)
1.9.39(Nov 3, 2022)
This is a new automatic release of Mailu. The new version can be seen in the tag name. The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images docker-compose pull && docker-compose up -d. The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.

To check what was changed:

Go to https://github.com/Mailu/Mailu/tree/master/towncrier/newsfragments

Change the branch to the tag of this release.

Read the news fragment files to check what was changed.

The release notes of the original release can be accessed via menu item 'Release notes' on mailu.io.
Source code(tar.gz)
Source code(zip)
1.9.38(Oct 24, 2022)
This is a new automatic release of Mailu. The new version can be seen in the tag name. The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images docker-compose pull && docker-compose up -d. The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.

To check what was changed:

Go to https://github.com/Mailu/Mailu/tree/master/towncrier/newsfragments

Change the branch to the tag of this release.

Read the news fragment files to check what was changed.

The release notes of the original release can be accessed via menu item 'Release notes' on mailu.io.
Source code(tar.gz)
Source code(zip)
1.9.37(Oct 8, 2022)
This is a new automatic release of Mailu. The new version can be seen in the tag name. The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images docker-compose pull && docker-compose up -d. The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.

To check what was changed:

Go to https://github.com/Mailu/Mailu/tree/master/towncrier/newsfragments

Change the branch to the tag of this release.

Read the news fragment files to check what was changed.

The release notes of the original release can be accessed via menu item 'Release notes' on mailu.io.
Source code(tar.gz)
Source code(zip)
1.9.36(Oct 7, 2022)
This is a new automatic release of Mailu. The new version can be seen in the tag name. The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images docker-compose pull && docker-compose up -d. The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.

To check what was changed:

Go to https://github.com/Mailu/Mailu/tree/master/towncrier/newsfragments

Change the branch to the tag of this release.

Read the news fragment files to check what was changed.

The release notes of the original release can be accessed via menu item 'Release notes' on mailu.io.
Source code(tar.gz)
Source code(zip)
1.9.35(Aug 29, 2022)
This is a new automatic release of Mailu. The new version can be seen in the tag name. The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images docker-compose pull && docker-compose up -d. The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.

To check what was changed:

Go to https://github.com/Mailu/Mailu/tree/master/towncrier/newsfragments

Change the branch to the tag of this release.

Read the news fragment files to check what was changed.

The release notes of the original release can be accessed via menu item 'Release notes' on mailu.io.
Source code(tar.gz)
Source code(zip)
1.9.34(Aug 19, 2022)
This is a new automatic release of Mailu. The new version can be seen in the tag name. The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images docker-compose pull && docker-compose up -d. The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.

To check what was changed:

Go to https://github.com/Mailu/Mailu/tree/master/towncrier/newsfragments

Change the branch to the tag of this release.

Read the news fragment files to check what was changed.

The release notes of the original release can be accessed via menu item 'Release notes' on mailu.io.
Source code(tar.gz)
Source code(zip)
1.9.33(Aug 19, 2022)
This is a new automatic release of Mailu. The new version can be seen in the tag name. The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images docker-compose pull && docker-compose up -d. The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.

To check what was changed:

Go to https://github.com/Mailu/Mailu/tree/master/towncrier/newsfragments

Change the branch to the tag of this release.

Read the news fragment files to check what was changed.

The release notes of the original release can be accessed via menu item 'Release notes' on mailu.io.
Source code(tar.gz)
Source code(zip)
1.9.32(Jul 6, 2022)
This is a new automatic release of Mailu. The new version can be seen in the tag name. The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images docker-compose pull && docker-compose up -d. The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.

To check what was changed:

Go to https://github.com/Mailu/Mailu/tree/master/towncrier/newsfragments

Change the branch to the tag of this release.

Read the news fragment files to check what was changed.

The release notes of the original release can be accessed via menu item 'Release notes' on mailu.io.
Source code(tar.gz)
Source code(zip)
1.9.31(Jun 8, 2022)
This is a new automatic release of Mailu. The new version can be seen in the tag name. The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images docker-compose pull && docker-compose up -d. The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.

To check what was changed:

Go to https://github.com/Mailu/Mailu/tree/master/towncrier/newsfragments

Change the branch to the tag of this release.

Read the news fragment files to check what was changed.

The release notes of the original release can be accessed via menu item 'Release notes' on mailu.io.
Source code(tar.gz)
Source code(zip)
1.9.30(Jun 7, 2022)
This is a new automatic release of Mailu. The new version can be seen in the tag name. The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images docker-compose pull && docker-compose up -d. The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.

To check what was changed:

Go to https://github.com/Mailu/Mailu/tree/master/towncrier/newsfragments

Change the branch to the tag of this release.

Read the news fragment files to check what was changed.

The release notes of the original release can be accessed via menu item 'Release notes' on mailu.io.
Source code(tar.gz)
Source code(zip)
1.9.29(May 18, 2022)
This is a new automatic release of Mailu. The new version can be seen in the tag name. The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images docker-compose pull && docker-compose up -d. The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.

To check what was changed:

Go to https://github.com/Mailu/Mailu/tree/master/towncrier/newsfragments

Change the branch to the tag of this release.

Read the news fragment files to check what was changed.

The release notes of the original release can be accessed via menu item 'Release notes' on mailu.io.
Source code(tar.gz)
Source code(zip)
1.9.28(May 9, 2022)
This is a new automatic release of Mailu. The new version can be seen in the tag name. The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images docker-compose pull && docker-compose up -d. The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.

To check what was changed:

Go to https://github.com/Mailu/Mailu/tree/master/towncrier/newsfragments

Change the branch to the tag of this release.

Read the news fragment files to check what was changed.

The release notes of the original release can be accessed via menu item 'Release notes' on mailu.io.
Source code(tar.gz)
Source code(zip)
1.9.27(Apr 29, 2022)
This is a new automatic release of Mailu. The new version can be seen in the tag name. The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images docker-compose pull && docker-compose up -d. The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.

To check what was changed:

Go to https://github.com/Mailu/Mailu/tree/master/towncrier/newsfragments

Change the branch to the tag of this release.

Read the news fragment files to check what was changed.

The release notes of the original release can be accessed via menu item 'Release notes' on mailu.io.
Source code(tar.gz)
Source code(zip)
1.9.26(Apr 18, 2022)
This is a new automatic release of Mailu. The new version can be seen in the tag name. The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images docker-compose pull && docker-compose up -d. The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.

To check what was changed:

Go to https://github.com/Mailu/Mailu/tree/master/towncrier/newsfragments

Change the branch to the tag of this release.

Read the news fragment files to check what was changed.

The release notes of the original release can be accessed via menu item 'Release notes' on mailu.io.
Source code(tar.gz)
Source code(zip)
1.9.25(Apr 4, 2022)
This is a new automatic release of Mailu. The new version can be seen in the tag name. The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images docker-compose pull && docker-compose up -d. The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.

To check what was changed:

Go to https://github.com/Mailu/Mailu/tree/master/towncrier/newsfragments

Change the branch to the tag of this release.

Read the news fragment files to check what was changed.

The release notes of the original release can be accessed via menu item 'Release notes' on mailu.io.
Source code(tar.gz)
Source code(zip)
1.9.24(Apr 4, 2022)
This is a new automatic release of Mailu. The new version can be seen in the tag name. The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images docker-compose pull && docker-compose up -d. The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.

To check what was changed:

Go to https://github.com/Mailu/Mailu/tree/master/towncrier/newsfragments

Change the branch to the tag of this release.

Read the news fragment files to check what was changed.

The release notes of the original release can be accessed via menu item 'Release notes' on mailu.io.
Source code(tar.gz)
Source code(zip)
1.9.23(Mar 22, 2022)
This is a new automatic release of Mailu. The new version can be seen in the tag name. The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images docker-compose pull && docker-compose up -d. The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.

To check what was changed:

Go to https://github.com/Mailu/Mailu/tree/master/towncrier/newsfragments

Change the branch to the tag of this release.

Read the news fragment files to check what was changed.

The release notes of the original release can be accessed via menu item 'Release notes' on mailu.io.
Source code(tar.gz)
Source code(zip)
1.9.22(Mar 19, 2022)
This is a new automatic release of Mailu. The new version can be seen in the tag name. The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images docker-compose pull && docker-compose up -d. The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.

To check what was changed:

Go to https://github.com/Mailu/Mailu/tree/master/towncrier/newsfragments

Change the branch to the tag of this release.

Read the news fragment files to check what was changed.

The release notes of the original release can be accessed via menu item 'Release notes' on mailu.io.
Source code(tar.gz)
Source code(zip)
1.9.21(Mar 18, 2022)
This is a new automatic release of Mailu. The new version can be seen in the tag name. The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images docker-compose pull && docker-compose up -d. The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.

To check what was changed:

Go to https://github.com/Mailu/Mailu/tree/master/towncrier/newsfragments

Change the branch to the tag of this release.

Read the news fragment files to check what was changed.

The release notes of the original release can be accessed via menu item 'Release notes' on mailu.io.
Source code(tar.gz)
Source code(zip)
1.9.20(Feb 24, 2022)
This is a new automatic release of Mailu. The new version can be seen in the tag name. The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images docker-compose pull && docker-compose up -d. The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.

To check what was changed:

Go to https://github.com/Mailu/Mailu/tree/master/towncrier/newsfragments

Change the branch to the tag of this release.

Read the news fragment files to check what was changed.

The release notes of the original release can be accessed via menu item 'Release notes' on mailu.io.
Source code(tar.gz)
Source code(zip)
1.9.19(Feb 23, 2022)
This is a new automatic release of Mailu. The new version can be seen in the tag name. The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images docker-compose pull && docker-compose up -d. The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.

To check what was changed:

Go to https://github.com/Mailu/Mailu/tree/master/towncrier/newsfragments

Change the branch to the tag of this release.

Read the news fragment files to check what was changed.

The release notes of the original release can be accessed via menu item 'Release notes' on mailu.io.
Source code(tar.gz)
Source code(zip)
1.9.18(Feb 19, 2022)
This is a new automatic release of Mailu. The new version can be seen in the tag name. The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images docker-compose pull && docker-compose up -d. The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.

To check what was changed:

Go to https://github.com/Mailu/Mailu/tree/master/towncrier/newsfragments

Change the branch to the tag of this release.

Read the news fragment files to check what was changed.

The release notes of the original release can be accessed via menu item 'Release notes' on mailu.io.
Source code(tar.gz)
Source code(zip)
1.9.17(Feb 18, 2022)
This is a new automatic release of Mailu. The new version can be seen in the tag name. The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images docker-compose pull && docker-compose up -d. The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.

To check what was changed:

Go to https://github.com/Mailu/Mailu/tree/master/towncrier/newsfragments

Change the branch to the tag of this release.

Read the news fragment files to check what was changed.

The release notes of the original release can be accessed via menu item 'Release notes' on mailu.io.
Source code(tar.gz)
Source code(zip)
1.9.16(Feb 18, 2022)
This is a new automatic release of Mailu. The new version can be seen in the tag name. The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images docker-compose pull && docker-compose up -d. The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.

To check what was changed:

Go to https://github.com/Mailu/Mailu/tree/master/towncrier/newsfragments

Change the branch to the tag of this release.

Read the news fragment files to check what was changed.

The release notes of the original release can be accessed via menu item 'Release notes' on mailu.io.
Source code(tar.gz)
Source code(zip)