This is the mail archive of the
mailing list for the Cygwin project.
Re: Transient fetchmail corruption problem under Windows 2000
- To: Cygwin <cygwin at sources dot redhat dot com>
- Subject: Re: Transient fetchmail corruption problem under Windows 2000
- From: "Gerrit P. Haase" <gerrit at nyckelpiga dot de>
- Date: Tue, 7 Aug 2001 21:26:03 +0100
- CC: Olaf Foellinger <Olaf dot Foellinger at bln dot sesa dot de>, Jason Tishler <jason at tishler dot net>
- References: <20010807113110.A1412@dothill.com>; from email@example.com on Tue, Aug 07, 2001 at 11:31:10AM -0400
Am 7 Aug 2001, um 15:39 hat Olaf Foellinger geschrieben:
> On Tue, Aug 07, 2001 at 11:31:10AM -0400, Jason Tishler wrote:
> > [I normally would not post such a vague bug report but since this
> > problem significantly impacts my mail delivery I hope that I will be
> > allowed some latitude...]
> > I am using fetchmail/procmail/mutt to retrieve, process, and read my
> > email. I recently changed from using a Windows NT 4.0 SP5 to a
> > Windows 2000 SP1 machine. Shortly thereafter, I started to notice
> > that some of the emails that I received with binary attachments were
> > corrupted.
What are the types of the binary attachments?
Is it various or are there only some files corrupted or are all
> > After sending the same message to myself repeatedly and examining
> > the raw message in an mbox file, I began to see the following
> > pattern. The corrupted messages are always larger than they should
> > be and there are chunks of garbage characters in them. Sometimes
> > the MIME separators are repeated as if fetchmail shuttered when
> > writing to down the pipe to procmail (this is probably just a
> > special case of the garbage characters).
> > Not all messages get corrupted. A little more half were corrupted
> > -- the others were fine. I also POP-ed directly into the mail
> > server and verified that the messages were not corrupt and only
> > became so when I used fetchmail to retrieve them.
> > I tried various versions of fetchmail (5.8.12, 5.8.14, 5.8.16) and
> > Cygwin (1.3.2, my CVS build, latest snapshot). All exhibit the same
> > transient binary attachment corruption problem.
> > When I repeat the same experiments on my old Windows NT 4.0 SP5
> > machine, I have not received any corrupted email (yet).
> > Is anyone using fetchmail under Windows 2000? If so, are you
> > experience any problems?
> I don't use fetchmail, but with mutt and ssmtp all my sent binary
> attachments get corrupted on W2000SP1. Don't know why, didn't try it
> under NT.
Sorry, I don't know enough to help you out of this misere since i
never used procmail, but io have some more questions.
Jason, do you use also use ssmtp as Olaf mentioned?
Anyway, since it only happens on NT5 and not on NT4 as you reported,
it seems not to be a problem with Fetchmail. Since Fetchmail does
nothing else but retrieve and send out to a smtp server i could not
think of big problems with this. Or is it an option to pipe directly
from fetchmail to procmail?
Are the files stored to disk between retrieving and sending out?
Does Procmail store to disk before delivering?
Are your mounts of binary type?
Please report if you track down the source of the problems, maybe a
problem with the pipes?
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
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html