Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: Tue, 22 Oct 2002 08:14:52 -0400 From: Jason Tishler Subject: Re: Cygwin/Procmail stops working after setup.exe upgrade In-reply-to: <20021022114820.GA2348@LEPIDUS> To: cygwin AT cygwin DOT com, Thomas Baker Mail-followup-to: cygwin AT cygwin DOT com, Thomas Baker Message-id: <20021022121452.GB992@tishler.net> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: Mutt/1.4i References: <20021022114820 DOT GA2348 AT LEPIDUS> Thomas, On Tue, Oct 22, 2002 at 01:48:20PM +0200, Thomas Baker wrote: > For starters, can anyone out there say whether the problem > lies with Cygwin (permissions), Fetchmail, or Procmail? My WAG is that your problem is due to incorrect file permissions. Recall that the latest Cygwin DLL now defaults to ntsec *on*. I would check the permissions of $PMDIR, $PMDIR/procmail.log, and your entire $MAILDIR tree. A quick test would be to shutdown all Cygwin processes and set CYGWIN=nontsec to see if procmail starts to function properly again. If this "fixes" the problem, then turn ntsec back on and fix your permissions problem for real. Jason -- 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/