In general you can have multiple filters and they operate in sequence. However, the "split:" filter should be last because any new messages that get split off will not have any of the later filters applied. That's the main reason that the "mx:" filter is run when forwarding (--client-filter), but it has the additional benefit that the IP address obtained from DNS is fully up-to-date. I don't see a problem in your case as long as your "net:" filter is specified first on the command-line or config...
Thanks -- switching to git and using separate feature branches has created quite a blockage for new releases. I'm not sure the complexity is justified for a one-man project, but it has been interesting keeping up with more modern development tools and methods. I have pushed all the feature branches to github, and also the merged release/v2.7 branch, which has a version number of 2.7rc1. I have also updated the emailrelay-build github repository and it has spat out windows build: https://github.com/graeme-walker/emailrelay-build/actions/runs/35090842782/artifacts/10446095744...
Merge branches 'feature/git-support', 'feature/icon-refresh', 'feature/sphinx-not-doxygen', 'feature/updated-build-scripts', 'feature/nowide-update', 'feature/poll-run', 'fix/winxp-mbedtls3', 'fix/dpi-awareness', 'fix/windows-tidy', 'fix/address-verifier-abort', 'fix/gui-translations', 'fix/maildir-delivery', 'fix/service-wrapper-cwd', 'feature/multiple-ports', 'feature/millisecond-timeouts', 'feature/small-build-update', 'task/version-2.7' into 'release/v2.7'
task: create new branch for version number update
task: create new branch for tidier small builds
task: revert DateTime namespace, add BRANCH.md
task: fix no-interfaces build, add BRANCH.md
task: create new branch to fix service wrapper