V_2_7_fixes branch from V_2_7 tag
I have finally released version 2.7, which includes the new "--poll-run" option. It also allows "--poll" to be used twice, with the the first value used for the interval between startup and the first poll. You can also now specify timeouts with "ms" for milliseconds (etc). The two built-in scripts for "--poll-run" are "unfail:" and "retry:" where unfail removes the ".bad" filename extensions from all envelope files, whereas retry will only do so up to five times for failure codes less that 500. I...
Thanks Graeme That's really good news to hear. The changes you are building into v2.7 would certainly solve my issue - I'm happy to beta test if that helps. Of course, I have a specific scenario here which I need logging for - I'm sure the ability to be flexible will be appreciated by many other users. Best wishes David From: feature-requests@emailrelay.p.re.sourceforge.net feature-requests@emailrelay.p.re.sourceforge.net On Behalf Of Graeme Walker Sent: 09 November 2026 01:42 To: [emailrelay:feature-requests]...
Thanks for the suggestion. I have made some progress on this for the 2.7 release. It is now possible to vary the verbosity of informational log messages based on their assigned log group using a new "--log-config" option. So for example you can reduce the verbosity of the "rx<<" and "tx>>" log messages, which are in the "io" log group, by using "--log-config=io-2". The "-2" cancels up to two "--verbose" options. Positive values have the effect of adding "--verbose" for those messages. It is also...
2.7 tag
2.7 to trunk
fix tests on windows
squash merge of branch release/v2.7 onto main
task: fix workflow build for winxp
task: extend admin interface for --log-config
less verbose
fix for filter=sleepms:n ms/us confusion
c++11
typos
make tidy
module to log-group
filter chains
hoist verbosity
fix
feature request reference
less is more
mx lookup verbosity
more
spaces
three bits of verbosity
filter verbosity
verbosity parsing
log modules
logoutput verbosity
module verbosity
filter verbosity
task: robustify make check wrt port numbers
fix: fix network interface code
task: tweak github workflow
task: improve build portability
task: improve documentation
task: improve poll-run usability and logging
task: clean up option parser
task: new branch, see BRANCH.md
task: update the test framework
task: update the test framework
task: make comments more consitent
task: implement more flexible logging [fr #45]
task: robustify make check wrt port numbers
fix: fix network --interface code
task: extend the github workflow
task: improve build portability for bsd
task: improve documentation
task: finish implementing --poll-run
task: bind windows null handles to the nul device
task: set version 2.7
task: build from workflow
task: de-duplicate readme files
task: regenerate options documentation
task: allow two --poll values
task: improve winbuildall.bat
task: improve make-sphinx
task: update licenses
task: update copyrights
fix: apply post-merge tweaks
now got it. --filter run when a mail message is stored. --client-filter run when a mail message is forwarded. so, MX filter must be client-filter, split must be filter . As you said network filter first, then the split filter, and finally the MX client filter; Final cmd args ; --filter="net:127.0.0.1:10101" --filter=split: --client-filter=mx:
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...
Using MX lookups and multiple filters
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
task: update, add BRANCH.md
task: create new branch for qt6 qtbase translations
task: update, add BRANCH.md
task: create new branch for windows clang-tidy
task: create new branch for WinAPI DPI awareness
task: create new branch for mbedtls v3 on winxp
task: revert millisecond-timeouts, add BRANCH.md
task: create new branch removing ansi build option
task: create new branch to update build scripts
update build scripts
task: create new branch for documentation update