Sometimes it is required to use another sender FROM without changing it automatically.

Can not mark ham messages as spam serverwide on Plesk Email Security Pro. Many spam messages and senders look HAM but actually spam. This should be handled by server admin, not individual email clients.

Add a setting to disable mail forwarding to certain domains in Panel for global configuration so that on user side wont be allowed to put the certain domains in the Forwarding Email in the Plesk Panel. Thank you.

like <request_subject> allows to repeat the subject in the auto-reply, it would be nice to have a similiar tag like "<request_body>" making it possible to include the sender's mail body in the auto-reply message body.
This would make the handling of web form request a lot easier on plesk.

Due to IT security implementations it is often necessary to know when users changed their password to force them to change it again.
From this change, new features could be added to improve the service.
-Number of saved passwords
-Force password change every x days
-Send password change reminder

Allow the user to define expressions or words in the subject or body of the message that would classify the email as SPAM. For example: if a rule was created that classifies as SPAM every email that has the word 'OFFER' in the subject.
Just blacklisting by email / domain is not enough, because SPAMERS change domains very easily.

It is quite annoying that when mails are detected as spam they are moved to the spam folder but there is no possibility in PLESK to mark them as read. In Thunderbird e.g. there is no possibility to do that automatically because the spam detection is done by an external spam detection (PLESK). So you always have a lot of unread mails in the spam folders.

Currently Plesk has not remove the domain from the remote SmarterMail server and just disabled the it due to business logic (When a subscription is suspended, mail service and hosting service will be temporarily stopped to avoid losing mail data)

Add possibility remove domain from remote SmarterMail, when mail service disabled by administrator manually

create a specific mailbox on a domain which customer has access where he is unable to delete the email address, change it's passwords, disable it, etc.

According to Postfix documentation, multiple Postfix instances are supported. Would like to have such support implemented in Plesk
http://www.postfix.org/MULTI_INSTANCE_README.html

Hello,

On plesk you can only configure the Let's encrypt SSL on the webmail not on Smartermail.

It would be a great addition to add the same support also for Smartermail

An option to customize outgoing SMTP port.
Both for SMTP relay and direct SMTP.
Currently there's only a temporary workaround for Google Cloud VMs with Plesk.
This configuration might be overwritten by an update:
https://support.plesk.com/hc/en-us/articles/115004060494

When email specified at Scheduled backup notification it sent on behalf of user and failed due to SPF check

For example, if you set email for backup notification as test@example.com the email will be sent FROM test@example.com. And if it does not exist on server it may fail during SPF checl

It is expected that email sent FROM administrative email.

Add an option to the Mail Addresses page to expand all the forwarding emails. For example, rather than saying "(and 4 more)" list all 5 forwarding email addresses, not just the first one for each email address on the display.

Add an ability change the mailbox quota threshold and send the mailbox quota warnings to server administrator or to a specified mailbox.

You should add a simple option to specify mail server hostname when autodiscover is enabled on domain level...

example:
main.domain -> Web
mail.main.domain ->Mail server (this one should be in autodiscover xml response for incoming/outgoing hostname )

Is it currently possible to set only one mailbox to forward the mail for non-existent users in Domains > example.com > Mail > Mail Settings > Forward to address.
Please allow to add more than one email address for this setting.

By current design of Plesk SSL certificates selected to secure webmail in Plesk doesn't secure IceWarp webmail URL.

Consider adding this functionality.