Gordon Messmer schrieb:
Gregor Friedrich wrote:
Gordon Messmer schrieb:
Gregor Friedrich wrote:
here are the config files:
----------
imapd
...
IMAPDSTART=NO
Really? Then what's running on port 143?
OK! but it's not used in the init script, i set it to YES and restart
imapd and imapd-ssl but no change!
That doesn't really answer the question... If IMAPDSTART was set to
"NO", and you were able to log in to port 143, then something else must
be running there.
Since you're using Linux, you should be able to use "netstat -tlnp" to
figure out what's listening on port 143. You'll need to shut that down
and remove it from the system.
Belive me it's courier!:
***
telnet localhost 143 :
* OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE
THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE ACL ACL2=UNION
XMAGICTRASH] Courier-IMAP ready. Copyright 1998-2005 Double Precision,
Inc. See COPYING for distribution information."
ps aux
lot of:
....
/usr/local/courier/bin/couriertls -server ...
/usr/local/courier/bin/imapd Maildir
...
***
THE IMAPDSTART=NO variable in it's not used in my init script to start
courier-imapd. There is no another imap server installed.
Thank's Gregor
7 messages in net.sourceforge.lists.courier-usersRe: [courier-users] mapd-ssl START TL...
