Amavis SQL-Problem / ISPConfig writes empty fields instead of NULL
i've a problem with the configuration of amavis:
i would like to use a special quarantine configuration for amavis. So i made an additional config-file /etc/amavis/conf.d/60-myconf, there i defined the different *_quarantine_method's and *_quarantine_to-variables, but it was never observed by amavis... :confused:
With $log_level = 4 (amavis) i saw in the logfile (mail.log) that he always takes the *_quarantine_to field from the db, but it was always empty --> No quarantine.
There is the Problem: Amavis takes an empty string as an value too, the field should be NULL, then amavis takes the value from the config file and it works. When i set the value to NULL manually, it works fine... but when i edit the policy in ISPConfig-Panel, it always set value to an empty string "".
some more infos about quarantine-config:
How could i solve this problem? Is it a bug?
Please set the variables in ispconfig and not the config file.
thanks for your fast answer...
Is this really possible? Where can i set the *_quarantine_method-Vars in the Panel? and sql-storage / logging (i.e. the var @storage_sql_dsn)?
You posted above that the variables are in the db and that the are set to an empty string. Every field that is in the db can also be set in the ispconfig interface.
yes thats true, but there are also vars which are not in the db.
As example: the field virus_quarantine_to in the db only allows local mail-aliases or a normal email-address for forwarding the mails. i would like to use local quarantine-dirs with different folders and sql-logging. So... when the field virus_quarantine_to in the db is set (empty string = set), amavis doesn't read the virus_quarantine_method-AND virus_quarantine_to-var out of the config-file, which would let me realize my config desired.
The vars *_quarantine_method couldn't set in the db.
i hope you understand, what i mean...
thanks & good night
|All times are GMT +2. The time now is 15:43.|
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2013, vBulletin Solutions, Inc.