Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Mon, 6 Aug 2001 14:22:50 +0000 From: Olaf Foellinger To: cygwin AT cygwin DOT com Subject: Re: problems with binary attachments and mutt Message-ID: <20010806142250.C1108@NBOF> References: <3B6A0E97 DOT 32492 DOT AEE9CCEB AT localhost>; <20010803081944 DOT B1304 AT NBOF> <3B6B31AC DOT 3137 DOT B35ADA96 AT localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <3B6B31AC.3137.B35ADA96@localhost>; from RPraetorius@aspenres.com on Fri, Aug 03, 2001 at 11:20:12PM +1000 On Fri, Aug 03, 2001 at 11:20:12PM +1000, Robert Praetorius wrote: > Looks fine. Bummer. That was my only guess. Unless the binary > file came from a place that wasn't mounted. > > Here's an experiment: > > pick a binary that mutt will break > > mail it to yourself with mutt > > mail it to yourself with working mail program > > extract both versions to disk > > compare them > > That way you can see what's getting broken. That might help you (or > someone else) track down the cause. Done this. I've compared the original and the send file. They differ on two lines. Should I mail an example to the list ? Gruss Olaf -- Olaf Föllinger S.E.S.A. AG GS Berlin mail: Olaf DOT Foellinger AT sesa DOT de fon: +49-30-390722291 -- 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/