Facebook
TwitterPlesk has a set of predefined values for MX-preferences, eg. 0, 5, 10, 15, etc, etc. I would like to propose to remove or change the predefined value of zero (0). Why?
- Google warns users that a MX preference of 0 should be changed to a non-zero value when using GHS. Actually, they request the user to change the zero value to 1 (one). Which is impossible in Plesk, as its lowest value other than 0 is 5.
- Although I could not find any specific reason why an MX-preference of zero isn't allowed in the RFC, there is a reference that domains without MX-records should see the domain's A or AAAA record as MX pref 0. See:
http://tools.ietf.org/html/rfc5321#section-5.1
- There are reports on the Internet that some DNS and/or mailserver software have issues with MX preference zero.
- Again on the Internet it looks common practice to not use the preference 0.
My suggested fix is to change the value 0 to 1. I think its a very small change that should not have any operational impact and will result in less support request by Plesk end-users using Google mail services.
- Google warns users that a MX preference of 0 should be changed to a non-zero value when using GHS. Actually, they request the user to change the zero value to 1 (one). Which is impossible in Plesk, as its lowest value other than 0 is 5.
- Although I could not find any specific reason why an MX-preference of zero isn't allowed in the RFC, there is a reference that domains without MX-records should see the domain's A or AAAA record as MX pref 0. See:
http://tools.ietf.org/html/rfc5321#section-5.1
- There are reports on the Internet that some DNS and/or mailserver software have issues with MX preference zero.
- Again on the Internet it looks common practice to not use the preference 0.
My suggested fix is to change the value 0 to 1. I think its a very small change that should not have any operational impact and will result in less support request by Plesk end-users using Google mail services.
