On Wed, Apr 6, 2016, at 09:12 AM, Noel Jones wrote:
> > postfix/postscreen[18826]: cache
> > btree:/var/lib/postfix/postscreen_cache full cleanup: retained=224
> > dropped=12 entries
> >
> > It looks like it's happening because they're 'full' at the time.
> They are removed because they are
On 4/6/2016 10:38 AM, jaso...@mail-central.com wrote:
> In my logs I see postscreen cache cleanups
>
> postfix/postscreen[18826]: cache
> btree:/var/lib/postfix/postscreen_cache full cleanup: retained=224 dropped=12
> entries
>
> It looks like it's happening because they're 'full' at the
brad.chand...@mbchandler.net:
> On 2015-06-03 10:49 am, wie...@porcupine.org wrote:
> > brad.chand...@mbchandler.net:
> >> How does the memcache interact with the
> >> proxy:btree:/var/lib/postfix/postscreen_cache?
> >
> > It happens in the Postfix memcache client.
> >
> > When you specify a back
On 2015-06-03 10:49 am, wie...@porcupine.org wrote:
brad.chand...@mbchandler.net:
How does the memcache interact with the
proxy:btree:/var/lib/postfix/postscreen_cache?
It happens in the Postfix memcache client.
When you specify a backup store in the Postfix memcache client
configuration file
brad.chand...@mbchandler.net:
> How does the memcache interact with the
> proxy:btree:/var/lib/postfix/postscreen_cache?
It happens in the Postfix memcache client.
When you specify a backup store in the Postfix memcache client
configuration file, the Postfix memcache client will update
both the
