From: Brian Ford <ford@vss.fsi.com>
To: gert_de_boer@ch.schindler.com
Cc: cygwin@cygwin.com
Subject: Re: mutt and ssmtp on Cygwin on Windows Server 2003 'child exited 127'
Date: Wed, 19 May 2004 14:28:00 -0000 [thread overview]
Message-ID: <Pine.CYG.4.58.0405190903500.2628@fordpc.vss.fsi.com> (raw)
In-Reply-To: <OF49609287.567833A9-ONC1256E99.003C861B-C1256E99.00415276@schindler.com>
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/
next prev parent reply other threads:[~2004-05-19 14:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 13:16 gert_de_boer
2004-05-19 14:28 ` Brian Ford [this message]
2004-05-19 15:11 ` Mark Bohlman
2004-05-19 13:54 Buchbinder, Barry (NIH/NIAID)
2004-05-19 14:07 ` Luc Hermitte
2004-05-19 15:10 Buchbinder, Barry (NIH/NIAID)
2004-05-24 15:14 gert_de_boer
2004-05-26 20:34 ` Brian Ford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.CYG.4.58.0405190903500.2628@fordpc.vss.fsi.com \
--to=ford@vss.fsi.com \
--cc=cygwin@cygwin.com \
--cc=gert_de_boer@ch.schindler.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).