18 Dec
2008
18 Dec
'08
8:54 a.m.
Hi folks,
After having tried >1 week I can't make perdition to start NOT even to
say to work. The packages, perdition and perdition-mysql, were
download on Debian repo;
Candidate: 1.17-7etch1
I don't know whether they are in problem?
On Internet I have download;
perdition_1.17-7etch1.diff.gz
What will be its use? To rectify a buggy package? If YES please
advise how to use it. TIA
B.R.
Stephen L
Send instant messages to your online friends http://uk.messenger.yahoo.com
18 Dec
18 Dec
11:16 p.m.
On Thu, Dec 18, 2008 at 04:54:44PM +0800, Stephen Liu wrote:
Hi folks,
After having tried >1 week I can't make perdition to start NOT even to
say to work. The packages, perdition and perdition-mysql, were
download on Debian repo;
Candidate: 1.17-7etch1
I don't know whether they are in problem?
On Internet I have download;
perdition_1.17-7etch1.diff.gz
What will be its use? To rectify a buggy package? If YES please
advise how to use it. TIA
Could tell us a little more information about the way in which
it is not working?
--
Simon Horman
VA Linux Systems Japan K.K., Sydney, Australia Satellite Office
H: www.vergenet.net/~horms/ W: www.valinux.co.jp/en
19 Dec
19 Dec
11:23 a.m.
--- Simon Horman <horms(a)verge.net.au> wrote:
On Thu, Dec 18, 2008 at 04:54:44PM +0800, Stephen Liu
wrote:
Hi Simon,
On running;
# /etc/init.d/perdition restart
Stopped /usr/sbin/perdition.pop3 (pid 2874).
No /usr/sbin/perdition.pop3s found running; none killed.
No /usr/sbin/perdition.imap4 found running; none killed.
No /usr/sbin/perdition.imaps found running; none killed.
Starting /usr/sbin/perdition.pop3...
Starting /usr/sbin/perdition.pop3s...
Starting /usr/sbin/perdition.imap4...
Starting /usr/sbin/perdition.imaps...
and
xen13:~# tail -f /var/log/syslog | grep perdition
Dec 19 11:14:15 xen13 perdition[3111]: Fatal error establishing SSL
context for listening
Dec 19 11:25:21 xen13 perdition[3129]: Error loading certificate chain
file "/etc/perdition/perdition.crt.pem"
Dec 19 11:25:21 xen13 perdition[3129]: Fatal error establishing SSL
context for listening
Dec 19 11:25:21 xen13 perdition[3132]: Error loading certificate chain
file "/etc/perdition/perdition.crt.pem"
Dec 19 11:25:21 xen13 perdition[3132]: Fatal error establishing SSL
context for listening
Dec 19 11:25:21 xen13 perdition[3135]: Error loading certificate chain
file "/etc/perdition/perdition.crt.pem"
Dec 19 11:25:21 xen13 perdition[3135]: Fatal error establishing SSL
context for listening
Dec 19 11:25:21 xen13 perdition[3138]: Error loading certificate chain
file "/etc/perdition/perdition.crt.pem"
Dec 19 11:25:21 xen13 perdition[3138]: Fatal error establishing SSL
context for listening
# find / -name perdition.crt.pem
No printout.
I can't find this file.
# cat /etc/default/perdition
RUN_PERDITION=yes
POP3=yes
POP3_FLAGS="--ssl_mode tls_listen"
POP3S=yes
POP3S_FLAGS="--ssl_mode ssl_listen -p 110"
IMAP4=yes
IMAP4_FLAGS="--ssl_mode tls_listen"
IMAP4S=yes
IMAP4S_FLAGS="--ssl_mode ssl_listen -p 143"
# cat /etc/perdition/perdition.conf
connection_logging
connection_limit 1000
map_library /usr/lib/libperditiondb_mysql.so.0
map_library_opt
"localhost:3306:dbPerdition:tblPerdition:perdition:mypasswd"
username_from_database
outgoing_server 127.0.0.1
B.R.
Stephen
Send instant messages to your online friends http://uk.messenger.yahoo.com
Hi folks,
After having tried >1 week I can't make perdition to start NOT even
to
say to work. The packages, perdition and
perdition-mysql, were
download on Debian repo;
Candidate: 1.17-7etch1
I don't know whether they are in problem?
On Internet I have download;
perdition_1.17-7etch1.diff.gz
What will be its use? To rectify a buggy package? If YES please
advise how to use it. TIA
Could tell us a little more information about the way in which
it is not working?
20 Dec
20 Dec
5:02 a.m.
On Fri, Dec 19, 2008 at 07:23:55PM +0800, Stephen Liu wrote:
--- Simon Horman <horms(a)verge.net.au> wrote:
You will need a certificate in order to listen for SSL or TSL connections.
A simple way to create a self-signed certificate is to use the following
command:
openssl req -new -x509 -nodes \
-out perdition.crt.pem -keyout perdition.key.pem -days 365
--
Simon Horman
VA Linux Systems Japan K.K., Sydney, Australia Satellite Office
H: www.vergenet.net/~horms/ W: www.valinux.co.jp/en
On Thu, Dec 18, 2008 at 04:54:44PM +0800, Stephen
Liu wrote:
Hi Simon,
On running;
# /etc/init.d/perdition restart
Stopped /usr/sbin/perdition.pop3 (pid 2874).
No /usr/sbin/perdition.pop3s found running; none killed.
No /usr/sbin/perdition.imap4 found running; none killed.
No /usr/sbin/perdition.imaps found running; none killed.
Starting /usr/sbin/perdition.pop3...
Starting /usr/sbin/perdition.pop3s...
Starting /usr/sbin/perdition.imap4...
Starting /usr/sbin/perdition.imaps...
and
xen13:~# tail -f /var/log/syslog | grep perdition
Dec 19 11:14:15 xen13 perdition[3111]: Fatal error establishing SSL
context for listening
Dec 19 11:25:21 xen13 perdition[3129]: Error loading certificate chain
file "/etc/perdition/perdition.crt.pem"
Dec 19 11:25:21 xen13 perdition[3129]: Fatal error establishing SSL
context for listening
Dec 19 11:25:21 xen13 perdition[3132]: Error loading certificate chain
file "/etc/perdition/perdition.crt.pem"
Dec 19 11:25:21 xen13 perdition[3132]: Fatal error establishing SSL
context for listening
Dec 19 11:25:21 xen13 perdition[3135]: Error loading certificate chain
file "/etc/perdition/perdition.crt.pem"
Dec 19 11:25:21 xen13 perdition[3135]: Fatal error establishing SSL
context for listening
Dec 19 11:25:21 xen13 perdition[3138]: Error loading certificate chain
file "/etc/perdition/perdition.crt.pem"
Dec 19 11:25:21 xen13 perdition[3138]: Fatal error establishing SSL
context for listening
# find / -name perdition.crt.pem
No printout.
I can't find this file. Hi folks,
After having tried >1 week I can't make perdition to start NOT even
to
say to work. The packages, perdition and
perdition-mysql, were
download on Debian repo;
Candidate: 1.17-7etch1
I don't know whether they are in problem?
On Internet I have download;
perdition_1.17-7etch1.diff.gz
What will be its use? To rectify a buggy package? If YES please
advise how to use it. TIA
Could tell us a little more information about the way in which
it is not working?
9:08 a.m.
--- Simon Horman <horms(a)verge.net.au> wrote:
Hi Simon,
Created certificate and key as advised. Thanks
# /etc/init.d/perdition restart
Stopped /usr/sbin/perdition.pop3 (pid 3111).
Stopped /usr/sbin/perdition.pop3s (pid 3114).
No /usr/sbin/perdition.imap4 found running; none killed.
No /usr/sbin/perdition.imaps found running; none killed.
Starting /usr/sbin/perdition.pop3...
Starting /usr/sbin/perdition.pop3s...
Starting /usr/sbin/perdition.imap4...
Starting /usr/sbin/perdition.imaps...
# tail -f /var/log/syslog | grep perdition
Dec 20 08:59:09 xen13 perdition[3111]: Exiting on signal 15
Dec 20 08:59:09 xen13 perdition[3114]: Exiting on signal 15
Dec 20 08:59:09 xen13 perdition[3176]: version=1.17, add_domain="",
authenticate_in=off, bind_address="", capability="UIDL USER",
client_server_specification=off,
config_file="/etc/perdition/perdition.conf", connection_limit=1000,
connection_logging=on, connect_relog=300, debug=off,
domain_delimiter="@", explicit_domain="", group="nogroup",
inetd_mode=off, listen_port="995", log_facility="mail",
login_disabled=off, lower_case="",
map_library="/usr/lib/libperditiondb_mysql.so.0",
map_library_opt="localhost:3306:dbPerdition:tblPerdition:perdition:mypasswd",
no_bind_banner=off, no_daemon=off, no_lookup=off,
nodename="xen13.satimis.com", ok_line="You are so in",
outgoing_port="110", outgoing_server="127.0.0.1",
pid_file="/var/run/perdition.pop3s/perdition.pop3s.pid",
protocol="POP3S", server_resp_line=off, strip_domain="",
timeout=1800,
username="nobody", username_from_database=on, query_key="",
quiet=off,
ssl_mode="ssl_listen", ssl_ca_file="",
ssl_ca_path="/etc/perdition/perdition.ca/", ssl_ca_accept_self_sign
Dec 20 08:59:09 xen13 perdition[3173]: version=1.17, add_domain="",
authenticate_in=off, bind_address="", capability="UIDL USER STLS",
client_server_specification=off,
config_file="/etc/perdition/perdition.conf", connection_limit=1000,
connection_logging=on, connect_relog=300, debug=off,
domain_delimiter="@", explicit_domain="", group="nogroup",
inetd_mode=off, listen_port="110", log_facility="mail",
login_disabled=off, lower_case="",
map_library="/usr/lib/libperditiondb_mysql.so.0",
map_library_opt="localhost:3306:dbPerdition:tblPerdition:perdition:mypasswd",
no_bind_banner=off, no_daemon=off, no_lookup=off,
nodename="xen13.satimis.com", ok_line="You are so in",
outgoing_port="110", outgoing_server="127.0.0.1",
pid_file="/var/run/perdition.pop3/perdition.pop3.pid",
protocol="POP3",
server_resp_line=off, strip_domain="", timeout=1800,
username="nobody",
username_from_database=on, query_key="", quiet=off,
ssl_mode="tls_listen", ssl_ca_file="",
ssl_ca_path="/etc/perdition/perdition.ca/", ssl_ca_accept_self_s
Dec 20 08:59:09 xen13 perdition[3182]: version=1.17, add_domain="",
authenticate_in=off, bind_address="", capability="IMAP4 IMAP4REV1",
client_server_specification=off,
config_file="/etc/perdition/perdition.conf", connection_limit=1000,
connection_logging=on, connect_relog=300, debug=off,
domain_delimiter="@", explicit_domain="", group="nogroup",
inetd_mode=off, listen_port="993", log_facility="mail",
login_disabled=off, lower_case="",
map_library="/usr/lib/libperditiondb_mysql.so.0",
map_library_opt="localhost:3306:dbPerdition:tblPerdition:perdition:mypasswd",
no_bind_banner=off, no_daemon=off, no_lookup=off,
nodename="xen13.satimis.com", ok_line="You are so in",
outgoing_port="143", outgoing_server="127.0.0.1",
pid_file="/var/run/perdition.imaps/perdition.imaps.pid",
protocol="IMAP4S", server_resp_line=off, strip_domain="",
timeout=1800,
username="nobody", username_from_database=on, query_key="",
quiet=off,
ssl_mode="ssl_listen", ssl_ca_file="",
ssl_ca_path="/etc/perdition/perdition.ca/", ssl_ca_accept_sel
Dec 20 08:59:09 xen13 perdition[3182]: Fatal error listening for
connections. Exiting.
Dec 20 08:59:09 xen13 perdition[3179]: version=1.17, add_domain="",
authenticate_in=off, bind_address="", capability="IMAP4 IMAP4REV1
STARTTLS", client_server_specification=off,
config_file="/etc/perdition/perdition.conf", connection_limit=1000,
connection_logging=on, connect_relog=300, debug=off,
domain_delimiter="@", explicit_domain="", group="nogroup",
inetd_mode=off, listen_port="143", log_facility="mail",
login_disabled=off, lower_case="",
map_library="/usr/lib/libperditiondb_mysql.so.0",
map_library_opt="localhost:3306:dbPerdition:tblPerdition:perdition:mypasswd",
no_bind_banner=off, no_daemon=off, no_lookup=off,
nodename="xen13.satimis.com", ok_line="You are so in",
outgoing_port="143", outgoing_server="127.0.0.1",
pid_file="/var/run/perdition.imap4/perdition.imap4.pid",
protocol="IMAP4", server_resp_line=off, strip_domain="",
timeout=1800,
username="nobody", username_from_database=on, query_key="",
quiet=off,
ssl_mode="tls_listen", ssl_ca_file="",
ssl_ca_path="/etc/perdition/perdition.ca/", ssl_ca_ac
Dec 20 08:59:09 xen13 perdition[3179]: Fatal error listening for
connections. Exiting.
It seems still fail.
I haven't entered data on tblPerdition yet. It is an empty table.
Neither there is a mail client connected to the server. Does it
matter?
B.R.
Stephen L
Send instant messages to your online friends http://uk.messenger.yahoo.com
# find / -name
perdition.crt.pem
No printout.
I can't find this file.
You will need a certificate in order to listen for SSL or TSL
connections.
A simple way to create a self-signed certificate is to use the
following
command:
openssl req -new -x509 -nodes \
-out perdition.crt.pem -keyout perdition.key.pem -days 365
21 Dec
21 Dec
12:08 a.m.
On Sat, Dec 20, 2008 at 05:08:46PM +0800, Stephen Liu wrote:
--- Simon Horman <horms(a)verge.net.au> wrote:
Hi Simon,
Created certificate and key as advised. Thanks
Hi Stephen,
# find /
-name perdition.crt.pem
No printout.
I can't find this file.
You will need a certificate in order to listen for SSL or TSL
connections.
A simple way to create a self-signed certificate is to use the
following
command:
openssl req -new -x509 -nodes \
-out perdition.crt.pem -keyout perdition.key.pem -days 365 # /etc/init.d/perdition restart
Stopped /usr/sbin/perdition.pop3 (pid 3111).
Stopped /usr/sbin/perdition.pop3s (pid 3114).
No /usr/sbin/perdition.imap4 found running; none killed.
No /usr/sbin/perdition.imaps found running; none killed.
Starting /usr/sbin/perdition.pop3...
Starting /usr/sbin/perdition.pop3s...
Starting /usr/sbin/perdition.imap4...
Starting /usr/sbin/perdition.imaps...
[snip]
Dec 20 08:59:09 xen13 perdition[3179]: Fatal error
listening for
connections. Exiting.
This error means that perdition is unable to bind to the port you
have requested. In this case port 993 for imaps and port 143 for imap4s.
This could mean that you don't have permision to bind to the ports -
you need to be root to bind to ports < 1024. But this seems unlikely
as can successfully start the pop3 and pop3s daemons which also
bind to ports < 1024.
So it seems that the likely problem is that you already have some other
daemon bound to ports 993 and 143. Most likely some other IMAP daemon.
You should be able to verify this by looking at the output of:
netstat --inet -ln
Look for tcp lines that include :143 and :993
And if you have fuser installed, you should be able to determine which
daemon it is by running the following commands as root:
fuser -v -n tcp 993; fuser -v -n tcp 143
You can also search for the process in question using lsof.
--
Simon Horman
VA Linux Systems Japan K.K., Sydney, Australia Satellite Office
H: www.vergenet.net/~horms/ W: www.valinux.co.jp/en
9:08 a.m.
--- Simon Horman <horms(a)verge.net.au> wrote:
- snip -
Hi Simon,
I have "psmisc" installed.
# apt-cache policy psmisc
psmisc:
Installed: 22.3-1
Candidate: 22.3-1
Version table:
*** 22.3-1 0
500 http://ftp.au.debian.org etch/main Packages
100 /var/lib/dpkg/status
# which fuser
/bin/fuser
# fuser -v -n tcp 993
# fuser -v -n tcp 143
both without printout
xen13:~# netstat --inet -ln | grep 143
xen13:~# netstat --inet -ln | grep 993
both also without printout.
They are NOT taken. Both ports have been forwarded to the local IP of
the routing server under testing.
# telnet localhost 143
Trying 127.0.0.1...
Connected to localhost.localdomain.
Escape character is '^]'.
* OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE
THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA AUTH=CRAM-MD5
AUTH=CRAM-SHA1 IDLE ACL ACL2=UNION STARTTLS] Courier-IMAP ready.
Copyright 1998-2005 Double Precision, Inc. See COPYING for distribution
information.
ehlo localhost
ehlo NO Error in IMAP command received by server.
# telnet localhost 993
Trying 127.0.0.1...
Connected to localhost.localdomain.
Escape character is '^]'.
ehlo localhost
Connection closed by foreign host.
B.R.
Stephen L
Send instant messages to your online friends http://uk.messenger.yahoo.com
#
/etc/init.d/perdition restart
Stopped /usr/sbin/perdition.pop3 (pid 3111).
Stopped /usr/sbin/perdition.pop3s (pid 3114).
No /usr/sbin/perdition.imap4 found running; none killed.
No /usr/sbin/perdition.imaps found running; none killed.
Starting /usr/sbin/perdition.pop3...
Starting /usr/sbin/perdition.pop3s...
Starting /usr/sbin/perdition.imap4...
Starting /usr/sbin/perdition.imaps...
[snip]
Dec 20 08:59:09 xen13 perdition[3179]: Fatal
error listening for
connections. Exiting.
This error means that perdition is unable to bind to the port you
have requested. In this case port 993 for imaps and port 143 for
imap4s.
This could mean that you don't have permision to bind to the ports -
you need to be root to bind to ports < 1024. But this seems unlikely
as can successfully start the pop3 and pop3s daemons which also
bind to ports < 1024.
So it seems that the likely problem is that you already have some
other
daemon bound to ports 993 and 143. Most likely some other IMAP
daemon.
You should be able to verify this by looking at the output of:
netstat --inet -ln
Look for tcp lines that include :143 and :993
And if you have fuser installed, you should be able to determine
which
daemon it is by running the following commands as root:
fuser -v -n tcp 993; fuser -v -n tcp 143
You can also search for the process in question using lsof.
22 Dec
22 Dec
3:35 a.m.
On Sun, Dec 21, 2008 at 05:08:24PM +0800, Stephen Liu wrote:
Hi Simon,
I have "psmisc" installed.
# apt-cache policy psmisc
psmisc:
Installed: 22.3-1
Candidate: 22.3-1
Version table:
*** 22.3-1 0
500 http://ftp.au.debian.org etch/main Packages
100 /var/lib/dpkg/status
# which fuser
/bin/fuser
# fuser -v -n tcp 993
# fuser -v -n tcp 143
both without printout
xen13:~# netstat --inet -ln | grep 143
xen13:~# netstat --inet -ln | grep 993
both also without printout.
They are NOT taken. Both ports have been forwarded to the local IP of
the routing server under testing.
Hi Stephen,
the forwarding sounds like it might be the cause of the problem,
though I must confess that I am not sure. How is the forwarding
being done?
--
Simon Horman
VA Linux Systems Japan K.K., Sydney, Australia Satellite Office
H: www.vergenet.net/~horms/ W: www.valinux.co.jp/en
3:55 a.m.
--- Simon Horman <horms(a)verge.net.au> wrote:
On Sun, Dec 21, 2008 at 05:08:24PM +0800, Stephen Liu
wrote:
Hi Simon,
This is a Xen Box, a Virtual Machine
Host - Debien Etch workstation, local_IP 192.168.0.110
Guest1 - routing mail server, local_IP 192.168.0.213
Guest2 - mail server, local_IP 192.168.0.208, domain1
Guest3 - mail server, local_IP 192.168.0.209, domain2
Guest4 - mail server, local_IP 192.168.0.210, domain3
On router all ports are forwarded to 192.168.0.213, the routing mail
server.
Example;
Service Ports Server IP
143 192.168.0.213
993 192.168.0.213
etc.
Mail clients connected to local network can find their own mail server
sending/receiving mails without problem. All incoming mails are
pointing to the same public IP and delivered to their own mail servers
by the routing mail server according to domains.
B.R.
Stephen L
Send instant messages to your online friends http://uk.messenger.yahoo.com
Hi Simon,
I have "psmisc" installed.
# apt-cache policy psmisc
psmisc:
Installed: 22.3-1
Candidate: 22.3-1
Version table:
*** 22.3-1 0
500 http://ftp.au.debian.org etch/main Packages
100 /var/lib/dpkg/status
# which fuser
/bin/fuser
# fuser -v -n tcp 993
# fuser -v -n tcp 143
both without printout
xen13:~# netstat --inet -ln | grep 143
xen13:~# netstat --inet -ln | grep 993
both also without printout.
They are NOT taken. Both ports have been forwarded to the local IP
of
the routing server under testing.
Hi Stephen,
the forwarding sounds like it might be the cause of the problem,
though I must confess that I am not sure. How is the forwarding
being done?
5623
days inactive
5627
days old
8 comments
2 participants
participants (2)
-
Simon Horman -
Stephen Liu