Hi, I have a system that received mail from a webmail product that adds a X-Originating-IP header with the IP of the webmail user.
Since Spamassassin for some reason considers that to be a Received-header that results in all mails from the webmail hitting the RDNS_NONE rule (only IP is added in the header) which I currently have set to 0 due to this. It also impacts how I can use the trusted_networks setting on my mx:es. If my mailrelays are trusted then the first "received" will be an untrusted IP and, since it's likely a residential IP, likely listed in spamhaus PBL... Which all leads me to my question. Is there some way I can configure Spamassassin to not consider X-Originating-IP to be a received-header? -- BR/Mvh. Dan Malm, Systems Engineer, One.com
