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, 26 May 2004 20:34:00 -0000 [thread overview]
Message-ID: <Pine.CYG.4.58.0405261212490.3604@fordpc.vss.fsi.com> (raw)
In-Reply-To: <OF22EB8D39.E3913334-ONC1256E9E.0036FD73-C1256E9E.00383134@schindler.com>
On Mon, 24 May 2004, gert_de_boer wrote:
> The trick worked for CRON. I let the cron service run under the local
> administration account with the additional rights as explained in the
> openssh.README.
Glad I could help, at least a little.
> But mutt still does not work. I do not get any clear message in the event
> viewer.
Sorry. I don't use mutt or ssmtp, so I'm out of ideas.
> Regards,
>
> Gert de Boer
>
> PS How do I get my mails under the tread in the maillist that I am
> answering to?
Get your mailer to add the header:
In-Reply-To: <Message-ID>
Normally, this happens automatically when you reply to a message.
--
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-26 17:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-24 15:14 gert_de_boer
2004-05-26 20:34 ` Brian Ford [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-19 15:10 Buchbinder, Barry (NIH/NIAID)
2004-05-19 13:54 Buchbinder, Barry (NIH/NIAID)
2004-05-19 14:07 ` Luc Hermitte
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=Pine.CYG.4.58.0405261212490.3604@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).