There’s a mail-server port that configures MacPorts postfix/dovecot/rspamd/…
and other tools to create a working mail server largely based on the old MacOS
Server.app mail server, complete with a functional PKI and fast solr-based mail
searches. Even APNS push notifications still work to Mail an
On 29/12/2023 15.28, Ubence Quevedo (thatrat) wrote:
That's just it, I am using mail from /opt/local/bin/:
uquevedo@ubence-mini-wired ~ % which mail
/opt/local/bin/mail
I shouldn't have to use a specific executable if it's attaching to a
standard port for a running service?
Unless there'
On 2023-12-28 at 10:53:06 UTC-0500 (Thu, 28 Dec 2023 07:53:06 -0800)
Ubence Quevedo (thatrat)
is rumored to have said:
Hi,
I’ve installed postfix and have configured it similarly to how I
have it configured on some Linux systems using this tutorial
[https://www.tutorialspoint.com/configure-p
I was just hoping that the postfix would just “work” after getting it compiled,
but with Apple doing their own thing with the postfix they ship with macOS
Sonoma, it doesn’t look like it’ll be as straightforward a thing as I thought
it would be.
This was a nice-to-have and not absolutely necess
I have MacPorts postfix with amavisd new, spamassassin and dovecot successful
working on macOS Ventura and High Sierra by sending external mail through icloud
and using getmail to fetch mail from icloud, outlook and gmail. I am using
submission
(port 587) to send mail.
I had to disable the macOS
On 29/12/2023 15.28, Ubence Quevedo (thatrat) wrote:
> That’s just it, I am using mail from /opt/local/bin/:
> uquevedo@ubence-mini-wired ~ % which mail
> /opt/local/bin/mail
>
> I shouldn’t have to use a specific executable if it’s attaching to a
> standard port for a running service…?
>
> Unles
That’s just it, I am using mail from /opt/local/bin/:
uquevedo@ubence-mini-wired ~ % which mail
/opt/local/bin/mail
I shouldn’t have to use a specific executable if it’s attaching to a standard
port for a running service…?
Unless there’s something configuration wise that I’m not seeing about wha
You should have only the postfix.log file and don’t worry about the warning not
owned by postfix on the .turd_postfix file.
I think you use the macOS mail command which will not use macports postfix.
Check the /opt/local/bin directory for the mail or mailx command, which you
should use.
instea
Huh, I’m only getting a /opt/local/var/log/postfix/postfix.log generated:
uquevedo@ubence-mini-wired ~ % tree /opt/local/var/log
/opt/local/var/log
└── postfix
└── postfix.log
2 directories, 1 file
With the following contents [which I fixed a few things and restarted the
service]:
uquevedo@u
You should with this logging you should get the information in your postfix log
as in mail.log, this is what I get.
Sent from my iPhone
> On 29 Dec 2023, at 09:36, Ubence Quevedo (thatrat) wrote:
>
> Thanks for pointing that out. I added that and tweaked the permissions, and
> I’m getting s
Thanks for pointing that out. I added that and tweaked the permissions, and
I’m getting some logging about the service starting/stopping, but I’m not
getting the same type of logging I’m expecting from my Linux systems.
I can usually look in /var/log/mail.log on my Ubuntu server to see the stat
I have postfix login to a file enabled as follow:
in the main.cf I added:
maillog_file = /opt/local/var/log/postfix/postfix.log
and in the master.cf:
postlog unix-dgram n - n - 1 postlogd
Make sure the directory /opt/local/var/log/postfix exists and is writeable vy
p
Hi,
I’ve installed postfix and have configured it similarly to how I have it
configured on some Linux systems using this tutorial
[https://www.tutorialspoint.com/configure-postfix-with-gmail-on-ubuntu], and
when I install and configure postfix in macOS [and make some slight changes
because eve
13 matches
Mail list logo