extend mailzu to support amavisd-new policy

[xpunkt]

i very much like mailzu, with postgresql, setup works, many questions is un answered, so i like to make a ticket to have it solved when time permits it

quantine management pr users is 100% done imho, but that does not mean it can't be done better, ej let users control more policy settings, more welcomelist/blocklists, this have being long time missed

most guides dokument mysql setups, missing sqlite3, postgresql, or ldap redis

ldap would be nice, but i don't have it :)

redis needs sysctl configs that i don't like, so i keep postgresql for all my data needs

[gnanet]

Scope of the project was (and currently is): MailZu is a simple and intuitive web interface to manage Amavisd-new quarantine.

For me it was clear,that managing quarantine means: finding, and releasing false positives; and getting rid of quarantined emails, which are not needed anymore.

1. I think the functionality to "let users control more policy settings, more welcomelist/blocklists, " is out of scope of the project.
2. the quarantine what MailZu is meant to manage can only be stored in either mysql or postgresql, a single file based sqlite is possible, but in production environment maybe not the best idea.
3. the LDAP part, its only the user-auth which has to be aligned to the mailserver setup
4. the usage of redis in amavisd-new, in my reading, does not relate to quarantined mail storage, so this seems also out of scope of the project