Il giorno ven 27 ott 2023 alle ore 09:17 Gandalf Corvotempesta
<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 mxh is working properly.
>
> # exim -be '${lookup dnsdb{>; a+=${lookup dnsdb{>; mxh=gmail.com}}}}'
>
> # exim -be '${lookup dnsdb{>; a+=${lookup dnsdb{>; mxh=ansa.it}}}}'
>
> # exim -be '${lookup dnsdb{>; a+=${lookup dnsdb{>; mxh=microsoft.com}}}}'
> 104.47.53.36;104.47.54.36
> # exim -be '${lookup dnsdb{>; a+=${lookup dnsdb{>; mxh=tex.cu}}}}'
> 190.92.116.36
Found the issue: when the remote domain as multiple MXs, the dnsdb
lookup for "A/AAAA" records fails.
I need to use a forany on the mx list, but if I understood correctly,
the forany can be used only inside an IF
--
## subscription configuration (requires account):
##
https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/
## unsubscribe (doesn't require an account):
## exim-users-unsubscribe@???
## Exim details at
http://www.exim.org/
## Please use the Wiki with this list -
http://wiki.exim.org/
