docker/docker-mailserver
1
0
Fork 0
mirror of https://github.com/tomav/docker-mailserver.git synced 2024-06-28 12:11:32 +02:00
Code Issues Releases Wiki Activity

Added FAQ about naked/bare domains

Browse Source
This commit is contained in:
Erik Wramner 2020-01-18 11:39:04 +01:00
parent 5d0715c2e1
commit 53f092e8c6
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/content/config/troubleshooting/faq.md
View File

@ -71,6 +71,18 @@ For a trailing white-space subject one can define the whole variable with quotes
- "SA_SPAM_SUBJECT=[SPAM] "
```
### Can I use naked/bare domains (no host name)?
Yes, but not without some configuration changes. Normally it is assumed that docker-mailserver runs on a host with a name, so the fully qualified host name might be mail.example.com with the domain is example.com. The MX records point to mail.example.com. To use a bare domain where the host name is example.com and the domain is also example.com, change mydestination from:
`mydestination = $myhostname, localhost.$mydomain, localhost`
To:
`mydestination = localhost.$mydomain, localhost`
Add the latter line to config/postfix-main.cf. That should work.
### Why are Spamassassin x-headers not inserted into my sample.domain.com subdomain emails?
In the default setup, amavis only applies Spamassassin x-headers into domains matching the template listed in the config file 05-domain_id (in the amavis defaults). The default setup @local_domains_acl = ( ".$mydomain" ); does not match subdomains. To match subdomains, you can override the @local_domains_acl directive in the amavis user config file 50-user with @local_domains_maps = ("."); to match any sort of domain template.