X-SA-Do-Not-Run is not added by SA-Exim; it's something the README suggested that the user adds in the ACLs to prevent scanning of some messages. The comments in the default config file recommends using ACL variables instead. X-SA-Exim-Version and X-SA-Exim-Scanned are always added, but aren't that sensitive, and may be useful for debugging. X-SA-Exim-Rcpt-To, X-SA-Exim-Mail-From, and X-SA-Exim-Connect-IP are only added if SAaddSAEheaderBeforeSA is set to 1 in sa-exim.conf, which it is by default, though. They should be removed from all mail, both remote and local, which is why I prefer doing it in the system filter. A future sa-exim version will likely handle greylisting internally instead of in a SpamAssassin plugin.
exim4 shouldn't have to adapt to various specific packages that depend on it, but it isn't too easy for a package like sa-exim to just drop a configuration snippet in /etc/exim4/conf.d that will take care of removing the headers. system_filter doesn't seem to be used in the default config though, so I *could* hijack that mechanism by shipping a filter file and setting system_filter to point at it directly after the place I set local_scan_path. Very ugly. Perhaps a system_filter.d directory, whose contents would either be concatenated into /var/lib/exim4/system_filter.autogenerated, or processed sequentially by Exim (patch needed)? -- Magnus Holmgren [EMAIL PROTECTED]
pgpm4UJmjwKkl.pgp
Description: PGP signature
