I've discovered today, that my smtp quarantine report haven't the "whitelist" links for each mail any more. The "release" link is already there.
Have I activate it in some settings? Where?
good that you found the source of the problem. You're indeed right that if you use AD than your additional email addresses get synced but with LDAP no additional email addresses are synced from the AD. And only user (precisely: the email addresses) which are defined/synced on the UTM can whitelist and blacklist senders. Therefore only they (precisely: there definied email addresses) get quaratine reports with a whitelist button. All other email addresses/users which don't have an entry in the users definition of the UTM can't white-/blacklist and therefore also don't see the whitelist button in the quarantine mail. The Quarantine Report btw is sent to every user of your internal domains which are defined in the "Mail Protection" category. Not only to the users you definied/synced.
If you want to use username@example.com as your login than the usage of the LDAP authentication method is currently your only choice. That the AD authentication service can't support logins like username@example.com is not a bug, but it is not yet supported. Thanks to your report we're considering implementing it.
good that you found the source of the problem. You're indeed right that if you use AD than your additional email addresses get synced but with LDAP no additional email addresses are synced from the AD. And only user (precisely: the email addresses) which are defined/synced on the UTM can whitelist and blacklist senders. Therefore only they (precisely: there definied email addresses) get quaratine reports with a whitelist button. All other email addresses/users which don't have an entry in the users definition of the UTM can't white-/blacklist and therefore also don't see the whitelist button in the quarantine mail. The Quarantine Report btw is sent to every user of your internal domains which are defined in the "Mail Protection" category. Not only to the users you definied/synced.
If you want to use username@example.com as your login than the usage of the LDAP authentication method is currently your only choice. That the AD authentication service can't support logins like username@example.com is not a bug, but it is not yet supported. Thanks to your report we're considering implementing it.