On 30/09/2024 19:41, Jim Fenton via Exim-users wrote:
> I’m switching over from procmail to sieve for server-side mail filtering. Sieve apparently doesn’t see the header fields added in the router, so it’s not refiling my spam messages properly.
I assume you mean a filter run by a redirect router that happens to be
a Sieve filter, as opposed to something external to Exim.
Yes, headers added by routers are not combined with the message
until transmission by a transport.
I wonder if the purview of $headers_added could be expanded to cover
this case? Would that be of interest?
> I’m guessing that my approach of adding the header fields in the router is the problem here and I need to go back to adding the header fields in acl_check_data. Should I remove the spam header fields in outgoing routers, or am I over concerned about that?
That comes down to how much info leakage you care about; what situations
versus whether you could avoid adding them in the first place. Unfortunately,
the latter seems to end up with duplicating the routing logic in ACLs...
so yes, just stripping internal headers on outbound transports may well be the
simpler option.
--
Cheers,
Jeremy
--
## subscription configuration (requires account):
##
https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/
## unsubscribe (doesn't require an account):
## exim-users-unsubscribe@???
## Exim details at
http://www.exim.org/
## Please use the Wiki with this list -
http://wiki.exim.org/
