I'm using Postfix with Postgres since few years.
Postfixadmin is in charge of updating the DB and with last update (to 3.1), I had to change the vacation plugin on Roundcube.
Trying yours, I realize it was not compatible with my environment, so I've made few changes.
Most important are bellow :
postgres boolean cannot be set by values 1 or 0, by default
DB structure was different from what you expected, some field's names changed and no schema present
vacation.pl's convention for autoreply address was making use of # character, not @
I've successfully tested my changes and maybe you want to check them before accepting this PR because it's very postgres oriented and might not work "as is" with mysql.
WARNING: it seems that today a new release of postfixadmin (3.2) is out and changes have been made to vacation.pl, according to the changelog. If required, I will upgrade my branch when I'll upgrade to that new version, but I don't know when.
I'm using Postfix with Postgres since few years. Postfixadmin is in charge of updating the DB and with last update (to 3.1), I had to change the vacation plugin on Roundcube.
Trying yours, I realize it was not compatible with my environment, so I've made few changes.
Most important are bellow :
I've successfully tested my changes and maybe you want to check them before accepting this PR because it's very postgres oriented and might not work "as is" with mysql.
WARNING: it seems that today a new release of postfixadmin (3.2) is out and changes have been made to vacation.pl, according to the changelog. If required, I will upgrade my branch when I'll upgrade to that new version, but I don't know when.