1

Topic: dovecot quota not enabled after 1.5.0 update

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release):
- Deployed with iRedMail Easy or the downloadable installer?
- Linux/BSD distribution name and version:
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):
- Web server (Apache or Nginx):
- Manage mail accounts with iRedAdmin-Pro?
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====
EE 1.5.0
Ubuntu
MySQL
Nginx

After upgrading to 1.5.0 postfix stopped accepting new mail, checking the postfix.log it was complaining about not being able to connect to localhost:12340, the Dovecot Quota port.

I noticed in the /etc/dovecot/dovecot.conf file no longer contains:

service quota-status {
    # '-p <protocol>'. Currently only 'postfix' protocol is supported.
    executable = quota-status -p postfix
    client_limit = 1000
    inet_listener {
        address = 127.0.0.1
        port = 12340
    }
}

I don't remember seeing any reference to this change in the release notes so not exactly sure how it happened. I used the saved config file and brought things back up and mail started flowing again.

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: dovecot quota not enabled after 1.5.0 update

Hi @barasmith,

This change is mentioned in EE changelog:
https://docs.iredmail.org/ee.changelog.html

# v1.5.0, Sep 8, 2025

Improvements:
    - ...
    - Disabled Dovecot quota status service (not much useful but takes up dict processes).

EE v1.5.0 updates Postfix main.cf too, but i guess you made your own copy or customization which happens to keep using it?

3

Re: dovecot quota not enabled after 1.5.0 update

ZhangHuangbin wrote:

Hi @barasmith,

This change is mentioned in EE changelog:
https://docs.iredmail.org/ee.changelog.html

# v1.5.0, Sep 8, 2025

Improvements:
    - ...
    - Disabled Dovecot quota status service (not much useful but takes up dict processes).

EE v1.5.0 updates Postfix main.cf too, but i guess you made your own copy or customization which happens to keep using it?

That would do it. I am still struggling to get the custom stuff working correctly on the EE version. I bet I did have something in my custom version of main.cf. I will check.
Thanks!

4

Re: dovecot quota not enabled after 1.5.0 update

barasmith wrote:

I am still struggling to get the custom stuff working correctly on the EE version.

FYI https://docs.iredmail.org/ee.best.practice.html