Automated XML Check/Generation

[Sancus]

We should provide some way to automatically check that proposed XML files are valid, and possibly some way to automatically generate one by filling in some form fields somewhere.

Note that this is not a suggestion that we return to the idea of a fully database backed live web app, only that we add/improve some tools.

[benbucksch]

The old tracking bug was bug 543614 and its dependencies.

Here's a list of things to check (with links to specs and rationale why it's necessary):

• Format of config file adhering to spec and good practices (compare existing config files)
• Mail server reachable and speaks protocol
• Check whether SSL is offered
• Check whether encrypted passwords are offered
• Mail server hostnames are on the email domain (not always true, but a good positive check)
• WHOIS lookups (important to compare ownership of email domain and mail server domain, where they don't match)
• Test with real live accounts

The above list should be considered the minimum, not sufficient. It helps a human reviewer, and does not replace him.

[benbucksch]

The above checks are tedious, but necessary, and it would really help reviewers to see a compiled report of such checks during the review. Compare AMO/ATN pre-review automated checks. The reviewer needs to see the test results, though.

[benbucksch]

See also https://github.com/thundernest/autoconfig/issues/5#issuecomment-753441397