Re: [exim] exiqgrep stops to work
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 now i was surprised by exiqgrep behaviour change, thus my question was generic. >exiqgrep -i -f.* Yes, i found this working already, while i cannot get why that is better than no filter at all. >exipick -i- Yes, that is equivalent, and it works (i guess that leading - is typo). Problem is, that in both cases i have to change my scripts on upgrade... regards -- Slavko https://www.slavino.sk/ -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
Re: [exim] exiqgrep stops to work
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 now, instead > of IDs as in 4.94. I found that at least the -c or -h option have to be > used. Wen i try to add the required -c, it returns line with count: > > exiqgrep -ci > > Please, how to get IDs list now? > exipick -i ? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
[exim] exiqgrep stops to work
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 to be used. Wen i try to add the required -c, it returns line with count: exiqgrep -ci Please, how to get IDs list now? regards -- Slavko https://www.slavino.sk pgpdkIdAzxl4I.pgp Description: Digitálny podpis OpenPGP -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
Re: [exim] User filters with file lookups in file from domain
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 being done for all of your users,
or for some large class, you could move the
processing into your mainline config rather
than needing a filter?
Or, you could set up a suitable variable
with this lookup result, done once in the
mainline config, for use by the filter.
You said "user filter" so presumably this
is being called by a redirect router; if
so then a $r_ variable created by a
"set" option on that router seems ideal.
--
Cheers,
Jeremy
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
Re: [exim] Routing based on sender and recipient
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 https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
Re: [exim] Message size condition in a router?
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 valid in a router. -- Cheers, Jeremy -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
Re: [exim] Solved: Routing based on sender and recipient
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 [mailto:exim-users-bounces+tt-admin=intranett...@exim.org] Im Auftrag von tt-admin via Exim-users Gesendet: Mittwoch, 4. Januar 2023 06:32 An: exim-users@exim.org Betreff: [exim] Routing based on sender and recipient Good Morning, we need to route some mail traffic based on sender AND recipient if that's possible. Configuration as of now: Everything from * to @example.com goes to 10.10.10.10 myrouter: driver = manualroute domains = example.com transport = remote_smtp route_list = * 10.10.10.10 What we tried: #testrouter: # driver = manualroute # senders = import...@example.net # domains = example.com # transport = remote_smtp # route_list = * 192.168.178.1 What we need: Everything from import...@example.net AND to f...@example.com---> 192.168.178.1 Everything else from import...@example.net should still go to 10.10.10.10. So we need to take one sender address, and route everything from that sender address to a defined list of recipients on 192.168.178.1, while everything else from that sender should still go to 10.10.10.10. Example with two addresses, that we want to route in a different way: >From import...@example.net and to f...@example.com --> 192.168.178.1 >From import...@example.net and to f...@example.com --> 192.168.178.1 >From import...@example.net and to r...@example.com --> 10.10.10.10 I see routers can decided based on domains and based on senders, but i don't see they can decide based on senders AND recipients. Have a nice day! -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/ -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
[exim] Message size condition in a router?
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 sending service for 1 domain on a multi-domain server
and have that router & transport working. But I wanted to add another condition
to the router that if a message size is over 1Mb, I want it to skip the email
sending service and continue to the default server for delivery. Thanks for any
ideas!
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
[exim] User filters with file lookups in file from domain
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 one or more files
for each domain with the local part as key.
For example, I have an optional file $home/.mail/alias/$domain-bounce file
which lists local parts which should be bounced immediately, with a
$home/.mail/alias/default-bounce fallback, and the current test for that is:
if
"${lookup{$original_local_part}lsearch{${if
exists{$home/.mail/alias/$original_domain
-bounce}{$home/.mail/alias/$original_domain-bounce}{$home/.mail/alias/default-bounce}}}{
$value} {}}"
matches "^(..*)\\$"
then
pipe "$home/.mail/scripts/bounce-mail"
finish
endif
My best effort at making it taint-safe (and a bit more readable) is:
"${lookup {$original_local_part} \
lsearch{\
${if exists{$home/.mail/alias/$original_domain-bounce} \
{${lookup {$original_domain-bounce} dsearch,ret=full
{$home/.mail/alias}}} \
{$home/.mail/alias/default-bounce}}} \
{$value} {}}"
It's annoyingly repetitive (and with several similar lookups I'm likely to make
a copy-paste error somewhere!), and wrapping the dsearch lookup with `if
exists` seems wrong, but seems necessary to avoid having the lsearch fail the
whole filter if this file doesn't exist. A "dsearch with default on fail"
would help.
Am I missing some better way to do this? I can change the way the lookup files
are organised if I have to, but I'd rather not to avoid accidentally breaking
anything!
Thanks,
Chris
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
