This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Antwort: Re: mutt and ssmtp on Cygwin on Windows Server 2003 'child exited 127'
- From: gert_de_boer at ch dot schindler dot com
- To: cygwin at cygwin dot com
- Date: Mon, 24 May 2004 11:24:45 +0200
- Subject: Antwort: Re: mutt and ssmtp on Cygwin on Windows Server 2003 'child exited 127'
Hello Mr Ford,
Thanks for your reaction. It seemed so close to my understanding of the
problem, but alas, it still does not work.
I assume you meant this part of the openssh.README:
Important note for Windows 2003 Server users:
---------------------------------------------
2003 Server has a funny new feature. When starting services under SYSTEM
account, these services have nearly all user rights which SYSTEM holds...
except for the "Create a token object" right, which is needed to allow
public key authentication :-(
There's no way around this, except for creating a substitute account which
has the appropriate privileges. Basically, this account should be member
of the administrators group, plus it should have the following user rights:
Create a token object
Logon as a service
Replace a process level token
Increase Quota
I did not find an 'increase quota' right, I assumed 'adjust memory for
process'
Regards,
Gert de Boer
Systemadministration and Development
FI-TE
Schindler Lifts Switzerland Ltd
Zugerstrasse 13
CH-6030 Ebikon
Telephone: +41 (0)41 4453010
mailto: gert_de_boer@ch.schindler.com
Brian Ford
<ford@vss.fsi.co An: gert_de_boer@ch.schindler.com
m> Kopie: cygwin@cygwin.com
Thema: Re: mutt and ssmtp on Cygwin on Windows Server 2003 'child exited 127'
05/19/2004 04:07
PM
Bitte antworten
an cygwin
On Wed, 19 May 2004, gert_de_boer wrote:
> Somehow I do not succeed in configuring mutt or ssmtp with Cygwin on a
> Windows 2003 server.
>
> As an example of what happens:
>
> $ echo hallo | mutt -s new_test myname@mycompany.com
> Error sending message, child exited 127 (Exec error.).
> Could not send the message.
>
> The error is exactly the same as when I have a wrong 'sendmail' defined
in
> my .muttrc on a server where cygwin runs without any problem. However I
> defined it correct:
> set sendmail=/usr/sbin/ssmtp
>
> Executing ssmtp on its own delivers an empty mail at
myname@mycompany.com,
> so the error is not there.
>
> It all works without any problem on Windows XP and Windows 2000.
>
> So it seems something has changed in Windows 2003: for some reason mutt
> cannot trigger ssmtp to do its job.
>
> Something similar seems to happen between the CYGWIN cron service and the
> scripts it is supposed to start. Nothing happens, but if I look in the
> eventviewer I see the following order of events:
>
> PID 3188: (myaccount) RELOAD (tabs/myaccount)
>
> PID 3392: (myaccount) CMD (/home/myaccount/bin/test_mail.sh)
>
> PID 3392: (CRON) error (can't switchuser context)
>
> So it is just an idea of mine that somehow (some) programs are not able
to
> start others, due to some rigid security settings.
>
> BTW, all the above is done as with a group account with administrator
> rights on the server.
Please read the Windows 2003 Server section of
/usr/share/doc/Cygwin/openssh.README and see if that helps. I know it
sounds weird, but trust me, it is relevant.
--
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
the best safety device in any aircraft is a well-trained pilot...
--
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/