IMS 5.2 : user with 2 email-addresses in in different domains

Question

in iMS 5.2, how can I add an user and configure MTA to accept 2 email (and mailalternateaddress) in 2 different domains ?
uid: joe
mailalternateaddress: [email protected]
mailalternateaddress: [email protected]
I have "o=siroe.com, o=isp" and "o=sunroe.com, o=isp" ?
and in o=internet.com, dc=com ... how to point these domains ?

Answer 1

The default structure is set up not to allow what you want. Initially I thought you could get an entity to receive mail just by putting the address you wanted as mail= or mailalternateaddress=. But it turns out that it uses both the directory structure and the individual properties. That is, if you send mail to [email protected], two things must be true:
- the entry for user must be in whatever hierarchy is pointed to when you track down dc=foo, dc=com, o=internet.
- the user must have mail= or mailalternate= with [email protected]
The problem is that your uid joe has to be located in o=siroe.com,o=isp in order to get mail addressed to anything @siroe.com, and in o=sunroe.com to get mail addressed to anything @sunroe.com. Since directory aliases aren't implemented, an entry can only be in one place at a time.
However there is an approach. In imta/config/option.dat, normally you have ALIAS_URL0, with ALIAS_URL1 and 2 commented out. If you add ALIAS_URL1=ldap:///$B?*?sub?$R, then if it can't find an entry in the appropriate place, it will do a global search for any entry with a matching mail= or mailalternateaddress=. I believe in your configuration the search will be all of o=isp. You can watch the access log in your directory server to see what the actual lookups are. If $B doesn't work you can hardcode o=isp in the URL.
Another approach would be to forget the structure entirely and just replace $V with $B in ALIAS_URL0. That depends upon how your system is going to be administered. If the administrators for the various domains are independent, you want to give entries in the domain priority access to names in the domain. That is, if there are several entries with mail or mailalternateaddress attributes of [email protected], you probably want to give priority to the one actually in siroe.com. Hence my original suggestion.
Note that I'm using direct LDAP access. I make no guarantees if you're not doing that.
When testing this sort of thing, remember that lookups are cached for 10 min. This can produce odd effects when you're testing. Changes seem not to do anything.
A better way of testing is to do "imsmta test -rewrite [-debug] foo@bar" That will show exactly how an address is treated, and if -debug is specified, you'll have a decent chance figuring out what it doesn't work the way you expected.