Re: Running ssh from procmail

On Jun 15 20:02, Peter Wisnovsky wrote: > No such luck...moreover wouldn't a missing binary or dll lead to a link > or exec failure? Not in this case since the WinSock DLL is loaded dynamically at runtime. The error messages seem to indicate that the child process couldn't find the WinSock DLL a

Re: Running ssh from procmail

No such luck...moreover wouldn't a missing binary or dll lead to a link or exec failure? Peter On Jun 15, 2004, at 1:34 AM, Corinna Vinschen wrote: Add the usual Windows paths to $PATH, e.g. on my system that would be PATH=/bin:/usr/bin:/pkg/mail/bin:/cygdrive/c/WINDOWS/system32:/ cygdrive/

Re: Running ssh from procmail

I'm running it using fetchmail -d #. Peter - Original Message - From: "Brian Dessent" To: <[EMAIL PROTECTED]> Sent: Tuesday, June 15, 2004 9:05 AM Subject: Re: Running ssh from procmail -#- MailID:TNFA > Peter Wisnovsky wrote: > > > socket: Op

Re: Running ssh from procmail

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

Re: Running ssh from procmail

On Jun 14 16:55, Peter Wisnovsky wrote: > More information on this problem with ssh hostname resolution failing. > > If my fetchmailrc has > > poll ... mda "/usr/bin/procmail -d %T" > > hostname resolution in the nested script fails with > + /usr/bin/ssh -g -n -e none -v -R p1:localhost:p1-

Re: Running ssh from procmail

More information on this problem with ssh hostname resolution failing. If my fetchmailrc has poll ... mda "/usr/bin/procmail -d %T" hostname resolution in the nested script fails with + /usr/bin/ssh -g -n -e none -v -R p1:localhost:p1-l me verklempt 'sleep 180' OpenSSH_3.8.1p1, OpenSSL 0.9.