Re: [exim] ldap returned data format

Phil Pennock wrote:
> Exim requires you to quote at the point of use, since different services
> require different quoting. So there are ${quote_foo:...} expansion
> operators for various foo. For Exim's own parsing, ${quote:...} is
> useful, for putting the string into double-quotes as needed.
>
>> ${lookup ldap{ldap:///ou=People,dc=spodhuis,dc=org?objectClass?sub?cn=Phil%20Pennock}}
> inetOrgPerson, posixAccount, top
>> ${quote:${lookup ldap{ldap:///ou=People,dc=spodhuis,dc=org?objectClass?sub?cn=Phil%20Pennock}}}
> "inetOrgPerson, posixAccount, top"

I don't see how that helps. If the lookup returns me

accountclass=2 contenthdrwarn="^((?i)date:\\s*), ^((?i)subject:\\s+).*((?i)snark)"

then quoting it further won't help me. Pulling out an attribute
of interest from the string returned by the lookup is simple, but
further pulling apart the multiple values of the attribute is the issue.
It seems to me that exim should, in reformatting a returned multiple-value
ldap attribute into a string, quote any contained commas (or whatever
character it uses for separating such multiple values) so as to
disambiguate them.

- Jeremy