Fixes spamassassin tagging and postfix config changes to postscreen

[mzummo]

Signed-off-by: Mathew Zummo [email protected]

Description of the issue/feature this PR addresses:

Current behavior before PR: no spam tags, couldnt recieve email from accounts like gmail

Desired behavior after PR is merged:

fixes

[ghost]

Don't use the expensive postscreen tests without having a whitelist for the big email providers, otherwise they'll never get through. The big email providers rarely resend a message using the same server so the expensive tests ends up creating an endless loop preventing the email from being delivered.

Expensive postscreen checks:

• postscreen_bare_newline_enable
• postscreen_non_smtp_command_enable
• postscreen_pipelining_enable

postscreen_dnsbl_sites =
    ...
    list.dnswl.org=127.0.[0..255].[1..3]*-5
postscreen_dnsbl_whitelist_threshold = -5

---

I've found that this setup catches 90-95% of bad senders, with SpamAssassin catching the rest:
```
postscreen_dnsbl_sites =
    zen.spamhaus.org*2
    bl.spamcop.net*1
    b.barracudacentral.org*1
    bl.spameatingmonkey.net*1
    bl.ipv6.spameatingmonkey.net*1
    list.dnswl.org=127.0.[0..255].[1..3]*-5
postscreen_dnsbl_threshold = 2
postscreen_dnsbl_whitelist_threshold = -5
postscreen_dnsbl_action = enforce
postscreen_greet_action = enforce
```

[kryskool]

I think blacklist that user want to use , must be defined in the instaler.cfg

[ksaadDE]

Opened and not closed since 2017. What about this?