25 May
2010
25 May
'10
8:05 a.m.
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
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
25 May
25 May
11:59 p.m.
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'
26 May
26 May
7:48 a.m.
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(a)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
<ldap://ldap.abc.com:389/dc=.?uid,mailHost?sub?%28mail=%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
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
8:13 a.m.
On Wed, May 26, 2010 at 03:48:21PM +0800, cktan wrote:
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(a)abc.com" passwd="XXXXXX" server="(null)"
port="110"
status="failed: Could not determine server"
Sorry for not noticing this the first time around but
I think that you are seeing the problem that is resolved by the following
patch:
http://hg.vergenet.net/perdition/perdition/rev/28264fe9e31b
# HG changeset patch
# User Simon Horman <horms(a)verge.net.au>
# Date 1263455327 -39600
# Node ID 28264fe9e31b7f34676260de9f26134399bd0372
# Parent c9763a7ea6adb242c7e837bc232f19ec6ebda6ca
LDAP: support schema-misc mailHost
This previously worked by chance when the get_server() internal API was
used, but broke when the ldap module was switched over to use get_server().
Tested-by: Dominique Marant <Dominique.Marant(a)univ-lille1.fr>
Signed-off-by: Simon Horman <horms(a)verge.net.au>
--- a/perdition/db/ldap/perditiondb_ldap.c Thu Dec 24 17:40:40 2009 +1100
+++ b/perdition/db/ldap/perditiondb_ldap.c Thu Jan 14 18:48:47 2010 +1100
@@ -516,12 +516,27 @@
ber = NULL;
/* Build the return string */
- if (returns[0])
- *user_str = returns[0];
- if (returns[1])
- *server_str = returns[1];
- if (returns[2])
- *port_str = returns[2];
+ if (returns[0] && !returns[1] && !returns[2]) {
+ user_server_port_t *usp = NULL;
+ if (user_server_port_str_assign(&usp, returns[0]) < 0) {
+ VANESSA_LOGGER_DEBUG("user_server_port_str_assign");
+ goto leave;
+ }
+ free(returns[0]);
+ *user_str = user_server_port_get_user(usp);
+ *server_str = user_server_port_get_server(usp);
+ *port_str = user_server_port_get_port(usp);
+ user_server_port_unassign(usp);
+ user_server_port_destroy(usp);
+ }
+ else {
+ if (returns[0])
+ *user_str = returns[0];
+ if (returns[1])
+ *server_str = returns[1];
+ if (returns[2])
+ *port_str = returns[2];
+ }
status = 0;
27 May
27 May
2:03 a.m.
Dear Simon,
I suppose this problem was noticed on perdition1.18rc1 and it was
resolved for the rc2, rc3 and so on? And how should I patch it in order
to work? Sorry because I'm not familiar with patching and hope to have
some assistance from you.
Sorry for not noticing this the first time around but
I think that you are seeing the problem that is resolved by the following
patch:
http://hg.vergenet.net/perdition/perdition/rev/28264fe9e31b
Regards
cktan wrote:
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(a)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
<ldap://ldap.abc.com:389/dc=.?uid,mailHost?sub?%28mail=%45s>)?!BINDNAME=cn=xxx%2cdc=.,X-BINDPW=yyy'
/
cktan wrote:
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
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
--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
believed to be clean.
--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
believed to be clean.
------------------------------------------------------------------------
______________________________________________
Perdition-users mailing list
Perdition-users(a)vergenet.net
http://lists.vergenet.net/listinfo/perdition-users
2:28 a.m.
On Thu, May 27, 2010 at 10:03:20AM +0800, cktan wrote:
Dear Simon,
I suppose this problem was noticed on perdition1.18rc1 and it was
resolved for the rc2, rc3 and so on? And how should I patch it in
order to work? Sorry because I'm not familiar with patching and hope
to have some assistance from you.
Hi,
I believe that the problem exists in perdition1.18 as well
as rc1, rc2, rc3, ... Basically it was introduced between 1.17 and
1.18 and the fix currently hasn't been included in a released version.
The patch command can be used to apply this change to perdition1.18.
e.g.
wget -O LDAP-support-schema-misc-mailHost.patch \
http://hg.vergenet.net/perdition/perdition/raw-rev/28264fe9e31b
wget http://www.vergenet.net/linux/perdition/download/1.18/perdition-1.18.tar.bz2
tar -jxf perdition-1.18.tar.bz2
cd perdition-1.18
patch -p1 < ../LDAP-support-schema-misc-mailHost.patch
31 May
31 May
3:12 a.m.
Hi,
Thank for your assistance and I tried to patched in and make install,
the error below show at the end. :-(
/bin/sh ../../../libtool --mode=install /usr/bin/install -c
libperditiondb_daemon.la '/usr/lib'
libtool: install: error: cannot install `libperditiondb_daemon.la' to a
directory not ending in /usr/local/lib
make[5]: *** [install-libLTLIBRARIES] Error 1
make[5]: Leaving directory `/root/perdition-1.18/perdition/db/daemon'
make[4]: *** [install-am] Error 2
make[4]: Leaving directory `/root/perdition-1.18/perdition/db/daemon'
make[3]: *** [install-recursive] Error 1
make[3]: Leaving directory `/root/perdition-1.18/perdition/db/daemon'
make[2]: *** [install-recursive] Error 1
make[2]: Leaving directory `/root/perdition-1.18/perdition/db'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/root/perdition-1.18/perdition'
make: *** [install-recursive] Error 1
/Hi,
I believe that the problem exists in perdition1.18 as well
as rc1, rc2, rc3, ... Basically it was introduced between 1.17 and
1.18 and the fix currently hasn't been included in a released version.
The patch command can be used to apply this change to perdition1.18.
e.g.
wget -O LDAP-support-schema-misc-mailHost.patch \
http://hg.vergenet.net/perdition/perdition/raw-rev/28264fe9e31b
wget http://www.vergenet.net/linux/perdition/download/1.18/perdition-1.18.tar.bz2
tar -jxf perdition-1.18.tar.bz2
cd perdition-1.18
patch -p1 < ../LDAP-support-schema-misc-mailHost.patch/
Regards
cktan wrote:
Dear Simon,
I suppose this problem was noticed on perdition1.18rc1 and it was
resolved for the rc2, rc3 and so on? And how should I patch it in
order to work? Sorry because I'm not familiar with patching and hope
to have some assistance from you.
Sorry for not noticing this the first time around but
I think that you are seeing the problem that is resolved by the following
patch:
http://hg.vergenet.net/perdition/perdition/rev/28264fe9e31b
Regards
cktan wrote:
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
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(a)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
<ldap://ldap.abc.com:389/dc=.?uid,mailHost?sub?%28mail=%45s>)?!BINDNAME=cn=xxx%2cdc=.,X-BINDPW=yyy'
/
cktan wrote:
--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
believed to be clean.
------------------------------------------------------------------------
______________________________________________
Perdition-users mailing list
Perdition-users(a)vergenet.net
http://lists.vergenet.net/listinfo/perdition-users
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
--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/>,
and is
believed to be clean.
--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/>,
and is
believed to be clean.
------------------------------------------------------------------------
______________________________________________
Perdition-users mailing list
Perdition-users(a)vergenet.net
http://lists.vergenet.net/listinfo/perdition-users
3:59 a.m.
Hi,
that is curious. Did you run ./configure more than once
with different arguments? If so, I am wondering if
the build system has got itself into an inconsistent
state somehow. Could you try again starting with a clean tree:
e.g.
cd ..
rm -r perdition-1.18
tar -jxf perdition-1.18.tar.bz2
cd perdition-1.18
patch -p1 < ../LDAP-support-schema-misc-mailHost.patch/
./configure --prefix /usr
make
make install
On Mon, May 31, 2010 at 11:12:15AM +0800, cktan wrote:
Hi,
Thank for your assistance and I tried to patched in and make
install, the error below show at the end. :-(
/bin/sh ../../../libtool --mode=install /usr/bin/install -c
libperditiondb_daemon.la '/usr/lib'
libtool: install: error: cannot install `libperditiondb_daemon.la'
to a directory not ending in /usr/local/lib
make[5]: *** [install-libLTLIBRARIES] Error 1
make[5]: Leaving directory `/root/perdition-1.18/perdition/db/daemon'
make[4]: *** [install-am] Error 2
make[4]: Leaving directory `/root/perdition-1.18/perdition/db/daemon'
make[3]: *** [install-recursive] Error 1
make[3]: Leaving directory `/root/perdition-1.18/perdition/db/daemon'
make[2]: *** [install-recursive] Error 1
make[2]: Leaving directory `/root/perdition-1.18/perdition/db'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/root/perdition-1.18/perdition'
make: *** [install-recursive] Error 1
/Hi,
I believe that the problem exists in perdition1.18 as well
as rc1, rc2, rc3, ... Basically it was introduced between 1.17 and
1.18 and the fix currently hasn't been included in a released version.
The patch command can be used to apply this change to perdition1.18.
e.g.
wget -O LDAP-support-schema-misc-mailHost.patch \
http://hg.vergenet.net/perdition/perdition/raw-rev/28264fe9e31b
wget http://www.vergenet.net/linux/perdition/download/1.18/perdition-1.18.tar.bz2
tar -jxf perdition-1.18.tar.bz2
cd perdition-1.18
patch -p1 < ../LDAP-support-schema-misc-mailHost.patch/
Regards
cktan wrote:
Dear Simon,
I suppose this problem was noticed on perdition1.18rc1 and it was
resolved for the rc2, rc3 and so on? And how should I patch it in
order to work? Sorry because I'm not familiar with patching and
hope to have some assistance from you.
Sorry for not noticing this the first time around but
I think that you are seeing the problem that is resolved by the following
patch:
http://hg.vergenet.net/perdition/perdition/rev/28264fe9e31b
Regards
cktan wrote:
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
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(a)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
<ldap://ldap.abc.com:389/dc=.?uid,mailHost?sub?%28mail=%45s>)?!BINDNAME=cn=xxx%2cdc=.,X-BINDPW=yyy'
/
cktan wrote:
--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
believed to be clean.
------------------------------------------------------------------------
______________________________________________
Perdition-users mailing list
Perdition-users(a)vergenet.net
http://lists.vergenet.net/listinfo/perdition-users 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
--
This message has been scanned for viruses and
dangerous content by *MailScanner*
<http://www.mailscanner.info/>, and is
believed to be clean.
--
This message has been scanned for viruses and
dangerous content by *MailScanner*
<http://www.mailscanner.info/>, and is
believed to be clean.
------------------------------------------------------------------------
______________________________________________
Perdition-users mailing list
Perdition-users(a)vergenet.net
http://lists.vergenet.net/listinfo/perdition-users ______________________________________________
Perdition-users mailing list
Perdition-users(a)vergenet.net
http://lists.vergenet.net/listinfo/perdition-users
5:29 a.m.
Hi,
Try redo back it was installed without error this time. However, error
below appear when I start perdition manual as suggested before and the
service just can't start. Any help?
May 31 13:26:37 mail2 perdition[11925]: version=1.18, add_domain="",
authenticate_in=off, authenticate_timeout=1800, bind_address="",
capability="UIDL USER", client_server_specification=off,
config_file="/usr/local/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/local/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="/usr/local/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=""
*May 31 13:26:37 mail2 perdition[11925]: Could not write pid file*
*May 31 13:26:37 mail2 perdition[11925]: Exiting on signal 1*
Regards
cktan wrote:
Hi,
Thank for your assistance and I tried to patched in and make install,
the error below show at the end. :-(
/bin/sh ../../../libtool --mode=install /usr/bin/install -c
libperditiondb_daemon.la '/usr/lib'
libtool: install: error: cannot install `libperditiondb_daemon.la' to
a directory not ending in /usr/local/lib
make[5]: *** [install-libLTLIBRARIES] Error 1
make[5]: Leaving directory `/root/perdition-1.18/perdition/db/daemon'
make[4]: *** [install-am] Error 2
make[4]: Leaving directory `/root/perdition-1.18/perdition/db/daemon'
make[3]: *** [install-recursive] Error 1
make[3]: Leaving directory `/root/perdition-1.18/perdition/db/daemon'
make[2]: *** [install-recursive] Error 1
make[2]: Leaving directory `/root/perdition-1.18/perdition/db'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/root/perdition-1.18/perdition'
make: *** [install-recursive] Error 1
/Hi,
I believe that the problem exists in perdition1.18 as well
as rc1, rc2, rc3, ... Basically it was introduced between 1.17 and
1.18 and the fix currently hasn't been included in a released version.
The patch command can be used to apply this change to perdition1.18.
e.g.
wget -O LDAP-support-schema-misc-mailHost.patch \
http://hg.vergenet.net/perdition/perdition/raw-rev/28264fe9e31b
wget http://www.vergenet.net/linux/perdition/download/1.18/perdition-1.18.tar.bz2
tar -jxf perdition-1.18.tar.bz2
cd perdition-1.18
patch -p1 < ../LDAP-support-schema-misc-mailHost.patch/
Regards
cktan wrote:
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Dear Simon,
I suppose this problem was noticed on perdition1.18rc1 and it was
resolved for the rc2, rc3 and so on? And how should I patch it in
order to work? Sorry because I'm not familiar with patching and hope
to have some assistance from you.
Sorry for not noticing this the first time around but
I think that you are seeing the problem that is resolved by the following
patch:
http://hg.vergenet.net/perdition/perdition/rev/28264fe9e31b
Regards
cktan wrote:
--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
believed to be clean.
------------------------------------------------------------------------
______________________________________________
Perdition-users mailing list
Perdition-users(a)vergenet.net
http://lists.vergenet.net/listinfo/perdition-users
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(a)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
<ldap://ldap.abc.com:389/dc=.?uid,mailHost?sub?%28mail=%45s>)?!BINDNAME=cn=xxx%2cdc=.,X-BINDPW=yyy'
/
cktan wrote:
--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/>,
and is
believed to be clean.
------------------------------------------------------------------------
______________________________________________
Perdition-users mailing list
Perdition-users(a)vergenet.net
http://lists.vergenet.net/listinfo/perdition-users
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
--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/>,
and is
believed to be clean.
--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/>,
and is
believed to be clean.
------------------------------------------------------------------------
______________________________________________
Perdition-users mailing list
Perdition-users(a)vergenet.net
http://lists.vergenet.net/listinfo/perdition-users
5:59 a.m.
Hi,
does /usr/local/var/run/ exist?
If not could you run mkdir /usr/local/var/run/ ?
On Mon, May 31, 2010 at 01:29:35PM +0800, cktan wrote:
Hi,
Try redo back it was installed without error this time. However,
error below appear when I start perdition manual as suggested before
and the service just can't start. Any help?
May 31 13:26:37 mail2 perdition[11925]: version=1.18, add_domain="",
authenticate_in=off, authenticate_timeout=1800, bind_address="",
capability="UIDL USER", client_server_specification=off,
config_file="/usr/local/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/local/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="/usr/local/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=""
*May 31 13:26:37 mail2 perdition[11925]: Could not write pid file*
*May 31 13:26:37 mail2 perdition[11925]: Exiting on signal 1*
Regards
cktan wrote:
Hi,
Thank for your assistance and I tried to patched in and make
install, the error below show at the end. :-(
/bin/sh ../../../libtool --mode=install /usr/bin/install -c
libperditiondb_daemon.la '/usr/lib'
libtool: install: error: cannot install `libperditiondb_daemon.la'
to a directory not ending in /usr/local/lib
make[5]: *** [install-libLTLIBRARIES] Error 1
make[5]: Leaving directory `/root/perdition-1.18/perdition/db/daemon'
make[4]: *** [install-am] Error 2
make[4]: Leaving directory `/root/perdition-1.18/perdition/db/daemon'
make[3]: *** [install-recursive] Error 1
make[3]: Leaving directory `/root/perdition-1.18/perdition/db/daemon'
make[2]: *** [install-recursive] Error 1
make[2]: Leaving directory `/root/perdition-1.18/perdition/db'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/root/perdition-1.18/perdition'
make: *** [install-recursive] Error 1
/Hi,
I believe that the problem exists in perdition1.18 as well
as rc1, rc2, rc3, ... Basically it was introduced between 1.17 and
1.18 and the fix currently hasn't been included in a released version.
The patch command can be used to apply this change to perdition1.18.
e.g.
wget -O LDAP-support-schema-misc-mailHost.patch \
http://hg.vergenet.net/perdition/perdition/raw-rev/28264fe9e31b
wget http://www.vergenet.net/linux/perdition/download/1.18/perdition-1.18.tar.bz2
tar -jxf perdition-1.18.tar.bz2
cd perdition-1.18
patch -p1 < ../LDAP-support-schema-misc-mailHost.patch/
Regards
cktan wrote:
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Dear Simon,
I suppose this problem was noticed on perdition1.18rc1 and it
was resolved for the rc2, rc3 and so on? And how should I patch
it in order to work? Sorry because I'm not familiar with
patching and hope to have some assistance from you.
Sorry for not noticing this the first time around but
I think that you are seeing the problem that is resolved by the following
patch:
http://hg.vergenet.net/perdition/perdition/rev/28264fe9e31b
Regards
cktan wrote:
--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
believed to be clean.
------------------------------------------------------------------------
______________________________________________
Perdition-users mailing list
Perdition-users(a)vergenet.net
http://lists.vergenet.net/listinfo/perdition-users 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(a)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
<ldap://ldap.abc.com:389/dc=.?uid,mailHost?sub?%28mail=%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
>
--
This message has been scanned for viruses and
dangerous content by *MailScanner*
<http://www.mailscanner.info/>, and is
believed to be clean.
--
This message has been scanned for viruses and
dangerous content by *MailScanner*
<http://www.mailscanner.info/>, and is
believed to be clean.
------------------------------------------------------------------------
______________________________________________
Perdition-users mailing list
Perdition-users(a)vergenet.net
http://lists.vergenet.net/listinfo/perdition-users
--
This message has been scanned for viruses and
dangerous content by *MailScanner*
<http://www.mailscanner.info/>, and is
believed to be clean.
------------------------------------------------------------------------
______________________________________________
Perdition-users mailing list
Perdition-users(a)vergenet.net
http://lists.vergenet.net/listinfo/perdition-users ______________________________________________
Perdition-users mailing list
Perdition-users(a)vergenet.net
http://lists.vergenet.net/listinfo/perdition-users
6:27 a.m.
Hi,
I've create the directory as suggested and it was started without the
error anymore. But still can't get the perdition work accordingly.
May 31 14:24:46 mail2 perdition[12777]: Auth:
202.73.11.224->202.73.10.20 user="cktan(a)abc.com" passwd="XXXXXX"
server="(null)" port="110" status="failed: Could not determine
server"
/Hi,
does /usr/local/var/run/ exist?
If not could you run mkdir /usr/local/var/run/ ?/
Regards
cktan wrote:
Hi,
Try redo back it was installed without error this time. However, error
below appear when I start perdition manual as suggested before and the
service just can't start. Any help?
May 31 13:26:37 mail2 perdition[11925]: version=1.18, add_domain="",
authenticate_in=off, authenticate_timeout=1800, bind_address="",
capability="UIDL USER", client_server_specification=off,
config_file="/usr/local/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/local/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="/usr/local/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=""
*May 31 13:26:37 mail2 perdition[11925]: Could not write pid file*
*May 31 13:26:37 mail2 perdition[11925]: Exiting on signal 1*
Regards
cktan wrote:
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Hi,
Thank for your assistance and I tried to patched in and make install,
the error below show at the end. :-(
/bin/sh ../../../libtool --mode=install /usr/bin/install -c
libperditiondb_daemon.la '/usr/lib'
libtool: install: error: cannot install `libperditiondb_daemon.la' to
a directory not ending in /usr/local/lib
make[5]: *** [install-libLTLIBRARIES] Error 1
make[5]: Leaving directory `/root/perdition-1.18/perdition/db/daemon'
make[4]: *** [install-am] Error 2
make[4]: Leaving directory `/root/perdition-1.18/perdition/db/daemon'
make[3]: *** [install-recursive] Error 1
make[3]: Leaving directory `/root/perdition-1.18/perdition/db/daemon'
make[2]: *** [install-recursive] Error 1
make[2]: Leaving directory `/root/perdition-1.18/perdition/db'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/root/perdition-1.18/perdition'
make: *** [install-recursive] Error 1
/Hi,
I believe that the problem exists in perdition1.18 as well
as rc1, rc2, rc3, ... Basically it was introduced between 1.17 and
1.18 and the fix currently hasn't been included in a released version.
The patch command can be used to apply this change to perdition1.18.
e.g.
wget -O LDAP-support-schema-misc-mailHost.patch \
http://hg.vergenet.net/perdition/perdition/raw-rev/28264fe9e31b
wget http://www.vergenet.net/linux/perdition/download/1.18/perdition-1.18.tar.bz2
tar -jxf perdition-1.18.tar.bz2
cd perdition-1.18
patch -p1 < ../LDAP-support-schema-misc-mailHost.patch/
Regards
cktan wrote:
--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
believed to be clean.
--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
believed to be clean.
------------------------------------------------------------------------
______________________________________________
Perdition-users mailing list
Perdition-users(a)vergenet.net
http://lists.vergenet.net/listinfo/perdition-users
Dear Simon,
I suppose this problem was noticed on perdition1.18rc1 and it was
resolved for the rc2, rc3 and so on? And how should I patch it in
order to work? Sorry because I'm not familiar with patching and hope
to have some assistance from you.
Sorry for not noticing this the first time around but
I think that you are seeing the problem that is resolved by the following
patch:
http://hg.vergenet.net/perdition/perdition/rev/28264fe9e31b
Regards
cktan wrote:
--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/>,
and is
believed to be clean.
------------------------------------------------------------------------
______________________________________________
Perdition-users mailing list
Perdition-users(a)vergenet.net
http://lists.vergenet.net/listinfo/perdition-users
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(a)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
<ldap://ldap.abc.com:389/dc=.?uid,mailHost?sub?%28mail=%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
>
>
--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/>,
and is
believed to be clean.
--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/>,
and is
believed to be clean.
------------------------------------------------------------------------
______________________________________________
Perdition-users mailing list
Perdition-users(a)vergenet.net
http://lists.vergenet.net/listinfo/perdition-users
--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/>,
and is
believed to be clean.
------------------------------------------------------------------------
______________________________________________
Perdition-users mailing list
Perdition-users(a)vergenet.net
http://lists.vergenet.net/listinfo/perdition-users
5100
days inactive
5106
days old
10 comments
2 participants
participants (2)
-
cktan -
Simon Horman