Hi,
I've tried that and it was started without any error but we can't login
with with the maillog error as below:
May 26 15:40:17 mail2 perdition[462]: version=1.18, add_domain="",
authenticate_in=off, authenticate_timeout=1800, bind_address="",
capability="UIDL USER", client_server_specification=off,
config_file="/etc/perdition/perdition.conf", connection_limit=0,
connection_logging=off, connect_relog=300, debug=off,
domain_delimiter="@", explicit_domain="", group="nobody",
inetd_mode=off, listen_port="110", log_facility="mail",
log_passwd="never", login_disabled=off, lower_case="",
map_library="/usr/lib/libperditiondb_gdbm.so.0",
map_library_opt="ldap://ldap.abc.com:389/dc=.?uid,mailHost?sub?(mail=%45s)?!BINDNAME=cn=xxx%2cdc=.,X-BINDPW=yyy",
no_bind_banner=off, no_daemon=off, no_lookup=off, nodename="mail2",
ok_line="You are so in", outgoing_port="110", outgoing_server="",
pid_file="/var/run/perdition.pop3/perdition.pop3.pid", protocol="POP3",
server_resp_line=off, strip_domain="", timeout=1800, username="nobody",
username_from_database=off, query_key="", quiet=off, ssl_mode="",
ssl_ca_file="", ssl_ca_pat
Auth user="cktan@abc.com" passwd="XXXXXX" server="(null)" port="110"
status="failed: Could not determine server"
Regards
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'
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'
Regards