X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=2.9 required=5.0 	tests=AWL,BAYES_00,BOTNET
X-Spam-Check-By: sourceware.org
Date: Thu, 25 Feb 2010 09:28:25 -0500
From: Jason Tishler <jason AT tishler DOT net>
To: cygwin AT cygwin DOT com
Subject: Re: Fetchmail call to procmail no longer works under Cygwin 1.7.1-1
Message-id: <20100225142825.GC940@tishler.net>
Mail-followup-to: cygwin AT cygwin DOT com
References: <3a8528891002230733x644a3bc1na91ddccacafb2e41 AT mail DOT gmail DOT com>  <20100223164927 DOT GA212 AT mimosa DOT garydjones DOT name>  <20100223182852 DOT GD4172 AT tishler DOT net>  <3a8528891002231114p3b23ef4cjced067a0b16fa9fd AT mail DOT gmail DOT com>  <20100223193543 DOT GE4172 AT tishler DOT net>  <3a8528891002231220w428ec33x74a19275e8a537bf AT mail DOT gmail DOT com>  <20100224132513 DOT GA3892 AT tishler DOT net>  <3a8528891002240702n5d17c520m88906fb24e9a1d49 AT mail DOT gmail DOT com>  <3a8528891002241504x6ed224b4k4b70f049bab483df AT mail DOT gmail DOT com>  <4B863157 DOT 2050202 AT gmx DOT de>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-disposition: inline
In-reply-to: <4B863157.2050202@gmx.de>
User-Agent: Mutt/1.4.2.1i
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

On Thu, Feb 25, 2010 at 09:14:15AM +0100, Matthias Andree wrote:
> Jason, would you include this EXITCODE/HOST stuff and other hints into
> your Cygwin README file? I don't think the upstream version will ever
> change again, procmail is apparently dead for nearly a decade. For
> debugging, I'd also suggest to mention LOGABSTRACT=all and LOGFILE
> along with VERBOSE=yes.  LOGFILE=/dev/stderr may prove useful in
> command line testing.

FWIW, the Cygwin procmail README contains the following:

    Install:

    Create a procmail run control file, ~/.procmailrc.  The contents of
    this file are extremely user specific and (way) beyond the scope of
    this README file.

    procmail is usually invoked by your mail transfer agent (MTA).
    Under Cygwin, I recommend using fetchmail to to retrieve your email.
    Cygwin fetchmail will automatically invoke procmail.

    I strongly encourage you to test your procmail recipes before for
    using them in an unattended mode.  Use a command like to following: 

        $ procmail VERBOSE=yes new-procmailrc <test.mail
        
    and examine your procmail log file.

    The following may be helpful with creating your run control file
    and/or finding other (possible) ways to invoke procmail:

        http://www.ii.com/internet/robots/procmail/qs/

> I'd suggest to drop procmail in the long run and provide Sam
> Varshavchik's maildrop instead. It is easier to configure and more
> robust, and it's actually maintained.

IIRC, I tried to get maildrop to run under Cygwin many years ago.
Unfortunately, I was not successful.  Maybe someone would be willing to
try with the latest Cygwin?

Jason

-- 
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D  8784 1AFD E4CC ECF4 8EF6

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple