Insular email distribution - mail server as Docker images

Overview

Mailu

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

Domains

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?

    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

    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

    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

    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
  • Resolve HOST to ADDRESS only if ADDRESS is not already set

    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

    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

    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
  • Nginx Reverse Proxy error

    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:

    imagen

    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

    imagen

    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

    imagen

    Nginx Folder: /nginx/

    imagen

    opened by vinanrra 48
  • Allow specific users to send email from any address

    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

    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
  • Harden postfix's configuration

    Harden postfix's configuration

    What type of PR?

    enhancement

    What does this PR do?

    It hardens the default configuration:

    • disable AUTH commands on port 25 (nginx was not advertising the capability: normal clients wouldn't attempt it)
    • fix Forward Secrecy by ensuring that we don't use session tickets and don't cache on forensically carveable mediums
    • prevent clear-text credentials from being sent while authenticating to remote relays (this may break things if the relay doesn't support challenge-based authentication NOR STARTTLS - unlikely).
    • switch to default RSA keysizes (2048 bits and they get rekeyed every 3 months -modern clients will do ECC)
    • enable ECC certificates (much smaller than RSA keys, faster for better security margin)
    • configure nginx so that it doesn't send the legacy/root CA (clients that require it are unlikely to do TLS1.2 any ways)

    I don't think that any of those changes is impactful enough to warrant being documented.

    Related issue(s)

    • close #1804

    Prerequistes

    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.
    priority/p1 type/security type/enhancement 
    opened by nextgens 44
  • Remove the dependency on pyOpenSSL

    Remove the dependency on pyOpenSSL

    What type of PR?

    enhancement

    What does this PR do?

    Remove the dependency on pyOpenSSL

    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
    • [ ] Unless it's docs or a minor change: add changelog entry file.
    priority/p2 type/enhancement 
    opened by nextgens 4
  • Make it clear that we don't delete users

    Make it clear that we don't delete users

    What type of PR?

    bug-fix

    What does this PR do?

    Make it clear that we don't delete users. Users can and should be disabled when not in use anymore.

    Related issue(s)

    • closes #1820

    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
    • [ ] Unless it's docs or a minor change: add changelog entry file.
    type/security type/bug 
    opened by nextgens 2
  • Misc dovecot config changes

    Misc dovecot config changes

    What type of PR?

    bug-fix

    What does this PR do?

    • fix RECIPIENT_DELIMITER (wrong scope, was ignored) This can be confirmed using: $nc imap 2525 ... and delivering to a VERP address
    • drop privileges of the LMTP daemon

    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
    • [ ] Unless it's docs or a minor change: add changelog entry file.
    opened by nextgens 10
  • Dynamic address resolution everywhere

    Dynamic address resolution everywhere

    What type of PR?

    enhancement

    What does this PR do?

    Use dynamic address resolution everywhere. Derive a new key for admin/SECRET_KEY Cleanup the environment

    This should allow restarting containers.

    Related issue(s)

    • closes #1341
    • closes #1013
    • closes #1430

    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/enhancement 
    opened by nextgens 6
  • rethink rspamd's overrides

    rethink rspamd's overrides

    Currently any override put in rspamd's folder will replace Mailu's default config.

    This may disable functionality (anti-spoof, oletools, ...) and doesn't make upgrades easy.

    We can probably do better.

    type/enhancement 
    opened by nextgens 0
Releases(1.9.42)
  • 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)
  • 1.9.15(Feb 17, 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.14(Feb 13, 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.13(Feb 13, 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)
Owner
Mailu
Insular email distribution - email server as Docker images
Mailu
A free & open modern, fast email client with user-friendly encryption and privacy features

Welcome to Mailpile! Introduction Mailpile (https://www.mailpile.is/) is a modern, fast web-mail client with user-friendly encryption and privacy feat

mailpile 8.7k Nov 21, 2022
Zulip server and webapp - powerful open source team chat

Zulip overview Zulip is a powerful, open source group chat application that combines the immediacy of real-time chat with the productivity benefits of

Zulip 16.8k Nov 26, 2022
Email-bomber - Email bomber unlike other email bombers u don't need your gmail email id to use this

Email-bomber - Email bomber unlike other email bombers u don't need your gmail email id to use this

rfeferfefe 71 Nov 20, 2022
GMailBomber is a form of Internet abuse which is perpetrated through the sending of massive volumes of email to a specific email address with the goal of overflowing the mailbox and overwhelming the mail server hosting the address, making it into some form of denial of service attack.

GMailBomber is a form of Internet abuse which is perpetrated through the sending of massive volumes of email to a specific email address with the goal of overflowing the mailbox and overwhelming the mail server hosting the address, making it into some form of denial of service attack.

Muneeb 5 Nov 13, 2022
Generates images with semantic content from distribution A in the style of distribution B

A2B Generates images with semantic content from distribution A in the style of d

Richard Herbert 2 Dec 27, 2021
a Scrapy spider that utilizes Postgres as a DB, Squid as a proxy server, Redis for de-duplication and Splash to render JavaScript. All in a microservices architecture utilizing Docker and Docker Compose

This is George's Scraping Project To get started cd into the theZoo file and run: chmod +x script.sh then: ./script.sh This will spin up a Postgres co

George Reyes 6 Aug 12, 2022
You take an email and password from the combo list file and check it on mail.com

Brute-Force-mail tool information: Combo Type: email:pass Domains: All domains of the site Url: https://www.mail.com Api: ☑️ Proxy: No ☑️ The correct

null 6 Jun 5, 2022
ghotok mail - lets you find available contact email addresses from target website

ghotok-mail ghotok mail - lets you find available contact email addresses from target website git clone https://github.com/josifkhan/ghotok-mail cd gh

Md Josif Khan 3 Mar 14, 2022
An automation program that checks whether email addresses are real, whether they exist and whether they are a validated mail

Email Validator It is an automation program that checks whether email addresses are real, whether they exist and whether they are a validated mail. Re

Ender MIRIZ 4 Dec 22, 2021
Red-mail - Advanced email sending library for Python

Red Mail Next generation email sender What is it? Red Mail is an advanced email

Mikael Koli 303 Nov 18, 2022
An image base contains 490 images for learning (400 cars and 90 boats), and another 21 images for testingAn image base contains 490 images for learning (400 cars and 90 boats), and another 21 images for testing

SVM Données Une base d’images contient 490 images pour l’apprentissage (400 voitures et 90 bateaux), et encore 21 images pour fait des tests. Prétrait

Achraf Rahouti 3 Nov 30, 2021
Distribution Analyser is a Web App that allows you to interactively explore continuous distributions from SciPy and fit distribution(s) to your data.

Distribution Analyser Distribution Analyser is a Web App that allows you to interactively explore continuous distributions from SciPy and fit distribu

Robert Dzudzar 46 Nov 8, 2022
A simple application that calculates the probability distribution of a normal distribution

probability-density-function General info An application that calculates the probability density and cumulative distribution of a normal distribution

null 1 Oct 25, 2022
A Django email backend that uses a celery task for sending the email.

django-celery-email - A Celery-backed Django Email Backend A Django email backend that uses a Celery queue for out-of-band sending of the messages. Wa

Paul McLanahan 423 Nov 2, 2022
A Django app that allows you to send email asynchronously in Django. Supports HTML email, database backed templates and logging.

Django Post Office Django Post Office is a simple app to send and manage your emails in Django. Some awesome features are: Allows you to send email as

User Inspired 850 Nov 26, 2022
A Django email backend for Amazon's Simple Email Service

Django-SES Info: A Django email backend for Amazon's Simple Email Service Author: Harry Marr (http://github.com/hmarr, http://twitter.com/harrymarr) C

null 878 Nov 15, 2022
Djrill is an email backend and new message class for Django users that want to take advantage of the Mandrill transactional email service from MailChimp.

Djrill: Mandrill Transactional Email for Django Djrill integrates the Mandrill transactional email service into Django. PROJECT STATUS: INACTIVE As of

Brack3t 327 Oct 1, 2022
Esio_dev 3 Oct 15, 2021