Integrate doc/legacy into sphinx docs

[nicolan]

• [ ] ag.html
• [ ] anoncvs.html
• [ ] bugs.html
• [ ] changes.html
• [ ] faq.html
• [ ] feedback.html
• [ ] index.html
• [ ] install-admin-mb.html
• [ ] install-auth.html
• [x] install-backups.html
• [ ] install-compile.html
• [ ] install-configure.html
• [ ] install-http.html
• [ ] install-murder.html
• [ ] install-netnews.html
• [ ] install-perf.html
• [ ] install-prereq.html
• [ ] install-replication.html
• [ ] install-sieve.html
• [ ] install-snmpmon.html
• [ ] install-testing.html
• [ ] install-upgrade.html
• [ ] install-virtdomains.html
• [ ] install.html
• [ ] mailing-list.html
• [ ] man.html
• [ ] murder.fig
• [ ] netnews.fig
• [ ] os.html
• [ ] overview.html
• [ ] questions.html
• [ ] readme.html
• [ ] sieve-protocol.html
• [ ] sieve.html
• [ ] specs.html

[morrme]

What does this require?

[elliefm]

@morrme:

• identify legacy docs which have already been integrated into RST (such as install-backups.html)
• identify information that the legacy docs contain, but which the RST docs do not
• determine whether it's still relevant/correct
• integrate it into the RST docs

(Some of this work has already been done, but the record of which files have been reviewed/dealt with already was lost with the death of one of our previous bug tracking systems :( So we started the list again to make sure nothing was missed.)

[nicolan]

install-compile: I'm tempted to remove this altogether as we have new compile docs already in sphinx. While it does outline the options to configure, I'm not sure this needs to be converted as this means more content that needs to be kept in sync with the code, and hopefully anyone who needs non-standard options to configure already will think to look there.

@elliefm What do you think? Convert or drop doc/legacy/install-compile.html?

[elliefm]

Yeah I'm happy to lose that file, it doesn't offer anything particularly unique and has a bunch of date or less than ideal instructions in it anyway