From: Michael Orlitzky <michael@orlitzky.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] clamav and spamassassin
Date: Wed, 07 Dec 2011 11:34:48 -0500 [thread overview]
Message-ID: <4EDF95A8.6080207@orlitzky.com> (raw)
In-Reply-To: <CAN0CFw3hwhiqk9vAOtrzLpBC90qs3DScDyP9Ey_wLCQpsSUz3Q@mail.gmail.com>
On 12/06/11 19:57, Grant wrote:
>> 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.
>
> Don't you let etc-update add them for you?
Well, etc-update offers to overwrite the old one with the new, but that
would be bad since we have a few custom services. I do try to patch the
new comments into my configuration files when possible, but my master.cf
is so far away from upstream's that the patch file is basically,
- Everything old
+ Everything new
These days I'm almost ready to claim that I actually understand how
postfix works, so I'm not afraid to maintain main.cf and master.cf by
hand anymore.
> Working now, thanks a lot. I should only need the tlsproxy line if my
> users connect to port 25 to send mail, correct?
You should enable it anyway: many remote MTAs will use encryption if you
let them.
next prev parent reply other threads:[~2011-12-07 16:36 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
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 [this message]
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=4EDF95A8.6080207@orlitzky.com \
--to=michael@orlitzky.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