Thanks for explaination.
Smtpd_content_filter=[127.0.0.1]:10026
Typo, or rather my cell phone auto completing things for me and me not
catching it.
If I might ask another peripheraly related and most probably very dumb
question - is it possible to the have the inverse of
"permit_authenticated_users"?
The rules for this outfit are - imap for picking up you mail, submission
(port 587) for sending. So if somebody who can authenticate themselves
turns up on port 25, they are in the wrong place.
John A
Sent from my S3
On February 2, 2016 4:50:11 AM Noel Jones <njo...@megan.vbhcs.org> wrote:
On 2/1/2016 12:30 AM, John A @ KLaM wrote:
My question is what is the /best/ way of getting postfix to forward
mail to the signing policy bank.
In one example the submission section of master.cf had the following
lines added
smtpd_proxy_filter=[127.0.0.1]:10026
milter_macro_deamon_name=ORIGINATING
Added, I think l understand the first line but why the second, it
does seem to appear anywhere else.
The first line assumes a before-queue proxy filter (amavisd-new)
configured to do DKIM etc. on port 10026. Your main.cf or regular
smtpd service would use a proxy filter on a different port.
The milter_macro_name parameter is used by some milters -- such as
opendkim -- to trigger DKIM signing. It's not used by amavisd-new,
but won't cause any problem to be there.
A brief discussion of before-queue filtering vs. after-queue
filtering can be found here:
http://www.postfix.org/SMTPD_PROXY_README.html#pros_cons
In another a single line was added to the submission section
Smtpd_content_filter=[127.0.0.1]:10026
This example uses an after-queue content filter.
Note: smtpd_content_filter is not a built-in postfix parameter, so
either this is a macro that must also be defined in main.cf or a typo.
This example omits the milter_macro_name, presumably because the
site does not use a milter, and has no plans to use a milter in the
future.
John A
KlaM
