> > I am testing a simple header_check that uses PREPEND to add a custom > > header >to >
> > messages. > > > > 1) I *always* want to add the header, so the detected header in the rule >doesn't > > > matter so much. Does anyone have advice for the best header to detect so > > I > > won't miss any messages? Is /^From:/ the best? Or maybe /^Date:/ ....? > > > > Anyhow, my PREPEND is working fine as a header_check in main.cf, but when I >put > > > it in master.cf in a smtpd listener that picks up mail from my content >filter, > > > it seems to be ignored completely. > > According to header_checks(5) this is implemented by the cleanup > server. header/body_checks are documented as parameters on the > cleanup(8) manpage. They are not documented as parameters on the > smtpd(8) manpage. > > All this confirms that header/body_checks are a cleanup(8) > feature, not an smtpd(8) feature, Meaning, it's pointless > to specify this on the smtpd(8) command line. OK, sorry again. I had assumed because you can turn off header checking by using receive_override_options, you could also override (change) them. Reading smtpd(8) manpage, it does seem like smtpd_data_restrictions would be a good place to be able to inspect the mail headers and use the PREPEND to insert a new header. But I was using check_client_access to do so, and that only seems to inspect the client address and related information.... but looking through the list of restrictions I cannot understand which one allows the inspection of the message data itself.
