This would allow you to see mailboxes that are no longer in use.

System could remember a certain number of old passwords (admin configurable) and prevent user from selecting these again.

Have had more cases than I'd like to admit where customer re-used a previously compromised password. If Plesk remembered the last x passwords used by that account it would help.

Also adding ability so Plesk checks a server configurable password blacklist before accepting customers new selection would be appreciated.

Allow users and admin to select subject lines and keywords as well as keywords in the email body to be added to the spamfilter blacklist.

Currently spammers are just changing domains and sending the same email templates.

Now i have to insert a mailadresse at each mailaccount-blacklist.
i think it easier to use, i im able to handle a whiltelist/blacklist for all mailaccounts

Sometimes is useful check the details about POP3/IMAP/SMTP traffic for a single email, to look and find problems.

I would like to enable and configure fetchmail on mailbox level. Main reason is easy migration for customers to new hosting providers including moving mails from existing mail servers.

"fetchmail" is already installed together with PLESK, needs just to get properly configured.

If i add a new domain in a subscription, greylisting is automaticly activated, just because it's enabled on the server.

It would be much better if customers have to activate greylisting manually in their settings, like the spamfilter.

A workaround with Event Manager is possible but a bit inconvenient.

Don't send Auto-Reply when message detected as spam

When a mail account has Auto-Reply and Spamassassin enabled, the Auto-Reply function should read the x-spam header and, if the incoming message was found to be spam, the automatic response should not be sent.

At the moment I often see Automatic replies stuck in the outgoing mail queue because they're being sent to spammers. This is silly!

Plesk does not currently support DNS Whitelists like it does RBLs, such as the list at dnswl.org. There needs to be a way to add this from the Plesk UI.
The Postfix main.cf config directive is permitdnswlclient.
Whenever a Plesk upgrade happens, the setting, if added is removed and needs to be added back manually.

Server-Wide Black List blocking only by domain name is insufficient, because spammers can spoof real sender adress. Not every sender has SPF record configured. And also email White List needs whitelist by domain name to block common spammers with no fixed IP.

DKIM - needed to import own keys

It is not fair solution that Plesk generate a private key, and i cannot extract and date them in a seperate Backup

Please let us import our own DKIM keys

To use Sympa instead of Mailman

Use case: One of our customer has uploaded files to his ftp server in a public internet cafe and his password was stolen. Afterwards there was a mass spam mail sending script on his webserver. Our server has been landed in black lists. It was very difficult to find and correct it.

Roundcube for Windows

Required External/Remote mail server like mailenable, smartermail with different server.