>>I'd blame Outlook Express but unfortunately I have another working IMAP >>server for comparision ;) >> > > I disagree. You're well justified in calling it buggy and recommending > something else.
I already heard people complaining like "this IMAP stuff is much worse than the POP3 and is not working at all" and sending me links to the sites trying to prove that whole UNIX concept is quite bad idea... About the subject. What about following quick solution: First, lets forget preforking. Second, lets modify master process to maintain table of incoming connections and certain timeouts. Next imapd daemon will be launched from same originator (IP address) only after certain timeout has expired. Worst case: local network is accessing mailserver though NAT-box. The performance is reduced for all connections. Not so bad case: multiple connections from same client are little bit "spread" in time and therefore reducing the risk of fetching wrong results from the server. All other connections are working OK. Performance is reduced only for creating connections, overall performance is not affected. I haven't read listings yet, so I'll ask before hacking: is it worth of trying? heiki
