Lawrence Greenfield wrote:
[snip...]
>
> I'm extremely confused how this could happen. I just tried it against
> my test server to be sure, and couldn't reproduce this.
>
> pop3d doesn't reuse processes, so after the first connection (with
> openssl s_client) exits, it doesn't respond to th
Lawrence Greenfield wrote:
> I've applied this patch against imapd.c. pop3d doesn't currently have
> this problem since it never services more than one connection.
Au Contraire, pop3d does indeed have the same problem. To duplicate it,
you connect to the pop3s port with 'openssl s_client', QUIT
Hajimu UMEMOTO wrote:
>
> nsayer> 2. imapd loses its "-s" argument the 2nd time around. I suspect this is a
> nsayer> setproctitle issue, but I haven't tried to prove it. If I do
> nsayer> 'openssl s_client -connect localhost:imaps', then '. logout' and then
> nsayer> very quickly 'telnet local
Date: Mon, 07 May 2001 11:06:18 -0700
From: Nick Sayer <[EMAIL PROTECTED]>
Cc: Hajimu UMEMOTO <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Lawrence Greenfield wrote:
> I've applied this patch against imapd.c. pop3d doesn't currently have
> this problem since it never services more
Date: Mon, 07 May 2001 04:04:44 +0900 (JST)
From: Hajimu UMEMOTO <[EMAIL PROTECTED]> (花宴)
[...]
How about this patch? It seems fixed the problem here. What I've
done is moving option parsing from service_main() to service_init().
I believe option parsing is good enough to b
> On Sat, 5 May 2001 09:21:55 -0700 (PDT)
> <[EMAIL PROTECTED]> said:
nsayer> 1. master crashes if the LMTP socket specified is in a nonexistent path.
nsayer> Yes, this is a misconfiguration, but master appears to work until it accepts
nsayer> the first imap/pop/whatever connection, then
> On Sat, 5 May 2001 09:21:55 -0700 (PDT)
> <[EMAIL PROTECTED]> said:
1. master crashes if the LMTP socket specified is in a nonexistent path.
Yes, this is a misconfiguration, but master appears to work until it accepts
the first imap/pop/whatever connection, then it crashes. The origi
I ran into a couple of issues with 2.0.13. I was able to work around them,
but I suspect they need to be addressed.
1. master crashes if the LMTP socket specified is in a nonexistent path.
Yes, this is a misconfiguration, but master appears to work until it accepts
the first imap/pop/whatever con
