Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Tue, 7 Aug 2001 11:31:10 -0400
From: Jason Tishler <jason AT tishler DOT net>
To: Cygwin <cygwin AT sources DOT redhat DOT com>
Subject: Transient fetchmail corruption problem under Windows 2000
Message-ID: <20010807113110.A1412@dothill.com>
Mail-Followup-To: Cygwin <cygwin AT sources DOT redhat DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.18i
Organization: Dot Hill Systems Corp.

[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.

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'm starting to slog through the fetchmail code, straces, and debugging
with gdb.  If anyone has any ideas on the best way to debug this problem
or whether the problem is in fetchmail or Cygwin, I would love to hear
them.

Thanks,
Jason

-- 
Jason Tishler
Director, Software Engineering       Phone: 732.264.8770 x235
Dot Hill Systems Corp.               Fax:   732.264.8798
82 Bethany Road, Suite 7             Email: jason AT tishler DOT net
Hazlet, NJ 07730 USA                 WWW:   http://www.dothill.com

--
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/