RE: [binc] RE: atomicity.h - OS X BincIMAP Compile errors

2004-01-02 Thread volve 
 From: Ralf Weber [mailto:[EMAIL PROTECTED]
 Sent: Friday, January 02, 2004 02:07
 Yes. Do:
   cd /service
   svc -u imaps
 and you should see a tcpserver process listening to port 143 and then
 be able to connect. Bincimap is configured not to autostart when you
 link it into service. If you want to change this simply remove all the
 down files in imaps and it's subdirectories (Don't forget down under
 the log directory or otherwise binc won't start).

Thanks Ralf - that worked perfectly. Everything is now running smoothly
(especially as I installed vpopmail and used vchkpw instead of DJB's
checkpassword).

Thanks for all your (and everyone else's) help! :)

Regards,
-VolVE

RE: [binc] RE: atomicity.h - OS X BincIMAP Compile errors

2003-12-31 Thread volve 
 From: AthlonRob [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, December 31, 2003 12:38
 
 Just to be sure, /etc/opt/bincimap/service/imap and imaps *do* exist,
 right?  That seems, to me, to be an odd place for the files to end up,
 but whatdoIknow?

Yup, they exist - it's the location that lifewithbincimap.org mentions
too...

 AFAIK, you shouldn't see bincimap in ps unless somebody has connected to
 the server and the server is active.  Daemontools is the thing to listen
 on the port, it controls bincimap.  Unless, of course, Daemontools is
 just totally different from inetd and xinetd.

Hmm, ok. :)

 Now, what exactly happens when you telnet to your port 143?  Do you get
 any output at all?  What do the daemontools logfiles show?  I do assume
 they log, right?

Connection refused - basically the port isn't listening :( I can't find any
daemontools logs either... wheee

Thanks,
-VolVE

RE: [binc] RE: atomicity.h - OS X BincIMAP Compile errors

2003-12-31 Thread volve 
 From: Peter Stuge [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, December 31, 2003 14:43

 There should be a tcpserver process, listening to port 143.

Nope :( I only have qmail-pop3d and qmail-smtpd tcpserver processes running.

 Please check how /service/imap/log/run is set up and that logging works.
 Also double check /service/imap/run to verify that tcpserver is available
 where the run script expects it to be.

/service/imap/log/run:
-
#!/bin/sh

# $Id: run.in,v 1.1 2003/08/23 12:53:25 andreaha Exp $
# daemontools supervise run-file for Binc IMAP Service.

exec 21

exec /usr/local/bin/multilog t n5 s1048576 /var/opt/log/bincimap
-

/usr/local/bin/multilog is definitely the right path. The
/var/opt/log/bincimap directory is empty though, but that maybe just because
there's no tcpserver running so there's been nothing to log (?)

/service/imap/run:
-
#!/bin/sh
# $Id: run.in,v 1.1.1.1 2003/08/18 18:06:05 andreaha Exp $
# daemontools supervise run-file for Binc IMAP Service.

exec 21

exec/usr/local/bin/tcpserver -c 100 -u 0 -g 0   \
-l ${hostname} -HDRP\
0 143   \
/opt/bincimap/bin/bincimap-up   \
--logtype=multilog  \
--conf=/etc/opt/bincimap/bincimap.conf --   \
/bin/checkpassword  \
/opt/bincimap/bin/bincimapd
-

/usr/local/bin/tcpserver is also definitely the right path.

I even checked the /etc/opt/bincimap/bincimap.conf file and made sure that
Log { type = multilog matched the above --logtype. Also I set
Authentication { allow plain auth in non ssl = yes just in case that maybe
had been causing problems.

I have been having some issues with DJB's /bin/checkpassword that I'm still
trying to resolve (it always gives authorization failed) but that
shouldn't stop BincIMAP's tcpserver from running should it? :-/

Thanks,
-VolVE