Re: [exim] Wildcards in aliases

On 13/02/18 11:07, Mike Brudenell via Exim-users wrote: > (I think Exim uses PCRE if memory > serves?) Yes. -- ## 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] Filter behavior when run from shell vs systemd

Gabe da Silveira via Exim-users (Di 13 Feb 2018 08:23:17 CET): > Hi all, > > I'm setting up exim to process emails based on the existence of a set of > centrally managed forward files. So I have an accept router configured as > follows: How did you test and what was the

Re: [exim] Wildcards in aliases

Please forgive me veering off topic a little for a moment, but in case it helps you Hardy I find these two web sites really useful for testing various flavours of regular expressions. (I think Exim uses PCRE if memory serves?) - https://www.debuggex.com/?flavor=pcre -

[exim] Filter behavior when run from shell vs systemd

Hi all, I'm setting up exim to process emails based on the existence of a set of centrally managed forward files. So I have an accept router configured as follows: email_address_check: driver = accept condition = ${if exists{DOMAINS_DIR/$domain/$local_part/forward}} verify_only The

Re: [exim] Wildcards in aliases

Thank you Heiko and Merlin, lookups are my really weak point ;-) and my lack on a grasp on regex hampers me even more. I know I should change this on the long run, but for now your short term help is very much appreciated... A one-time change to the conf is acceptable, of course. I had hope

Re: [exim] Wildcards in aliases

Mike Brudenell via Exim-users (Di 13 Feb 2018 12:07:56 CET): > Please forgive me veering off topic a little for a moment, but in case it > helps you Hardy I find these two web sites really useful for testing > various flavours of regular expressions. (I think Exim uses PCRE

Re: [exim] Wildcards in aliases

On Tue, 13 Feb 2018, Hardy via Exim-users wrote: Hi folks, my aim is to have something in the way of myname.*: myname for the local user myname, if this is possible to do in the alias file. I would rather like to have it here than to change the conf. Possible? I wonder whether you are

Re: [exim] Filter behavior when run from shell vs systemd

Hello, It might be selinux that's preventing access to that file. try running setenforce 0 and see if the error goes away. Marius On 13/2/2018 9:23 AM, Gabe da Silveira via Exim-users wrote: Hi all, I'm setting up exim to process emails based on the existence of a set of centrally managed

Re: [exim] Wildcards in aliases

Hardy via Exim-users (Di 13 Feb 2018 11:40:11 CET): … > data = ${lookup{$local_part}dbm{/etc/exim/$domain.aliases.db}} > > Can I still do what I want with dbm, and how would I write the alias file > for entries meaning > > myname[digits]: myname As far as I know, DBM

Re: [exim] Wildcards in aliases

Hardy via Exim-users (Di 13 Feb 2018 09:44:38 CET): > Hi folks, > > my aim is to have something in the way of > > myname.*: myname > > for the local user myname, if this is possible to do in the alias file. I > would rather like to have it here than to change the conf.

Re: [exim] Wildcards in aliases

Or even full expansion options - which puts huge power into the aliases file: data = ${expand:${lookup{$local_part}lsearch{/etc/aliases}}} Hope this is useful! Merlin -- Merlin Hartley Computer Officer MRC Mitochondrial Biology Unit University of Cambridge Cambridge, CB2 0XY United Kingdom >

[exim] OCSP stapling with multiple keys {ECDSA/RSA}

Hi, I asked in the past, if OCSP stapling can also be made with a list. This part of code implementation is still not done for actual openssl or gnutls implementations. I found now a way to do it with plain config: tls_certificate = ecdsa_chain.pem:rsa_chain.pem tls_privatekey =

[exim] Wildcards in aliases

Hi folks, my aim is to have something in the way of myname.*: myname for the local user myname, if this is possible to do in the alias file. I would rather like to have it here than to change the conf. Possible? Hardy -- ## List details at

Re: [exim] Exim-users Digest, Vol 165, Issue 9 [verification failed - body hash mismatch]

On 2018-02-12 at 18:53 -0500, Phil Pennock via Exim-users wrote: > > On 12/02/18 12:12, Martin Nicholas via Exim-users wrote: > > > I notice this from "Exim-users Digest, Vol 165, Issue 9": > I've subscribed another address to the mailing-list, in digest mode, to > see what happens next time.

Re: [exim] Filter behavior when run from shell vs systemd

On Tue, Feb 13, 2018 at 4:15 AM, Marius Stan via Exim-users < exim-users@exim.org> wrote: > It might be selinux that's preventing access to that file. > try running setenforce 0 and see if the error goes away. > That was it! This is the third time selinux has had me scratching my head,

Re: [exim] [META/OT] DKIM sender rewriting [Was: TLS error in incoming emails from *.outlook.com]

On 2018-02-12 at 19:45 -0800, Ian Zimmerman via Exim-users wrote: > I note with horror that now I am also a 'via Exim-users' despite > intentionally NOT using DKIM for list messages, including this one. > Why? Is the rewriting now done regardless? Yes. I don't know who/why. from_is_list has

[exim] lowest numbered MX record points to local host

Hi, I have two routers: dnslookup: driver = dnslookup # domains = ! +local_domains # check mx for all domains transport = remote_smtp ignore_target_hosts = 0.0.0.0 : 127.0.0.0/8 self = pass no_more localuser: driver = accept condition = ${lookup sqlite {...}{yes}{no}} transport

Re: [exim] lowest numbered MX record points to local host

Because exim4 by default disallows delivery to local host to prevent mail loops. When remote delivery fails, delivery will be attempted to a local user. Thats why it doesn't fail with a valid user. The ! +local_domains skips this router for local users, so remote delivery isn't even attempted

Re: [exim] Wildcards in aliases

On 13.02.2018 13:14, Andrew C Aitchison via Exim-users wrote: > On Tue, 13 Feb 2018, Hardy via Exim-users wrote: >> my aim is to have something in the way of >> >> myname.*: myname >> > > I wonder whether you are trying to implement a feature > already explicitly supported in exim ? > > If you