Re: Perdition1.18 problem with LDAP query

On Tue, May 25, 2010 at 04:05:25PM +0800, cktan wrote:
> Dear all perdition users and experts,
> 
> I used to have perdition-1.17 work for my mail servers to query for LDAP 
> for mailHost for POP3 and IMAP proxy and normally I will just add a flag 
> in /etc/sysconfig/perdition for POP3 and IMAP and everything will just 
> working fine. Today, I've just setup another mail server (to load 
> balance the mail scanning process and POP/IMAP login) and install with 
> perdition-1.18 (tried also with perdition-1.18rc1), the configuration is 
> the same with my old perdition but I've problem to start the service the 
> error message below. If I remove the (mail=%45s), the service will just 
> start perfect but off course I can't login because ldap will not return 
> anything without the filter. Is there any issue with the new perdition 
> for LDAP query? Looking forward your kind assistance in this matter.
> 
> Starting perdition services (POP3): /bin/bash: -c: line 0: syntax error 
> near unexpected token `('
> /bin/bash: -c: line 0: `ulimit -S -c 0 >/dev/null 2>&1 ; 
> /usr/sbin/perdition.pop3 -m 
> ldap://ldap.abc.com:389/dc=.?uid,mailHost?sub?(mail=%45s)?!BINDNAME=cn=xxx%2cdc=.,X-BINDPW=yyy'

Hi,

If you are executing perdition on the command line,
then you need to either use quotes or escape sequences
as the ldap query string contains characters that
have special meaning in the shell and I think
that is why you are seeing this problem.

Could you try the following?

/usr/sbin/perdition.pop3 -m 'ldap://ldap.abc.com:389/dc=.?uid,mailHost?sub?(mail=%45s)?!BINDNAME=cn=xxx%2cdc=.,X-BINDPW=yyy'
______________________________________________
Perdition-users mailing list
[email protected]
http://lists.vergenet.net/listinfo/perdition-users