On Wed, Oct 31, 2012 at 7:12 AM, Cyborg <[email protected]> wrote: > # exim -bt [email protected] > [email protected] -> /path/to/Maildir/ > transport = address_directory > [email protected] > <-- [email protected] > <-- [email protected] > router = remoteusers, transport = remote_smtp > host mx00.kundenserver.de [212.227.15.150] MX=10 > host mx00.kundenserver.de [212.227.15.134] MX=10 > host mx00.kundenserver.de [212.227.15.186] MX=10 > host mx00.kundenserver.de [212.227.15.169] MX=10 > > It's clear, that we have a local delivery and an external one. > But what do those two "<--" mean exactly ?
Looking at the code, it means two "parents". So there is somehow a chain of addresses. Look at the output from my system where [email protected] is forwarded to [email protected],[email protected]. You can see in the router "virtual_forwarder" that it detects the recipient is a forwarder and expands it to the two new recipients. Then one at a time, it runs each one through the routers to figure out how to deliver it. CentOS58[root@ivwm51 ~]# exim -bt [email protected] Router: save_for_inspection for [email protected] Router: quarantine_mail for [email protected] Router: system_aliases for [email protected] Router: virtual_forwarder for [email protected] Router: save_for_inspection for [email protected] Router: quarantine_mail for [email protected] Router: dnslookup_smtp_auth for [email protected] Router: dnslookup_webmail for [email protected] Router: dnslookup_iv_hosts for [email protected] Router: dnslookup_forwarder for [email protected] Router: save_for_inspection for [email protected] Router: quarantine_mail for [email protected] Router: dnslookup_smtp_auth for [email protected] Router: dnslookup_webmail for [email protected] Router: dnslookup_iv_hosts for [email protected] Router: dnslookup_forwarder for [email protected] [email protected] <-- [email protected] router = dnslookup_forwarder, transport = remote_smtp_forwarder host gmail-smtp-in.l.google.com [74.125.141.27] MX=5 host alt1.gmail-smtp-in.l.google.com [74.125.142.26] MX=10 host alt2.gmail-smtp-in.l.google.com [74.125.137.27] MX=20 host alt3.gmail-smtp-in.l.google.com [173.194.68.27] MX=30 host alt4.gmail-smtp-in.l.google.com [74.125.131.27] MX=40 [email protected] <-- [email protected] router = dnslookup_forwarder, transport = remote_smtp_forwarder host gmail-smtp-in.l.google.com [74.125.141.27] MX=5 host alt1.gmail-smtp-in.l.google.com [74.125.142.26] MX=10 host alt2.gmail-smtp-in.l.google.com [74.125.137.27] MX=20 host alt3.gmail-smtp-in.l.google.com [173.194.68.27] MX=30 host alt4.gmail-smtp-in.l.google.com [74.125.131.27] MX=40 Then when it prints out the results, it shows that [email protected] is a parent of [email protected], and is a parent of [email protected]. > [email protected] > <-- [email protected] > <-- [email protected] In your case, it shows that [email protected] is a parent of [email protected] which is a parent of [email protected]. I do not know with certainty what causes that train of lineage to occur, maybe something in address rewriting? Without seeing your config, it's not likely that we'll be able to guess that. ...Todd -- The total budget at all receivers for solving senders' problems is $0. If you want them to accept your mail and manage it the way you want, send it the way the spec says to. --John Levine -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
