Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Wed, 28 May 2003 20:21:55 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: qmail cygwin port successfull Message-ID: <20030529002155.GB19817@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <1214.212.0.200.22.1054121128.mtc@mail.moldtelecom.md> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1214.212.0.200.22.1054121128.mtc@mail.moldtelecom.md> User-Agent: Mutt/1.4.1i On Wed, May 28, 2003 at 02:25:28PM +0300, linamat@moldtelecom.md wrote: >I am successfully ported qmail-1.03 and it seems to work good. >I've replaced flock() with fcntl() such as somebody did from one japan site. >Problem with spooling (absent mkfifo() and UNIX named pipe implementation >under Cygwin) was resolved by turning to UNIX socket. The only one problem >that the first message is not triggered immediately after sending, but >with the next all OK. >And now in my ISP filials where Win2k lives qmail+vpopmail+mysql under >Win32 works. >Here is a only qmail patch. > >I can send Win32 binaries Unless something has changed, I don't believe that you can legally send patched win32 binaries of qmail. I believe that violates the qmail license. cgf -- 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/