postscreen's temp. whitelist-database
HI Wietse, as a curious admin which I am, I tried to take a look into the whitelist-database. example: 103.25.223.73 1415110281;1415031447;1417615882;1417615882;1417615882 80.148.29.141415427374;1415351796;0;0;0 May you tell me, what that timestamps in column two to six means? cul8r 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
Re: postscreen's temp. whitelist-database
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
Re: Postfix stable release 3.4.3
RPM 4 CentOS7 are build => http://repo.mailserver.guru/7/testing/x86_64/repoview/index.html
Re: Postfix Mailman integration
HI Ruben, Am 25.10.2015 um 11:09 schrieb Ruben Safir: > What can cause the list mail to hang for 3 hour or more? Have you tried to look into /var/log/mailman/error and /var/log/mailman/smtp-failure ? ttyl Django -- "Bonnie & Clyde der Postmaster-Szene!" approved by Postfix-God http://wetterstation-pliening.info http://dokuwiki.nausch.org http://wiki.piratenpartei.de/Benutzer:Django
Question to postscreen and memcache...
Hi List, while looking to the Postfix-Doku under: http://www.postfix.org/POSTSCREEN_README.html#temp_white_sharing we keep an eye on the Example 4: # Example 4: proxied btree: whitelist with memcache: accelerator. /etc/postfix/main.cf: postscreen_cache_map = memcache:/etc/postfix/postscreen_cache proxy_write_maps = proxy:btree:/var/lib/postfix/postscreen_cache ... other proxied tables ... # See note 1 below. # postscreen_cache_cleanup_interval = 0 /etc/postfix/postscreen_cache: # Note: the $data_directory macro is not defined in this context. memcache = inet:127.0.0.1:11211 backup = proxy:btree:/var/lib/postfix/postscreen_cache key_format = postscreen:%s Following statemant was written to "Example 4" at the Postfix-Doku: A non-persistent memcache: temporary whitelist can be shared between postscreen(8) daemons on the ---> same host or different hosts. <-- Disable cache cleanup (postscreen_cache_cleanup_interval = 0) in all postscreen(8) daemons because memcache: does not implement this (but see example 4 below for memcache: with persistent backup). QUESTION(s): How can shared a postscreen whitelist between 4 Server? How can this be configured in postfix for example? Is that even possible? Or we're totally wrong? Thank you! -- -- e-Mail : kl...@tachtler.net Homepage: http://www.tachtler.net DokuWiki: http://www.dokuwiki.tachtler.net --
Re: Question to postscreen and memcache...
Hello Wietse, Am 27.11.2015 um 16:08 schrieb Wietse Venema: > As documented, the whitelist in that example "can be shared only > between postscreen(8) daemons that run under the same master(8) > daemon". Hmmm, O.K. we discussed a further way. Via clusterfs Klaus may share /var/lib/postfix/cachepool between all 4 MX. With this config in his main.cf, Klaus can share the postscreen temporary whitelist: /etc/postfix/main.cf: postscreen_cache_map = lmdb:$data_directory/cachepool/postscreen_cache postscreen_cache_cleanup_interval = 0 I do not if that works even if this is performant enough. Wietse, as I read in your docu, the memcache-client could only use one memcached, right? What's then the prefferd solution to share postscreen_temporary_whitlist between i.e. 4 postfix's? Thanx 4 help! Best regards Django -- "Bonnie & Clyde der Postmaster-Szene!" approved by Postfix-God http://wetterstation-pliening.info http://dokuwiki.nausch.org http://wiki.piratenpartei.de/Benutzer:Django
Re: Question to postscreen and memcache...
HO p@rick! Am 27.11.2015 um 16:20 schrieb Patrick Ben Koetter: > Would it be possible to come up with something that allows to run a cluster of > Postfix hosts, sharing a temporary postscreen whitelist? Ohhh yes. ;) > It would be > desireable to serve a consistent policy throughout all cluster nodes. FULLACK! ttyl Django -- "Bonnie & Clyde der Postmaster-Szene!" approved by Postfix-God http://wetterstation-pliening.info http://dokuwiki.nausch.org http://wiki.piratenpartei.de/Benutzer:Django
