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 Message-ID: <4105459A.4090204@sbcglobal.net> Date: Mon, 26 Jul 2004 10:55:38 -0700 From: George Reply-To: d1945 AT sbcglobal DOT net User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) MIME-Version: 1.0 To: ">"@delorie.com CC: cygwin AT cygwin DOT com Subject: Re: Fetchmail and Procmail References: <4103A54E DOT 20906 AT sbcglobal DOT net> <20040726123756 DOT GA50716 AT tishler DOT net> <410503BC DOT 9030607 AT sbcglobal DOT net> <20040726171031 DOT GA50948 AT tishler DOT net> In-Reply-To: <20040726171031.GA50948@tishler.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Jason Tishler wrote: >George, > >On Mon, Jul 26, 2004 at 06:14:36AM -0700, George wrote: > >>Jason Tishler wrote: >> >>>On Sun, Jul 25, 2004 at 05:19:26AM -0700, George wrote: >>> >>> >>>>[snip] >>>> >>>See the procmail man page. >>> >>> >>I've read all man page and all related manpages. >> > >Hmm... > >What about the following? > > $ man procmail > [snip] > > Suspicious rcfile "x" The owner of the rcfile was not the recipient > or root, the file was world writable, or the > directory that contained it was world > writable, or this was the default rcfile > ($HOME/.procmailrc) and either it was group > writable or the directory that contained it > was group writable (the rcfile was not used). > Ok. I am thoroughly embarassed. Maybe instead of reading the man page several times, I should have read a single time but more carefully? :-( > >>>>[snip] >>>> >>>> >>>[snip] >>> >>> >>[snip] >> >>As for testing on a Unix box, I'm in that category of Cygwin users who >>need to make something work in a Windows environment. My question >>relates more to whether I should be disppointed or satisfied with the >>results. >> > >I suggested a comparison to help you find the "bottleneck." If the cost >of the fork (of procmail) is the issue, then Cygwin is slowing you down. >If the network speed or the way that fetchmail interacts with the mail >server is the issue, then it's not. Note these are just some ideas... >I will leave it to you to dig deeper, if interested. > > I'm confident the fetchmail part of the equation is not the problem, and as my procmail recipes are minimal I'll have to assume, at least for the moment, that the forking is the issue. Thanks again for the comments, Jason. They've been helpful. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/