The Exim SPF docs page on Github describes how to handle perm errors
amongst others.
On Friday, December 15, 2017, Jonathan Gilpin via Exim-users <
exim-users@???> wrote:
> Now that explains why this hasn’t come up before, thanks a lot. Their SPF
> record was indeed invalid.
>
> I can’t help but think that since it has a soft-fail with ~all it should
> have failed safe not failed-failed but in any case, it is right that exim
> expects the SPF record to be valid.
>
> Jonathan
>
> > On 15 Dec 2017, at 10:46, Jeremy Harris <jgh@???> wrote:
> >
> > On 15/12/17 10:19, Jonathan Gilpin via Exim-users wrote:
> >> 2017-12-14 13:09:26 H=smtp1.galacsys.net [217.24.81.209]
> X=TLSv1:DHE-RSA-CAMELLIA256-SHA:256 CV=no F=<VillaManagement@???>
> rejected RCPT <jana@???>: SPF check failed
> >
> >
> >> sibarth.com descriptive text "v=spf1 ip4:192.254.220.186/24 include:
> mailwise.com include:galacsys.net include:electric.net include:
> mailanyone.net ~all"
> >>
> >> Since the SPF record shows ~all shouldn’t this mail have been allowed
> through as it is not a -all ? or is it my configuration that is incorrect?
> >
> > I'm no SPF expert, but this tool:
> >
> > http://www.kitterman.com/spf/validate.html
> >
> > says:
> >
> > Results - Permanent Error SPF Permanent Error: No valid SPF record for
> > included domain: galacsys.net: include:galacsys.net
> >
> > --
> > Cheers,
> > Jeremy
> >
> > --
> > ## List details at https://lists.exim.org/mailman/listinfo/exim-users
> > ## Exim details at http://www.exim.org/
> > ## Please use the Wiki with this list - http://wiki.exim.org/
>
>
> --
> ## List details at https://lists.exim.org/mailman/listinfo/exim-users
> ## Exim details at http://www.exim.org/
> ## Please use the Wiki with this list - http://wiki.exim.org/
>
