From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] clamav and spamassassin
Date: Wed, 7 Dec 2011 07:16:36 +0700 [thread overview]
Message-ID: <CAA2qdGWsGvBCWskbwZoq2KsWG+ZaO4akeet_w=owq5jbt5MaVg@mail.gmail.com> (raw)
In-Reply-To: <CAEH5T2MtaBbccrZQM_J=Phqjy4J+_XHSnDGb9PU+BPYUqB=Hzw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2111 bytes --]
On Dec 7, 2011 2:22 AM, "Paul Hartman" <paul.hartman+gentoo@gmail.com>
wrote:
>
> On Tue, Dec 6, 2011 at 11:11 AM, Michael Orlitzky <michael@orlitzky.com>
wrote:
> > On 12/06/11 11:32, Grant wrote:
> >>
> >> 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?
> >>
> >
> > That will disable postgrey, but isn't enough to enable postscreen. There
> > are a couple of daemons you have to enable in master.cf (steps 2
through 6):
> >
> > http://www.postfix.org/POSTSCREEN_README.html#enable
> >
> > That README refers to lines that are commented-out in master.cf; of
> > course, if you've upgraded from an earlier of postfix, you won't have
them.
> >
> > What I did was to untar the latest postfix release under my home
> > directory, and find the master.cf that ships with it. Then, I
> > copy/pasted the lines mentioned in the README over to my real master.cf.
> >
> > After a restart, you should see lines like this in your mail log:
> >
> > Dec 6 03:13:46 mx1 postfix/postscreen[2810]: CONNECT from ...
> >
> > that let you know its' working.
>
> Thanks for bringing up postscreen and the rest of your responses to
> Grant in this thread, I wasn't aware of it either. None of the HOWTOs
> I read ever mentioned it. :) I'm going to give it a try and see how it
> goes.
>
Indeed. They are also unclear on how to configure SASL (but that's a
different story).
Luckily, I'm building my mailfiltering gateway from scratch, and have been
logging everything I do. When everything's finished and the mfgw works
well, I'll distill my log into yet-another-wiki-article.
Rgds,
[-- Attachment #2: Type: text/html, Size: 3111 bytes --]
next prev parent reply other threads:[~2011-12-07 0:19 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
2011-12-06 17:11 ` Michael Orlitzky
2011-12-06 19:17 ` Paul Hartman
2011-12-07 0:16 ` Pandu Poluan [this message]
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='CAA2qdGWsGvBCWskbwZoq2KsWG+ZaO4akeet_w=owq5jbt5MaVg@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