Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com From: Christian Weinberger Subject: uw-imap & Cygwin secrets revealed, at least a bit! Date: Mon, 29 Nov 2004 06:38:58 +0000 (UTC) Lines: 30 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet AT sea DOT gmane DOT org X-Gmane-NNTP-Posting-Host: main.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 62.180.31.25 (Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)) X-IsSubscribed: yes The initial problem was: - uw-imap on cygwin ran well with Outlook Express - but hung upon connection when using Outlook 2003 In the end I made it to get it work with the following workaround: In inetd.conf, I don´t start the daemon directly, but use the following wrapper script. #!/bin/sh tee NUL | /usr/sbin/imapd This slows down communication a bit, but I can connect and had no more hangs up till now. So the original problem seems to be timing specific. My guesses are: - the cygwin port of uw-imap may have a problem here. I couldn´t find any similar error reports for any other platform uw-imap is running on. - cygwin causes the problem itself - inetd is out of the line since I also tested with xinetd and had similar effects I´d be glad to assist one of the "gurus" going deeper into this. Even more, I´d like to invest more time again to debug it myself, but my gdb knowledge is non-existing. If someone would show me how to start, the I definitely would do so. My concern is that usual debugging approaches will fail because of the timing related cause of the problem. Thanks to all of you so far! Christian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/