Moving to this Poste.io version

[kennylajara]

``I have the original Poste.io installed and I am planning to move to this version.

Do I only have to change the container in the docker-compose.yml file? The persisted data and configuration will work the same way?

This is my current docker-compose.yml file:

# mailserver
version: '3.8'

services:
  mailserver:
    image: analogic/poste.io:latest
    container_name: mailserver
    hostname: mail
    domainname: example.com # Censured for privacy
    restart: always
    ports:
      # Ports 80 and 443 are handled by reverse proxy
      - "25:25"
      - "110:110"
      - "143:143"
      - "465:465"
      - "587:587"
      - "993:993"
      - "995:995"
      - "4190:4190"
    environment:
      - HTTPS=OFF # HTTPS handled by proxy
      - VIRTUAL_HOST=imap.example.com,mail.example.com,smtp.example.com
      - DISABLE_CLAMAV=TRUE
    volumes:
      - "/etc/localtime:/etc/localtime:ro"
      - "data:/data"
      # Sever-wide sieve filter
      - "/data/custom-sieve/sieve.d:/var/lib/dovecot/sieve.d"
      - "/data/custom-sieve/90-sieve.conf:/etc/dovecot/conf.d/90-sieve.conf"
    networks:
      - "frontend"

volumes:
  data:

networks:
  frontend:
    external: true

[pjeby]

Your configuration doesn't use host mode networking, so it's not just a mater of switching images. This image has not been tested with virtual networking, as its whole reason for existence is to safely support host mode. In principle, it should still work with the default proxy networking mode, but I have not had any reason to test it.

The storage is indeed the same (though this version has additions for plugins and routing), but you may prefer to create a second container with a copy of the data, so you can test it first with an option to roll back.

[kennylajara]

Yes, I understand that this is the reason why you created it, but I may be interested on the plugin due to the Roundcube thing.

I will probably make the copy and test. Thank you.

[pjeby]

Good luck!