{"action":"closed","issue":{"url":"https://api.github.com/repos/tomav/docker-mailserver/issues/161","repository_url":"https://api.github.com/repos/tomav/docker-mailserver","labels_url":"https://api.github.com/repos/tomav/docker-mailserver/issues/161/labels{/name}","comments_url":"https://api.github.com/repos/tomav/docker-mailserver/issues/161/comments","events_url":"https://api.github.com/repos/tomav/docker-mailserver/issues/161/events","html_url":"https://github.com/tomav/docker-mailserver/issues/161","id":150939680,"number":161,"title":"Discussion: more restrictive Postfix configuration to block spam early","user":{"login":"stonemaster","id":1463490,"avatar_url":"https://avatars.githubusercontent.com/u/1463490?v=3","gravatar_id":"","url":"https://api.github.com/users/stonemaster","html_url":"https://github.com/stonemaster","followers_url":"https://api.github.com/users/stonemaster/followers","following_url":"https://api.github.com/users/stonemaster/following{/other_user}","gists_url":"https://api.github.com/users/stonemaster/gists{/gist_id}","starred_url":"https://api.github.com/users/stonemaster/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/stonemaster/subscriptions","organizations_url":"https://api.github.com/users/stonemaster/orgs","repos_url":"https://api.github.com/users/stonemaster/repos","events_url":"https://api.github.com/users/stonemaster/events{/privacy}","received_events_url":"https://api.github.com/users/stonemaster/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/tomav/docker-mailserver/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2016-04-25T18:02:04Z","updated_at":"2016-04-27T09:24:39Z","closed_at":"2016-04-27T09:24:39Z","body":"I am using an issue here to discuss the possibility to have a more restrictive ***Postfix*** configuration to block spam before it is even looked at by Spamassasin etc.\r\n\r\nI recently switched to **docker-mailserver** and I observed an increase in daily spam mails that actually land in my INBOX. Looking at the diff between the container's postfix configuration I noticed that the container's configuration doesn't impose many restrictions on the sending server. But there are some configurations option which block many typical spam sending server (dynamic IPs etc.) using some more restrictive configurations options as described here: https://www.webstershome.co.uk/2014/04/07/postfix-blocking-spam-enters-server/.\r\n\r\nIn production I noticed that configurations described as those in the blog post actually the number of spam mails that hit the server and thus don't need to be processed by Spamassasin (and eventually getting in the INBOX).\r\n\r\nDoes something like that makes sense as a default configuration? I think we could figure out some settings which should work for most mail servers. And optionally this could be made an startup option?\r\n\r\nThanks!"}}