Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <019a01c2cff0$415538c0$6b7c86d9@webdev> Reply-To: "Elfyn McBratney" From: "Elfyn McBratney" To: "cygwin" , "Iain Tuddenham" References: 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@exposure.org.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/