Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Wed, 28 May 2003 20:21:55 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: qmail cygwin port successfull
Message-ID: <20030529002155.GB19817@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <1214 DOT 212 DOT 0 DOT 200 DOT 22 DOT 1054121128 DOT mtc AT mail DOT moldtelecom DOT 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 AT moldtelecom DOT 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/