> Are you certain?
“Often wrong, never in doubt.”
Yes, I am certain:
> sudo launchctl unload -w
> /System/Library/LaunchDaemons/com.apple.postfix.master.plist
>
> /System/Library/LaunchDaemons/com.apple.postfix.master.plist: Operation not
> permitted while System Integrity Protection is enga
On Jan 11, 2020, at 12:32, Steven Smith wrote:
> First, as Gerben points out, macOS‘s postfix launch daemon is in
> /System/Library, so you’d have to disable SIP to unload it, which at best is
> a major PITA, and realistically a non-option.
Are you certain? Certainly modifying anything in /S
On Jan 10, 2020, at 11:37, Gerben Wierda wrote:
> Given that postfix writes a pid file in
> /opt/local/var/spool/postfix/pid/master.pid would it be possible to use a
> startupitem.pidfile entry that triggers daemondo to try to relaunch when this
> happens?
That seems reasonable. I filed:
h
> On 11 Jan 2020, at 22:08, Bill Cole
> wrote:
>
> That should not matter, because 10.14+ (Mojave & Catalina) are entirely unfit
> for and hostile to server duties. The best answer to the question "How do I
> make Postfix work well on modern macOS?" is simply: "You don't.”
Though I heartily
On 11 Jan 2020, at 13:32, Steven Smith wrote:
• Edit /etc/postfix/master.cf as Gerben suggests.
My concern about the second option is that it will never give the
macOS postfix a chance to do what it wants to do a boot time
That gives Apple too much credit, e.g. assumes that someone competent
It was Bill Cole who gave the answer on postfix users.
G
> On 11 Jan 2020, at 19:32, Steven Smith wrote:
>
> Thank you very much for troubleshooting this issue.
> On 11 Jan 2020, at 19:32, Steven Smith wrote:
>
> Second, I see these two possible fixes:
>
> • Include a little bash script in the postfix launch daemon that tests for
> macOS postfix being loaded, or port 25 in use, then wait a bit, and try a few
> times before giving up. I do this hack
Thank you very much for troubleshooting this issue.
First, as Gerben points out, macOS‘s postfix launch daemon is in
/System/Library, so you’d have to disable SIP to unload it, which at best is a
major PITA, and realistically a non-option.
Second, I see these two possible fixes:
• Include a l
On 11 Jan 2020, at 12:17, Gerben Wierda wrote:
This might break things as some Apple stuff may rely on
/usr/sbin/sendmail being able to deliver mail.
Indeed it does. As does anything Unixy which is not explicitly
configured to look elsewhere, e.g. cron.
Not certain, though. It might be a
This might break things as some Apple stuff may rely on /usr/sbin/sendmail
being able to deliver mail. Not certain, though. It might be a simple solution.
G
> On 11 Jan 2020, at 12:17, daniel Azuelos wrote:
>
> [ My questions and answers are in the normal reading order. ]
>
> On 11/01/2020,
[ My questions and answers are in the normal reading order. ]
On 11/01/2020, Gerben Wierda wrote :
[...]
| It is not necessary as the cause has (probably) been found.
|
| macOS still contains a postfix and it is launched at boot time during 60
seconds with a launchdaemon plist
/System/Library
> On 10 Jan 2020, at 18:37, Gerben Wierda wrote:
>
> postfix is started during boot on my macOS system. This fails with:
>
> Jan 10 18:00:08 mail postfix/master[488]: fatal: bind 0.0.0.0 port 25:
> Address already in use
> Jan 10 18:00:10 mail /postfix-script[511]: fatal: mail system startup
postfix is started during boot on my macOS system. This fails with:
Jan 10 18:00:08 mail postfix/master[488]: fatal: bind 0.0.0.0 port 25: Address
already in use
Jan 10 18:00:10 mail /postfix-script[511]: fatal: mail system startup failed
but when I shortly thereafter launch it it just starts fi
13 matches
Mail list logo
