Ahoj,
Dňa Sun, 23 Feb 2025 11:00:34 +0100 Heiko Schlittermann via Exim-users
<exim-users@lists.exim.org> napísal:
> And, of course, the format of the bogook file would change to include
> the full address or an asterisk as localpart:
This remind me one question, which i didn't ask ;-)
I have pipe transport (to process DMARC reports) as this:
reports_pipe:
driver = pipe
path = CONFDIR/scripts
temp_errors = *
...
Router which use it:
reports_dmarc:
driver = redirect
domains = +relay_to_domains
data = |process_dmarc.py /srv/mail/dmarcrep
pipe_transport = reports_pipe
...
The process_dmarc.py is my own script, which does some checks on
message before process it and returns some (various) return code on
defect. If that script returns error code, message stays in queue,
mostly to i can inspect if it is mistake in my script or garbage. It
works as expected for multiple years.
After i inspect report in queue i manually reject it (or i fix script),
but recently i decided to leave it as is, to be removed after queue
retry time is exceed and i start to play with retry rule for it to be
removed after shorten time, but i fail...
I found some dated post [1] about domain used in pipe (and file)
transports, which suggested, that pipe uses script name as domain,
starting with pipe symbol and without local_part, thus i tried to define
retry rule as this:
^\N\@\|.+$\N ...
Then i tried to test it with -brt option, that one finds right retry
rule:
exim -brt '@|process_dmarc.py'
Retry rule: ^\N\@\|.+$\N ...
But this returns default retry rule:
exim -brt '|process_dmarc.py'
Retry rule: * ...
Then i start to play with exinext, after some play with escaping and @ i
got:
exinext '\|process_dmarc.py'
No remote hosts found for \|process_dmarc.py
Transport: |process_dmarc.py error ...
command: /etc/exim4/scripts/process_dmarc.py
first failed: 21-Feb-2025 11:57:57
last tried: 21-Feb-2025 11:57:57
next try at: 22-Feb-2025 11:57:57
Now i do don't know which one is proper "address" to check in -brt,
in exinext nor in retry rule...
Please, can someone point me?
BTW, the dates in exinext output are interesting, in that time the
message was in queue about 5 days, but output shows first failed in
that day. Is that date reset after success delivery of other message?
[1] https://utcc.utoronto.ca/~cks/space/blog/sysadmin/EximLocalRetries
regards
--
Slavko
https://www.slavino.sk
--
## subscription configuration (requires account):
## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/
## unsubscribe (doesn't require an account):
## exim-users-unsubscr...@lists.exim.org
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
