From: Grant <emailgrant@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] clamav and spamassassin
Date: Tue, 6 Dec 2011 08:32:14 -0800 [thread overview]
Message-ID: <CAN0CFw3ET1dxx2gjVpHwDZhwkGA0827Oe4voOstCS-O-h_taNg@mail.gmail.com> (raw)
In-Reply-To: <4EDD9D88.7080407@orlitzky.com>
>> What about trouble with the DNSBL lists? I know when I changed my IP
>> address I had to work to get the new one removed from a few blacklists
>> it had previously been placed on. I wasn't sending spam, but my
>> messages would have been blocked under that config if I hadn't done
>> the work to get the IP off the lists.
>>
>> - Grant
>>
>
> We do get false positives from the blacklists on rare occasion, but they're
> the same ones we got before postscreen.
>
> Before postscreen, we had,
>
> smtpd_recipient_restrictions =
> permit_mynetworks,
> ...
> reject_rbl_client psbl.surriel.com,
> reject_rbl_client bl.spamcop.net,
> reject_rbl_client zen.spamhaus.org,
> reject_rbl_client b.barracudacentral.org,
> permit
>
> After postscreen, we have,
>
> smtpd_recipient_restrictions =
> permit_mynetworks,
> ...
> permit
>
>
> postscreen_dnsbl_sites =
> psbl.surriel.com,
> bl.spamcop.net,
> zen.spamhaus.org,
> b.barracudacentral.org
>
> The two should be more or less equivalent considering that
> postscreen_dnsbl_threshold = 1. (I should mention that you have to register
> with barracuda before using their list.)
Got it. Your explanations are positively lucid.
I added this to /etc/postifx/main.cf:
postscreen_greet_action = enforce
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
and I commented this and restarted postfix:
#check_policy_service inet:127.0.0.1:10030
Should this effectively disable postgrey and enable postscreen?
- Grant
next prev parent reply other threads:[~2011-12-06 16:33 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
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 [this message]
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=CAN0CFw3ET1dxx2gjVpHwDZhwkGA0827Oe4voOstCS-O-h_taNg@mail.gmail.com \
--to=emailgrant@gmail.com \
--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