On Wed, Oct 31, 2012 at 7:12 AM, Cyborg <cyborg2@???> wrote:
> # exim -bt post@???
> post@??? -> /path/to/Maildir/
> transport = address_directory
> post@???
> <-- post@???
> <-- post@???
> 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 ida@??? is forwarded
to happy@???,smile@???. 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 ida@???
Router: save_for_inspection for ida@???
Router: quarantine_mail for ida@???
Router: system_aliases for ida@???
Router: virtual_forwarder for ida@???
Router: save_for_inspection for happy@???
Router: quarantine_mail for happy@???
Router: dnslookup_smtp_auth for happy@???
Router: dnslookup_webmail for happy@???
Router: dnslookup_iv_hosts for happy@???
Router: dnslookup_forwarder for happy@???
Router: save_for_inspection for smile@???
Router: quarantine_mail for smile@???
Router: dnslookup_smtp_auth for smile@???
Router: dnslookup_webmail for smile@???
Router: dnslookup_iv_hosts for smile@???
Router: dnslookup_forwarder for smile@???
smile@???
<-- ida@???
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
happy@???
<-- ida@???
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 ida@??? is
a parent of smile@???, and is a parent of happy@???.
> post@???
> <-- post@???
> <-- post@???
In your case, it shows that post@??? is a parent of
post@??? which is a parent of post@???. 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
