Thomas Winterstein via Exim-users <exim-users@???> (Do 21 Nov 2019 21:42:04 CST):
> its solved.
>
> Exim's configuration syntax can't handle spaces. The crypteq line needs to
> be completely without spaces to make it work.
The Exim's configuration handles spaces, but probably in another way
you'd expect :)
{crypteq{$auth2}{${lookup ldap{ldap://mailvz.rz.uni-augsburg.de/ou=users,dc=uaux,dc=de?userPassword?sub?(&(objectClass=inetorgperson)(uid=${quote_ldap:$auth1}))} } } } \
{crypteq{$auth2}{${lookup ldap{…} } } }
| | `-----LDAP-------'
`----' `-----string2------'
string1
So, you asked Exim for the extra space there :) But yes, this is
probably not what most users expect.
BTW, why don't you use the ldapauth conditional? It shouldn't be Exim's
job to care about the format the password is stored in, when you have
the passwords in the userPassword field.
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: F69376CE -
! key id 7CBF764A and 972EAC9F are revoked since 2015-01 ------------ -
