Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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 06:40:38 +0000 From: Marc Chantreux To: cygwin AT cygwin DOT com Subject: Re: fetchmail still corrupts files ? Message-ID: <20020417064038.A1480@MILLENIUM> References: <187370369322 DOT 20020416162553 AT familiehaase DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from g.r.vansickle@worldnet.att.net on Tue, Apr 16, 2002 at 08:45:22PM -0500 On Tue, Apr 16, 2002 at 08:45:22PM -0500, Gary R. Van Sickle wrote: > It's certainly possible that mutt is the guilty party, as it's rather > aggregiously Unix-text-files-only-please oriented. no , it's not ! i've already posted that *fetchmail* has a *known bug* when dealing with the W2K winsock. > Do things work if you > configure mutt to go directly to your POP3 server? works fine ... but i don't know if it is possible to use procmail with the mutt POP support. > Or if you change the inbox > format to maildir? not tried. why do you want to do that ? > I'm a changelog away from updating mutt to 1.3.28; I could send you the new .exe > if you'd like to try it and see if it makes any difference (and I'd appreciate > the additional testing). Let me know. will be great ! Marc -- 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/