public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christian Franke <Christian.Franke@t-online.de>
To: cygwin@cygwin.com
Subject: Re: Postfix+Cygwin: "mail system startup failed"
Date: Fri, 21 Jun 2019 18:02:00 -0000	[thread overview]
Message-ID: <f8d3592b-101f-a505-3102-9f1f2a2b325b@t-online.de> (raw)
In-Reply-To: <297441be-d2cc-a2cb-968a-b9c82329673b@starwolf.com>

Greywolf wrote:
> Greetings!
>
> First the important stuff:
> [uname -a]:
> CYGWIN_NT-10.0 milliways 3.0.7(0.338/5/3) 2019-04-30 18:08 x86_64 Cygwin
>
> [windows]:
> Windows 10 Pro for Workstations
> Build 16299.rs3_release_svc.180808-1748
>
> [this is a work computer so getting updates for it may not be possible]
>
> Now the problem:
>
> I'm trying to get postfix up and running, and all I get is "fatal: 
> mail system
> startup failed", with no further explanation; to wit, from 'postfix -v 
> start':
> ...
> postfix/postfix-script: starting the Postfix mail system
> postfix/postfix-script: fatal: mail system startup failed
> [end output]
>
> Between starting and fatal, I expect that I would get a more detailed 
> dump
> of what's gone wrong.  Anyone have any insight?

Please consult Cygwin syslog output. The postfix daemons (master, ...) 
report problems via syslog(3). If no syslog daemon is installed and 
running, Cygwin sends all syslog output to the Windows event log.

Note that there is a /usr/bin/postfix-config stript to install postfix 
as a Windows service. It should handle all the details like creation of 
the local user $mail_owner. Try 'postfix-config --dryrun' to see what 
would happen.

Regards,
Christian


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2019-06-21 18:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-19 23:08 Greywolf
2019-06-21 18:02 ` Christian Franke [this message]

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=f8d3592b-101f-a505-3102-9f1f2a2b325b@t-online.de \
    --to=christian.franke@t-online.de \
    --cc=cygwin@cygwin.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).