Maygyver, if I understand correctly, the normal function is to offer whitelisting only for an email address known to the Astaro. If the Astaro isn't aware of an email "account" then it doesn't create a whitelist for it.
If you think you have a secondary address that doesn't give a whitelist opportunity, please check the spelling of the address in the Astaro user definition. If it is indeed correct, then please show an edit of that user and a picture of a quarantine email that doesnt offer whitelisting for that user.
I try to attach Screenshots, but I am on holiday next week, so please wait a little bit.
The Spelling is correct, cause it has been synced from Active Directory.
Hi this is a normal behaviour on the astaro. We only add the whitelist button to the spam report if a user object is created on the astaro with that e-mail address.
Andreas, I think you misunderstood. There is a user on the Astaro, created automatically from a backend AD-authenticated group. Maygyver says the additional addresses aren't being given the whitelist option on quarantine emails. If he has everything configured correctly, this would seem to be a bug.
thanks for the tip. But generally the AD user object has only one E-Mail field. So it should be only possible to sync the prímary address between AD and Astaro. This knowledge is based on AD 2003 do you know if it is possible to have more than one e-mail adress into a 2008 Server?
when the user is created automatically, all email field from Exchange are synced into Astaro.
The User is getting a Spam report for primary and all secondary. But only primary has a Whitelist action.
when the user is created automatically, all email field from Exchange are synced into Astaro.
The User is getting a Spam report for primary and all secondary. But only primary has a Whitelist action.
