On 7 Jun 2019, at 12:52, Niamh Holding wrote:
Hello RW,
Friday, June 7, 2019, 5:21:01 PM, you wrote:
R> This is the reason:
R>
X-Originating-IP: 162.208.32.167
R> Perhaps the rule should be modified to test for by=\S
It's certainly not a Received: header so should not be checked.
You are free to change this locally. See the documentation of
originating_ip_headers (perldoc Mail::SpamAssassin::Conf)
SA uses X-Originating-IP and the other headers specified in
originating_ip_headers to synthesize a logical relay event because in
many cases that can be an accurate representation of how a message was
initially submitted to the Internet mail system. Unfortunately, there's
no specification that defines what exactly X-Originating-IP *means* so
when it is used in a manner that isn't consistent with the usage in
common webmail systems, there is a risk of SA misinterpreting it. It
looks like your own mail server is adding it in this case (because it is
amidst other headers added during local delivery) so it would make sense
to remove it from originating_ip_headers locally.
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire
