On 12/17/2009 02:27 AM, Yevheniy Demchenko wrote:
> On 12/17/2009 01:31 AM, Sam Varshavchik wrote:
>> Yevheniy Demchenko writes:
>>
>>>> It seems, that asterisks (and possibly other special symbols) in mail
>>>> addresses should be escaped before passing them to ldap.
>>> Proposed patch attached. Tested briefly.
>>> May need somewhat better memory handling.
>>
>> Thanks for the patch, but I see that according to RFC 2254, only "*",
>> "(", and ")" characters need escaping, furthermore, escaped
>> characters are hex-encoded. Also, I prefer a different style. Please
>> try to test the attached patch instead.
>>
> You are right about RFC, rest of them are only for DN. Not sure about
> hex-encoding, works well with just escaping and ldap authlib doesn't
> use hex-encoding, too. Will try your patch tomorrow, thanks.
>> Furthermore, regarding your other patch, unfortunately it forces the
>> usage of objectClass=CourierMailAccount, and would break all existing
>> installations that use a different schema.
> You are right again. Maybe, adding another parameter to ldapaliasrc
> worth considering. I personally am fond of user-configurable part of
> ldap filter, it gives the most flexibility. i.e. LDAP_USER_FILTER
> objectlass=courierMailAlias. It won't be difficult to implement that.
>
>
--
Ing. Yevheniy Demchenko
Senior Linux Administrator
UVT s.r.o.
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
