docker-mailserver: [BUG] Dovecot quota not updated

Miscellaneous first checks

• I checked that all ports are open and not blocked by my ISP / hosting provider.
• I know that SSL errors are likely the result of a wrong setup on the user side and not caused by DMS itself. I’m confident my setup is correct.

Affected Component(s)

Dovecot quota

What happened and when does this occur?

I have been installing DMS for a few weeks, until a few days ago the following command seemed to work correctly:

docker exec -it mailserver setup quota set user@domain.tld 2500M

In fact, the modification could be immediately found on the file /tmp/docker-mailserver/dovecot-quotas.cf and also in the output of the command docker exec -it mailserver setup email list.

For a few days, however, this has not happened anymore, in the sense that the file /tmp/docker-mailserver/dovecot-quotas.cf is updated correctly, but the output of the command docker exec -it mailserver setup email list remains unchanged, with the old values of the quotas.

Going deeper I noticed that the quotas within the file /etc/dovecot/userdb are not updated.

Looking at the code, it seems to me that the file /etc/dovecot/userdb is updated at this point https://github.com/docker-mailserver/docker-mailserver/blob/master/target/scripts/check-for-changes.sh#L158 , but when is the script check-for-changes.sh run? do I have to launch it manually?

I also tried deleting the quota and recreating it.

I also tried restarting docker project docker-compose down and then docker-compose up -d.

What did you expect to happen?

I expect that the quota update docker exec -it mailserver setup quota set user@domain.tld 2500M to be reflected immediately on the command output docker exec -it mailserver setup email list.

How do we replicate the issue?

1. docker exec -it mailserver setup quota set user@domain.tld 2500M
2. docker exec -it mailserver setup email list
3. the output does not show the quota update

DMS version

v10.2.0

What operating system is DMS running on?

Linux

What instruction set architecture is DMS running on?

x86_64 / AMD64

What container orchestration tool are you using?

Docker

docker-compose.yml

version: '3.9'

services:
  mailserver:
    image: docker.io/mailserver/docker-mailserver:${MAILSERVER_TAG:-latest}
    container_name: mailserver
    hostname: ${MAILSERVER_HOSTNAME}
    domainname: ${MAILSERVER_DOMAINNAME}
    env_file: .env
    # More information about the mail-server ports:
    # https://docker-mailserver.github.io/docker-mailserver/edge/config/security/understanding-the-ports/
    # To avoid conflicts with yaml base-60 float, DO NOT remove the quotation marks.
    ports:
      - "25:25"    # SMTP  (explicit TLS => STARTTLS)
      - "110:110"  # POP3
      - "143:143"  # IMAP4 (explicit TLS => STARTTLS)
      - "465:465"  # ESMTP (implicit TLS)
      - "587:587"  # ESMTP (explicit TLS => STARTTLS)
      - "993:993"  # IMAP4 (implicit TLS)
      - "995:995"  # POP3 (with TLS)
    volumes:
      - ${PWD}/sys/mailserver/data:/var/mail
      - ${PWD}/sys/mailserver/state:/var/mail-state
      - ${PWD}/sys/mailserver/logs:/var/log/mail
      - ${PWD}/sys/mailserver/config:/tmp/docker-mailserver
      - ${PWD}/sys/mailserver/config/dovecot/15-mailboxes.conf:/etc/dovecot/conf.d/15-mailboxes.conf:ro
      - /etc/localtime:/etc/localtime:ro
    restart: always
    stop_grace_period: 1m
    cap_add:
      - NET_ADMIN
      - SYS_PTRACE

Relevant log output

No response

Other relevant information

No response

What level of experience do you have with Docker and mail servers?

I am uncomfortable with the CLI

Code of conduct

• I have read this project’s Code of Conduct and I agree
• I have read the README and the documentation and I searched the issue tracker but could not find a solution

Improvements to this form?

No response