Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sources DOT redhat DOT com
Date: Thu, 13 Sep 2001 09:37:31 +0000
From: Olaf Foellinger <Olaf DOT Foellinger AT bln DOT sesa DOT de>
To: cygwin AT cygwin DOT com
Subject: Mutt (on cygwin) and binary attachments
Message-ID: <20010913093731.E432@NBOF>
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

Hi,

here's a mail I've received that give hints about the attachment
corruption of mutt.

----- Forwarded message from Ulf Erikson <ulferikson AT yahoo DOT com> -----

Date: Sat, 25 Aug 2001 11:55:34 +0200
From: Ulf Erikson <ulferikson AT yahoo DOT com>
Subject: Mutt (on cygwin) and binary attachments
To: Olaf Föllinger <Olaf DOT Foellinger AT sesa DOT de>

Hi,

Sorry to jump on you personally like this, but I found your discussion
on cygwin AT cygwin DOT com, a mailing list which I don't follow myself.

Thing is that a similar question arose at news://comp.mail.mutt, which
had me recall that there were something in the announcement of
mutt-1.2.5i-2 for cygwin that I couldn't understand at first and later
thought were very clever. Now I think that is what causes your
troubles, though.. After rethinking (again) I guessed that if it was
such a problem then all should have gone back to mutt-1.2.5i-1.
Checking the ftp-sites this doesn't seem to be the case. and.. your
discussion of corrupted binary files had me try out my theory.

I've not used Mutt on Cygwin for half a year or so (with my slow
machine mutt on win32 is much smoother:), but still got it installed.
Downloading the two pre-compiled packages and send binary attachements
with both I came to the conclusion that:

 The pre-compiled binary for Mutt, named mutt-1.2.5i-2, corrupt files.


This is an excerpt of the old announcements for "-1": 
____________________

| ************************************************************
| ***   Mutt treats all files as binary files regardless   ***
| ***   whether a mount point is textmode or binmode!      ***
| ************************************************************
| 
| So care for the mutt configuration files, too. They must not have
| CR/LF line endings. This includes /etc/Muttrc and /etc/mime.types.
| This may change in a future version.
____________________


For "-2" things got changed into:
____________________

| *********************************************************************
| ***       Mutt treats now all input files as text files and       ***
| ***      writes all output files as binary files regardless       ***
| ***         whether a mount point is textmode or binmode!         ***
| *********************************************************************
____________________


Of course this fixes the need for Unix like configuration files, but
it corrupts binaries...

So in case you have not compiled mutt yourself, from the sources at
www.mutt.org, going back to the first cygwin patchlevel could be worth
a try.

-- 
Ulf


----- End forwarded message -----

I've changed back to mutt 1.2.5-1 and everything seems to work now. 


Gruss Olaf

--
Olaf Föllinger
Leiter Fachbereich IT
S.E.S.A. Software und Systeme AG

Alt-Moabit 91a
D-10559 Berlin
Germany
Tel:   +49 30 390722 -291
Fax:   +49 30 390722 -222
Mobil: +49 173 6227080
http://www.sesa.de
mailto: Olaf DOT Foellinger AT sesa DOT de

--
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/