<?xml version="1.0" encoding="UTF-8" ?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>milter-greylist at Yahoo! Groups</title>
    <link>http://groups.yahoo.com/group/milter-greylist/</link>
    <description>milter-greylist</description>

    <item>
      <title>Re: nsupdate support</title>
      <pubDate>Mon, 20 May 2013 13:30:36 GMT</pubDate>
      <dc:creator>Jim Klimov</dc:creator>
      <link>http://groups.yahoo.com/group/milter-greylist/message/6122</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/milter-greylist/message/6122</guid>
      <description>... Hmm... I guess you&#39;re right. Still, it can be part of the expiration mechanism - if the server has the blacklist entry removed by the time of TTL</description>
    </item>
    <item>
      <title>Re: nsupdate support</title>
      <pubDate>Mon, 20 May 2013 04:39:29 GMT</pubDate>
      <dc:creator>manu@...</dc:creator>
      <link>http://groups.yahoo.com/group/milter-greylist/message/6121</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/milter-greylist/message/6121</guid>
      <description>... Another idea: for each A record stored, I can add a TXT record for the current date. For instance, for today may 20th, I blacklist 192.0.2.1 and 192.0.2.2.</description>
    </item>
    <item>
      <title>milter-greylist-4.5.1 is available</title>
      <pubDate>Mon, 20 May 2013 04:36:02 GMT</pubDate>
      <dc:creator>manu@...</dc:creator>
      <link>http://groups.yahoo.com/group/milter-greylist/message/6120</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/milter-greylist/message/6120</guid>
      <description>Here is milter-greylist-4.5.1 http://ftp.espci.fr/pub/milter-greylist/milter-greylist-4.5.1.tgz MD5 (milter-greylist-4.5.1.tgz) =</description>
    </item>
    <item>
      <title>Re: nsupdate support</title>
      <pubDate>Sun, 19 May 2013 14:39:16 GMT</pubDate>
      <dc:creator>Peter Bonivart</dc:creator>
      <link>http://groups.yahoo.com/group/milter-greylist/message/6119</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/milter-greylist/message/6119</guid>
      <description>... Don&#39;t log the addition until you have actually done the nsupdate op, after that it&#39;s BINDs responsibility and it uses journaling for the transactions so it</description>
    </item>
    <item>
      <title>Re: nsupdate support</title>
      <pubDate>Sun, 19 May 2013 14:23:23 GMT</pubDate>
      <dc:creator>manu@...</dc:creator>
      <link>http://groups.yahoo.com/group/milter-greylist/message/6118</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/milter-greylist/message/6118</guid>
      <description>... That may be the easiest way. Using the greylisting database requires heavy refactoring, as the stored object is quite different from the current tuple. One</description>
    </item>
    <item>
      <title>Re: nsupdate support</title>
      <pubDate>Sun, 19 May 2013 11:10:36 GMT</pubDate>
      <dc:creator>Peter Bonivart</dc:creator>
      <link>http://groups.yahoo.com/group/milter-greylist/message/6117</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/milter-greylist/message/6117</guid>
      <description>... Maybe the addition could be logged and the timestamp could be used by an external script to remove old entries. /peter</description>
    </item>
    <item>
      <title>Re: nsupdate support</title>
      <pubDate>Sun, 19 May 2013 11:03:00 GMT</pubDate>
      <dc:creator>manu@...</dc:creator>
      <link>http://groups.yahoo.com/group/milter-greylist/message/6116</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/milter-greylist/message/6116</guid>
      <description>... Yes, you are right. TTL is no expiration mechanism. -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu@...</description>
    </item>
    <item>
      <title>Re: nsupdate support</title>
      <pubDate>Sun, 19 May 2013 09:37:59 GMT</pubDate>
      <dc:creator>Peter Bonivart</dc:creator>
      <link>http://groups.yahoo.com/group/milter-greylist/message/6115</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/milter-greylist/message/6115</guid>
      <description>... But TTL is for the client to decide if it should refresh it&#39;s cache or not (use cache or ask server again), it doesn&#39;t mean the record will expire on the</description>
    </item>
    <item>
      <title>Re: Feature request - include in greylist.conf</title>
      <pubDate>Sun, 19 May 2013 09:27:36 GMT</pubDate>
      <dc:creator>Jim Klimov</dc:creator>
      <link>http://groups.yahoo.com/group/milter-greylist/message/6114</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/milter-greylist/message/6114</guid>
      <description>I do use site-specific configurations (likely anyone does somehow) by creating a number of files named like &quot;greylist-01-common.conf&quot; and so on for manual</description>
    </item>
    <item>
      <title>Re: nsupdate support</title>
      <pubDate>Sun, 19 May 2013 09:17:44 GMT</pubDate>
      <dc:creator>Jim Klimov</dc:creator>
      <link>http://groups.yahoo.com/group/milter-greylist/message/6113</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/milter-greylist/message/6113</guid>
      <description>... Well, I used dynamic DNS in our LAN to point a service name to recently-working instances of the service (i.e. &quot;proxy&quot; points to several SQUID instances if</description>
    </item>
    <item>
      <title>Re: Feature request - include in greylist.conf</title>
      <pubDate>Sun, 19 May 2013 08:42:03 GMT</pubDate>
      <dc:creator>Peter Bonivart</dc:creator>
      <link>http://groups.yahoo.com/group/milter-greylist/message/6112</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/milter-greylist/message/6112</guid>
      <description>... A simple way would be not to change anything! If we change an included file we touch the greylist.conf-file ourselves to trigger a reload. I think those</description>
    </item>
    <item>
      <title>nsupdate support</title>
      <pubDate>Sun, 19 May 2013 05:12:05 GMT</pubDate>
      <dc:creator>manu@...</dc:creator>
      <link>http://groups.yahoo.com/group/milter-greylist/message/6111</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/milter-greylist/message/6111</guid>
      <description>Hi I am working on nsupdate support in milter-greylist, so that an action clause in an ACL can trigger a DNS update, which enables milter-greylist to feed a</description>
    </item>
    <item>
      <title>Re: Feature request - include in greylist.conf</title>
      <pubDate>Sun, 19 May 2013 01:43:03 GMT</pubDate>
      <dc:creator>manu@...</dc:creator>
      <link>http://groups.yahoo.com/group/milter-greylist/message/6110</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/milter-greylist/message/6110</guid>
      <description>... You need to monitor included file changes to detect configuration changes. Feel free to send a patch to the list. -- Emmanuel Dreyfus </description>
    </item>
    <item>
      <title>Re: Feature request - include in greylist.conf</title>
      <pubDate>Sat, 18 May 2013 18:49:03 GMT</pubDate>
      <dc:creator>elrond421</dc:creator>
      <link>http://groups.yahoo.com/group/milter-greylist/message/6109</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/milter-greylist/message/6109</guid>
      <description>[Reviving an old discussion...] ... This would also make distribution maintaining easier. Parts of the file maintained by the distributor (socket location for</description>
    </item>
    <item>
      <title>Re: Determining how successful milter-greylist is?</title>
      <pubDate>Tue, 09 Apr 2013 16:09:40 GMT</pubDate>
      <dc:creator>Emmanuel Dreyfus</dc:creator>
      <link>http://groups.yahoo.com/group/milter-greylist/message/6108</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/milter-greylist/message/6108</guid>
      <description>... I address that by having user-configurable recipient-dependent greylisting delays. They can choose no greylisting, 15mn greylisting, 15mn greylisting + 12h</description>
    </item>

  </channel>
</rss>
<!-- rss1.grp.bf1.yahoo.com uncompressed Tue May 21 04:55:02 PDT 2013 -->
