X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.0 required=5.0 tests=BAYES_00,SARE_MSGID_LONG40
X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
In-Reply-To:	<20100223131352.GA4172@tishler.net>
References:	<3a8528891002220612q63d1ee8fxc69140f9b41685c5 AT mail DOT gmail DOT com> <20100222220208 DOT GA1308 AT tishler DOT net> <3a8528891002221452h48008b49t2a17aa42a97ee5e AT mail DOT gmail DOT com> <20100223021729 DOT GA6116 AT tishler DOT net> <3a8528891002221948k38c0cc7ei24a4822a86803df6 AT mail DOT gmail DOT com> <20100223131352 DOT GA4172 AT tishler DOT net>
Date:	Tue, 23 Feb 2010 10:33:24 -0500
Message-ID:	<3a8528891002230733x644a3bc1na91ddccacafb2e41@mail.gmail.com>
Subject:	Re: Fetchmail call to procmail no longer works under Cygwin 1.7.1-1
From:	Thomas Baker <thomasbaker49 AT googlemail DOT com>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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 Tue, Feb 23, 2010 at 8:13 AM, Jason wrote:
>> > =C2=A0 =C2=A0 http://cygwin.com/acronyms#PPIOSPE
>>
>> My apologies if I overlooked that - I'm temporarily working in
>> googlemail because of this procmail situation and feel out of my usual
>> element (mutt).
>
> Unfortunately, you are still overlooking the above. :,(

Understand the principle now - correcting outgoing mail now by hand.

> I meant running procmail from the command line with a mail message like
> the following:
>
> =C2=A0 =C2=A0$ procmail <foo.mail
>
> Does the above work on your desktop machine?

If I pipe one message into procmail with:

	procmail -v -d tbaker <msg.mbox

procmail reports:

	Locking strategies:     dotlocking, fcntl()
	Default rcfile:         $HOME/.procmailrc
	Your system mailbox:    /var/spool/mail/TBaker

and appends the message to the file /var/spool/mail/TBaker,
ignoring the recipe in $HOME/.procmailrc.

This also does not work:

	procmail -d tbaker <msg.mbox

However, on the netbook

	procmail -d tbaker <msg.mbox

works fine, delivering the message where it is supposed to go.

Tom


--=20
Tom Baker

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

- Raw text -