On Sat, Dec 20, 2008 at 05:08:46PM +0800, Stephen Liu wrote:
--- Simon Horman <horms(a)verge.net.au> wrote:
# 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
Hi Simon,
Created certificate and key as advised. Thanks
Hi Stephen,
# /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