• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

allow users to manage own email aliases?

T

Tormente

Guest
is there a way to have users manage their own email aliases?

I see only the domain admin can do that, but I really need to have the users do it themselves.
 
Under a mail account's permissions you can set whether the mail user can login to Plesk to manage that mailname's settings.
 
yep,
but when that mail user logs into the control panel - they don't have an option to manage their aliases.

A list of their current aliases is displayed, but no way to manage it.
 
Hi:

At one time, mail users were able to manage their aliases. I believe that ability was removed sometime early in Plesk 6.0 because it constituted a security risk. I don't remember what that risk was.

John
 
that's strange,
I don't understand how that could be a security risk.

What's even stranger is that i've seen the same thing on other qmail based admin control panels, only site admins are usually allowed to do mail aliases - not endusers.

that is really annoying, as I myself am using aliases to help sort mail at the source and prevent/minimize and identify spam and sources of the spam.
I have told some of our users to do the same, but - now I'm the one having to add/delete aliases! :(
 
Back
Top