Re: [exim] Further details about Exchange/Exim routing - doe…

Startseite
Nachricht löschen
Nachricht beantworten
Autor: Derrick MacPherson
Datum:  
To: Exim-users
Betreff: Re: [exim] Further details about Exchange/Exim routing - does anyone have this working as per the website?
Derrick MacPherson wrote:
> I've found in exchange where I can bounce addresses that aren't in the
> Global Catalog, yet the lookup in the web page of the site is still not
> working. Below is some debug for an existing exchange account Does
> anyone have this working as per the webpage? could you send me similiar
> output showing the exchange router working? I know i could route these
> using the local part looked up in a text file, but I'd like something
> more functional.
>
> --------> exchange_user router <--------
> local_part=derrick domain=studiobproductions.com
> checking domains
> studiobproductions.com in "studiobproductions.com"? yes (matched
> "studiobproductions.com")
> studiobproductions.com in "+exchange_domains"? yes (matched
> "+exchange_domains")
> calling exchange_user router
> rda_interpret (string): ${lookup ldap {user="CN=exim
> Connector,CN=Users,DC=studiob,DC=dom" pass="PASSWORDHIDDEN"
> ldap:///${quote_ldap:DC=studiob,DC=dom}?mail?sub?(&(|(objectClass=user)(objectClass=publicFolder)(objectClass=group))(proxyAddresses=smtp:${quote_ldap:${local_part}@${domain}}))}
> {${local_part}@${domain}}{:fail: User unknown}}
> search_open: ldap "NULL"
> search_find: file="NULL"
> key="user="CN=exim Connector,CN=Users,DC=studiob,DC=dom"
> pass="PASSWORDHIDDEN"
> ldap:///DC%3Dstudiob%2CDC%3Ddom?mail?sub?(&(|(objectClass=user)(objectClass=publicFolder)(objectClass=group))(proxyAddresses=smtp:derrick%40studiobproductions.com))"
> partial=-1 affix=NULL starflags=0
> LRU list:
> internal_search_find: file="NULL"
> type=ldap key="user="CN=exim Connector,CN=Users,DC=studiob,DC=dom"
> pass="PASSWORDHIDDEN"
> ldap:///DC%3Dstudiob%2CDC%3Ddom?mail?sub?(&(|(objectClass=user)(objectClass=publicFolder)(objectClass=group))(proxyAddresses=smtp:derrick%40studiobproductions.com))"
> database lookup required for user="CN=exim
> Connector,CN=Users,DC=studiob,DC=dom" pass="PASSWORDHIDDEN"
> ldap:///DC%3Dstudiob%2CDC%3Ddom?mail?sub?(&(|(objectClass=user)(objectClass=publicFolder)(objectClass=group))(proxyAddresses=smtp:derrick%40studiobproductions.com))
> LDAP parameters: user=CN=exim Connector,CN=Users,DC=studiob,DC=dom
> pass=PASSWORDHIDDEN size=0 time=0 connect=0 dereference=0 referrals=on
> perform_ldap_search: ldap URL =
> "ldap:///DC%3Dstudiob%2CDC%3Ddom?mail?sub?(&(|(objectClass=user)(objectClass=publicFolder)(objectClass=group))(proxyAddresses=smtp:derrick%40studiobproductions.com))"
> server=XX.XX.XX.XX port=3268 sizelimit=0 timelimit=0 tcplimit=0
> after ldap_url_parse: host=XX.XX.XX.XX port=3268
> ldap_initialize with URL ldap://XX.XX.XX.XX:3268/
> initialized for LDAP (v3) server XX.XX.XX.XX:3268
> LDAP_OPT_X_TLS_TRY set
> binding with user=CN=exim Connector,CN=Users,DC=studiob,DC=dom
> password=PASSWORDHIDDEN
> Start search
> ldap_result loop
> LDAP entry loop
> search ended by ldap_result yielding 101
> ldap_parse_result: 0
> ldap_parse_result yielded 0: Success
> LDAP search: found no attributes
> lookup failed
> expanded: :fail: User unknown
> file is not a filter file
> parse_forward_list: :fail: User unknown
> extract item: :fail: User unknown
> exchange_user router forced address failure
> derrick@??? is undeliverable: User unknown
> search_tidyup called
> unbind LDAP connection to XX.XX.XX.XX:3268
>
>
>

So I've gotten a lot closer. I had to remove from exchange the
authoratative domain, and enable the spam filtering to get the recip
verification to work. One last hurdle which I hope is not a killer.

When processing a working exchange account, it works fine, other than
that, it's not passing on to the router that's after that if it fails, -
localuser - I'm wondering if that is seen as a 'hard failure' meaning
all routing is stopped at that point? I don't have a no_more in the
exchange lookup and exchange manualroute, and after that is localuser -
shouldn't it pass on to the next router after that exchage lookup failure?