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
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Sat, 02 Mar 2002 21:47:19 -0500
From: Jason Tishler <jason AT tishler DOT net>
Subject: Re: fetchmail 5.9.8 and maildrop 1.3.7
In-reply-to: <20020302221220.A4040@LOKI>
To: Rui Carmo <rui DOT carmo AT accao DOT net>
Cc: cygwin AT cygwin DOT com
Mail-followup-to: Rui Carmo <rui DOT carmo AT accao DOT net>, cygwin AT cygwin DOT com
Message-id: <20020303024718.GB2116@hp.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
User-Agent: Mutt/1.3.24i
References: <20020302004512 DOT A1936 AT LOKI> <20020302160332 DOT GA1976 AT hp DOT com>
 <20020302221220 DOT A4040 AT LOKI>

Rui,

On Sat, Mar 02, 2002 at 10:12:20PM +0000, Rui Carmo wrote:
> On Sat, Mar 02, 2002 at 11:03:32AM -0500, Jason Tishler wrote:
> > However, so far no one else seems to have noticed this problem.
> 
> I was under the impression that recv() bugs had been twiddled in
> 1.3.10... Or did the changes in recv() not address MSG_PEEK?

Hmm, I will look into this.  It would be great if my patch just became
obsolete.

> I did not notice any corruption issues with my fetchmail build - but
> then, I did not transfer much more than a few megs of mail (around 25MB,
> I think).

Like I said, no one else seems to have this corruption problem.  Note
that I spent quite a few hours one day last summer inside of gdb trying
to get to the bottom of this problem.  I saw the read() return less
characters than requested even though the number requested is less than
or equal to what was returned from the recv(..., MSG_PEEK).  Trust me,
this causes bad things to happen to your mail.

> I'm also not entirely sure that fetchmail is not the one inserting
> (or handing over, or whatever) the extra blank line upon mailbox creation
> (appends work fine...). I'll have to check later.

My WAG would be on the MDA (i.e., maildrop) not fetchmail.  BTW, I have
had no such problems with procmail regardless of mailbox creation or
appending.

> Anyway, if you've been using fetchmail + procmail since September,
> what's keeping it from being added to the packages list? :) Is it the
> BIND issue?

No, it's not BIND -- it's just laziness on my part.  I really would like
to contribute fetchmail and procmail.  Unfortunately, it appears that I
have chosen unwisely selecting the packages that I currently maintain --
PostgreSQL and Python.  These two seem to keep me quite busy.

Maybe I should have chosen packages that no one ever uses.  You know...
Shelfware.  That would have minimized my support efforts. :,)

> (I'd be glad to lend a hand, mind you...)

If you would like to contribute BIND, fetchmail, or procmail, please let
me know.  I will supply you with my build recipes and help you in anyway
that I can.

Thanks,
Jason

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/