On April 12, 2023 2:00:01 PM UTC, Steffen Nurpmeso via Postfix-users <postfix-users@postfix.org> wrote: >Matus UHLAR - fantomas wrote in > <zdaiapmc+64tv...@fantomas.sk>: > |On 12.04.23 12:41, Fourhundred Thecat via Postfix-users wrote: > ... > |>Does it mean that I should either: > |> > |> 1) create SPF record for mail.mydomain.com > ... > |I would do the first: > | > |fantomas.fantomas.sk descriptive text "v=spf1 a -all" > >Interesting this still works for you. I had to change to ~all >because some behind-alias-expansion-and-forward collocutor >de-facto uses a GMail address. Just three weeks ago on the LUGA >ML that also came up > > | host gmail-smtp-in.l.google.com said: 550-5.7.26 The MAIL FROM > | domain [....] has an SPF record with a hard fail 550-5.7.26 policy > | (-all) but it fails to pass SPF checks with the ip: > >My (earlier own) communication then ended with > > |> 2015. Changing to ~all could be done, i do not know if Google > |> gets that. > | > |Google may have been ignoring your -all until recently. > > Google seems to have been laxe regarding FreeBSD forwarding. > I have cloned https://github.com/roehling/postsrsd.git to have > a look at it.
Generally the interoperability issues that can arise with SPF for Mail From don't come up with HELO. I don't think I've ever heard of a problem with -all for HELO. For Mail From, some people have issues, as you describe. Scott K _______________________________________________ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org