| 1 |
> Here's the entirety of my main.cf postscreen section for reference. I've |
| 2 |
> deemed these safe, but you shouldn't enable them without reading what they |
| 3 |
> do! |
| 4 |
> |
| 5 |
> |
| 6 |
> # |
| 7 |
> # Postscreen settings |
| 8 |
> # |
| 9 |
> |
| 10 |
> postscreen_greet_action = enforce |
| 11 |
> |
| 12 |
> postscreen_dnsbl_sites = |
| 13 |
> psbl.surriel.com, |
| 14 |
> bl.spamcop.net, |
| 15 |
> zen.spamhaus.org, |
| 16 |
> b.barracudacentral.org |
| 17 |
> |
| 18 |
> postscreen_dnsbl_threshold = 1 |
| 19 |
> postscreen_dnsbl_action = enforce |
| 20 |
> |
| 21 |
> |
| 22 |
> ## |
| 23 |
> ## Deep protocol tests |
| 24 |
> ## |
| 25 |
> |
| 26 |
> postscreen_pipelining_enable = yes |
| 27 |
> postscreen_pipelining_action = enforce |
| 28 |
> |
| 29 |
> postscreen_non_smtp_command_enable = yes |
| 30 |
> postscreen_non_smtp_command_action = enforce |
| 31 |
> |
| 32 |
> postscreen_bare_newline_enable = yes |
| 33 |
> postscreen_bare_newline_action = enforce |
| 34 |
|
| 35 |
I've looked up each of those parameters and they sound fine to me. |
| 36 |
How long have you been running them? Have you been notified of any |
| 37 |
mistakenly rejected mail? It's very important my server doesn't miss |
| 38 |
any mail, even if it means dealing with more spam. |
| 39 |
|
| 40 |
- Grant |
Archives