Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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:	<40CF1E5C.FC999BC4@dessent.net>
Date:	Tue, 15 Jun 2004 09:05:48 -0700
From:	Brian Dessent <brian AT dessent DOT net>
Organization:	My own little world...
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Running ssh from procmail
References:	<004b01c44fe3$68ff0350$ac050b0a AT PWISNOVSKY>
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com

Peter Wisnovsky wrote:

>     socket: Operation not permitted
>     ssh: connect to host #.#.#.# port 22: Operation not permitted

How are you scheduling fetchmail to run?  From cron?  If it's running
from cron, then it will be running as the SYSTEM user.  It will be
impersonating your regular user account, but since it's launched from a
service it will actually be the SYSTEM account that owns the process. 
I've read that on recent server versions (e.g. Win2k3) the SYSTEM
account has less privileges assigned to it by default, one of which
might be "access the network."  If that's the case then it would explain
why it cannot gethostbyaddr() to resolve the hostname, and why the
socket functions fail with "operation not permitted" if supplied a
dotted-quad.  Try adding that privilege, or have crun run as the
"NetworkService" instead of "LocalServer" or whatever it's called.

Brian

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

- Raw text -