Domain Manager: Prevent users from adding MX records when they have email forwarding enabled

[ghost]

In previous versions of the Domain Manager, a user was given an error message when they had email forwarding enabled and attempted to add another MX record, they had an error:

In Calypso, MX records can still be added when forwarding is enabled:

To reproduce:

1. Navigate to /domains and choose a site with a custom domain
2. Under Email, make sure to enable, add and verify a forwarder
3. Under Name Servers and DNS> DNS Records, Add New DNS Record
4. Notice the "Mail handled by WordPress.com email forwarding" MX Record
5. Add a new MX record, it is allowed and saves.

I think the best solution is highlighting the two MX records in red, and alert messaging near the top "Conflicting MX records for %DOMAIN may prevent email from being delivered."

I can see arguments being made for preventing them from adding the MX record altogether, but if their intention is to turn off mail forwarding, they would have to retype their new record another time.

Educating the user on how domain records works instead of forcing them to retype/click around more would be more helpful and aligned with how happiness works.

Another option would be an accept or deny dialog of some sort that deletes one the conflicting MX Records (could be more than one) depending on the user's choice. I'd prefer the first choice.

[designsimply]

Tested and confirmed that I can add an MX record if I already have email forwarding setup.

^{Seen at https://wordpress.com/domains/manage/threedotonefour.com/dns/design5279.wordpress.com using Safari 9.1 on Mac OS X 10.11.4}

However, recommend closing or moving to a milestone where it will be reviewed in a reasonable time since this was opened 144 days ago, was marked [Pri] Low 99 days ago, and has had no activity since.

@umurkontaci, we are leaning toward closing very old [Pri] Low issues as wontfix, should this issue be closed?

[umurkontaci]

It's definitely not a priority right now, but I'd rather not forget to fix this in the future since it will break the user's ability to receive emails.

[dcoleonline]

I also encountered this in ticket 2894181-t while helping a WordPress.com user.

[klimeryk]

Marking this as wontfix - I like the solution proposed here, but we're focusing on our own custom solution now.