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:	Sun, 9 Feb 2003 03:48:09 +0000
From:	Iain Tuddenham <tuddenham AT ntlworld DOT com>
X-X-Sender:	"Iain Tuddenham"@LILAC
To:	cygwin AT cygwin DOT com
Subject:	Re: 1.3.19: fetchmail's "authentication failed" message corrupted
In-Reply-To:	<Pine.CYG.4.53.0302090118500.1352@LILAC>
Message-ID:	<Pine.CYG.4.53.0302090332140.3244@LILAC>
References:	<Pine DOT CYG DOT 4 DOT 53 DOT 0302090118500 DOT 1352 AT LILAC>
MIME-Version:	1.0

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

Iain Tuddenham.


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

- Raw text -