some things no longer work after switch to direct LDAP mode

Hi,

today i have tried switching to direct ldap mode following the documentation

now i can no longer send mail directed to hosts as

email@hostname.domain.com

i always get a 5.1.1 unknown or illegal alias:

whereas email@{subdomain}.domain.com is ok, as long as the subdomain is known to the MTA, ie it is an alias object in the DC tree

also, some aliases defined in the file "aliases" are no longer recognized,

for convenience, i had some default forward lines likes

*@domain.com: @otherrelay:*@domain.com

which effectively acted like a smarthost, ie mail to addresses not known in domain.com were forwarded to "otherrelay"

now, probably i could solve the second problem either using a smarthost in the DC tree 's domain config

the first problem, however, puzzles me...it look like if it doesn't find a matching address, and the host is not known as a domain, then further rewrite rules are not applied ?

[995 byte] By [709035] at [2007-11-25 8:27:36]
# 1

i found the problem,

in option.dat, DOMAIN_UPLEVEL must be set to 0, in order to have the old behaviour (wildcards in aliasfile, and possibility to send mails directly to specified hosts)

i had set it to 1, in the hope the MTA would be more tolerant to find users (if user@sub.domain.com is not found, then maybe it exists at user@domain.com, so use this instead) as some of our users have quite problems addressing other users in the correct subdomain.

709035 at 2007-7-1 14:53:44 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...
# 2

I am having the same problem--and changing the options.dat as suggested above does not solve it. The rewrite rules suggested for the direct LDAP mode do not allow delivery to anything other than username@domain.com, even though every user entry has a proper mailHost entry pointing to a machine.

I am looking at the output from imsimta test -rewrite -debug but so far no changes I have made to the rewrite rules in imta.cnf produce useful results.

mpstarr at 2007-7-1 14:53:44 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...
# 3
Solution is to set DOMAIN_UPLEVEL=3 in ../imta/config/option.datIt is described on p. 546 of the iMS Adminstrator's Guide Feb 2002.
mpstarr at 2007-7-1 14:53:44 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...