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, 17 Apr 2002 14:07:36 -0400
From:	Jason Tishler <jason AT tishler DOT net>
Subject:	Re: fetchmail-5.9.11-2 now uploaded (was: Re: fetchmail still corrupts
	files ?)
In-reply-to:	<154462958118.20020417180902@familiehaase.de>
To:	cygwin AT cygwin DOT com
Mail-followup-to:	cygwin AT cygwin DOT com
Message-id:	<20020417180736.GB1572@tishler.net>
MIME-version:	1.0
User-Agent:	Mutt/1.3.24i
References:	<154462958118 DOT 20020417180902 AT familiehaase DOT de>

Gerrit,

On Wed, Apr 17, 2002 at 06:09:02PM +0200, Gerrit P. Haase wrote:
> I would be pleased to hear if it works on W2K without corrupting
> binary attachments (or was it even corrupting text attachments?).

Initially, I thought that it had to do with binary attachments.
After reading the fetchmail code, I feel relatively sure that any aspect
of the mail can get corrupted because the routine that I patched is very
low level. In fact, it is the routine that reads characters off of the
socket connected to the mail server.

I think that the probability of corruption is higher with larger
messages which may explain why I first noticed the problem with a
message that contained a binary attachment.

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/

- Raw text -