Domain alias in iMS 5.2

Hi,
Objective: The Users of Domain abc.com want that mails can be sent to them at xyz.com domain too.
Methods: flat alias file (not recommended)
vanity Domains ( fit for small no of users only)
Domain Alias ( recommended)
Discussion:
I created a Domain alias for abc.com to be xyz.com
ldif used
=======
dn: dc=xyz,dc=com,o=internet
objectclass: alias
objectclass: inetDomainAlias
aliasedObjectName: dc=abc,dc=com,o=internet
dc: xyz.com
ldapmodify -a -D "cn=Directory manager" -w mypassword -f aboveldiffile
My option.dat has entries for aliasurl and alias magic
Now I try to login using user@xyz : success
I try to send mail to user@xyz instead of [email protected]: failure
What happens ..in directpry access logs:
dc root is checked for xyz domain ...on finding ...the search base is adjusted to abc.com....
But now the e-mail address searched for is [email protected]..in domain abc ...which is not set ...
SO I DEFINE ALTERNATEMAILADDRESS ATTRIBUTE FOR DOMAIN USERS ABC.COM
so that search matches...
Now things work fine ....
I also check some postings here on the sunbject ....
where JAY suggests to use DOMAIL_LEVEL = 2 in option.dat file..
I delete mailalternateaddresses ...for users add DOMAIN_UPLEVEL=2...
now sendinf mail addressed at [email protected] suceeds....
Looing at ldap access logs I find ...that the search is directly started at abc.com ???
and the mails searched for are [email protected] aswell as [email protected] ...
So my concern is WHAT DOES DOMAIN_LEVEL actually DO????
Thanks

For a very good description of how direct ldap works, please see here:
http://docs.sun.com/source/816-6009-10/dirldap.htm#27650

Similar Messages

Still about domain alias and domain migration

Our company is under a domain name transition. Currently, our domain is lab.D.com, and we are moving to aaa.com.During the transition, we wish both domains could work for us for a long time.
I added a domain alias aaa.com for our domain lab.D.com, the ldif shows:
dn: dc=aaa, dc=com, o=internet
objectclass: alias
objectclass: inetDomainAlias
aliasedObjectName: dc=lab, dc=D, dc=com, o=internet
dc: aaa
after restarting msg server, I can send email to [email protected] which is acutually [email protected]
However, this is only half-way to my goal. I wish our emails at receivers' mailboxes were [email protected], not [email protected], if we send emails though loging in web mail typing [email protected] in the user ID box, or by creating [email protected] accounts in MS Outlook.
===> Is there any way to do it?
===> can [email protected] account be created in MS Outlook?
In another post about domain migration, you suggested:
If you want to stop using the old domain, and make the new domain your "default domain", that's a little harder. It involves several steps:
1. changing all the mail addresses.
2. changing the "default domain" settings everywhere.
===> I wonder, how to do it? is there any command? ldapmodify?
as an alternative approach, if we decide to change our email addresses to [email protected] first,
===> will emails sending to either [email protected] or [email protected] arrive at users who are still in the lab.D.com, if I only change all the mail addresses' domian part to aaa.com since I have added domain alias aaa.com?
and, I do not think sending emails from [email protected] to the internet would be a problem, right???
The iMS we use is iPlanet Messaging Server 5.2 (built Feb 21 2002), Directory Server is 4.16 which are very old versions :(
Thanks.

I make no claim to be a programmer, nor am I expert
with ldap commands.
I know of no easy way to change all, other than
export to ldif, and use a global change with a text
editor, and then re-import.So, db2ldif -> change in text editor -> ldif2db, right?
Another question here is about Direct LDAP.
I enabled Direct LDAP.
aaa.com is the domain alias to lab.oldD.com (our old domain).
I also have changed user alas' email addresss from alas@ lab.oldD.com to [email protected] and added mailAlternateaddress for alas as [email protected], as you instructed in previous posts.
However, whenever I click "send" either to aaa.com or lab.oldD.com, it shows errors, for examples, - "Returning unknown or illegal alias: [email protected]", "Returning unknown or illegal alias: [email protected]"
The log shows:
19:17:27.62: mmc_address_to_tree: Parsing address.
19:17:27.62: Address: "user@[127.0.0.1]" 0x00000000
19:17:27.62: Right default: honey.lab.oldD.com
19:17:27.62: Parsing address with null fixup.
19:17:27.62: mmc_address_to_tree: Returning.
19:17:27.62: Rewriting: Mbox = "user", host = "[127.0.0.1]", domain = "$*", literal = "", tag = ""
19:17:27.62: Rewrite: "$*", position 0, hash table -
19:17:27.62: Found: "$E$F$U%[email protected]"
// honey is our email server
19:17:27.62: Rewrite failed, not forward.
19:17:27.62: Rewrite: "$*", position 1, hash table -
19:17:27.62: Failed.
19:17:27.62: Rewrite: "$*", position 0, rewrite database -
19:17:27.62: Failed
19:17:27.62: Rewriting: Mbox = "user", host = "[127.0.0.1]", domain = "[127.0.0.1]", literal = "", tag = ""
19:17:27.62: Rewrite: "[127.0.0.1]", position 0, hash table -
19:17:27.62: Failed
19:17:27.62: Rewrite: "[127.0.0.1]", position 0, hash table -
19:17:27.62: Failed.
19:17:27.62: Rewrite: "[127.0.0.1]", position 0, rewrite database -
19:17:27.62: Failed
19:17:27.62: Rewriting: Mbox = "user", host = "[127.0.0.1]", domain = "[127.0.0.]", literal = "1", tag = ""
19:17:27.62: Rewrite: "[127.0.0.*]", position 0, hash table -
19:17:27.62: Failed
19:17:27.62: Rewrite: "[127.0.0.]", position 0, hash table -
19:17:27.62: Failed.
19:17:27.62: Rewrite: "[127.0.0.]", position 0, rewrite database -
19:17:27.62: Failed
19:17:27.62: Rewriting: Mbox = "user", host = "[127.0.0.1]", domain = "[127.0.]", literal = "0.1", tag = ""
19:17:27.62: Rewrite: "[127.0.*.*]", position 0, hash table -
19:17:27.62: Failed
19:17:27.62: Rewrite: "[127.0.]", position 0, hash table -
19:17:27.62: Failed.
19:17:27.62: Rewrite: "[127.0.]", position 0, rewrite database -
19:17:27.62: Failed
19:17:27.62: Rewriting: Mbox = "user", host = "[127.0.0.1]", domain = "[127.]", literal = "0.0.1", tag = ""
19:17:27.62: Rewrite: "[127.*.*.*]", position 0, hash table -
19:17:27.62: Failed
19:17:27.62: Rewrite: "[127.]", position 0, hash table -
19:17:27.62: Failed.
19:17:27.62: Rewrite: "[127.]", position 0, rewrite database -
19:17:27.62: Failed
19:17:27.62: Rewriting: Mbox = "user", host = "[127.0.0.1]", domain = "[]", literal = "127.0.0.1", tag = ""
19:17:27.62: Rewrite: "[]", position 0, hash table -
19:17:27.62: Found: "$E$R${INTERNAL_IP,$L}$U%[$L]@tcp_intranet-daemon"
19:17:27.62: Mapping: name = "INTERNAL_IP", input = "127.0.0.1".
19:17:27.62: Mapping 2 applied to 127.0.0.1
19:17:27.62: Entry #2 matched, pattern "127.0.0.1", template "$Y", match #0.
19:17:27.62: New target ""
19:17:27.62: Exiting...
19:17:27.62: Final result ""
19:17:27.62: Mapping result:
19:17:27.62: New mailbox: "user".
19:17:27.62: New host: "[127.0.0.1]".
19:17:27.62: New route: "tcp_intranet-daemon".
19:17:27.62: New channel system: "tcp_intranet-daemon".
19:17:27.62: Looking up host "tcp_intranet-daemon".
19:17:27.62: - found on channel tcp_intranet
19:17:27.62: mmc_winit('tcp_intranet','[email protected]','') called.
19:17:27.62: mmc_determine_url beginning with pattern , xadr , mbox , subaddress
19:17:27.62: Queue area size 18871794, temp area size 18871794
19:17:27.62: 4717948 blocks of effective free queue space available; setting d
isk limit accordingly.
19:17:27.62: mmc_address_to_tree: Parsing address.
19:17:27.62: Address: "[email protected]" 0x00000000
19:17:27.62: Right default: lab.oldD.com
19:17:27.62: Parsing address with local fixup.
19:17:27.62: mmc_address_to_tree: Returning.
19:17:27.62: Rewriting: Mbox = "alas", host = "newD.com", domain = "$*", literal
= "", tag = ""
19:17:27.62: Rewrite: "$*", position 0, hash table -
19:17:27.62: Found: "$E$F$U%[email protected]"
19:17:27.62: Rewrite failed, not forward.
19:17:27.62: Rewrite: "$*", position 1, hash table -
19:17:27.62: Failed.
19:17:27.62: Rewrite: "$*", position 0, rewrite database -
19:17:27.62: Failed
19:17:27.62: Rewriting: Mbox = "alas", host = "newD", domain = "newD.com", litera
l = "", tag = ""
19:17:27.62: Rewrite: "newD.com", position 0, hash table -
19:17:27.62: Failed.
19:17:27.62: Rewrite: "newD.com", position 0, rewrite database -
19:17:27.62: Failed
19:17:27.62: Rewriting: Mbox = "alas", host = "newD", domain = ".com", literal =
"", tag = ""
19:17:27.62: Rewrite: "*.com", position 0, hash table -
19:17:27.62: Failed
19:17:27.62: Rewrite: ".com", position 0, hash table -
19:17:27.62: Found: "$U%$H$D@TCP-DAEMON"
19:17:27.62: New mailbox: "alas".
19:17:27.62: New host: "newD.com".
19:17:27.62: New route: "TCP-DAEMON".
19:17:27.62: New channel system: "TCP-DAEMON".
19:17:27.62: Looking up host "TCP-DAEMON".
19:17:27.62: - found on channel tcp_local
19:17:27.62: mmc_address_to_tree: Parsing address.
19:17:27.62: Address: "[email protected]" 0x00000000
19:17:27.62: Right default: lab.oldD.com
19:17:27.62: Parsing address with null fixup.
19:17:27.62: mmc_address_to_tree: Returning.
19:17:27.62: Rewriting: Mbox = "alas", host = "newD.com", domain = "$*", literal
= "", tag = ""
19:17:27.62: Rewrite: "$*", position 0, hash table -
19:17:27.62: Found: "$E$F$U%[email protected]"
19:17:27.62: Rewrite failed, not forward.
19:17:27.62: Rewrite: "$*", position 1, hash table -
19:17:27.62: Failed.
19:17:27.62: Rewrite: "$*", position 0, rewrite database -
19:17:27.62: Failed
19:17:27.62: Rewriting: Mbox = "alas", host = "newD", domain = "newD.com", litera
l = "", tag = ""
19:17:27.62: Rewrite: "newD.com", position 0, hash table -
19:17:27.62: Failed.
19:17:27.62: Rewrite: "newD.com", position 0, rewrite database -
19:17:27.62: Failed
19:17:27.62: Rewriting: Mbox = "alas", host = "newD", domain = ".com", literal =
"", tag = ""
19:17:27.62: Rewrite: "*.com", position 0, hash table -
19:17:27.62: Failed
19:17:27.62: Rewrite: ".com", position 0, hash table -
19:17:27.62: Found: "$U%$H$D@TCP-DAEMON"
19:17:27.62: New mailbox: "alas".
19:17:27.62: New host: "newD.com".
19:17:27.62: New route: "TCP-DAEMON".
19:17:27.62: New channel system: "TCP-DAEMON".
19:17:27.62: Looking up host "TCP-DAEMON".
19:17:27.62: - found on channel tcp_local
19:17:27.62: Mapped return address: [email protected]
19:17:27.62: mmc_rrply: Return detailed status information.
19:17:27.62: mmc_rrply: Returning return address and channel OK
19:17:27.62: mmc_wadr(0x001abd40,'','[email protected]') called.
19:17:27.62: Copy estimate before address addition is 1
19:17:27.62: Parsing address [email protected]
19:17:27.62: mmc_address_to_tree: Parsing address.
19:17:27.62: Address: "[email protected]" 0x00000000
19:17:27.62: Right default: lab.oldD.com
19:17:27.62: Parsing address with local fixup.
19:17:27.62: mmc_address_to_tree: Returning.
19:17:27.62: Rewriting: Mbox = "alas", host = "lab.oldD.com", domain = "$*", l
iteral = "", tag = ""
19:17:27.62: Rewrite: "$*", position 0, hash table -
19:17:27.62: Found: "$E$F$U%[email protected]"
19:17:27.62: Match, pattern = "lab.oldD.com", current = "(*domaincheck*)"
19:17:27.62: old state = not checked.
19:17:27.62: Performing domainMap check on lab.oldD.com.
19:17:27.62: Added domainMap result 1 to cache for lab.oldD.com.
19:17:27.62: new state = succeeded.
19:17:27.62: New mailbox: "alas".
19:17:27.62: New host: "lab.oldD.com".
19:17:27.62: New route: "honey.lab.oldD.com".
19:17:27.62: New channel system: "honey.lab.oldD.com".
19:17:27.62: Looking up host "honey.lab.oldD.com".
19:17:27.62: - found on channel l
19:17:27.62: Routelocal flag set; scanning for % and !
19:17:27.62: Address [email protected] requires local processing.
19:17:27.62: Variant #1 = [email protected]
19:17:27.62: Variant #2 = *@lab.oldD.com
19:17:27.62: Checking for [email protected] in the system alias file
19:17:27.62: - not found
19:17:27.62: Checking for *@lab.oldD.com in the system alias file
19:17:27.62: - not found
19:17:27.62: - adding address [email protected] to headers.
19:17:27.62: Copy estimate after address addition is 1
19:17:27.63: mmc_rrply: Return detailed status information.
19:17:27.63: mmc_rrply: Returning unknown or illegal alias: [email protected]
I wonder why?
Thanks.

Domain Alias approch - Best Practice Request

Hello,
I am managing a company that has many domains. We have been using standard sendmail for mail server.
I have set it up through relay-domains etc... such that a user can get mail at any of the listed domains (there are 76 of them!). So, if I have jdoe mail will route to that user if you send mail to [email protected], [email protected] etc... all 76 of them.
My question is how to best replicate this functionallity with minimal (one time?) administration in msgsrvr... imta.cnf? some other means?
Thanks for reading...
Mike

Mike, this question looks very much like the one that's been getting discussion in the ims-info forum. Please understand, I read that forum, daily. . .
The advise you get there should be considered totally authoratative.
Domain Alias is indeed the correct way to have our Messaging Server handle this task for you.

Domain aliasing with iMS 5.2?

We're testing iMS 5.2 with direct ldap to ds 5.1 and need to do a domain alias. We have our-name.com and ourname.com. We always use ourname.com but some still use the original our-name.com so we would like it to work as an alias. Vanity domain isn't viable.
The provisioning guide has the ldif code for creating an aliased domain entry in the directory. This went without a problem. But what do I have to do to get IMS to recognize our-name.com is just an alias for ourname.com?
THANKS!

In 5.2 or even 5.1, you can simply create the domain alias in LDAP and let the MTA do the rest.
dc=sample,dc=com,o=internet
inetdomainbasedn: o=sample, o=hostings, o=isp.com
dc=alias,dc=com,o=internet
aliasedobjectname=dc=sample,dc=com,o=internet
it used to work fine in 5.1 but I can't make it work in 5.2 (direct ldap) : I looked at the directory server logs and ims indeed follows "aliasedobjectname", then searches in the inetdomainbasedn. BUT it searches for the "alias domain" email address ([email protected]), not for the aliased one ([email protected])
Adding [email protected] as a mailAlternate or mailSupplement attribute is NOT a workaround :<

Setting up a Mail domain Alias

Hi
We are trying to set up a mail domain alias so that a user can receive mails on either [email protected] or [email protected], the default mail domain on which OCS has been installed is domainA.com
I've tried the rewrite rules for inbound SMTP as:
Pattern To Match
$[email protected]
Action
Apply Rewrite
Rewrite To Apply
$[email protected]
But it does not seem to work (I'm just not receiving any test mails and don't know where we can check for logs for any discarded mails)
Is there any simple way to set up this 'maildomain alias'?
Many thanks for your assistance
Rgds
Vicky

Marc,
In this situation, I think you only need to add the additional addresses, into the Email Address entry box in Mail Preferences/Accounts/Account Information. You put a comma after the existing address, and add another. Put a comma after the new, one, and you can add still another.
http://docs.info.apple.com/article.html?artnum=302215
and
http://docs.info.apple.com/article.html?path=Mail/2.0/en/ml1019.html
You will need to be sure to select the correct one, in each reply or new message. The latter link is also found in Mail Help.
Does this fulfill your need?
Ernie

Adding an a domain alias

Dear All,
Would anyone please point me how can I add a domain alias for my existing domain...
let's suppose my existing domain has the following dn
dn: o=company.com,dc=company,dc=com
my new alias should be in the form
o=com-pany.net,dc=company,dc=com
I am using messaging server 6.3 and DSEE 6.3
Thanks,
Scotty

s@mira123 wrote:
Would anyone please point me how can I add a domain alias for my existing domain...
let's suppose my existing domain has the following dn
dn: o=company.com,dc=company,dc=comIf you are using schema 2 then domain 'aliases' are set with the associatedDomain attribute.
http://docs.sun.com/app/docs/doc/819-4428/bgahk?a=view
So to add an "alias" domain you add the appropriate associatedDomain e.g.
dn: o=company.com,dc=company,dc=com
associatedDomain: com-pany.netRegards,
Shane.

Domain alias problem

Hi Jay and all,
we are running Sun Java messaging 2004Q4 on solaris 9.
We want to create a domain alias so that our server can receive mails on different domain also.
Let's say we have already x.com and want y.com to be domain alias for it. So i ran this below script and it was successful
++++++
echo dn: o=x.com,dc=x,dc=com >>/sbin/ldap99.txt
echo changetype: modify >>/sbin/ldap99.txt
echo add: associatedDomain >>/sbin/ldap99.txt
echo associatedDomain: y.com >>/sbin/ldap99.txt
cd /var/opt/mps/serverroot/shared/bin
./ldapmodify -D uid=admin,ou=people,o=x.com,dc=x,dc=com -w <admin-pass> -R -f /sbin/ldap99.txt
++++++++++++++
Now i suppose y.com has become an alias to x.com so that i can receive mails destined to [email protected] also and get them forwarded to the [email protected] mailbox (No need for user level aliasing again)
But when i say "telnet <mail-server> 25" and rcpt to:[email protected], it says "550 5.1.1 unknown or illegal alias: [email protected]".
it means that the vanity domain created successfully but not able to identify users already created on x.com (it did not throw the error - 550 5.7.1 Relaying not allowed: [email protected])
Please advise me.
TIA
Prvn

Hi,
Now i suppose y.com has become an alias to x.com so
that i can receive mails destined to [email protected] also
and get them forwarded to the [email protected] mailbox (No
need for user level aliasing again)You still need to add the user-level address attribute e.g.
mailalternateaddress: [email protected]
Just adding the associatedDomain attribute doesn't automatically result in emails sent to [email protected] being delivered to the mailbox of [email protected]
But when i say "telnet <mail-server> 25" and rcpt
to:[email protected], it says "550 5.1.1 unknown or illegal
alias: [email protected]".
Try adding the mailalternateaddress: [email protected] to the [email protected] account.
Regards,
Shane.

Create domain alias

I created domain alias using the following LDIF sentences:
A:
dn: dc=b, dc=a, dc=com, dc=cn, o=internet
changetype: add
objectclass: alias
objectclass: inetDomainAlias
aliasedObjectName: dc=x, dc=y, dc=com, o=internet
dc:b
Later, I also tried B::
dn: dc=b.a.com.cn, o=internet
changetype: add
objectclass: alias
objectclass: inetDomainAlias
aliasedObjectName: dc=x, dc=y, dc=com, o=internet
dc:b.a.com.cn
it seemed both works.
I wonder which way is right?
or, when should I use which?
thanks.

Let me clarify over the previous clarification:
my goal:
A. When users send emails to internal addresses
([email protected] and [email protected]), the senders' addresses
should be looks like [email protected] or
[email protected] at the recipients' mailboxes, in
another word, the "from" section of the email.
And,
B. When users send emails to external addresses
including [email protected] and other
address, e.g. [email protected], "from" sections of
senders' emails should be like [email protected], or
[email protected]
That is, users from the Internet will only see the [email protected]/[email protected] address.
>
So,
What I am thinking is:
1. apply rewrite rule at tcp_local to rewite the
"from" section of emails sent to the Internet
2. create domain alias b.a.com.cn and c.b.a.com.cn
for x.com and y.x.com respectly.
So emails sent to [email protected]/[email protected] will be delivered to [email protected]/[email protected]
>
I do not think I need to add mailalternateaddress to
each user's defination in ldif. Right?
Would this work?
Thanks.Thank you.

Rewrite Rules with Domain Alias

Version:
iPlanet Messaging Server 5.2 HotFix 2.03 (built Nov 22 2004)
libimta.so 5.2 HotFix 2.03 (built 13:20:08, Nov 22 2004)
I am hosting 1 domain with an domain alias for the same hosted domain.
I would like all mail coming in as domain A to be rewritten as domain B. Same for all outgoing mail outgoing as domain A to rewritten as domain B
What should my rewrite rules look like?
domain.a $U%domain.b

That makes senses. I am using mailequivalentaddress with a domain alias. I also have the following rule in my imta.cnf:
domain.A $R$U%domain.B
domain.A $U%domain.B
There rewrites all of the mailheaders but I noticed the the envelope headers are not rewritten. Is it a good idea to rewrite the envelope headers although the domain beinging rewritten to is an alias? The mail headers on the to: and from: address are rewritten as domain.B but envelope headers show [email protected] for delivery.

Problems installing SSL certificates for more than one alias on iMS 5.2

I have a problem to getting encyption on IMAP/HTTP/SMTP when they are on the same server. I only getting one SSL certificate installed by the Netscape console wizard, and therefore only one alias.
Let's say I have 3 aliases to the same server just for the scalability, imap.vxu.se, smtp.vxu.se and mail.vxu.se for http (https). Then I can only have one certificate installed at the same time, for example https://mail.vxu.se. And the others, like (S)IMAP I getting a dialouge that says the hostname doesnt is the same as the registred in the certificate. How do I solve this? Is there some possibillity to install more than ONE certificate, so I can have one certificate for each alias?
Environment: Full 420R, Solaris 8, iMS5.2
Thanks in advice

Although I completely agree the comments that suggestion this is not a great configuration idea, the error you are seeing ("...bean not found...") likely has nothing to do with the configuration - at least not as mentioned. My first guess is that if you are running the same exact form (FMX) as you ran for your first test then there should be no error. The only way such an error would appear is if the proper jar files are not being pulled to the client JRE or if the fmx was not properly generated. Be sure you are including config=webutil in the URL or that you have added the Webutil configuration info to your own named configuration section of formsweb.cfg
Regardless, if this is a Windows machine, the probability of having problems with multiple installations of the same version is high. Consider that the system PATH, CLASSPATH, ORACLE_HOME and various other system variables needed by the server side of the installation will overlap for each installation. This will cause problems. On the client side, attempting to download jars of the same name from the same server, but which are not actually the same files will confuse the JRE. If the JRE detects that a file which it has already cached is coming from the same server (host) then it will not attempt to pull it again. This will be a problem if the jars are not exactly the same in both installation. Making the problem worse is that you may not be able to easily determine from which installation the jars (or any files) were obtained.
So. as a general rule, regardless of whether multple installations can co-exist, I would not recommend it. This is especially true on a Windows platform.

Email workflow showing domain and alias and not the name in the email

I created an email workflow for a specific user field value to receive an email on a trigger event.
However, the email received shows the DOMAIN/Alias and not the "Name" in the email content.
How to correct this error? Not sure where is the issue is.
Sample:
Hello [%Current Item: Reviewer%] is the greeting line.
If Reviewer is say Domain A/v-abcd and Name is Abcd.
The email reads
"Hello Domain A/v-abcd" and not "Hello Abcd"

Hi,
Just select "Display Name" instead of "Login Name" in the "Return field as" field of Lookup dialog.
It should help.
Regards Michael (http://sp2013-blog.com)
Please, don't forget to upvote and mark as an answer if appropriate

Local host alias with 2 domains?

Hi!
I want 2 domains to use the same mailboxes/users. A simple domain-alias if you will. Mail sent to [email protected] and [email protected] should be delivered to the same mailbox ([email protected]).
Have read about virtual hosts etc but it seems to complex, isn't there an easy way to just alias the domain?
Btw, I got it to work by adding the second domain in serveradmin/mail/hosts and then adding the second adress to the user in WGM, but i dont want to have to do that with all the users. And its highly likely that its forgotten when creating new users
Using 10.5.2 Server.

Just add the second domain as a local host alias.
You do not need to add the domain part to your users in WGM. Be it for the first be it for the second domain. This is only needed for virtual domains.

Do i need alias domain

hi
i'm new on solaris and Sun Messaging Server
I have some question about my work
now i have aaa.com and my boss need add new domain like bbb.com ( he want to use bbb.com is default for out going mail ( keep aaa.com too ))
and he want all mail to bbb.com and aaa.com point to the same mailbox
i use Messaging Server Ver. 6.2
i found someone talk about domain alias do i need it??
and how should i do ?
Please explain such as command or exsample 'cz i'm a baby with this system ,Please help
Thank you very much for all reply
~>_<~

shane_hjorth wrote:
_naiton_ wrote:
i'm new on solaris and Sun Messaging Server Please in future always provide the exact version of messaging server (./imsimta version). This may not be essential for this question but it is a good habit to get into.
Sun Java(tm) System Messaging Server 6.2-3.04 (built Jul 15 2005)
libimta.so 6.2-3.04 (built 01:43:03, Jul 15 2005)
SunOS mail1 5.9 Generic_118558-34 sun4u sparc SUNW,Sun-Fire-V210
now i have aaa.com and my boss need add new domain like bbb.com ( he want to use bbb.com is default for out going mail ( keep aaa.com too ))A straight-forward enough request.
and he want all mail to bbb.com and aaa.com point to the same mailboxNo problem.
i found someone talk about domain alias do i need it??This is where it gets tricky. There are two types of directory schema (specifications) which translate emails domains e.g. @domain.com to a location in the directory where users with @domain.com addresses exist e.g. o=myorg,o=isp. Schema 1 is the old layout, schema 2 is the new layout -- do you know which one you are using?
i don't know how i can check it??
What tools are you using to provision (create/modify/edit) user accounts for Messaging Server?
Are you using Delegated Administrator (e.g. the web GUI -> http://hostname/da or the CLI -> ./commadmin <blah>) or do you edit the directory manually to allow new users to login?
Regards,
Shane.I dont have web GUI and i dont' know how to use ./commadmin command ~>_<~
there is script for adding new user
some of the script code
./ldapmodify -D cn="directory manager" -w xxxxxxx -a << EOF
dn: uid=$name,ou=people,o=xxx.co.th,dc=xxx,dc=co,dc=th
psIncludeInGAB: true
iplanet-am-modifiable-by: cn=Top-level Admin Role,dc=eta,dc=co,dc=th
inetCOS: platinum
objectClass: top
objectClass: iplanet-am-managed-person
objectClass: iplanet-am-user-service
objectClass: inetadmin
objectClass: iplanetpreferences
objectClass: inetsubscriber
objectClass: person
objectClass: organizationalperson
objectClass: inetorgperson
objectClass: inetuser
objectClass: ipuser
objectClass: nsmanagedperson
objectClass: userpresenceprofile
objectClass: inetmailuser
objectClass: inetlocalmailrecipient
objectClass: dspswuser
mailHost: mail.xxx.co.th
mail: [email protected]
givenName: $name

Creating aliases once for all domains

I have a number of domain aliases but I have to create a seperate mailalternateaddress entry for each user to receive mail under that domain.
Main domain is msai.mea.com.
fang.msai.com is a domain alias and points to msai.mea.com.
If I have a mailalternateaddress [email protected] I can receive there fine but If I want to receive email to [email protected] I have to have a seperate mailalternate address [email protected]
Is there a way to only have a single mailalternateaddress defined on the primary domain handle the alias for both domains?
I'm running iMS 5.2 with HotFix 0.6 and iDS 5.1.
Thanks

" I know that each time a user logs in it creates a new folder for this users profile"
I have no experience with Active Directory, but I think I have seen people customize the default home configuration in the appropriate language folder found in "/System" > "Library" > "User Template" in this situation ("root" privileges required). The template contains the basic folders ("Deskop", "Documents", "Library", etc.) so standardized ".plist" files for user level settings can be placed in the "Library" > "Preferences" folder of the template so that they will be copied along with everything else when the new "home" folder is created.
Often, an existing account will be configured as desired, then the appropriate files copied to the template. The caveat is that there can't be any references in eg. the "sidebar" or "Dock" to items within the home directory since the alias data in the ".plist" files will point to the original item in the model account used to create the template, rather than the corresponding items in the newly generated "home" folder.

Emails for multiple domains

Hi,
I ve a problem with IMS 5.2 on Win 2K, I applied the patch Hotfix 1.
I installed IMS to manage domain xxx.com but I also need to be able to create users for other email adresses routed on my server, like yyy.be. When I send an email with an adress @yyy.be, I can retrieve it with the correct adress (e.g. [email protected]), but when I send an email to this user [email protected] I receive an error : smtp;530 5.7.1 Relaying not allowed: [email protected]
From the other side I can send and retrieve every mail from an adress @xxx.com.
Some say I must create a domain Alias, like explained in the doc, but when I want to import a LDIF file, it doesn't want, sending error : 0 entries imported, 1 entry rejected, and the file reject contains : Error 32 .... Could someone explain me how and where to create such an alias because I am new to IMS and I am a bit lost at this time?
Thank you in advance,
a user who needs help !!!

What behavior do you want? If you want the two domains to be separate, I would use Distributed Admin to create a new domain. That will create entries in o=internet and in your main tree. If you don't use iDA, the Provisioning Guide tells you what entries to create. I haven't tried it, but the manual suggests that "imadmin domain create" might do the job as well.
If you want the second domain to be an alias for the first, the sleazy approach is add lines to imta.cnf. Here's an example for a server installed as rulink-mail.rutgers.edu, configured to receive mail for [email protected]:
moltar.rutgers.edu $U%[email protected]
This causes [email protected] to be treated the same as [email protected] I'm sure there are more elegant approaches. Of course this only causes mail sent to [email protected] to work. It doesn't make the system recognize moltar.rutgers.edu in other contexts (e.g. when users login).

Domain alias in iMS 5.2

Similar Messages

Maybe you are looking for