On 11 Jan 2019, at 4:08 am, Wietse Venema wrote:
>
> Larry Stone:
>>> # Log file to use for error messages. "syslog" logs to syslog,
>>> # /dev/stderr logs to stderr.
>>> #log_path = syslog
>>> log_path = /var/log/mail.log
>>>
>>> So I?ve had to change this so that it writes directly to the
li...@lazygranch.com:
> I'm wondering if I have my rate limiting set up correctly. Note I have
> that perl script that sniffs out dynamic IP addresses, so I am not sure
> how this user is even getting concurrent connections.
Postfix receives more than 4 concurrent connections at a rate of
more
Jacky:
> Hi Wietse,
>
> Thank you for the information.
>
> Just wonder that will Postfix support the Message Submission BURL Extension?
Possibly. See my other post on that subject. BURL does not
require changes to Postfix's AUTH= support.
Wietse
Hello,
I have made a small patch for counting milter rejections in pflogsumm.
I put it on http://test.fantomas.sk/pflogsumm-milter-test.patch
pflogsumm now displays erors below when using amavisd-milter refusals.
I would strip the "from ", but first I would like to ask people who use
header
> On Jan 11, 2019, at 9:02 AM, Gary wrote:
>
> Now with that interpretation of the log, this makes sense. I was thinking
> rate and concurrency were different things.
They are different things. Both the rate and the concurrency were exceeded
in the logs you posted.
* Concurrency = Number
Now with that interpretation of the log, this makes sense. I was thinking rate
and concurrency were different things.
Original Message
From: wie...@porcupine.org
Sent: January 11, 2019 4:21 AM
To: postfix-users@postfix.org
Reply-to: postfix-users@postfix.org
Subject: Re: concurrency rate
