Hi Sigmund, > It seems to be running as ps -x reports: > > tcpserver -c 100 -u 0 -g 0 -l post -HDRP 0 143 /opt/bin/bincimapd --logtype=multilog > --conf=/etc/opt/bincimap/bincimap.conf /opt/bincimap/bincimap-auth-checkpassword > /bin/checkpassword /opt/bincimap/bin/bincimap-uidpqd > multilog t n5 s1048576 /var/opt/log/bincimap
As you're obviously running with daemontools, you're easier with: svstat /service/bincimap svstat /service/bincimap/log It tells you if the service is running, and how long (if it actually runs). > However, I am not able to connect to it from a MUA running on a workstation. That means..? A timeout error? > I have confirmed that the call gets through the firewall (its in the log). In the firewall log, or in the bincimap log? If you meant the firewall log, look into the bincimap log. > I suspect that the problem is related to ssl authentication Why do you think so? Maybe you're connecting to port 993..? Judging from your ps output, you have Binc IMAP running only on port 143, which gives the client the possibility to use STARTTLS to initiate the SSL session. If the client expects a SSL-only server on port 993, that's your problem. Set up the according service then. > Are there any tests I could perform to track down the fault? Please give us some more information: * Which version of Binc IMAP are you using? * How did you install it (RPM, Source RPM, manually from Source)? * Use netstat to see if Binc IMAP is actually listen to port 143 (and 993, if you think it should listen there, too) * In general, please be a little bit more specific, i.e. give details, examples, log messages... ps output has been a good start! Jonas
