[exim-dev] [Bug 1289] 10.14: Is there a wrong example?

Startseite
Nachricht löschen
Nachricht beantworten
Autor: Todd Lyons
Datum:  
To: exim-dev
Betreff: [exim-dev] [Bug 1289] 10.14: Is there a wrong example?
------- You are receiving this mail because: -------
You are on the CC list for the bug.

http://bugs.exim.org/show_bug.cgi?id=1289

Todd Lyons <tlyons@???> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tlyons@???
             Status|NEW                         |ASSIGNED





--- Comment #4 from Todd Lyons <tlyons@???> 2012-08-27 17:10:32 ---
I too agree that the way it explains it currently is very accurate, but do
consider a better example and/or readability enhancements worthwhile for this
complicated logic.

1) With a small modification to the paragraph after the warning about
temporary dns errors, this might make the readability better without changing
any of the detail explanation:

.cindex "&`+ignore_unknown`&"
Exim parses a host list from left to right. If it encounters a permanent
lookup failure in any item in the host list before it has found a match, Exim
treats it as a failure and the default behavior is as if the host does not
match the list. This may not always be what you want to happen. To change
Exim's behaviour, the special items &`+include_unknown`& or
&`+ignore_unknown`& may appear in the list (at top level &-- they are not
recognized in an indirected file).


2) IMHO with the above more verbose paragraph leading into the detail items,
it seems to make the explanations a lot clearer to me and so adjustment is not
needed. However, if you deem clarification to be needed, a second way to
achieve that would be to use basically the same configuration line with each
different setting and detail the result (using a combination of Phil's and
Regid's submission, both have enhanced readability). How does this look as a
general blueprint?

host_reject_connection = *.enemy.ex : *.notfriend.ex
DNS failure on reverse DNS or *.enemy.ex makes Exim behave as if it _does_not_
match the list, even if *.notfriend.ex would match (i.e. it aborts processing
the list due to the DNS failure).

host_reject_connection = +include_unknown : *.enemy.ex : *.notfiend.ex
DNS failure on *.enemy.ex *OR* any reverse DNS failure makes Exim behave as if
it _does_ match the list.

host_reject_connection = +ignore_unknown : *.enemy.ex : *.notfriend.ex
DNS failure on *.enemy.ex *OR* any reverse DNS failure makes Exim ignore those
entries and continues processing the rest of the host list.


--
Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email