Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Date: Mon, 6 Aug 2001 14:22:50 +0000
From: Olaf Foellinger <Olaf.Foellinger@bln.sesa.de>
To: cygwin@cygwin.com
Subject: Re: problems with binary attachments and mutt
Message-ID: <20010806142250.C1108@NBOF>
References: <3B6A0E97.32492.AEE9CCEB@localhost>; <20010803081944.B1304@NBOF> <3B6B31AC.3137.B35ADA96@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.Foellinger@sesa.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/