Updating docker image 12->13 #3701

MarcS1975 · 2023-12-15T17:30:43Z

MarcS1975
Dec 15, 2023

I have been running version 12.1.0 for a while now and am unsure how upgrading to V 13 would impact my settings. I spent alot of time manually amending configs and settings around:

postfix
fail2ban
DKIM
SPF
DMARC
Is there a way to preserve the settings?

polarathene · 2023-12-15T20:31:00Z

polarathene
Dec 15, 2023
Maintainer

I spent alot of time manually amending configs and settings around

How did you manage that?

If you followed our documentation you should be using config files provided to DMS via volume mounts. Upgrading the container rarely has any impact on that data, but just in case make a backup copy before you do.

On the Github Releases page of the project you will find release notes, while on the main repo page, there is a CHANGELOG.md which is a bit more detailed (I revised the v13 changelog so it's a better source than the GH releases for users to grok changes). You want to pay special attention to the "Breaking Changes" section as this is a major version something may break for you with the upgrade (usually you can roll back to the prior version if necessary, especially with a backup of your volume data).

Is there a way to preserve the settings?

What settings are you concerned about being affected? Are they not managed by volumes?

0 replies

MarcS1975 · 2023-12-16T10:42:42Z

MarcS1975
Dec 16, 2023
Author

Thanks for the reply. Below is my compose file. Yes I am using volumes as suggested but still /etc/postfix/main.cf will be updated by the container upgrade. right? And I had to make changes in there because a lot of valid email got rejected.

services:

  mailserver:
    image: docker.io/mailserver/docker-mailserver:latest
    container_name: mailserver2
    # Provide the FQDN of your mail server here (Your DNS MX record should point to this value)
    # added one vol for import aj
    hostname: xxx.mydomain.xxx
    ports:
      - "yy:25"
      - "yyy:143"
      - "yyy:587"
      - "yyy:993"
      - "yyy:465"
    volumes:
    - /srv/dev-disk-by-uuid-c8781cb8-41f2-42a6-9ee0-acd14b06524f/Dockerapps/ajmail2/mail-data/:/var/mail/
    - /srv/dev-disk-by-uuid-c8781cb8-41f2-42a6-9ee0-acd14b06524f/Dockerapps/ajmail2/mail-state/:/var/mail-state/
    - /srv/dev-disk-by-uuid-c8781cb8-41f2-42a6-9ee0-acd14b06524f/Dockerapps/ajmail2/mail-logs/:/var/log/mail/
    - /srv/dev-disk-by-uuid-c8781cb8-41f2-42a6-9ee0-acd14b06524f/Dockerapps/ajmail2/config/:/tmp/docker-mailserver/
    - /etc/localtime/:/etc/localtime:ro
    - /srv/dev-disk-by-uuid-c8781cb8-41f2-42a6-9ee0 acd14b06524f/Dockerapps/letsencrypt/fromDSM_T17/xxxxxxx/:/tmp/dms/custom-certs/
    - /srv/dev-disk-by-uuid-c8781cb8-41f2-42a6-9ee0-acd14b06524f/Dockerapps240/ajmail2/import/:/tmp/import/
    environment:
      - LOG_LEVEL=debug #by AJ
      - PFLOGSUMM_TRIGGER=daily_cron # by AJ
      - [email protected] # by AJ
      - LOGWATCH_INTERVAL=daily # by AJ
      - ENABLE_SPAMASSASSIN=1
      - SPAMASSASSIN_SPAM_TO_INBOX=1
      - ENABLE_CLAMAV=0 # by AJ
      - ENABLE_FAIL2BAN=1
      - ENABLE_POSTGREY=0
      - SSL_TYPE=manual
      - SSL_CERT_PATH=/tmp/dms/custom-certs/fullchain.pem

1 reply

polarathene Dec 16, 2023
Maintainer

but still /etc/postfix/main.cf will be updated by the container upgrade. right? And I had to make changes in there because a lot of valid email got rejected.

/etc/postfix/main.cf is an internal file. You should only modify this via user-patches.sh or our override file postfix-main.cf (see our docs), both files are provided via the volume to /tmp/docker-mailserver.

You've not said how you're modifying /etc/postfix/main.cf, if it's not via either of those two and you don't have a direct volume mount, know that changes to files within the container aren't persisted across new container instances.

This is important to be aware of, since some users rely on stopping/starting and restart of a container. However DMS startup scripts are not always prepared for this and expect to work with fresh internal state as provided by our image, so that can lead to bugs. Instead we encourage always starting/restarting DMS with a fresh container instance (docker compose up --force-recreate).

If you have been relying on the same container instance, your changes to such files will be lost, not just from an upgrade but anything that would remove that container instance and start a new one (I believe an ENV or volume change can do that for example). So best to back that up.

MarcS1975 · 2023-12-16T21:17:25Z

MarcS1975
Dec 16, 2023
Author

OK thanks. I understand. The way I amend configuration files is that I log I to the container (via portainer) and then simply nano config.file. I know from experience that upgrades overwrite my changes. That's why I raised the question here.

…

On Sat, 16 Dec 2023, 21:04 Brennan Kinney, ***@***.***> wrote: but still /etc/postfix/main.cf will be updated by the container upgrade. right? And I had to make changes in there because a lot of valid email got rejected. /etc/postfix/main.cf is an internal file. You should only modify this via user-patches.sh or our override file postfix-main.cf (see our docs), both files are provided via the volume to /tmp/docker-mailserver. ------------------------------ You've not said how you're modifying /etc/postfix/main.cf, if it's not via either of those two and you don't have a direct volume mount, know that changes to files within the container aren't persisted across new container instances. This is important to be aware of, since some users rely on stopping/starting and restart of a container. However DMS startup scripts are not always prepared for this and expect to work with fresh internal state as provided by our image, so that can lead to bugs. Instead we encourage always starting/restarting DMS with a fresh container instance (docker compose up --force-recreate). If you have been relying on the same container instance, your changes to such files will be lost, not just from an upgrade but anything that would remove that container instance and start a new one (*I believe an ENV or volume change can do that for example*). So best to back that up. — Reply to this email directly, view it on GitHub <#3701 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMNNHGXJO7MPJRSFNH33QNTYJYEHRAVCNFSM6AAAAABAWYOQDOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TQNZTGM3DA> . You are receiving this because you authored the thread.Message ID: <docker-mailserver/docker-mailserver/repo-discussions/3701/comments/7873360 @github.com>

1 reply

polarathene Dec 16, 2023
Maintainer

The way I amend configuration files is that I log I to the container (via portainer) and then simply nano config.file. I know from experience that upgrades overwrite my changes.

No worries, use the features we provide instead and that won't be an issue 👍

MarcS1975 · 2023-12-16T22:19:40Z

MarcS1975
Dec 16, 2023
Author

Awesome, thank you so much!

…

On Sat, 16 Dec 2023, 21:45 Brennan Kinney, ***@***.***> wrote: The way I amend configuration files is that I log I to the container (via portainer) and then simply nano config.file. I know from experience that upgrades overwrite my changes. No worries, use the features we provide instead and that won't be an issue 👍 — Reply to this email directly, view it on GitHub <#3701 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMNNHGS3X5PF4ADUNW65HR3YJYJA3AVCNFSM6AAAAABAWYOQDOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TQNZTGU3DS> . You are receiving this because you authored the thread.Message ID: <docker-mailserver/docker-mailserver/repo-discussions/3701/comments/7873569 @github.com>

0 replies

MarcS1975 · 2023-12-16T22:21:22Z

MarcS1975
Dec 16, 2023
Author

By the way, will you think about adding a simple mail client to the container (like roundcube or so)? That would be an awesome package....

…

On Sat, 16 Dec 2023, 21:45 Brennan Kinney, ***@***.***> wrote: The way I amend configuration files is that I log I to the container (via portainer) and then simply nano config.file. I know from experience that upgrades overwrite my changes. No worries, use the features we provide instead and that won't be an issue 👍 — Reply to this email directly, view it on GitHub <#3701 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMNNHGS3X5PF4ADUNW65HR3YJYJA3AVCNFSM6AAAAABAWYOQDOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TQNZTGU3DS> . You are receiving this because you authored the thread.Message ID: <docker-mailserver/docker-mailserver/repo-discussions/3701/comments/7873569 @github.com>

2 replies

polarathene Dec 17, 2023
Maintainer

You can make a feature request, but I think it's unlikely as all maintainers have little time to spare on new features

casperklein Dec 17, 2023
Maintainer

It's really easy to do so, just add these lines to your existing DMS compose.yaml.

MarcS1975 · 2023-12-17T11:59:04Z

MarcS1975
Dec 17, 2023
Author

Wow. I will try that. Thank you very much Casper!

…

On Sun, Dec 17, 2023 at 11:35 AM Casper ***@***.***> wrote: It's really easy to do so, just add these lines <https://github.com/roundcube/roundcubemail-docker/blob/28069c0316b8130d16445b8d05fe9a4efe2bb749/examples/docker-compose-simple.yaml#L4-L17> to your existing DMS compose.yaml. — Reply to this email directly, view it on GitHub <#3701 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMNNHGRUOPQBW7HI4MFPASTYJ3KGNAVCNFSM6AAAAABAWYOQDOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TQNZWGI4DA> . You are receiving this because you authored the thread.Message ID: <docker-mailserver/docker-mailserver/repo-discussions/3701/comments/7876280 @github.com>

0 replies

MarcS1975 · 2023-12-17T14:17:16Z

MarcS1975
Dec 17, 2023
Author

Hello again. I just tried the Roundcube container and it worked like a charm. I needed to tweak the ports a bit but after that it all runs smoothly...And the speed is impressive. Lets see how it goes after a few months. One step closer to terminating Gmail surveilance :))) thank you guys!

…

On Sun, Dec 17, 2023 at 11:35 AM Casper ***@***.***> wrote: It's really easy to do so, just add these lines <https://github.com/roundcube/roundcubemail-docker/blob/28069c0316b8130d16445b8d05fe9a4efe2bb749/examples/docker-compose-simple.yaml#L4-L17> to your existing DMS compose.yaml. — Reply to this email directly, view it on GitHub <#3701 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMNNHGRUOPQBW7HI4MFPASTYJ3KGNAVCNFSM6AAAAABAWYOQDOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TQNZWGI4DA> . You are receiving this because you authored the thread.Message ID: <docker-mailserver/docker-mailserver/repo-discussions/3701/comments/7876280 @github.com>

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Docker Mailserver

Updating docker image 12->13 #3701

{{title}}

Replies: 7 comments 4 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Docker Mailserver

Updating docker image 12->13 #3701

MarcS1975 Dec 15, 2023

Replies: 7 comments · 4 replies

polarathene Dec 15, 2023 Maintainer

MarcS1975 Dec 16, 2023 Author

polarathene Dec 16, 2023 Maintainer

MarcS1975 Dec 16, 2023 Author

polarathene Dec 16, 2023 Maintainer

MarcS1975 Dec 16, 2023 Author

MarcS1975 Dec 16, 2023 Author

polarathene Dec 17, 2023 Maintainer

casperklein Dec 17, 2023 Maintainer

MarcS1975 Dec 17, 2023 Author

MarcS1975 Dec 17, 2023 Author

MarcS1975
Dec 15, 2023

Replies: 7 comments 4 replies

polarathene
Dec 15, 2023
Maintainer

MarcS1975
Dec 16, 2023
Author

polarathene Dec 16, 2023
Maintainer

MarcS1975
Dec 16, 2023
Author

polarathene Dec 16, 2023
Maintainer

MarcS1975
Dec 16, 2023
Author

MarcS1975
Dec 16, 2023
Author

polarathene Dec 17, 2023
Maintainer

casperklein Dec 17, 2023
Maintainer

MarcS1975
Dec 17, 2023
Author

MarcS1975
Dec 17, 2023
Author