1 (edited by harro.verton 2019-06-19 20:17:43)

Topic: Amavisd connection timeout on releasing quarantined mail

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 0.9.5-1.
- Deployed with iRedMail Easy or the downloadable installer? No idea.
- Linux/BSD distribution name and version: CentOS 7.5
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MariaDB Galera Cluster
- Web server (Apache or Nginx): Apache
- Manage mail accounts with iRedAdmin-Pro? Yes, 2.4.0-MySQL
====

Not sure if this was already reported, and/or already addressed. But if not:

Was called to a client this morning running iRedMail, because they got timeout errors when they tried to release quarantined email.

After spending some time checking the amavisd config (which turned out to be fine) I found that quarantine.py uses amavisd_db_host to connect to port 9998, which doesn't work if you use a shared database cluster instead of a local DB, like this client did.

To fix it, I have addded amavisd_quarantine_host to settings.py, with a value of "127.0.0.1", and changed quarantine.py to use that.

Now it releases without problems.

----

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

2

Re: Amavisd connection timeout on releasing quarantined mail

harro.verton wrote:

To fix it, I have addded amavisd_quarantine_host to settings.py, with a value of "127.0.0.1", and changed quarantine.py to use that.

Please store your custom setting in iRedAdmin-Pro config file "settings.py", do not modify any other ".py" files (the changes will be lost after upgrading iRedAdmin-Pro). In your case, you should add this setting in "settings.py" like this:

AMAVISD_QUARANTINE_HOST = "127.0.0.1"