From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] clamav and spamassassin
Date: Tue, 6 Dec 2011 07:45:09 +0700 [thread overview]
Message-ID: <CAA2qdGU4=NQcUrFhyGrs5Qqh3dz=ooXucwmQWsA2OESUpWVr5g@mail.gmail.com> (raw)
In-Reply-To: <CAN0CFw2oS5s6PrVPhYB7U58wR+m--q8hAzN4vcuF+PKFuO8f0Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1461 bytes --]
On Dec 6, 2011 7:19 AM, "Grant" <emailgrant@gmail.com> wrote:
>
> > Here's the entirety of my main.cf postscreen section for reference. I've
> > deemed these safe, but you shouldn't enable them without reading what
they
> > do!
> >
> >
> > #
> > # Postscreen settings
> > #
> >
> > postscreen_greet_action = enforce
> >
> > postscreen_dnsbl_sites =
> > psbl.surriel.com,
> > bl.spamcop.net,
> > zen.spamhaus.org,
> > b.barracudacentral.org
> >
> > postscreen_dnsbl_threshold = 1
> > postscreen_dnsbl_action = enforce
> >
> >
> > ##
> > ## Deep protocol tests
> > ##
> >
> > postscreen_pipelining_enable = yes
> > postscreen_pipelining_action = enforce
> >
> > postscreen_non_smtp_command_enable = yes
> > postscreen_non_smtp_command_action = enforce
> >
> > postscreen_bare_newline_enable = yes
> > postscreen_bare_newline_action = enforce
>
> I've looked up each of those parameters and they sound fine to me.
> How long have you been running them? Have you been notified of any
> mistakenly rejected mail? It's very important my server doesn't miss
> any mail, even if it means dealing with more spam.
>
Similar situation with me. Because my company is in the financial sector,
false negatives are much more preferred than false positives.
(Although I can always weasel my way out of any problems caused by slight
configuration mistakes, I prefer not having to put myself into a situation
where weasel-ing is needed :-)
Rgds,
[-- Attachment #2: Type: text/html, Size: 2207 bytes --]
next prev parent reply other threads:[~2011-12-06 0:46 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-03 19:52 [gentoo-user] clamav and spamassassin Grant
2011-12-03 22:54 ` Michael Orlitzky
2011-12-04 0:59 ` Grant
2011-12-04 1:35 ` Michael Orlitzky
2011-12-04 1:57 ` Grant
2011-12-04 2:10 ` Michael Orlitzky
2011-12-04 1:59 ` Pandu Poluan
2011-12-04 2:17 ` Michael Orlitzky
2011-12-04 2:48 ` Pandu Poluan
2011-12-04 3:06 ` Michael Orlitzky
2011-12-04 8:27 ` Pandu Poluan
2011-12-06 0:15 ` Grant
2011-12-06 0:45 ` Pandu Poluan [this message]
2011-12-06 0:52 ` Michael Orlitzky
2011-12-06 1:01 ` Pandu Poluan
2011-12-06 1:14 ` Michael Orlitzky
2011-12-06 3:24 ` Grant
2011-12-06 4:43 ` Michael Orlitzky
2011-12-06 16:32 ` Grant
2011-12-06 17:11 ` Michael Orlitzky
2011-12-06 19:17 ` Paul Hartman
2011-12-07 0:16 ` Pandu Poluan
2011-12-06 21:34 ` Grant
2011-12-06 22:20 ` Michael Orlitzky
2011-12-07 1:02 ` Grant
2011-12-07 16:38 ` Michael Orlitzky
2011-12-07 18:16 ` Grant
2011-12-07 18:56 ` Michael Orlitzky
2011-12-07 19:00 ` Michael Orlitzky
2011-12-08 0:49 ` Grant
2011-12-07 9:15 ` Pandu Poluan
2011-12-07 16:01 ` Grant
2011-12-07 16:47 ` Pandu Poluan
2011-12-07 0:57 ` Grant
2011-12-07 1:11 ` Pandu Poluan
2011-12-07 16:34 ` Michael Orlitzky
2011-12-07 18:08 ` Grant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA2qdGU4=NQcUrFhyGrs5Qqh3dz=ooXucwmQWsA2OESUpWVr5g@mail.gmail.com' \
--to=pandu@poluan.info \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox