Deepak M
My feedback
16 results found
-
17 votes
An error occurred while saving the comment An error occurred while saving the comment Deepak M
commented
As of now Tools & Settings => Mail Server Settings => Blacklist we can only add domain name but can't add IP addres. Where as in white list we can add IP address but not domain names
Actulally in both we should be able to add IP address as well as domain name
If there is hugh traffic coming from particular IP address then then admin need to block IP address. Also if sender is genuine and admin want to whitelist particular domain in white there should be option
Keeping only one option in whitelist and black list does not solve purpose fully
Deepak M
supported this idea
·
-
1,071 votes
Hi all, Thanks for your input, really appreciate this! As you know, in Plesk Onyx 17.8 we made a significant improvement that allows you to use several cloud storages or even SFTP for remote backups. In Plesk Onyx 17.9 we will continue to improve Plesk Backup Manager in general and Flexible Backup Scheduler Manager in particular.
Based on the initial description and comments I can highlight 3 scenarios in the scope of this request:
#1. Keep Daily & Weekly & Monthly backups at the same time: (Example: 2 weeks of daily backups + weekly backups by each Monday)
#2. Backup to different storages (like daily to FTP and monthly to Google Drive)
#3. Multiple Storages of the same type (like 2 different FTP servers)
ID in our Issue Tracker: PPM-1701
-DLDeepak M
supported this idea
·
-
63 votes
Thank you for your input! We will consider this functionality in upcoming releases, if it will be popular.
Everyone, please continue voting for this feature if you consider it important.—
IGDeepak M
supported this idea
·
-
59 votes
Look at this solution for Postfix – http://webmasters.stackexchange.com/questions/57746/plesk-email-journaling
But anyway, thank you for your input! We will consider this suggestion in upcoming releases if it will be popular.
Everyone, please continue voting for this feature and add your comments if you consider it important.
—
IGDeepak M
supported this idea
·
-
36 votesDeepak M
supported this idea
·
-
192 votes
Thank you for your input! We will consider this functionality in upcoming releases, if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
—
ETDeepak M
supported this idea
·
-
388 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
— AY
Deepak M
supported this idea
·
-
82 votesDeepak M
supported this idea
·
-
214 votesDeepak M
supported this idea
·
-
24 votesDeepak M
supported this idea
·
-
238 votesDeepak M
supported this idea
·
-
1,197 votesDeepak M
supported this idea
·
-
679 votesDeepak M
supported this idea
·
-
543 votes
We have serious doubts this function can really increase server security:
1) Plesk has built-in protection against brute-force on login – it will lock the login form. So no one can try multiple attempts
2) Arbitrary login name adds very little guess-complexity to a proper password. If you have concerns for your login brute-forced – add another 5-7 characters into your password and feel safe.As changed login name is still very likely to be some sort of vocabulary word or derived from your other account name – this function would only give a false sense of better security. Your security strength is in complex password, not in a complex login name. If you have one good password, you don’t need to treat login as your “second password” – one good password is enough.
As for concerns that default password requirement is set in “weak”, that fail2ban module is not…
Deepak M
supported this idea
·
-
43 votesDeepak M
supported this idea
·
An error occurred while saving the comment Deepak M
commented
yes
Email Notifications to customers should go from reseller id or let it go from plesk@domain.com and to reseller it can be sent from server admin id or plesk@serverhostname.com
Capnel does it similar way if it goes via reseller id that is better so if customer reply to that email he can attend it immediately
-
418 votesDeepak M
supported this idea
·
An error occurred while saving the comment Deepak M
commented
Yes there should be option to enable Spamassassin on domain level if not subscription level.
As it very bad idea to activate individual mailbox level i have 250 mailboxes so ti enable spam setting individually is time consuming process. Even there should be domain level spam scoring which will be inherited to all mailboxes, then if require spam score can be changed for individual mailbox
Same way white list / black should be domain level so that will be inherited to all mailboxes. Individual mailboxes can have their own white / black list
Antivirus should be activated for entire server for all mailboxes as Odin premium antivirus is server license not user license. By default everyone need email scanning. These should be option to to scan incoming , outgoing or both on server wide itself
serverwide mail setting we can only add ip in whitelist not domain name
at user level we can add domain in individual domain settings