[exim] Re: SEGV_MAPERR

2023-10-27 Thread Jeremy Harris via Exim-users
On 27/10/2023 04:12, Julian Waters via Exim-users wrote: I haven’t raised a debian bug, I’m assuming it’s just my incompetence. That a segv can happen at all constitutes a bug, however it was triggered. Can you run with debug? This would have helped, but Can you get a coredump (note: Exim

[exim] Re: Destination address in a transport

2023-10-27 Thread Thomas Andrews via Exim-users
On 10/27/23 06:09, Jasen Betts via Exim-users wrote: On 2023-10-26, Thomas Andrews via Exim-users wrote: On 10/26/23 11:51, Jeremy Harris via Exim-users wrote: On 26/10/2023 10:11, Thomas Andrews via Exim-users wrote: The external program is delivering the email to another server for further 

[exim] Re: Routing based on *recipient* IP address

2023-10-27 Thread Gandalf Corvotempesta via Exim-users
Il giorno ven 27 ott 2023 alle ore 10:10 Jasen Betts via Exim-users ha scritto: > Yes, in your config use the dnslookup router for that smarthost use > ignore_target_hosts with an > inverted host list ( that is put a ! in front of it ) > > hostlist iran_ips = . > > iram_mx: >driver=dns

[exim] Re: Routing based on *recipient* IP address

2023-10-27 Thread Gandalf Corvotempesta via Exim-users
Il giorno ven 27 ott 2023 alle ore 10:10 Jasen Betts via Exim-users ha scritto: > Yes, in your config use the dnslookup router for that smarthost use > ignore_target_hosts with an > inverted host list ( that is put a ! in front of it ) > > hostlist iran_ips = . > > iram_mx: >driver=dns

[exim] Re: Routing based on *recipient* IP address

2023-10-27 Thread Gandalf Corvotempesta via Exim-users
Il giorno ven 27 ott 2023 alle ore 10:07 Kirill Miazine via Exim-users ha scritto: > You'd have to do MX lookup, yes (as the example in the docs show), but > then dnslists would do the matching for you. I'd say it's easier to use > an existing matching facility, rather than re-implementing it (and

[exim] Re: SEGV_MAPERR

2023-10-27 Thread Julian Waters via Exim-users
Thanks for the replies. I don’t fully understand everything you asked but as much as i’ve been able to figure out is pasted below. Also the config incase there’s an obvious issue there. I haven’t raised a debian bug, I’m assuming it’s just my incompetence. Any assistance deeply appreciated.

[exim] Re: Destination address in a transport

2023-10-27 Thread Jasen Betts via Exim-users
On 2023-10-26, Thomas Andrews via Exim-users wrote: > On 10/26/23 11:51, Jeremy Harris via Exim-users wrote: >> On 26/10/2023 10:11, Thomas Andrews via Exim-users wrote: >>> The external program is delivering the email to another server for >>> further processing. >> >> If that's all it is doing,

[exim] Re: Routing based on *recipient* IP address

2023-10-27 Thread Jasen Betts via Exim-users
On 2023-10-26, Gandalf Corvotempesta via Exim-users wrote: > Hi guys > > TL;DR: how can i route, to a specific smarthost, all email based on > the *recipient* mx IP address ? Yes, in your config use the dnslookup router for that smarthost use ignore_target_hosts with an inverted host list ( th

[exim] Re: Routing based on *recipient* IP address

2023-10-27 Thread Kirill Miazine via Exim-users
• Gandalf Corvotempesta [2023-10-27 09:44]: Il giorno ven 27 ott 2023 alle ore 09:30 Kirill Miazine via Exim-users ha scritto: Have you considered using the dnslists ACL condition and set an appropriate ACL message variable to check in a router? There's an example at the end of section 30 for h

[exim] Re: Routing based on *recipient* IP address

2023-10-27 Thread Lena--- via Exim-users
> From: Gandalf Corvotempesta > # exim -be '${lookup dnsdb{>; a+=${lookup dnsdb{>; mxh=gmail.com' Must be : instead or ; before mxh. -- ## subscription configuration (requires account): ## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/ ## unsubscribe (doesn't r

[exim] Re: Routing based on *recipient* IP address

2023-10-27 Thread Gandalf Corvotempesta via Exim-users
Il giorno ven 27 ott 2023 alle ore 09:17 Gandalf Corvotempesta ha scritto: > As you can see here, with some hosts the MXs are returned properly > (even with IPv6, i've cheded), > but with some others, don't. (it also fails on some of my domains). Any clue ? > > It's the "a+" lookup that fails, the

[exim] Re: Looking for generic tutorial for implementing SMTP AUTH against LDAP

2023-10-27 Thread Alan Hicks via Exim-users
On 27/10/2023 05:24, Mihamina RKTMB via Exim-users wrote: Hi all, I want to setup an Exim SMTP AUTH server, where my users are in a POSIX compliant LDAP. I am running ArchLinux, so a generic tutorial would be fine (Debian specific ones need some transformations to remove the Debians package

[exim] Re: Routing based on *recipient* IP address

2023-10-27 Thread Gandalf Corvotempesta via Exim-users
Il giorno ven 27 ott 2023 alle ore 09:30 Kirill Miazine via Exim-users ha scritto: > Have you considered using the dnslists ACL condition and set an > appropriate ACL message variable to check in a router? There's an > example at the end of section 30 for how to query dnslists for multiple > expli

[exim] Re: Routing based on *recipient* IP address

2023-10-27 Thread Kirill Miazine via Exim-users
• Kirill Miazine via Exim-users [2023-10-27 09:26]: The countries.nerd.dk zone contains two-letter ISO 3166 country-code subdomains you can use to determine whether an IP is from that particular country. ah, the list doesn't seem to be active anymore... :( -- ## subscription configuration (re

[exim] Re: Routing based on *recipient* IP address

2023-10-27 Thread Kirill Miazine via Exim-users
• Gandalf Corvotempesta via Exim-users [2023-10-27 08:40]: Il gio 26 ott 2023, 21:22 Kirill Miazine via Exim-users < exim-users@lists.exim.org> ha scritto: Maybe you could solve the task at a lower level, e.g. use operating system's networking facilities e.g. to redirect connections to port 25

[exim] Re: Routing based on *recipient* IP address

2023-10-27 Thread Gandalf Corvotempesta via Exim-users
Il giorno gio 26 ott 2023 alle ore 18:43 Jeremy Harris via Exim-users ha scritto: > Run it seperately using "-be" expansion-test mode As you can see here, with some hosts the MXs are returned properly (even with IPv6, i've cheded), but with some others, don't. (it also fails on some of my domains