Sorry yes, penny drop now..
Jonathan
> On 26 Nov 2020, at 15:06, RW wrote:
>
> On Thu, 26 Nov 2020 10:39:29 +
> Jonathan Gilpin wrote:
>
>> The header: x-originating-ip: [86.129.191.88]
>>
>> is being put in by office 365.. it is already in when our e
relay.
>
> But yeah I don't know where that x originating IP header is coming from.
> What are you using as your glued implement spam assassin?
>
>
>
>
> On Wed, Nov 25, 2020, 09:05 Jonathan Gilpin <mailto:jonat...@fluent.ltd.uk>> wrote:
>
>
eaders.. so is this a setup error on my part or a
spam-assassin change? or a mistake?
Obviously I need to resolve/stop this to reduce false positives..
Kind Regards,
Jonathan Gilpin
Full headers are:
Return-path:
Envelope-to: jonat...@fluent.ltd.uk
Received: from [40.107.8.121] (port=
found
anyone using spamassassin that is not getting the same result
Jonathan
> On 23 Jan 2020, at 13:46, Dominic Raferd wrote:
>
>
>
> On Thu, 23 Jan 2020 at 13:06, Jonathan Gilpin <mailto:jonat...@fluent.ltd.uk>> wrote:
> Hi,
>
> It seems that SpamAsassin is
Has anyone come across this before or can someone give any advise of what the
cause of this might be? most importantly how to fix it?
Kind Regards,
Jonathan Gilpin
fluent Ltd
www.fluent.ltd.uk <http://www.fluent.ltd.uk/>
