Question 1

How do I fix Modoboa failing to connect to a managed MySQL or PostgreSQL database when SSL is required?

Accepted Answer

Upgrade to a Modoboa release containing the fix for issue #1835, which preserves database `OPTIONS` passed through `--dburl`. If you cannot upgrade, manually add the SSL settings to `settings.py`. For PostgreSQL, use: ```python DATABASES = { 'default': { 'ENGINE': 'django.db.backends.postgresql', 'NAME': '', 'USER': '', 'PASSWORD': '', 'HOST': '', 'PORT': '5432', 'OPTIONS': { 'sslmode': 'require', }, } } ``` To verify the server certificate, use `sslmode: 'verify-full'` and add `'sslrootcert': '/path/to/ca.crt'`. For MySQL, add: ```python DATABASES = { 'default': { 'ENGINE': 'django.db.backends.mysql', 'NAME': '', 'USER': '', 'PASSWORD': '', 'HOST': '', 'PORT': '3306', 'OPTIONS': { 'ssl': { 'ca': '/path/to/ca.pem', 'cert': '/path/to/client-cert.pem', 'key': '/path/to/client-key.pem', } }, } } ``` Omit `cert` and `key` if only the CA certificate is required. Ensure the database user running Modoboa can read the certificate files, then restart the Modoboa application service (for example uWSGI or Gunicorn); restarting Nginx alone is not sufficient.

Question 2

Why does a renamed Modoboa mailbox become unavailable with Postfix returning 450?

Accepted Answer

A failed or unprocessed rename leaves a row in `admin_mailboxoperation`; Postfix's `sql-maintain` query then keeps treating the mailbox as pending and rejects mail with `450`. Upgrade Modoboa to a release containing the fix "never leave a mailbox blocked by a pending rename operation." As an immediate workaround, verify the mailbox/maildir state, then remove the stale row from MySQL:

```sql
SELECT * FROM admin_mailboxoperation;
DELETE FROM admin_mailboxoperation WHERE id = <stale_rename_operation_id>;
```

If the rename failed because of an existing destination, `mv`, or `makedirs` error, correct the mail directory manually before deleting the row. Also ensure Modoboa's mailbox handling/`handle_mailboxes` setting is enabled if you expect the application to rename mail directories automatically.

Question 3

How do I deploy Modoboa when Redis only listens on a Unix socket instead of TCP port 6379?

Accepted Answer

Upgrade to a Modoboa release containing the `--redisurl` option, then pass your Redis socket URL during deployment:

```bash
modoboa-admin.py deploy --redisurl unix:///run/redis/redis.sock
```

This writes the supplied value to `REDIS_URL` in the generated `settings.py` instead of assuming `redis://localhost:6379`.

On Modoboa 2.4.10, where the option is unavailable, temporarily enable Redis on TCP loopback (`bind 127.0.0.1 -::1` and `port 6379` in `redis.conf`), restart Redis, run the deployer, then set `REDIS_URL = "unix:///run/redis/redis.sock"` manually and restart Modoboa services.

Question 4

How to fix doveadm -A reporting "User no longer exists, skipping" in Modoboa?

Accepted Answer

The message occurs when `core_user` contains an admin account with an empty `email` field and Dovecot's `iterate_query` returns that empty username. Verify with:

```sql
SELECT username, email AS user FROM core_user;
```

Fix it by either assigning a valid email address to the admin account or filtering empty addresses in `/etc/dovecot/dovecot-sql.conf.ext`:

```conf
iterate_query = SELECT email AS user FROM core_user WHERE email != ''
```

Then restart Dovecot:

```bash
sudo systemctl restart dovecot
```

Retest, for example:

```bash
doveadm search -A mailbox Trash savedbefore 14d
```

Question 5

Why does modoboa 1.4.2 alias import fail with 'Local recipient not found'?

Accepted Answer

A bug in modoboa 1.4.2 causes alias import to fail when the target account doesn’t exist yet. The method `Alias.set_recipients()` checks if the recipient exists, and if not, it throws a `NotFound` exception instead of creating it. This breaks imports where aliases reference accounts defined later in the same CSV file.

**Workaround**: Edit `modoboa/admin/models/alias.py` and comment out lines 133–139:

```python
                    # if rcpt is None:
                    #     raise NotFound(
                    #         _("Local recipient {}@{} not found")
                    #         .format(local_part, domname)
                    #     )
                    # if rcpt.address == self.address:
                    #     raise Conflict
```

This skips the premature check and allows the import to succeed. Note that after commenting, the import will create the alias even if the target is missing—ensure your CSV lists accounts before aliases if needed.

Modoboa

Core Features

What It Can't Do

Use Cases

Tags

Getting Started

Similar Projects