Re: [exim] SPF issue: acting like -all when ~all

2017-12-18 Thread Sander Smeenk via Exim-users
Quoting Jonathan Gilpin via Exim-users (exim-users@exim.org): > 2017-12-14 13:09:26 H=smtp1.galacsys.net [217.24.81.209] > X=TLSv1:DHE-RSA-CAMELLIA256-SHA:256 CV=no > F= rejected RCPT : SPF > check failed Even though this was already tracked back to

Re: [exim] SPF issue: acting like -all when ~all

2017-12-16 Thread James Gibbard via Exim-users
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@exim.org> wrote: > Now that explains why this hasn’t come up before, thanks a lot. Their SPF > record was indeed invalid. > > I can’t

Re: [exim] SPF issue: acting like -all when ~all

2017-12-15 Thread Jonathan Gilpin via Exim-users
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

Re: [exim] SPF issue: acting like -all when ~all

2017-12-15 Thread Jeremy Harris
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= > rejected RCPT : SPF check failed > sibarth.com descriptive text "v=spf1

[exim] SPF issue: acting like -all when ~all

2017-12-15 Thread Jonathan Gilpin via Exim-users
Log Entry: 2017-12-14 13:09:26 H=smtp1.galacsys.net [217.24.81.209] X=TLSv1:DHE-RSA-CAMELLIA256-SHA:256 CV=no F= rejected RCPT : SPF check failed exim configure file: denymessage = $sender_host_address is not allowed to send mail from