public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Greywolf <greywolf@starwolf.com>
To: cygwin@cygwin.com
Subject: Postfix+Cygwin: "mail system startup failed"
Date: Wed, 19 Jun 2019 23:08:00 -0000	[thread overview]
Message-ID: <297441be-d2cc-a2cb-968a-b9c82329673b@starwolf.com> (raw)

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':

[since the IPs are all RFC-1918, I don't really care about their visibility...]

postfix: name_mask: ipv4
postfix: name_mask: subnet
postfix: inet_addr_local: configured 8 IPv4 addresses
postfix: been_here: 192.168.238.0/24: 0
postfix: been_here: 192.168.40.0/22: 0
postfix: been_here: 169.254.0.0/16: 0
postfix: been_here: 169.254.0.0/16: 1
postfix: been_here: 169.254.0.0/16: 1
postfix: been_here: 192.168.44.0/22: 0
postfix: been_here: 169.254.0.0/16: 1
postfix: been_here: 127.0.0.0/8: 0
postfix: mynetworks: 192.168.238.0/24 192.168.40.0/22 169.254.0.0/16
192.168.44.0/22 127.0.0.0/8
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?

				--*greywolf;

--
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-19 23:08 UTC|newest]

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

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=297441be-d2cc-a2cb-968a-b9c82329673b@starwolf.com \
    --to=greywolf@starwolf.com \
    --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).