On 08/11/2020 22:15, Michael Haardt via Exim-users wrote:
If the documentation stated that somehow, it would ease migrations.
Suggestions for (wording and where to put it) welcome.
The generic discussion how a router works sounds like a good place
to me for giving a hint on the intended
Jeremy Harris via Exim-users wrote:
> On 08/11/2020 14:47, Michael Haardt via Exim-users wrote:
> > In the old days, that was the standard way of matching. Then conditions
> > were added, many people switched to them, and now we go back to the old
> > domains/local_parts way, because that sets
On 08/11/2020 14:47, Michael Haardt via Exim-users wrote:
In the old days, that was the standard way of matching. Then conditions
were added, many people switched to them, and now we go back to the old
domains/local_parts way, because that sets the *_data variables.
If the documentation stated
> I think I have have gotten my head around this now ...
Yes, you got the structure right.
> I have a global domain list:
> which I already use for routing non-local domains to our outgoing relays
> (smart hosts). I can reference this in again in each router.
>
> ... and I don't need a
Ok,
I think I have have gotten my head around this now ...
I have a global domain list:
#
# local_domains -> domains that land here
#
domainlist local_domains = ${lookup mysql{SELECT domain FROM domains
WHERE type='local' AND active='1'}{${sg{$value}{\\n}{ : }} }}
which I already use for
On 08/11/2020 12:12, Andrew C Aitchison via Exim-users wrote:
On Sun, 8 Nov 2020, Mike Tubby via Exim-users wrote:
Now it looks like I have to use additional look-ups, perhaps
something like this:
$domain_data = ${lookup mysql{SELECT domains.domain AS domain FROM \
On Sun, 8 Nov 2020, Mike Tubby via Exim-users wrote:
Now it looks like I have to use additional look-ups, perhaps something like
this:
$domain_data = ${lookup mysql{SELECT domains.domain AS domain FROM \
users LEFT JOIN domains ON users.domain_id=domains.id WHERE \
On 07/11/2020 23:30, Michael Haardt via Exim-users wrote:
Ok, have had a 5 minute scan read ... seems that tainted data is a
{potential} problem, but in my case the variables that I use to build a
path in transport 'local_delivery':
[...]
have already been used as keys in a database look-up
On 07/11/2020 23:30, Michael Haardt via Exim-users wrote:
Previously, a single lookup that checked both local part and domain to
let the router match was popular. Now that's fighting against the design.
Use two lookups, one for local_parts and one for domains, even if both
perform the same
> Ok, have had a 5 minute scan read ... seems that tainted data is a
> {potential} problem, but in my case the variables that I use to build a
> path in transport 'local_delivery':
> [...]
> have already been used as keys in a database look-up previously in the
> router that cause the transport
On 07/11/2020 22:45, Mike Tubby via Exim-users wrote:
Basically 'tainted as default' unless you turn it back off ...?
Sigh. You should preferably actually check that the
values exist in your database.
Yes, you can game it. Don't be so stupid.
--
Cheers,
Jeremy
--
## List details at
On 07/11/2020 20:54, Jeremy Harris via Exim-users wrote:
On 07/11/2020 20:43, Mike Tubby via Exim-users wrote:
What do I need to know to fix this one?
Either
- read back through exim-users, which has amply covered tainting
or
- start by hauling up the concept index in the docs, and search
On 07/11/2020 20:43, Mike Tubby via Exim-users wrote:
What do I need to know to fix this one?
Either
- read back through exim-users, which has amply covered tainting
or
- start by hauling up the concept index in the docs, and search on
the string "taint. Then , if that doesn't answer your
All,
So you can tell its Lockdown 2.0 as I am catching up with email server
sysadmin, updating spam scanning and antivirus ready for when the
thought police visit next month.
I have been running Exim 4.93.0.4 successfully with virtual domains with
a MySQL backend in first-normal form and
14 matches
Mail list logo
