> On May 10, 2022, at 5:57 PM, Martin Gregorie <mar...@gregorie.org> wrote: > > On Tue, 2022-05-10 at 17:29 -0600, Philip Prindeville wrote: >> >> You're correct that they're different in every message received. >> > So write a rule that fires on any header name that *doesn't* match > anything in the list of legit headers as defined in the relevant RFCs. See my original message. I can't think of a single way to match each header, and then test for any of them not matching the pattern... > > Of course you may need to extend that list to include some extras, such > as headers injected by SA itself, as well as DMARC, DKIM, SPF etc. That's the easy part. > > Martin > >
- Re: Rule to detect non-standard headers that aren'... Philip Prindeville
- Re: Rule to detect non-standard headers that a... Martin Gregorie
- Re: Rule to detect non-standard headers th... Philip Prindeville
- Re: Rule to detect non-standard header... Martin Gregorie
- Re: Rule to detect non-standard header... Henrik K
- Re: Rule to detect non-standard h... Henrik K
- Re: Rule to detect non-standa... Henrik K
- Re: Rule to detect non-standa... Philip Prindeville
- Re: Rule to detect non-standa... Henrik K
- Re: Rule to detect non-standard h... Philip Prindeville
- Re: Rule to detect non-standard headers th... Philip Prindeville
- Re: Rule to detect non-standard headers that aren't X- ... Loren Wilton
- Re: Rule to detect non-standard headers that aren't X- ... Bill Cole
- Re: Rule to detect non-standard headers that aren't X- ... John Hardin
- Re: Rule to detect non-standard headers that aren'... Philip Prindeville