public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Buchbinder, Barry (NIH/NIAID)" <BBuchbinder@niaid.nih.gov>
To: "'gert_de_boer@ch.schindler.com'" <gert_de_boer@ch.schindler.com>,
	cygwin@cygwin.com
Subject: RE: mutt and ssmtp on Cygwin on Windows Server 2003 'child exited 127'
Date: Wed, 19 May 2004 13:54:00 -0000	[thread overview]
Message-ID: <F76C9B2DA2FC4C4CA0A18E288BBCBCF708217948@nihexchange24.nih.gov> (raw)

If I remember correctly (I have not played with mutt for quite a while),
mutt can connect directly to a IMAP or POP server.  So might you be able to
eliminate the use of ssmtp and have mutt send mail directly to the place
that ssmtp sends it?

-----Original Message-----
From: gert_de_boer@ch.schindler.com [mailto:gert_de_boer@ch.schindler.com] 
Sent: Wednesday, May 19, 2004 7:53 AM
To: cygwin@cygwin.com
Subject: mutt and ssmtp on Cygwin on Windows Server 2003 'child exited 127'

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.

Gert de Boer

gert de boer at ch schindler com

cygcheck.out:
(See attached file: cygcheck.out):

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

             reply	other threads:[~2004-05-19 13:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-19 13:54 Buchbinder, Barry (NIH/NIAID) [this message]
2004-05-19 14:07 ` Luc Hermitte
  -- strict thread matches above, loose matches on Subject: below --
2004-05-24 15:14 gert_de_boer
2004-05-26 20:34 ` Brian Ford
2004-05-19 15:10 Buchbinder, Barry (NIH/NIAID)
2004-05-19 13:16 gert_de_boer
2004-05-19 14:28 ` Brian Ford
2004-05-19 15:11 ` Mark Bohlman

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=F76C9B2DA2FC4C4CA0A18E288BBCBCF708217948@nihexchange24.nih.gov \
    --to=bbuchbinder@niaid.nih.gov \
    --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).