atom feed9 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Re: courier-imap ...
FromSent OnAttachments
Peter PeltonenJan 15, 2001 7:58 am 
Peter PeltonenJan 16, 2001 3:07 am 
Tomas FasthJan 16, 2001 3:23 am 
Tomas FasthJan 16, 2001 3:50 am 
Tomas FasthJan 16, 2001 4:53 am 
Sam VarshavchikJan 16, 2001 4:57 am 
Peter PeltonenJan 16, 2001 6:03 am 
Lindsay HaisleyJan 16, 2001 6:12 pm 
Daniel BiddleJan 16, 2001 6:58 pm 
Subject:Re: [courier-users] Re: courier-imap startup errors
From:Daniel Biddle (del@osian.net)
Date:Jan 16, 2001 6:58:39 pm
List:net.sourceforge.lists.courier-users

On Tue, 16 Jan 2001, Lindsay Haisley wrote:

Thus spake Sam Varshavchik on Tue, Jan 16, 2001 at 06:57:23AM CST

You do have something listening on the IMAP port. Find out what it is, and kill it.

I have configured everything imap/pop related out from my inetd.conf (I'm running RH6.2). For my knowledge I am not running any other imap-server than Courier's:

[root@kiila /root]# rpm -qa |grep imap

You probably still have inet listening on the IMAP port.

As root, run

lsof -i tcp:imap2

The name of the file which started the service is truncated to 9 characters, at least on my system.

Alternatively, use this (also as root):

fuser -v imap/tcp

which puts the command at the end and doesn't truncate it so much. fuser appears to be more common than lsof.

You can use ps, pstree etc. on the pid to find out more about the process.