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 From: "Gary R. Van Sickle" To: Subject: RE: fetchmail still corrupts files ? Date: Tue, 16 Apr 2002 20:45:22 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal In-Reply-To: <187370369322.20020416162553@familiehaase.de> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal > 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/