On Tue, Mar 05, 2013 at 11:16:18PM -0500, Wietse Venema wrote:
> Viktor Dukhovni:
> > Arguably, all lookup keys in tables should be in "external" (RFC-5322)
> > form. The suggested doubling of internal spaces is far less important
> > in practice that avoiding the loss of leading spaces.
>
> Which external form?
>
> - RFC 5321 and 5322 have different rules.
I was a bit sloppy in my wording, I guess 5321 is the right one
for processing envelope addresses, and perhaps 5322 for processing
header addresses (with canonical and generic rewrites for example).
This complicates recipient extension support, since to compute an
address sans extension we'd need to dequote, lose the extension
and then requote (using the right quoting style). This is not
trivial.
> - Worse, The mappings are not one-to-one. That is, there are multiple
> correct implementations for quote_821_local() and quote_822_local().
So long as we pick something consistent and documented, users can
likely adapt their table keys. In most cases the external form
and the internal form are identical, but the exceptions are a pain.
For this specific LDAP issue, if changing the query works that's
the fastest path to success, and we can adjust the ldap_table(5)
document with the latest best practice syntax.
The more things change, the less they stay the same. :-)
--
Viktor.
