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 Message-ID: <00af01c1e5c8$b6485c60$86aa0142@tus21290> From: "Eric Vorrie" To: "Gary R. Van Sickle" , References: Subject: Re: fetchmail still corrupts files ? Date: Tue, 16 Apr 2002 21:31:13 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 ----- Original Message ----- From: "Gary R. Van Sickle" To: Sent: Tuesday, April 16, 2002 6:45 PM Subject: RE: fetchmail still corrupts files ? > > I cannot confirm that fetchmail is guilty. > > I use fetchmail to retrieve all my mails and feed them to our SMTP > > server. Then I fetch them from the local POP3 server with my windows > > client. No mails with attachments are corrupted! > > So just fetching with fetchmail seems to work ( works for me(tm) ) > > > > It seems that another program in the toolchain is > > causing that damage. Mutt? Procmail? > > > > It's certainly possible that mutt is the guilty party, as it's rather > aggregiously Unix-text-files-only-please oriented. Do things work if you > configure mutt to go directly to your POP3 server? Or if you change the inbox > format to maildir? > > 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. > > -- > Gary R. Van Sickle > Brewer. Patriot. > > > -- > 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/ > -- 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/