Andreas Metzler wrote:
>
..[snip]...
>
> We started on spec.txt to (with 11.5, the matches condition) but now
> that I am going to send the mail I realize that there are probably
> dozens of occurences. - I had not realized until now that
> downhill.at.eu.org matched
> domainlist local_domains = @:\N^downhill.a\N:localhost
>
> Perhaps a big fat note in chapter 8?
> | In this document the term "a regular expression matches" refers | to
> partial matching, i.e. the expression "oo" matches "foobar", it | is not
> necessary to match the whole string with something like | ".oo.*".
> cu andreas
--
I do not know if there needs to be a wording change as it is clear that
it is a regular expression match, and not a string/partial string type of
equality matching... But, just a few other examples of gotchas on matching
in general is how 'we/people' tend to think of a what we are matching vs.
what actually happens in the match. Take a multi-record LDAP lookup, by
default it is returned as "value1, value2, value3" which means that any
match can no longer be the entire string,
i.e lookup returns 'foobar, foobuz, foofur':
match{foobar, foobuz, foobar}{\N^foobar$\N}
to match just foobar, we need to make this {\Nfoorbar\N}, once you do that,
you now also match THISfoobarTO or .mail.foobar.org. So all in all,
doing any type of "string comparision" in exim succesfully means that
you must not only know how you want to match (eq/eqi/match) but how the
data you are comparing actually looks.
Anyone want to make a companion book for Philip?
--EAL--
