1 Topic by m3gz

  • m3gz
  • Member
  • Offline
  • Registered: 2013-08-07
  • Posts: 3

Topic: unchecked_lovers_maps and unchecked_lover

==== Required information ====
- iRedMail version: 0.8.4 upgrading to 0.8.5
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): LDAP
- Linux/BSD distribution name and version: CentOS 6.4
- Related log if you're reporting an issue: None
====

In the upgrade guide to 0.8.5, there is a section: "Fix incorrect SQL column name in Amavisd database"
When doing the query, the table does not exist there. I am using amavisd-new-2.8.0 (20120630)

Amavisd has been running fine, but I was wondering why I didn't have either unchecked_lovers_maps or unchecked_lover tables.

What triggers this table to be created and has the table creation query been fixed with the upgrade to 0.8.5?

----

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

2 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,091

Re: unchecked_lovers_maps and unchecked_lover

iRedMail-0.8.4 installs Amavisd-new-2.6.x on CentOS 6, the SQL structure is old (compare to Amavisd-new-2.8).

Column "unchecked_lovers" is in table "amavisd.policy", this table is used while you have '@lookup_sql_dsn' enabled in Amavisd. But it's disabled by default in iRedMail, so no impact.

You can ignore it, or delete the whole Amavisd database then re-create it with the latest SQL structure here:
https://bitbucket.org/zhb/iredmail/src/ … .7.0.mysql