Clients log into the Plesk control panel, but can't configure their email accounts spam detection settings in there.
For that they have to log into Plesk using their email account and its password. (And can only do that if in Plesk the email addresses option "Can be used to log in to Plesk" is selected).
So instead of configuring spam detection on a domain level [which apparently can't be done at all at the moment] (or as an example on 15 email addresses right in Plesk) management or IT of the clients company has to log into all the mail accounts separately and adjust it if so desired.
Now, logging into Plesk using an email and its pw we CAN change the spam detection level.
The very "funny" [or actually not; i confuses the hell out of clients] part is, if the client now logs out of Plesk (which was logged in using a clients email address) and logs back into Plesk using Plesks proper login details, the client STILL sees the Plesk page they just logged out of! The one showing the clients email address with all the options to configure the spam detection levels!!
There is something VERY unfinished in the integration between Plesk and the Plesk email security extension.
-
What our clients would want: integrate it to the point where anything to do with spam can be configured right in the normal Plesk login. domain level, and email level. (Like it is when using Plesk without the PES extension). Currently it's a mess and not reasonably explainable to clients.
For that they have to log into Plesk using their email account and its password. (And can only do that if in Plesk the email addresses option "Can be used to log in to Plesk" is selected).
So instead of configuring spam detection on a domain level [which apparently can't be done at all at the moment] (or as an example on 15 email addresses right in Plesk) management or IT of the clients company has to log into all the mail accounts separately and adjust it if so desired.
Now, logging into Plesk using an email and its pw we CAN change the spam detection level.
The very "funny" [or actually not; i confuses the hell out of clients] part is, if the client now logs out of Plesk (which was logged in using a clients email address) and logs back into Plesk using Plesks proper login details, the client STILL sees the Plesk page they just logged out of! The one showing the clients email address with all the options to configure the spam detection levels!!
There is something VERY unfinished in the integration between Plesk and the Plesk email security extension.
-
What our clients would want: integrate it to the point where anything to do with spam can be configured right in the normal Plesk login. domain level, and email level. (Like it is when using Plesk without the PES extension). Currently it's a mess and not reasonably explainable to clients.