Officer assignment not holding

After officer elctions a few weeks back I updated the officer assignments in Membership Management. I am running Windows 7, and most current version of Chrome. Cookies are enabled. Club 2207975

When I come back in to the site, the new assignments are no longer selected and the former board is showing. At first I thought I might not have saved, but I have tried a couple of times, even assigned each officer and saving one at a time. It looks right when I am done, but reverts on the next login. Any thoughts?

Tried this suggestion by Brian listed on another request:
Remove the offending email, leave blank, click save.
System will assign dummy email.
Remove her from the vped position.
When she gets a working email remove 5he dummy and add the valid email.

The email is flagged as BAD, but sending directly works..Could one bad email prevent all officer assignments from sticking? How can I determine why the email is flagged BAD?

After removing the email and allowing a system generated dummy email to go in, I went into the users profile, removed the "BAD" email from the secondary email and put it in the primary email. Now it is not flagged and the officer assignments seem to be working properly. I will try it for a while to see if it holds. Did log out and return and new officer assignments (including the formerly "BAD" email address) seem to be working.

Seems like the officer assignment problem was fixed, by removing the offending email and then SAVING. Apparently one BAD email prevents all other changes from sticking until the offending email is removed. However now the offending email seems to still be BAD. Having the member check with their email provider about whitelisting.

Assuming we are talking about the mountprospect.com address.

I did some investigation on this, and my conclusion is that this email address is "flakey" ... it has some sort of variable lag built into the SMTP server connection that is very long. Our tests time out after 30 seconds and call it a failed connection which invalidates the email address.

Checks I did:

www.verifyemailaddress.org : BAD... cannot connect to SMTP server
tools.verifyemailaddress.io/ : BAD... RetyLater TransientNetworkFault (Trust Score = 3/10)
www.checktls.com/TestReceiver : OK... However, the test log shows that the connection takes a very long time and will likely timeout for us.

Therefore, I conclude that there is a intermittent connection issue with this email address... not our fault. The member should either address the long connect time with their SMTP server (might be a config issue) or they should use one of the reliable free email addresses.

Frankly, we should not have to do anything on our end to work around an email address that clearly has issues.

Appreciate the help Steve! And now I know some tools to diagnose email issues!