Quoting Evgeniy Berdnikov via Exim-users (exim-users@???):
> Yes, it seems bug is triggered by chain longer then one alias, and if
> dnslookup router is encountered in router chain. Here is my example:
>
> # exim4 -bt dummy@???
> dummy@???
> <-- dummy@???
Thanks!
Indeed it seems to be related to CNAME chains like in your situation and
the ones discussed before this. Another test i built myself, with just
one CNAME works just as expected:
| foo@www.yottabit.nl
| router = remote_nobatv, transport = remote_smtp
| host mx.yottabit.nl [213.136.8.74] MX=100
Where the MX-lookup looks like this:
| www.yottabit.nl. 286 IN CNAME yottabit.nl.
| yottabit.nl. 286 IN MX 100 mx.yottabit.nl.
Add another CNAME to the mix and presto:
| www.yottabit.nl. 300 IN CNAME quux.yottabit.nl.
| quux.yottabit.nl. 300 IN CNAME yottabit.nl.
| yottabit.nl. 300 IN MX 100 mx.yottabit.nl.
| $ exim4 -bt foo@www.yottabit.nl
| foo@???
| <-- foo@www.yottabit.nl
--
| If a chemist dies, you barium.
| 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2
--
## 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/
