Hello, the spec says that commas/double commas are used as delimiter...
But given the following LDAP entry ,------------------------ |# heiko, schlittermann.de |dn: uid=heiko,dc=schlittermann,dc=de |.. |x-MailPrimaryAddress: [email protected] |x-MailAlternateAddress: [email protected] |x-MailAlternateAddress: [email protected] |description: a |description: b |... `--------------------- As expected I get the multiple values separated by commas: $ exim -be '${lookup ldapm{ldap:///dc=schlittermann,dc=de?description?sub?uid=heiko}}' ,----- |a,b `---- But I did not expect the following: $ exim -be '${lookup ldapm{ldap:///dc=schlittermann,dc=de?mail?sub?uid=heiko}}' ,------ |[email protected][email protected],[email protected] `----- ^^ ^ x-MailPrimaryAddress and x-MailAlternateAddress are both defined as SUP mail. So these attributes *are* 'mail' and I expected to see their values, but I expected to see the comma separator between all of them. The corresponding LDAP search $ root@jumper:~# ldapsearch -LLL -x uid=heiko mail ,------ |dn: uid=heiko,dc=schlittermann,dc=de |x-MailPrimaryAddress: [email protected] |x-MailAlternateAddress: [email protected] |x-MailAlternateAddress: [email protected] `------- Bug or feature? I'd guess "bug", isn't it? Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de ---------------------------- internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - gnupg encrypted messages are welcome --------------- key ID: 7CBF764A - gnupg fingerprint: 9288 F17D BBF9 9625 5ABC 285C 26A9 687E 7CBF 764A - (gnupg fingerprint: 3061 CFBF 2D88 F034 E8D2 7E92 EE4E AC98 48D0 359B)-
signature.asc
Description: Digital signature
-- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
