Question 1

Why does fail2ban show '/usr/local/bin/fail2ban_banned_db: not found' on Ubuntu 24.04?

Accepted Answer

The script /usr/local/bin/fail2ban_banned_db has an incorrect shebang (#!/usr/local/bin/bash). On Ubuntu 24.04, bash is at /usr/bin/bash. Fix it by running: sed -i 's|^#!/usr/local/bin/bash|#!/usr/bin/bash|' /usr/local/bin/fail2ban_banned_db. This issue is resolved in the upcoming iRedMail release.

Question 2

Why does Amavis show 'ALL VIRUS SCANNERS FAILED' and cannot connect to ClamAV socket on Debian 12?

Accepted Answer

The Amavis service is configured to look for the ClamAV socket at '/var/run/clamav/clamd.sock', but the ClamAV daemon creates a socket named 'clamd.ctl' by default (or due to packaging). To fix this, either align the socket path in Amavis to use 'clamd.ctl' or ensure ClamAV creates the expected socket. The recommended solution is to edit Amavis's virus scanner configuration.

1. Open '/etc/amavis/conf.d/50-user' (create if missing) and add:

```
@av_scanners = (
  ['ClamAV-clamd',
    \&ask_daemon, ["CONTSCAN {}\n", '/var/run/clamav/clamd.ctl'],
    qr/\bOK$/m, qr/\bFOUND$/m, qr/^.*?: (?!Infected Archive)(.*) FOUND$/m ],
);
```

2. Ensure the 'amavis' user can read the socket by adding it to the 'clamav' group:

`sudo usermod -a -G clamav amavis`

3. Restart both services:

`sudo systemctl restart clamav-daemon amavis`

If you prefer to change ClamAV's socket to 'clamd.sock', edit '/etc/clamav/clamd.conf', set 'LocalSocket /var/run/clamav/clamd.sock', and restart ClamAV. Then ensure Amavis points to the same path as in step 1.

Question 3

Why does iRedMail installation fail with 'Package verification failed' for netdata on Ubuntu?

Accepted Answer

This error occurs because the netdata tarball is missing or mismatched in the installer's misc/ directory. The development team has resolved this in the latest iRedMail version. To fix it, update your local installer files: either run `git pull` inside the iRedMail directory (if cloned from Git), or re-download the latest installer from the official iRedMail website. Then rerun the installation script. If the problem persists, verify that the file misc/netdata-v*.gz.run exists and matches the expected checksum in misc/sha256sum.txt.

Question 4

How to use a custom DKIM selector in iRedMail EE instead of the forced 'DKIM' selector?

Accepted Answer

iRedMail EE forces the DKIM selector to 'DKIM', causing conflicts with multiple servers under the same domain. Workaround: manually generate a key pair with your custom selector, update the database to reflect the new key and selector, publish the public key in DNS, and monitor the database after upgrades to remove any auto-reinserted 'DKIM' selector entries. No native customization yet; track future releases for official support.

iRedMail

Core Features

What It Can't Do

Use Cases

Tags

Getting Started

Similar Projects