On 2021-11-06 Wietse Venema wrote:
> li...@lazygranch.com:
>> Reply-To: jm84450...@gmail.com
>
> Use header_checks (not body_checks) if you want to block that.
> Still, I would be concerned about rejecting legitimate email.
It's true that this can reject legitimate e-mail. However, the abuse of
Gm
On 08/11/2021 08:43, Ansgar Wiechers wrote:
On 2021-11-06 Wietse Venema wrote:
li...@lazygranch.com:
Reply-To: jm84450...@gmail.com
Use header_checks (not body_checks) if you want to block that.
Still, I would be concerned about rejecting legitimate email.
It's true that this can reject legit
[An on-line version of this announcement will be available at
http://www.postfix.org/announcements/postfix-3.6.3.html]
Fixed in Postfix 3.6.3, 3.5.13, 3.4.23, 3.3.20:
* (problem introduced in Postfix 2.4, released in 2007): queue
file corruption after a Milter (for example, MIMEDefang) mad
Hi
I have aliasgroup (I mean a...@domain.ltd)
schema:
To:--a...@domain.ltd->postfix->amavis+SA--->-back-to-postfix--robalck-from-aliasgroup-lmtp>dovecot
works fine but I have one question is avilable in postfix (to limit
rolback) e-mail in alias group ?
I limited smtpd_re
natan:
> Hi
> I have aliasgroup (I mean a...@domain.ltd)
>
> schema:
> To:--a...@domain.ltd->postfix->amavis+SA--->-back-to-postfix--robalck-from-aliasgroup-lmtp>dovecot
>
> works fine but I have one question is avilable in postfix (to limit
> rolback) e-mail in alias grou
natan:
Hi
I have aliasgroup (I mean a...@domain.ltd)
schema:
To:--a...@domain.ltd->postfix->amavis+SA--->-back-to-postfix--robalck-from-aliasgroup-lmtp>dovecot
works fine but I have one question is avilable in postfix (to limit
rolback) e-mail in alias group ?
On 08.11
Hi
My configurations is not standard beacuse:
master.cf:
smtp inet n - y - 100 smtpd
-o receive_override_options=no_address_mappings
In main.cf
I put all connections to local haproxy who called to 3 x amavis. And
amavis return to
xxx.xxx.xxx.184:10027 inet n
Sorry for the delay, but the scanner had network issues and could not re-scan
the MTA
It turns out that the scanner is in the subnets defined by "mynetworks"
But here is the interesting part: all the message attempts made by the scanner
were rejected. I went through the logs with a fine-toothe
I would like to check if I am understanding setting a backup MX correctly.
Am I missing something here ?
DNS settings
example.com primary-mx.example.com 10
example.com backup-mx.example.com 20
Backup MX postfix settings
/etc/postfix/main.cf:
myorigin = example.com
mydestinat
Hi there,
We're testing a custom filter for PHP using spawn services.
During our tests, we noticed that every time that we invoke the
check_policy_service through docker container it takes about 1 second to
run the filter script.
I first thought it was the local spawn that would be taking too lo
> For testing purposes, the policy_service script just returns "PERMIT" so it
> won't have any heavy processing.
What script? Perl? Python? PHP? Nodejs? Bash?
Maybe which ever script language you are using is expensive to start, loading
libraries, dependencies, etc.
On Mon, Nov 08, 2021 at 02:32:58PM -0300, Rafael Azevedo wrote:
> We're testing a custom filter for PHP using spawn services.
Make sure your script loops reading multiple requests until it sees a
connection close from the client (smtpd(8)). Reading just one request
and exiting can lead to perfor
Rafael Azevedo:
> Hi there,
>
> We're testing a custom filter for PHP using spawn services.
>
> During our tests, we noticed that every time that we invoke the
> check_policy_service through docker container it takes about 1 second to
> run the filter script.
The mistake is to EXIT the PHP scrip
Its a PHP simple script:
#!/usr/bin/php
I have other scripts running on Gentoo doing much "harder" work and it
performs in less than 0.1 second...
Sample output:
08/11/2021 15:25:15 - Message 2 sent to mya...@test.com in 1023 ms.
08/11/2021 15:25:16 - Message 3 sent to mya...@test.com in 1022
Wietse Venema:
> Rafael Azevedo:
> > Hi there,
> >
> > We're testing a custom filter for PHP using spawn services.
> >
> > During our tests, we noticed that every time that we invoke the
> > check_policy_service through docker container it takes about 1 second to
> > run the filter script.
>
> T
> Its a PHP simple script:
>
> #!/usr/bin/php
> print_r("action=PERMIT\n\n");
> ?>
As Wietse stated, the policy server is designed to be recycled to avoid a
script start up expense for each email. I created this in PHP before deciding
to use a milter instead. Here is an example of how i was
Thanks a lot Wietse, the problem was the PHP script not being reused.
Problem fixed.
Huge thanks to everyone here, you guys are awesome!
Thanks!!!
Em seg., 8 de nov. de 2021 às 14:55, Wietse Venema
escreveu:
> Rafael Azevedo:
> > Hi there,
> >
> > We're testing a custom filter for PHP using s
Thank you so much for your time and help.
You guys are the best!
Thanks
Em seg., 8 de nov. de 2021 às 16:16, escreveu:
> > Its a PHP simple script:
> >
> > #!/usr/bin/php
> > > print_r("action=PERMIT\n\n");
> > ?>
>
>
> As Wietse stated, the policy server is designed to be recycled to avoid a
18 matches
Mail list logo
