• Reset password only after full authentication
• Wording

• Revert possibility to check password policy using email address

• Move checks into the SQL query

In D5388#69819, @mollekopf wrote:

A more generic solution might be that the client can simply list the thing's it wants. which would be 'id' in this case (I suppose having the access_token implicit makes sense?).

A more generic solution might be that the client can simply list the thing's it wants. which would be 'id' in this case (I suppose having the access_token implicit makes sense?).

The slow_log becomes kinda redundant, but it's a "warning" level, so we can keep that.

I think at some point we should come up with a generic solution for more granular logging, but this will work for now.

• More debug logs

• Simplify

New diff created D5376: Include shared folders and resources when looking for a mail recipient

• Use walletOwner() where appropriate

Ok, maybe it's indeed less problematic this way.

Ignore subscriptions in the non-kolab4 branch too.

not tested yet