Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Thu, 06 Jun 2002 09:20:24 -0400
From: Jason Tishler <jason AT tishler DOT net>
Subject: Re: [ANNOUNCEMENT] Updated Cygwin Package: fetchmail-5.9.11-3
In-reply-to: <15614.52985.963207.491507@gargle.gargle.HOWL>
To: cygwin AT cygwin DOT com
Mail-followup-to: cygwin AT cygwin DOT com
Message-id: <20020606132024.GA376@tishler.net>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
User-Agent: Mutt/1.4i
References: <20020528162123 DOT 1F32C1B867 AT redhat DOT com>
 <20020604210513 DOT GD1588 AT tishler DOT net>
 <15614 DOT 52985 DOT 963207 DOT 491507 AT gargle DOT gargle DOT HOWL>

Pete,

On Wed, Jun 05, 2002 at 09:54:49PM -0500, Pete McCann wrote:
> This version seems to work ok (at least it worked for a 2M attachment
> that I sent to myself just now).

Thanks for the status.  If you would like to verify that the Winsock
workaround code is actually being triggered, then just run fetchmail
with the --verbose option.  You should see many of the following
messages in your fetchmail logfile:

    Cygwin socket read retry

> I will post again if I see a recurrence of the problem.

Please do.

> Yes, I had gotten the source code for 5.9.11-1 from a cygwin mirror,
> not the fetchmail homepage.  Sorry about the confusion.

No problem.

> Thanks for your efforts maintaining this critical piece of software.

You are very welcome.  Since I use Cygwin fetchmail at both work and
home, I'm not doing much more than what I would have to do to maintain
the package privately.

BTW, I use Cygwin fetchmail at work to avoid the Outlook/Exchange thing
myself.  There are some known MS Exchange issues that you should know
about:

    o POP3/IMAP access can truncate messages:

      http://support.microsoft.com/default.aspx?scid=kb;EN-US;q296869

    o attachments (e.g., PDF) can be incorrectly encoded so that some
      mail clients (e.g., mutt) will not be able to decode them:

      http://support.microsoft.com/default.aspx?scid=kb;EN-US;q178241
      http://support.microsoft.com/default.aspx?scid=kb;en-us;Q182307

I worked around the above by adding a rule in Outlook to copy all new
messages to a "copy" folder and then instructing fetchmail to retrieve
the messages from this folder instead.  In this way, I can always get
back the original message, if necessary.  Additionally, I configured
AutoArchive to remove "old" messages from the Inbox so I don't
eventually exceed our corporate maximum disk space usage policy.

Thanks,
Jason

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