Rspamd config for users/domains is generated with greylist = null

Regarding at least ispconfig versions 3.2.12p1 and 3.3.0p2.

There are some inconsistencies in regards of the generation of the rspamd config files for domains/users.

Domain config

The domain config is always generated with "greylist = null", even if the chosen domain policy is set to rspamd_greylist = 'y'. This is (probably) due to the $check variable always failing on a domain (in rspamd_plugin.inc.php). Domains must be handled in the "get policy for entry" section accordingly.

User config

The user config gets generated with greylist = null, when set to a policy (and there is rspamd_greylist set to y) and the "Enable greylist" is unchecked (which is the default). This is pretty unintuitive/cumbersome, since there is no reflection on the policy in detail in the backend. The user has no direct knowledge if the policy is configured with greylisting active. Activating greylisting in a second step will not(!) update the users policy. This has to be done, in a single step (chose policy, activate greylisting, save). The option should be negated in my opinion. "Disable greylisting", instead of "Enable greylisting".