Fix for issue #1223

optional/fetchmail/Dockerfile

@@ -12,6 +12,9 @@ RUN apk add --no-cache \
 RUN apk add --no-cache fetchmail ca-certificates openssl \
  && pip3 install requests
 
+RUN mkdir -p /data
+RUN chown fetchmail:fetchmail /data
+
 COPY fetchmail.py /fetchmail.py
 
 USER fetchmail

optional/fetchmail/fetchmail.py

@@ -13,6 +13,7 @@ import traceback
 
 FETCHMAIL = """
 fetchmail -N \
+    --idfile /data/.fetchids \
     --sslcertck --sslcertpath /etc/ssl/certs \
     -f {}
 """

setup/flavors/compose/docker-compose.yml

@@ -129,6 +129,8 @@ services:
     image: ${DOCKER_ORG:-mailu}/${DOCKER_PREFIX:-}fetchmail:${MAILU_VERSION:-{{ version }}}
     restart: always
     env_file: {{ env }}
+    volumes:
+      - "{{ root }}/fetchmail:/data"
     {% if resolver_enabled %}
     depends_on:
       - resolver

setup/flavors/stack/docker-compose.yml

@@ -110,7 +110,7 @@ services:
     image: ${DOCKER_ORG:-mailu}/${DOCKER_PREFIX:-}fetchmail:${MAILU_VERSION:-{{ version }}}
     env_file: {{ env }}
     volumes:
-      - "{{ root }}/data:/data"
+      - "{{ root }}/fetchmail:/data"
     deploy:
       replicas: 1
     healthcheck:

towncrier/newsfragments/1223.bugfix

@@ -0,0 +1,4 @@
+Fixed fetchmail losing track of fetched emails upon container recreation. 
+The relevant fetchmail files are now retained in the /data folder (in the fetchmail image).
+See the docker-compose.yml file for the relevant volume mapping.
+If you already had your own mapping, you must double check the volume mapping and take action.