Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com From: "Gerrit P. Haase" To: Cygwin Date: Wed, 8 Aug 2001 23:28:51 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Transient fetchmail corruption problem under Windows 2000 Message-ID: <3B71CB33.5471.1F92417@localhost> In-reply-to: <20010807161042.A576@dothill.com> References: <3B705CEB DOT 5417 DOT 1F137AC AT localhost> X-mailer: Pegasus Mail for Win32 (v3.12cDE) X-Sender: 320081107336-0001 AT t-dialin DOT net Am 7 Aug 2001, um 16:10 hat Jason Tishler geschrieben: > Gerrit, > > [This message was received corrupted... I have attached it for > perusal by the curious.] Holla, this attached message looks really like garbage. > On Tue, Aug 07, 2001 at 09:26:03PM +0100, Gerrit P. Haase wrote: > > What are the types of the binary attachments? > > Actually, after further investigation it appears that even plain text > attachments are affected too. > > > Is it various or are there only some files corrupted or are all > > attachment > ^^ > > Note the null character above, this is part of the corruption. > > If I send the same message (which includes an attachment) to myself > repeatedly, most of the time to it is corrupted when fetched via POP > by fetchmail. And for this test sendings you used ssmtp? Plus mutt? But as you said, it is only a problem when retrieving via fetchmail, i will try to install 'my' fetchmail version at my box, maybe in conjunction with procmail. Really interesting, never tried before. > > Are your mounts of binary type? > > Yes. Then that should be no problem. > > Please report if you track down the source of the problems, maybe a > > problem with the pipes? > > After further experimentation, I believe that I have ruled out > procmail as a potential culprit. I replaced procmail with a shell > script that just cats stdin to a file. Even without procmail in the > picture, I'm still getting corrupted messages. Hence, the problem is > with fetchmail (or Cygwin itself). Hmmm, still there is piping... I will test at my win2k workstation if there is a problem with pipes tomorrow. > > Olaf could you please report exactely what you do to send out a > > corrupt message? Is it a known issue? I never heard before of > > problems with mailing through ssmtp on win2k. I will try tomorrow to > > send some mail with ssmtp and binaries attached. > > I have not had any problems sending email (without or with > attachments) with ssmtp under Windows 2000. How is a file attached to ssmtp? Only via mutt? gph -- =^..^= -- 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/