On 7/26/2011 10:41 PM, Jared Johnson wrote:
We discussed doing this once at my organization and someone astutely
pointed out that considering that this is DNS, the better solution would
really be to run a local caching DNS server, e.g. bind9 and point
resolv.conf to 127.0.0.1 with forwarders to
On Wed, 27 Jul 2011, Jared Johnson wrote:
That sounds like a pretty sweet configuration!
[Note if you are running qpsmtpd-async, as we do, it's not really
possible to route DNS queries differently for DNSBLs versus other DNS
queries qpsmtpd does. ParaDNS doesn't handle paralleled DNS queries
On Wed, Jul 27, 2011 at 2:05 PM, Matt Sergeant m...@sergeant.org wrote:
However I'm unlikely to maintain much on Qpsmtpd now that Haraka has taken
off.
Matt.
how about a plugin adapter, so Haraka can use Qpsmtpd plugins or v/v?
That probably implies
either a node.js -- perl integration layer,
On Wed, 27 Jul 2011, David Nicol wrote:
On Wed, Jul 27, 2011 at 2:05 PM, Matt Sergeant m...@sergeant.org wrote:
However I'm unlikely to maintain much on Qpsmtpd now that Haraka has taken
off.
Matt.
how about a plugin adapter, so Haraka can use Qpsmtpd plugins or v/v?
That probably implies
Dear Chris,
On Mit 27.07.2011 10:59, Chris Lewis wrote:
On 7/26/2011 10:41 PM, Jared Johnson wrote:
[snipp]
Now each of our qpsmtpd instances has their own rbldnsd (serving ~700Mb
zone consisting of almost all the DNSBLs we use as one merged zone)
plus the Unbound DNS server package. This
