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, 17 Apr 2002 14:07:36 -0400 From: Jason Tishler Subject: Re: fetchmail-5.9.11-2 now uploaded (was: Re: fetchmail still corrupts files ?) In-reply-to: <154462958118.20020417180902@familiehaase.de> To: cygwin@cygwin.com Mail-followup-to: cygwin@cygwin.com Message-id: <20020417180736.GB1572@tishler.net> 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: <154462958118.20020417180902@familiehaase.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/