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
Message-ID: <019a01c2cff0$415538c0$6b7c86d9@webdev>
Reply-To: "Elfyn McBratney" <cygwin AT cygwin DOT com>
From: "Elfyn McBratney" <elfyn-cygwin AT exposure DOT org DOT uk>
To: "cygwin" <cygwin AT cygwin DOT com>, "Iain Tuddenham" <tuddenham AT ntlworld DOT com>
References: <Pine DOT CYG DOT 4 DOT 53 DOT 0302090118500 DOT 1352 AT LILAC> <Pine DOT CYG DOT 4 DOT 53 DOT 0302090332140 DOT 3244 AT LILAC>
Subject: Re: 1.3.19: fetchmail's "authentication failed" message corrupted
Date: Sun, 9 Feb 2003 04:03:50 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

> Sorry - me again...
>
> Today at 1:31am, Iain Tuddenham wrote:
>
> | My .fetchmailrc includes
> |   mda "procmail -d '%T'; notify"
> | (where notify is a little script to ring a bell).
>
> Having broadcast that to the world, I've just noticed what a bad idea it
> is:
>   "procmail -d '%T'; notify"
> returns always notify's status code of 0, so fetchmail never becomes aware
> of any procmail failure.
>
>   mda "procmail -d '%T' && notify"
> fixes that (and also differs in that it doesn't ring if the mail isn't
> delivered).


WOW!

If only everyone were able to answer their own questions ;-)


Regards,

Elfyn McBratney
elfyn AT exposure DOT org DOT uk
www.exposure.org.uk



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