You may also be able to find something here:
http://blogs.msdn.com/dlemson/archiv...27/100558.aspx or even get
David to say something about this. I haven't seen a great way to get done
what you're after outside of writing a sink or using a different MTA in
front of the Exchange server in the mail stream.
I'm not a great C++ programmer (although I play one on the internet
sometimes ;) but this is no easy feat if you want to get it done without
too
much degradation.
FWIW, I've seen people add quite a bit more than 2 million attribute
values;
AD can handle it in other words. 10mb worth of data in the dit is not a
big
deal really although the initial indexing might be non-trivial for all
DC's
across the forest. Not sure the impact in your environment; you'd have to
study that if you changed your mind. Keep in mind, this was a performance
hit in 5.5 as well and you've been dealing with it till now (assumption on
my part) just fine. Your dir wasn't as bloated, but you did have the IMS
handling the conversion which is a sizeable hit.
">> > 60 secondary addresses for 40000 users, thats more than 2 million of
attributes added to AD!!"
On another note, do you have an anti-virus host in front of Exchange in
the
mail stream? If so, that might be a better place to rewrite the TO field.
I think Microsoft should put the rewrite feature in there automatically.
The address rewrite tool wasn't intended for incoming mail, so a better
answer would be good. Something along the lines of 'define the recip
policy, choose a checkbox to apply the domain to all recipients without
bothering to do an exact match for lhs and rhs address parts' would work.
I'm sure it's more involved, but basically....
Al
"al" <sutec@netcourrier.com> wrote in message
news:%235%23vDNK$EHA.2568@TK2MSFTNGP10.phx.gbl...
Hi,
The mails must arrive to any user with any address... so it's no use
filtering.
In fact, we are now using Exchange 5.5, and in the internet mail service
we
have configured routing for our smtp domains (inbound) so that we don't
need
to set all the smtp suffixes for all users.
We would want to do the same thing with Exchange 2003, some king of
"rewriting" the smtp suffix so that when a mail arrives for
user1@aliasdomain5.com, it's transformed into
user1@realdomain.com.
I think we could do that through an event sink, but we would prefer any
other solution because we think sinks will consume a lot of CPU time.
Any advice would be appreciated.
Thanks
Al
"Al Mulnick" <amulnick_No_SPAM@ncDOTrr.com> a écrit dans le message de
news:
OwLU3$o#EHA.3236@TK2MSFTNGP15.phx.gbl...
Why do you feel like you need to create all 60 secondary addresses for
each
mailbox-enabled user?
You can specify filters to only apply to particular sets of users.
Al
"al" <sutec@netcourrier.com> wrote in message
news:enx6g9k%23EHA.3372@TK2MSFTNGP10.phx.gbl...
Hello,
I would like to configure an Exchange 2003 organization that manage
about
60
different smtp domains. There are approx. 40000 users that have a
mail
address (user@domain.net) but they must receive the mail adressed to
user@otherdomainX.com, (where X goes from 1 to 60).
I know how to implement the recipient policy to manage this 60 smtp
suffixes, but the problem is I don't want to make the AD database
heavier:
60 secondary addresses for 40000 users, thats more than 2 million of
attributes added to AD!!
I know there is a tool for Exchange that rewrites the adresses for
relayed
mail (i.e., incoming mail that is relayed in direction to an external
mail
server), so that can't be applied here.
Is there a way to reroute the mail addressed to
"user@otherdomain.com"
to
"user@domain.net"?
Thanks
I will post the solution if I get it
Al, Paris
Reply With Quote