Re: Bug in bincimap-up it seems

On Sun, 22 May 2005, Peter Stuge wrote:
>after throwing NOOPs at Binc for a while I just let the telnet sit
>there, and when it timed out it looks like so:
>a noop
>a OK NOOP completed
>a noop
>a OK NOOP completed
>* BYE Timeout after 1860 seconds of inactivity.
>a NO LOGIN failed: Login failed. Either your user name or your
>password was wrong. Please try again, and if the problem persists,
>please contact your system administrator.
>* BYE Timeout after 60 seconds of inactivity.
>Connection closed by foreign host.
>This isn't right. Why is bincimap-up still running at all? Shouldn't
>it exec() bincimapd?

Hi, Peter. No, bincimap-up can't just exec() bincimapd. One reason for 
this is that it has to use checkpasswd, which may or may not fail (exit). 
So bincimap-up forks and execs checkpasswd, and checkpasswd either exits 
or exec's bincimapd. The other reason is that bincimap-up has all the SSL 
logics in it. If it were to exec() bincimapd, you would suddenly have a 
plain-text connection.

Although, what you have observed here is very strange. Is it reproducable?

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."