Re: [exim] exiqgrep stops to work

2023-01-04 Thread Slavko via Exim-users
I got off list reply, continue in ML... Dňa 4. januára 2023 13:08:52 UTC používateľ Jeremy Harris napísal: >On 04/01/2023 12:05, Slavko via Exim-users wrote: >> exiqgrep -i > >You didn't say what use you'll be making of the info, >which could make for neater solutions. Perhaps, but for

Re: [exim] exiqgrep stops to work

2023-01-04 Thread Odhiambo Washington via Exim-users
On Wed, Jan 4, 2023 at 3:09 PM Slavko via Exim-users wrote: > Hi, > > i start to play with exim 4.96 (debian testing, if that matter) and i > cannot get exiqgrep to work. I want to retrieve message IDs in queue > with: > > exiqgrep -i > > but it returns help message only with return code 1

[exim] exiqgrep stops to work

2023-01-04 Thread Slavko via Exim-users
Hi, i start to play with exim 4.96 (debian testing, if that matter) and i cannot get exiqgrep to work. I want to retrieve message IDs in queue with: exiqgrep -i but it returns help message only with return code 1 now, instead of IDs as in 4.94. I found that at least the -c or -h option have

Re: [exim] User filters with file lookups in file from domain

2023-01-04 Thread Jeremy Harris via Exim-users
On 02/01/2023 11:52, Chris Emerson via Exim-users wrote: A "dsearch with default on fail" would help. ${lookup {$original_domain-bounce} dsearch,ret=full \ {$home/.mail/alias} \ {$home/.mail/alias/default-bounce} \ } Am I missing some better way to do this? If this is

Re: [exim] Routing based on sender and recipient

2023-01-04 Thread Jeremy Harris via Exim-users
On 04/01/2023 05:32, tt-admin via Exim-users wrote: What we tried: #testrouter: # driver = manualroute # senders =import...@example.net # domains = example.com # transport = remote_smtp # route_list = * 192.168.178.1 And what happened? -- Cheers, Jeremy -- ## List details at

Re: [exim] Message size condition in a router?

2023-01-04 Thread Jeremy Harris via Exim-users
On 04/01/2023 00:59, secure_1--- via Exim-users wrote: Is it possible to use a condition statement to evaluate message size in the routerstart? Not sure what you mean by "routerstart", but yes, except where the documentation says otherwise a variable that is valid in a transport will also be

Re: [exim] Solved: Routing based on sender and recipient

2023-01-04 Thread tt-admin via Exim-users
Found the solution by using "local_parts": # driver = manualroute # senders = import...@example.net # domains = example.com # local_parts = foo1: foo2 # transport = remote_smtp # route_list = * 192.168.178.1 -Ursprüngliche Nachricht- Von: Exim-users

[exim] Message size condition in a router?

2023-01-04 Thread secure_1--- via Exim-users
Hello all. Is it possible to use a condition statement to evaluate message size in the routerstart? I looked in the documentation but didn't find any variable for message size in the router, only transport. Something like condition = "${if !>{$message_size}{1000k}}" I use a 3rd party email

[exim] User filters with file lookups in file from domain

2023-01-04 Thread Chris Emerson via Exim-users
Hi, I have a user filter which has been (as far as I know!) working fine for many years, which I'm revisiting now that it trips the taint checks after an upgrade, as it involves `lsearch` lookups in files named after $original_domain. I receive e-mails to several domains to this user, and have