Hi, I'm just back to trying to solve this problem. I don't have a
'checkpassword' but I do have a 'checkpw' command, and the man page says
that it reads ~/Maildir/.password which is what I would expect.

I created the link /usr/local/bin/checkpassword to point to
/usr/bin/checkpw but I get the same error when using the openssl test.
(The error is, "* BYE The server died unexpectedly. Please contact your
system administrator for more information.".)

I checked /var/log/bincimaps/current and it contains the following
lines:

=== begin ======
2004-04-06_09:50:03.42474 tcpsvd: info: status 1/100
2004-04-06_09:50:03.42522 tcpsvd: info: pid 21418 from 127.0.0.1
2004-04-06_09:50:03.42589 tcpsvd: info: concurrency 21418 127.0.0.1 1/14
2004-04-06_09:50:03.42605 tcpsvd: info: start 21418 0:127.0.0.1
::127.0.0.1:2009
2004-04-06_09:50:03.78410 21418 0 [EMAIL PROTECTED]:] connection from
127.0.0.1
^M
2004-04-06_09:50:10.86799 21418 1 [EMAIL PROTECTED]:] <mike>
authentication fai
led: server  returned 111 (internal error)^M
2004-04-06_09:50:10.86879 21418 2 [EMAIL PROTECTED]:] shutting down -
read:21 b
ytes, wrote:255 bytes.^M
2004-04-06_09:50:10.87384 tcpsvd: info: end 21418 exit 0
2004-04-06_09:50:10.87418 tcpsvd: info: status 0/100
=== end ======

So it does appear to be related to the checkpassword/checkpw program.
I'm a bit confused about how the checkpw program is supposed to work...
the man page says that it reads its input from descriptor 3. How can I
force the input onto descriptor 3? (A bash construct like '1>&3'
predictably fails with '3: Bad file descriptor'.) I'm not familiar
enough with the subtleties of Unix IPC to know whether I can
programmatically force input onto a given descriptor in a subprocess...
which means that I'm unable to test whether checkpw even works as
advertised. I'm a novice linux user so please forgive my limited
problem-solving abilities here. What should I do next?

Mike.

-----Original Message-----
From: Andreas Aardal Hanssen [mailto:[EMAIL PROTECTED] 
Sent: March 22, 2004 10:14 AM
To: Binc IMAP General
Subject: Re: [binc] 'The server died unexpectedly'

On Mon, 22 Mar 2004, Mike Iles wrote:
>I'm having some trouble getting Binc to work. I'm running a Debian box
>with Binc IMAP 1.2.3.  I was initially getting authorization failures
>until I found this note [1] that said that I should put a password in
>~/Maildir/.password. When I do that, the server crashes.

Most likely, this is caused by a problem with the setup of the server;
for
instance, checkpassword may be dying for some reason or maybe
checkpassword is missing / not found.

Binc IMAP should not just die like that, so I'll note it as a bug, but
I'm
sure we can get it all working for you.

Andy :-)

--
Andreas Aardal Hanssen   | http://www.andreas.hanssen.name/gpg
Author of Binc IMAP      |  "It is better not to do something
http://www.bincimap.org/ |        than to do it poorly."


Reply via email to