Hi,
We are running Postfix on macOS and making use of `maillog_file = /dev/stdout`
and `postfix start-fg` to send our logs to stdout. Not using Docker.
We would like to pipe the logs from stdout to another process to do some
analysis and post-processing, like so:
$ postfix start-fg | o
On 2020-09-21 20.39, Viktor Dukhovni wrote:
On Mon, Sep 21, 2020 at 08:09:41PM +0200, Peter Lindgren wrote:
I build postfix 3.5.7 from source on OpenBSD 6.7. I seem to have problem
with the certificate I generated. They work fine with Dovecot, though.
If you're linking against LibreSSL, and no
On Mon, Sep 21, 2020 at 08:20:07AM -0400, micah anderson wrote:
> > Please note that the Let's Encrypt intermediate CA certificate "X3" will
> > soon be
> > phased out in favour of "R3" and "E1" which have new keys, and so any DANE
> > TLSA
> > "2 1 1" records matching "X3" will not match "R3" o
Peter Lindgren:
> Hi!
>
> I build postfix 3.5.7 from source on OpenBSD 6.7. I seem to have problem
> with the certificate I generated. They work fine with Dovecot, though.
>
> In the moment postfix/master starts the smtpd and it's trying to do
> something with the certificate (on the smtp submi
On Mon, Sep 21, 2020 at 08:09:41PM +0200, Peter Lindgren wrote:
> I build postfix 3.5.7 from source on OpenBSD 6.7. I seem to have problem
> with the certificate I generated. They work fine with Dovecot, though.
If you're linking against LibreSSL, and not OpenSSL, that's not
supported.
--
Hi Dnia,
On 21-09-2020 18:39, Jaroslaw Rafa wrote:
> Dnia 21.09.2020 o godz. 18:15:00 Hans van Zijst pisze:
>> I'll fix my setup with amavisd-milter, which makes the setup simpler as
>> well.
>
> Is there anything *besides* running SpamAssassin that you need Amavis for?
>
> Because if you want *
Hi!
I build postfix 3.5.7 from source on OpenBSD 6.7. I seem to have problem
with the certificate I generated. They work fine with Dovecot, though.
In the moment postfix/master starts the smtpd and it's trying to do
something with the certificate (on the smtp submission port 587), it
crashes
Dnia 21.09.2020 o godz. 18:15:00 Hans van Zijst pisze:
> I'll fix my setup with amavisd-milter, which makes the setup simpler as
> well.
Is there anything *besides* running SpamAssassin that you need Amavis for?
Because if you want *only* to run SpamAssassin, it's simpler to use
spamass-milter (o
Hi Damian,
Thanks for your quick answer.
On 21-09-2020 18:03, Damian wrote:
>> I've defined OpenDKIM and OpenDMARC as smtpd_milters, using UNIX
>> sockets. In the "normal" setup they work like a charm, but now I add
>> Amavis to the mix, with smtpd_proxy_filter, and suddenly both milters
>> disap
> I've defined OpenDKIM and OpenDMARC as smtpd_milters, using UNIX
> sockets. In the "normal" setup they work like a charm, but now I add
> Amavis to the mix, with smtpd_proxy_filter, and suddenly both milters
> disappear. Why?
>From [1]:
> When you use the before-queue content filter for incomin
I'm trying to do all my scanning before-queue: spf, dkim, dmarc and
SpamAssassin. There are strong arguments to do SpamAssassin after the
message has been queued, but for this one I need everything before-queue.
I've defined OpenDKIM and OpenDMARC as smtpd_milters, using UNIX
sockets. In the "norm
On Mon, Sep 21, 2020 at 11:15:01AM -0400, Wietse Venema wrote:
> > > I don't know what you're finding surprising here. There's no magic, the
> > > restrictions are evaluated *exactly* as written. There's no mention
> > > of virtual here, so for remote senders, only recipients listed in
> > >
> >
Alex:
> Hi,
>
> On Sun, Sep 20, 2020 at 10:06 PM Viktor Dukhovni
> wrote:
> >
> > On Sun, Sep 20, 2020 at 08:53:36AM -0400, Alex wrote:
> >
> > > > > smtpd_recipient_restrictions =
> > > > > permit_mynetworks,
> > > > > permit_sasl_authenticated,
> > > > > check_recipient_access pcre:/etc/p
Hi,
On Sun, Sep 20, 2020 at 10:06 PM Viktor Dukhovni
wrote:
>
> On Sun, Sep 20, 2020 at 08:53:36AM -0400, Alex wrote:
>
> > > > smtpd_recipient_restrictions =
> > > > permit_mynetworks,
> > > > permit_sasl_authenticated,
> > > > check_recipient_access pcre:/etc/postfix/local_recip_map,
> >
September 21, 2020 10:13 AM, "Viktor Dukhovni"
wrote:
> On Mon, Sep 21, 2020 at 08:09:25AM +, pat...@patpro.net wrote:
>
>> Just to ensure I've understood this well: if I'm using "3 1 1" I don't
>> need to change anything, right?
>
> Correct. But in that case, see:
>
> https://mail.sys4.d
On Mon, Sep 21, 2020 at 08:09:25AM +, pat...@patpro.net wrote:
> Just to ensure I've understood this well: if I'm using "3 1 1" I don't
> need to change anything, right?
Correct. But in that case, see:
https://mail.sys4.de/pipermail/dane-users/2018-February/000440.html
which describes
Hello,
Just to ensure I've understood this well: if I'm using "3 1 1" I don't need to
change anything, right?
thanks
patpro
September 21, 2020 9:49 AM, "Viktor Dukhovni"
wrote:
> On Mon, Sep 21, 2020 at 04:22:42AM -0200, Viktor Dukhovni wrote:
>
>> Links to the actual certificates can be fo
On Mon, 21 Sep 2020, Dan Mahoney (Gushi) wrote:
Figured it out.
Turns out with a virtual domain, you still need to point it somwhere, and
the reject map needs to match the RIGHT HAND SIDE of that map, not the
left.
In my case, I pointed it at webmaster@localhost, and updated the
recipient_m
On Mon, Sep 21, 2020 at 04:22:42AM -0200, Viktor Dukhovni wrote:
> Links to the actual certificates can be found at:
>
> https://letsencrypt.org/certificates/
> https://letsencrypt.org/certs/lets-encrypt-r3.pem
> https://letsencrypt.org/certs/lets-encrypt-e1.pem
>
> The "2 1 1"
On Mon, 21 Sep 2020, Koga Hayashi wrote:
Dan,
-Original Message-
From: owner-postfix-us...@postfix.org On
Behalf Of Dan Mahoney (Gushi)
Sent: Monday, September 21, 2020 10:29 AM
To: postfix-users@postfix.org
Subject: Custom reject message for one address?
Hey there all,
At the dayjo
20 matches
Mail list logo
