1. Clarify that you need to manually create the user and group
when building from source. ./build.sh does not do that since
it is a packaging tool, not system configuration one.
2. Do not require "go" command to be present when running
./build.sh install. go installation may be user-specific and
unavailable when running with sudo.
3. Ease UMask restrictions. Allow group access.
This allows CLI commands to be run by any user in maddy group.
See #569.
Based on the spf documnet:
http://www.open-spf.org/action_browse_id_FAQ/Common_mistakes_revision_26/#helo
```
example.com. IN TXT "v=spf1 mx -all"
mailserver.example.com. IN TXT "v=spf1 a -all"
```
the second spf record in doc should set to a record.
otherwise the mail-tester will show
```SPF_HELO_SOFTFAIL SPF: HELO does not match SPF record (softfail)
```
softfail
Add more recommended best practice and fix a few mistakes.
1. SPF record should also be available via MX hostname (more precisely, HELO hostname we identify as)
2. MTA-STS requires an TXT record
3. TLSRPT can be used to get information about MTA-STS breakage.
4. Use p=quarantine in DMARC
5. Recommend deploying DANE in addition to MTA-STS
* Update setting-up.md
replacing hostname mx.example.org by example.org accordingly to the rest of the tutorial which doesn't refer to it (i.e. DNS configuration).
* readding MX1, with more detail
* adding A entry for mx1
* fixing ========
Now imapsql module does not handle authentication. (it was not doing it so well
anyway)
sql_table module was introduced and used in the default configuration as
a replacement for functionality that was implemented by imapsql before.
Parts of maddyctl code were rewritten to make it work transparently with
any IMAP backend or credentials store.
Closes#212.
Remove examples/ dir reference from REDME. It no longer exists.
Mention scdoc in installation tutorial.
Fix vim joke formatting.
Mention systemctl daemon-reload in intallation tutorial.
