On 10/30/2016 5:16 AM, Den1 wrote: > > You are saying that "there is only one action allowed per header". I guess > this is the reason why it does not work. My > /^User-Agent: .*/ IGNORE triggers > > and all the other rules like > /^Received: .*/ IGNORE > /^X-Originating-IP:/ IGNORE > and so on are not taken into account/consideration then and therefore do not > work, is that right?
One action per header line. header_checks wouldn't be very useful if it only allowed one entry for the entire header section. Surely this is clear in the documentation. > > Plus, you mentioned in your other post that header_checks and > smtp_header_checks if used together may mangle each other and conflict? Did No, that's not what I said. header_checks work on input. smtp_header_checks work during smtp delivery to a remote system. A separate statement: don't mangle headers that aren't yours. Although I'm somewhat dismayed you can't get your header_checks working, I'll remind you that Received: headers are extremely low-value in terms of information leakage. So this isn't really worth wasting any more time on. -- Noel Jones
