Hi, does /usr/local/var/run/ exist? If not could you run mkdir /usr/local/var/run/ ?
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: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/28264fe9e31bRegards
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@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
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
______________________________________________ Perdition-users mailing list Perdition-users@vergenet.net http://lists.vergenet.net/listinfo/perdition-users
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
______________________________________________ Perdition-users mailing list Perdition-users@vergenet.net http://lists.vergenet.net/listinfo/perdition-users
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
______________________________________________ Perdition-users mailing list Perdition-users@vergenet.net http://lists.vergenet.net/listinfo/perdition-users
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
______________________________________________ Perdition-users mailing list Perdition-users@vergenet.net http://lists.vergenet.net/listinfo/perdition-users
--
This message has been scanned for viruses and
dangerous content by
MailScanner, and is
believed to be clean.