Feature Suggestions
Please provide here your suggestion for new functionality for Plesk. We encourage you to review and vote for suggestions of others. The top-ranked suggestions are likely to be included in the next versions of Plesk.
Please write in English so that voters from all over the world can read and support your request.
Off-topic posts will be removed from here
3 results found
-
Add IgnoreHosts options to Plesk`s DMARC implementation
Currently it is possible to whitelist only domain with IgnoreMailFrom parameter. However there could be false-positive DMARC failures (in case sender's strict policy and mail going throughout relay) due to which it could be useful to have option to whitelist specific network. It would be nice having this option available
10 votesDuring research, we have found that the request is about passing emails via intermediate mail gateway (which works as an anti-spam solution) and the idea of the request is do not check SPF for these emails on Plesk side.
In Plesk, there is already exist a solution for that: need to use "SPF Local rules" setting to configure an SPF record which will be used by Plesk to validate emails (including emails from an intermediate anti-spam solution). See KB article for mode details (https://support.plesk.com/hc/en-us/articles/360022753174) and Plesk documentation.
If it does not solve the issue on you Plesk environment and you still need the "IgnoreHost" option, let us know more details about you case for that in comments below.
— AY
-
Allow CNAME to point to another CNAME
Allow CNAME records to point to another CNAME record. Currently it is not possible to do so in Plesk and shows the error:
Error: Incorrect combination of DNS records is present in the DNS zone.
3 votesCould you please give an example why a CNAME needs to point to another CNAME and cannot point directly to the target? -- PD
-----
A CNAME can point to another CNAME, although this configuration is generally not recommended for performance reasons. When applicable, the CNAME should point as closely as possible to the target name in order to avoid unnecessary performance overheads. But 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. — IG
-
Set MX priority 100 or customize to any value
Possbility to add MX record with priority 100 but plesk allows only to select priorities from 0 to 50. For example to enable mail server to work properly at the OVH they require the configuration to priority 100
1 voteThe actual value of an MX priority does not influence the behavior of other servers directly. It is more a "sorting" criteria. When OVH asks for "100" in a list of their five MX servers as 1, 5, 50, 100, 200, you can also rearrange that list to values like 1, 5, 10, 15, 20 with 15 representing the 100, because it is in the same order "slot" as their manual suggests. Currently you can configure ten MX entries for the same domain, but in real-world configurations we've never encountered a domain where ten MX entries were needed.
If you know of an example where a provider asks for a fixed value like "100" and does not deliver mail if that value is not present in an MX record, please let us know in your comments.
-- PD
- Don't see your idea?