On Wed, May 24, 2023 at 01:07:06PM +0200, Sander Smeenk via Exim-users wrote:
> Quoting Evgeniy Berdnikov via Exim-users (exim-users@???):
>
> > I treat the change of target domain as Exim's bug and tried to reproduce it
> > for test alias chains, with no success. But it definitely triggers for
> > email.postcodeloterij.nl, that's intriguing.
>
> Another example: 'foobar@???' also gets the same treatment and
> reroutes to 'foobar@???'.
>
> The commonality in DNS here is the MX-lookup returns:
> originaldomain IN CNAME newdomain
> newdomain IN CNAME otherdomain
> otherdomain IN MX targethost
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:
# host email.tedisk.ru.
email.tedisk.ru is an alias for email.protva.ru.
email.protva.ru is an alias for email.ascit.ru.
email.ascit.ru is an alias for tedisk.ru.
tedisk.ru has address 176.32.35.178
tedisk.ru mail is handled by 10 mx2.tedisk.ru.
tedisk.ru mail is handled by 20 mx3.tedisk.ru.
# exim4 -bt dummy@???
...
dummy@???
<-- dummy@???
router = dnslookup, transport = remote_smtp
host mx2.tedisk.ru [176.32.35.178] MX=10
host mx3.tedisk.ru [45.144.2.235] MX=20
--
Eugene Berdnikov
--
## 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/
