• 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.

Is it possible to restrict users or domains to only particular email protocols?

W

whitecurve

Guest
Is it possible to restrict users or domains to only particular email protocols?

For instance can I have the server running pop3, pop3s, imap & imaps but only allow:
user1@domain1 access to the pop3's but not the imap's?
user2@domain1 access to the pop3s, not pop3, imaps & no access to imap.
Or any any other combination, you get the idea. . .. .
 
The control panel and entire Plesk server system was not intended to be used that way, so there are no built in functions like that.

The only (nightmarish) way I can see of doing it would require your clients to have static IPs, then use the firewall to block certain IPs from specific ports. This is really not a feasible solution, just one theoretical nightmare possibility (upkeep would be bad).
 
Back
Top