David Goodwin

We should really use a database transaction - 1. begin transaction 2. change database 3. run script, if OK, commit transaction, else roll back?

Hm, well, in this case I think we could wrap the calls into a transaction, but I'm not sure it's a good idea - see https://github.com/postfixadmin/postfixadmin/compare/feature-save-in-transaction Problems : * Some...

Hi - thanks for the bug report. I'd agree it would be better if we had a better identifier in the popup. Unfortunately for fetchmail we only have the `id`...

Hello - thank you for the contribution? I've no experience of helm, but am curious why the 'official' docker image couldn't have been used? ( https://github.com/postfixadmin/docker )

setup password stuff - https://github.com/postfixadmin/docker/pull/48 I like this bit - ``` # create config.local.pgp with vaules from env with POSTFIXADMIN_ prefix POSTFIXADMIN_ENV_VARS=($(env | sort | grep --perl-regexp '^POSTFIXADMIN_.*')) ``` and...

I'm not quite sure what the data should look like, but perhaps : ``` MariaDB [postfix_legacy]> select * From virtual_aliases -> ; +-----+-----------+--------+-------------------------+ | id | domain_id | source |...

I've added DOCUMENTS/Migration.md to master; it's basically the above. It probably contains bugs :-)

well, you already have an entry for '[email protected]'. You could change the statement to 'INSERT IGNORE INTO alias ....' which would just ignore the error :)

Hi @worgenrage - no need to apologise for your excellent english (it's probably better than mine!).

To summarise you'd like to split the current 'mailbox.active' field into two boolean type fields - perhaps called something like 'enable_smtp' and 'enable_pickup' where * enable_smtp is used by postfix...