On Tuesday, April 05, 2016 08:10:26 PM Noel Jones wrote:
> On 4/5/2016 6:05 PM, jaso...@mail-central.com wrote:
> > I'm pretty sure this is a pypolicyd issue, not Postfix, but asking here
> > just in case someone's seen it already.
> >
> > I've moved my Postfix SPF checks out of Amavisd/Spamassass
On 4/5/2016 6:05 PM, jaso...@mail-central.com wrote:
> I'm pretty sure this is a pypolicyd issue, not Postfix, but asking here just
> in case someone's seen it already.
>
> I've moved my Postfix SPF checks out of Amavisd/Spamassassin to pypolicyd-spf.
>
> It works as expected, when I use "Header
I'm pretty sure this is a pypolicyd issue, not Postfix, but asking here just in
case someone's seen it already.
I've moved my Postfix SPF checks out of Amavisd/Spamassassin to pypolicyd-spf.
It works as expected, when I use "Header_Type=SPF" in the config. When I
switch ONLY the "Header_Type=A
On 5 Apr 2016, at 10:59, jaso...@mail-central.com wrote:
looking at my notes, I found
...
With smtpd_delay_reject=no milters always follow built-in restriction
processing.
With smtpd_delay_reject=yes, milters process: connect -> helo/ehlo ->
from: before any smtpd_mumble_restricti
> I'll set the
>
> smtpd_delay_reject=yes
>
> and watch that for awhile to see what happens.
Okay, I remembered what I was *trying* to make sure happened by setting
smtpd_delay_reject=no
For now I'm trying to do everything stepwise and more-or-less separated in
Postfix config,
jaso...@mail-central.com:
> What plans are there, if any, to move to using PCRE v2 in Postfix?
If someone has time to port dict_pcre to dict_pcre2 (including the
documentation in pcre_table to pcre2_table, and including all the
postfix documentation that mentions pcre) then that would be great.
O
I build & use the latest Postfix release from source instead of depending on
distro packages.
I use regex alot, including in Postfix. I try to keep up to date with upstream
PCRE too.
PCRE has released a v2, where all new features appear, and maintains (bug-fixes
only) v1.
http://www.
Yep, I had
smtpd_delay_reject=no
set in main.cf
Wondeing WHY I
"set the non-default non-recommended "smtpd_delay_reject = no"."
looking at my notes, I found
...
With smtpd_delay_reject=no milters always follow built-in restriction
processing.
With smt
On 4/5/2016 9:17 AM, jaso...@mail-central.com wrote:
> On 04/05/2016 07:08 AM, Wietse Venema wrote:>> I'm not exactly sure why I'm
> getting one CONNECT and 2 REJECTs.
>>
>> The client sent two RCPT TO commands. Why did it try the same
>> recipient twice? No idea, I didn't write the client code.
>
On 5 Apr 2016, at 10:08, Wietse Venema wrote:
jaso...@mail-central.com:
I've added blocking by TLD to my setup. Right now, it blocks at helo
checks.
It's working.
Looking at my logs, EVERY time I get a 'bad TLD' connection, there's
always 2 similar reject entries, but only one CONNECT/PASS
On 04/05/2016 07:08 AM, Wietse Venema wrote:>> I'm not exactly sure why I'm
getting one CONNECT and 2 REJECTs.
>
> The client sent two RCPT TO commands. Why did it try the same
> recipient twice? No idea, I didn't write the client code.
I was just looking to make sure I'm not doing something wro
jaso...@mail-central.com:
> I've added blocking by TLD to my setup. Right now, it blocks at helo checks.
>
> It's working.
>
> Looking at my logs, EVERY time I get a 'bad TLD' connection, there's always 2
> similar reject entries, but only one CONNECT/PASS For example
>
> Apr 4 19:55:3
I've added blocking by TLD to my setup. Right now, it blocks at helo checks.
It's working.
Looking at my logs, EVERY time I get a 'bad TLD' connection, there's always 2
similar reject entries, but only one CONNECT/PASS For example
Apr 4 19:55:38 mail01 postfix/postscreen[7444]: CONNE
13 matches
Mail list logo
