W dniu 2015-11-28 03:32, wie...@porcupine.org napisał(a):
bi...@dev-ops.pl:
W dniu 2015-11-27 16:52, wie...@porcupine.org napisa?(a):
> Wietse Venema:
>> Django [BOfH]:
>> > Via clusterfs Klaus may share /var/lib/postfix/cachepool between all 4 MX.
>>
>> LMDB Postfix caches support sharing; non-
Wietse:
> What is the latency for looking up information that is NOT in the
> memcache? If it is 10 millseconds, then postscreen can handle only
> 100 connections per second, and it becomes a performance bottleneck.
bi...@dev-ops.pl:
> I have no idea what is the latency for lookup not cached infor
On Fri, Nov 27, 2015 at 09:26:20PM -0500, David Mehler wrote:
> In particular can I eliminate the rbl checks in
> smtpd_recipient_restrictions since they're going in the postscreen
> setup?
Keep both.
--
Viktor.
Il 26/11/15 21:43, Wietse Venema ha scritto:
Do not greylist sites that have many *different*
outbound MTA IP addresses. This is a greylisting problem,
not postscreen,
Wietse
Thanks for your clarification, Wietse.
I have found my (macroscopic!) configuration issue instead: Enablin
Viktor Dukhovni wrote:
> On Fri, Nov 27, 2015 at 09:26:20PM -0500, David Mehler wrote:
>
>> In particular can I eliminate the rbl checks in
>> smtpd_recipient_restrictions since they're going in the postscreen
>> setup?
>
> Keep both.
Please ignore my ignorance, but: why would one keep both?
On 11/28/2015 3:16 PM, Michael Grimm wrote:
> Viktor Dukhovni wrote:
>
>> On Fri, Nov 27, 2015 at 09:26:20PM -0500, David Mehler wrote:
>>
>>> In particular can I eliminate the rbl checks in
>>> smtpd_recipient_restrictions since they're going in the postscreen
>>> setup?
>>
>> Keep both.
>
> Pl
