Hi, Sigmund.
You posted this run output from ps fax:
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
First, we need to find out where your binary files are installed. The
first path suggests /opt/bin, the next /opt/bincimap and the first
/opt/bincimap/bin.
It might be as simple as tcpserver not finding the bincimapd binary. You
installed this from the RPM, so the all Binc IMAP binaries are located
under
/opt/bincimap/bin
So with a few minor adjustments, we have this:
tcpserver -c 100 -u 0 -g 0 -l post -HDRP 0 143 /opt/bincimap/bin/bincimapd
--logtype=multilog --conf=/etc/opt/bincimap/bincimap.conf
/opt/bincimap/bin/bincimap-auth-checkpassword /bin/checkpassword
/opt/bincimap/bin/bincimap-uidpqd
multilog t n5 s1048576 /var/opt/log/bincimap
Now, does ps fax report "bincimap-uidpqd"? If it's the bundled binary, it
should be called "bincimap-uidpwd". Please check the run file
/etc/opt/bincimap/supervise/imap/run and make a few adjustments.
Finally, with only the 143 service, you will have SSL access through
STARTTLS. Not all clients support this, so if you want to run the 993
service too, you'll have to symlink:
ln -s /etc/opt/bincimap/supervise/imaps /service/imaps
Then, do a "ps fax" and check that there are two new supervise
processes, one for imaps and one for multilog.
When you try connecting to the service again now, check the
/var/opt/log/bincimap/current and /var/opt/log/bincimaps/current files for
changes. If no changes are detected, make sure multilog is running with
"ps fax". If it isn,t you need to start them:
svc -u /service/imap{,s}/log
Good luck!
Andy :-)
--
Andreas Aardal Hanssen | http://www.andreas.hanssen.name/gpg
Author of Binc IMAP | Nil desperandum
