On Jun 19, 2019, at 04:56, Matt Anton wrote:
>
> IMHO, you should have put ‘-o milter_macro_daemon_name=ORIGINATING’ to
> services to let milters know the mail stream from authenticated connections
> is considered local.
That’s something to keep in mind, for sure, but I have one milter and I
On 19 Jun 2019, at 4:00, jdow wrote:
FORGED_MUA_MOZILLA is misfiring on my emails. You should be able to
see that in an SA run against this email since it seems to trigger on
all my emails.
Nope.
This may be specific to relays through groups.io.
Yep.
I've committed a fix that excludes
On Wed, 19 Jun 2019 01:00:43 -0700
jdow wrote:
> FORGED_MUA_MOZILLA is misfiring on my emails. You should be able to
> see that in an SA run against this email since it seems to trigger on
> all my emails. I am filtering with 3.004000 on a Scientific Linux 7.x
> system. I noticed this, finally,
On 18 Jun 2019, at 22:45, @lbutlr wrote:
> Solution was ridiculously simple.
>
> I added
>
> -o smtpd_milters=
> -o milter_connect_macros=
>
> To submission and smpts in master.cf
>
> (I doubt the second line is needed, but eh… it’s not going to hurt)
You did post on postfix-users how you
FORGED_MUA_MOZILLA is misfiring on my emails. You should be able to see that in
an SA run against this email since it seems to trigger on all my emails. I am
filtering with 3.004000 on a Scientific Linux 7.x system. I noticed this,
finally, today when an email to a mailing list came back and
