A previous careless merge caused tests that counted on 3 users for @kolab.org to fail, I hope you don't mind I simply fixed them here.

• Validate with joe@kolab.org added
• Make the columns for this output sorted

• Wallet discounts (by a separate table)
• Fix discount migration, use uuid as discount identifier
• Add simple discount tests
• Add discount test
• Display discounted prices in UI

Unfortunately missed this for 0.9.6, so I'll pick it up in the next release.

This has already been merged.

This has been resolved in packaging as far as I know.

Available since 0.9.5.

Now available in 0.9.6

• Rebase on master

This will also need a rebase on master for tests to pass.

• Wallet discounts (by a separate table)

• Improve logon form, fix tests, remove dummy method

I'd re-check on 1st of month.

• Update for review

Here's an example of a more complex tls_config I use on my servers (using certbot + letsencrypt):

Looks good to me.

Apply patch to the develop branch

Looks like a nice simple change.

You need to supply Guam with a valid X.509 certificate (issued by Let's Encrypt, for example) and adapt the tls_config section of /etc/guam/sys.config accordingly.

In rK16b688d80237f2f24b9e01bfca7e692b2d0e6c1b#511210, @bohlender wrote:

in addition, the 2FA checkbox could use an explicit (as in not hidden behind the info button) hint
that this only works when the users also sets it up in roundcube,
as well as a hint that this will disable the usage of external clients for now

Guam should be listening on port 993, so please check if the Guam service is up and running.

Worked fine, I could't reproduce the issue. Closing this.

• Remove unused lang entries
• Fix phpstan errors

• Remove configured factors on entitlement delete, added tests

in addition, the 2FA checkbox could use an explicit (as in not hidden behind the info button) hint
that this only works when the users also sets it up in roundcube,
as well as a hint that this will disable the usage of external clients for now

I will look into integrating the patches.

• Use the actual hosted root dn
• Obsolete domain-specific roles
• Create the base roles

• Also progress certain roles

• Add postfix configuration changes to poll for the new status

Rebase on master