These pages documented very straightforward screens and flows that a
user can easily figure out without the help of dedicated documentation.
Besides, those screens are frequently reworked, thus requiring to
maintain the related pages very closely.
This commit removes such low values pages to reduce the technical debt
and allow focusing on actually useful documentation pages.
A page "How to set up a multifunction device or application to send email using
Office 365" explain how to configure Office 365 to make it work with Odoo
Closes#271
Coming from https://www.odoo.com/web#id=39964&view_type=form&model=project.task&action=333&active_id=880&menu_id=4720
Purpose
=======
Add following topics to email server doc:
how to use office 365 servers with Odoo on-premise (spf, dkim)
how to setup bounce system
Office 365: when customer use their business addresses or a custom domain in the "From":
1. SPF: if they have an SPF record, it is absolutely necessary that this record be modified to contain "include: _spf.odoo.com"
2. DKIM: We have enabled automatic DKIM signature for all domains, and to be valid they can add a DNS "odoo._domainkey" CNAME record to "odoo._domainkey.odoo.com". For example, for "foo.be" they should have a record "odoo._domainkey.foo.be" that is a CNAME with the value "odoo._domainkey.odoo.com".
This is especially useful if their domain pro is hosted by Office 365, and they want to enable the "DKIM" option in Office 365.
3. For domains hosted by Office 365, the previous 2 points are important, but not always enough to send emails from Odoo. They can improve the results by ensuring that the "Alias Domain" in Odoo's General Settings is their Office 365 domain (for example "foo.be") rather than "foo.odoo.com". But be careful, so that answers and bounces always reach Odoo, they must create a mail redirection in Office 365 for the "catchall @" (for example redirect "catchall@foo.be" to "catchall@foo.odoo.com" )
