HI Wietse!
Am 07.11.2014 um 13:28 schrieb Wietse Venema:
> This is internal data. Programs that depend on this are not supported.
O.K. THat's what I thought ... ;)
Next Question:
On one installation I've four MX all with the same DNS priority. If I
want to share the temp. whitelist-database between all this hosts, I
shouldwould do:
First I must define one master-memcache-host with IP 217.91.103.190. On
this host I've to install memcached, setup an run the memcache-Daemon.
Then I must confige all four Postfix-Servers to talk with the running
memcached:
/etc/postfix/main.cf
postscreen_cache_map = memcache:/etc/postfix/postscreen_cache
proxy_write_maps = proxy:btree:/var/lib/postfix/postscreen_cache
and further I must create the following file:
/etc/postfix/postscreen_cache
memcache = inet:217.91.103.190:11211
backup = proxy:btree:/var/lib/postfix/postscreen_cache
key_format = postscreen:%s
Is that correct or have I made a design-error?
With that setup, all four Postfix will share the temp. whitelist table
with the three others and they are writing a local backup? Right?
If memcached isn't aviable, every MX works with it own local written
backup file. Right?
But what happens, if memcached is back again. Whould the four temp.
whitlist tables get resynced, so every MX knows all the datas from the
other MX's? Or would it restart with a blank table an build it once
again from scratch?
Maybe you can bring a little light into my darkness. ;)
Thanx for help an answer!
ttyl
Django
--
"Bonnie & Clyde der Postmaster-Szene!" approved by Postfix-Master Peer
http://wetterstation-pliening.info
http://dokuwiki.nausch.org/doku.php/centos:mail_c7:start
