exim-dev at spodhuis
May 27, 2009, 2:39 PM
Views: 409
Permalink
|
|
[Bug 847] Enabled DNSDB by default
|
|
------- You are receiving this mail because: -------
You are on the CC list for the bug.
http://bugs.exim.org/show_bug.cgi?id=847
--- Comment #1 from Phil Pennock <exim-dev[at]spodhuis.org> 2009-05-27 22:39:34 ---
Exim generally provides clean and simple ways of doing things but enough
flexibility to not constrain and to let people do other stuff not previously
thought of. Often, use of dnsdb can later be solved better with new features
integral to Exim (which might be regarded as bloat); dnsdb means that the
administrators can solve some current problems now instead of waiting for a new
release.
Eg, a recent request to extract the lowest value MX record for a domain, with
error checking for no MX (but other records so that the dnsdb lookup itself
does not raise an expansion failure) might be:
${if !eq{${reduce{<\n ${lookup dnsdb{mx=$domain}}}{70000 .}{${if
<{${extract{1}{ }{$item}}}{${extract{1}{ }{$value}}}{$item}{$value}}}}}{70000
.}{${reduce{<\n ${lookup dnsdb{mx=$domain}}}{70000 .}{${if <{${extract{1}{
}{$item}}}{${extract{1}{ }{$value}}}{$item}{$value}}}}}fail}
(This would be significantly simpler if expansion conditions set variables like
$condvalue_left $condvalue_right for use later on in the same expansion)
The above would also be simpler if dnsdb had a fail_nodata keyword to go before
the option type, so that a successful lookup yielding no data is converted into
a fail.
--
Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email
--
## List details at http://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
|
[Bug 847] Enabled DNSDB by default