| Author |
Message |
Boris Lokhvitsky
Guest
|
 Posted:
Wed Dec 29, 2004 5:50 am Post subject:
Exchange mail routing question |
|
|
We have a problem concerning Exchange mail routing, and I hope to be able to
find some advises here.
We use multiple parallel mail systems in the company, with messages being
delivered to all systems simultaneously. Users can connect to either system
(depending on the client, e.g. desktop, laptop, or PDA) and still read their
messages.
To accomplish this, we use an internal SMTP namespace @exchange.company.com
for our Exchange environment, and different external namespace @company.com
for general e-mail. There is an SMTP connector configured pointing to an
external smart host. The underlying reason is - we need _all_ messages, even
those addressed to another existing Exchange users, be routed to the smart
host in order to reach parallel mail systems.
Currently we use the simple but inconvenient mechanism having users to type
explicit user@company.com address instead of using the GAL, when sending
e-mails. Since Exchange does not have this suffix in its recipient policy,
it treats recipients as remote and routes all messages to the smart host. It
works, but users are not happy, especially those who have the
@exchange.company.com addresses somehow in their local Outlook address
cache.
I thought there could be a solution based on creating another (higher
priority) recipient policy with @company.com address in it and
"authoritative" flag cleared, so that GAL will receive the @company.com
suffix but Exchange will not consider itself authoritative for these
addresses, hence routing to the smart host. However, it doesn't work in my
test environment, since - in accordance with MS KB articles I could find -
Exchange does not care about being authoritative or not as soon as it finds
a recipient in AD (btw I think this is odd).
A hardly acceptable workaround is to create a Contacts public folder with
all @company.com addresses in it and reconfigure all clients to use this
folder as an address book. Another (very cumbersome) way is to create a
(hidden) contact for each user with the @company.com address and forward
messages to this contact. But we are looking for a better solution.
Is there something we are missing when trying the recipient policies trick?
Is there another solution that we could implement to accomplish our routing
goal?
I would greatly appreciate any help.
Best regards and Christmas / New Year wishes,
Boris
P.S.
Some details how I tried the policies trick basing on the description in KB
823158, 319759, 822943, and 321721:
1. Default policy defines the primary @something.com SMTP suffix;
"responsible" flag is set for it.
2. Another (higher priority) policy defines the primary @company.com suffix;
"responsible" flag is not set for it.
3. SMTP connector is configured for * namespace to send all messages to the
outside smart host.
Now I see in the GAL the proper @company.com addresses. However, when I send
a message to user@company.com, it reaches the local user's mailbox and is
not routed outside. I think it's because Exchange checks the AD (and not a
particular recipient policy) for a user's address.
|
|
| Back to top |
|
 |
Boris Lokhvitsky
Guest
|
| Posted:
Wed Dec 29, 2004 11:28 pm Post subject:
Re: Exchange mail routing question |
|
|
Hmmm. No reaction yet. Too bad :(
Let me try to reformulate the question making it shorter:
I have Exchange 2003 SP1. I need to forward _ALL_ e-mail messages to the
external smart host.
ALL. Even messages addressed to the internal Exchange/AD recipients.
How can I accomplish this?
Thanks a lot in advance,
Boris
======================================================
"Boris Lokhvitsky" <msexpert@community.nospam> wrote in message
news:u9asCgT7EHA.2156@TK2MSFTNGP10.phx.gbl...
| Quote: | We have a problem concerning Exchange mail routing, and I hope to be able
to
find some advises here.
We use multiple parallel mail systems in the company, with messages being
delivered to all systems simultaneously. Users can connect to either
system
(depending on the client, e.g. desktop, laptop, or PDA) and still read
their
messages.
To accomplish this, we use an internal SMTP namespace
@exchange.company.com
for our Exchange environment, and different external namespace
@company.com
for general e-mail. There is an SMTP connector configured pointing to an
external smart host. The underlying reason is - we need _all_ messages,
even
those addressed to another existing Exchange users, be routed to the smart
host in order to reach parallel mail systems.
Currently we use the simple but inconvenient mechanism having users to
type
explicit user@company.com address instead of using the GAL, when sending
e-mails. Since Exchange does not have this suffix in its recipient policy,
it treats recipients as remote and routes all messages to the smart host.
It
works, but users are not happy, especially those who have the
@exchange.company.com addresses somehow in their local Outlook address
cache.
I thought there could be a solution based on creating another (higher
priority) recipient policy with @company.com address in it and
"authoritative" flag cleared, so that GAL will receive the @company.com
suffix but Exchange will not consider itself authoritative for these
addresses, hence routing to the smart host. However, it doesn't work in my
test environment, since - in accordance with MS KB articles I could find -
Exchange does not care about being authoritative or not as soon as it
finds
a recipient in AD (btw I think this is odd).
A hardly acceptable workaround is to create a Contacts public folder with
all @company.com addresses in it and reconfigure all clients to use this
folder as an address book. Another (very cumbersome) way is to create a
(hidden) contact for each user with the @company.com address and forward
messages to this contact. But we are looking for a better solution.
Is there something we are missing when trying the recipient policies
trick?
Is there another solution that we could implement to accomplish our
routing
goal?
I would greatly appreciate any help.
Best regards and Christmas / New Year wishes,
Boris
P.S.
Some details how I tried the policies trick basing on the description in
KB
823158, 319759, 822943, and 321721:
1. Default policy defines the primary @something.com SMTP suffix;
"responsible" flag is set for it.
2. Another (higher priority) policy defines the primary @company.com
suffix;
"responsible" flag is not set for it.
3. SMTP connector is configured for * namespace to send all messages to
the
outside smart host.
Now I see in the GAL the proper @company.com addresses. However, when I
send
a message to user@company.com, it reaches the local user's mailbox and is
not routed outside. I think it's because Exchange checks the AD (and not a
particular recipient policy) for a user's address.
|
|
|
| Back to top |
|
|
Peter Johnson
Guest
|
| Posted:
Thu Dec 30, 2004 12:18 am Post subject:
Re: Exchange mail routing question |
|
|
Have you tried creating an external contact for each mailbox and making each
external contact an alternative mail recipient for the requisite mailbox and
then hiding the contact? You could probably script this via vbscript and
ldif.
Regards
Peter Johnson
"Boris Lokhvitsky" <msexpert@community.nospam> wrote in message
news:%23vf9Zvc7EHA.4040@TK2MSFTNGP14.phx.gbl...
| Quote: | Hmmm. No reaction yet. Too bad :(
Let me try to reformulate the question making it shorter:
I have Exchange 2003 SP1. I need to forward _ALL_ e-mail messages to the
external smart host.
ALL. Even messages addressed to the internal Exchange/AD recipients.
How can I accomplish this?
Thanks a lot in advance,
Boris
======================================================
"Boris Lokhvitsky" <msexpert@community.nospam> wrote in message
news:u9asCgT7EHA.2156@TK2MSFTNGP10.phx.gbl...
We have a problem concerning Exchange mail routing, and I hope to be able
to
find some advises here.
We use multiple parallel mail systems in the company, with messages being
delivered to all systems simultaneously. Users can connect to either
system
(depending on the client, e.g. desktop, laptop, or PDA) and still read
their
messages.
To accomplish this, we use an internal SMTP namespace
@exchange.company.com
for our Exchange environment, and different external namespace
@company.com
for general e-mail. There is an SMTP connector configured pointing to an
external smart host. The underlying reason is - we need _all_ messages,
even
those addressed to another existing Exchange users, be routed to the
smart
host in order to reach parallel mail systems.
Currently we use the simple but inconvenient mechanism having users to
type
explicit user@company.com address instead of using the GAL, when sending
e-mails. Since Exchange does not have this suffix in its recipient
policy,
it treats recipients as remote and routes all messages to the smart host.
It
works, but users are not happy, especially those who have the
@exchange.company.com addresses somehow in their local Outlook address
cache.
I thought there could be a solution based on creating another (higher
priority) recipient policy with @company.com address in it and
"authoritative" flag cleared, so that GAL will receive the @company.com
suffix but Exchange will not consider itself authoritative for these
addresses, hence routing to the smart host. However, it doesn't work in
my
test environment, since - in accordance with MS KB articles I could
find -
Exchange does not care about being authoritative or not as soon as it
finds
a recipient in AD (btw I think this is odd).
A hardly acceptable workaround is to create a Contacts public folder with
all @company.com addresses in it and reconfigure all clients to use this
folder as an address book. Another (very cumbersome) way is to create a
(hidden) contact for each user with the @company.com address and forward
messages to this contact. But we are looking for a better solution.
Is there something we are missing when trying the recipient policies
trick?
Is there another solution that we could implement to accomplish our
routing
goal?
I would greatly appreciate any help.
Best regards and Christmas / New Year wishes,
Boris
P.S.
Some details how I tried the policies trick basing on the description in
KB
823158, 319759, 822943, and 321721:
1. Default policy defines the primary @something.com SMTP suffix;
"responsible" flag is set for it.
2. Another (higher priority) policy defines the primary @company.com
suffix;
"responsible" flag is not set for it.
3. SMTP connector is configured for * namespace to send all messages to
the
outside smart host.
Now I see in the GAL the proper @company.com addresses. However, when I
send
a message to user@company.com, it reaches the local user's mailbox and is
not routed outside. I think it's because Exchange checks the AD (and not
a
particular recipient policy) for a user's address.
|
|
|
| Back to top |
|
|
Boris Lokhvitsky
Guest
|
| Posted:
Thu Dec 30, 2004 5:35 am Post subject:
Re: Exchange mail routing question |
|
|
Thanks for your suggestion Peter,
This solution is described in my initial post, where I call it "cumbersome".
Imagine this task for several thousand users... not even talking about
making the AD unmanageable with those thousands of contacts...
Another point is that in some cases we need to forward teh messages to more
than 1 external address. I can only configure 1 for frowarding... Hence, I
will need tio create a Windows group for each user (!!!), create necessary
number of contacts, put them into this group and set up forwarding to teh
group alias... This is an administrative suicide :)
Any other suggestions?
Thanks,
Boris
"Peter Johnson" <peterj@mailzone.co.za> wrote in message
news:cqusjb$5k7$1@ctb-nnrp2.saix.net...
| Quote: | Have you tried creating an external contact for each mailbox and making
each
external contact an alternative mail recipient for the requisite mailbox
and
then hiding the contact? You could probably script this via vbscript and
ldif.
Regards
Peter Johnson
"Boris Lokhvitsky" <msexpert@community.nospam> wrote in message
news:%23vf9Zvc7EHA.4040@TK2MSFTNGP14.phx.gbl...
Hmmm. No reaction yet. Too bad :(
Let me try to reformulate the question making it shorter:
I have Exchange 2003 SP1. I need to forward _ALL_ e-mail messages to the
external smart host.
ALL. Even messages addressed to the internal Exchange/AD recipients.
How can I accomplish this?
Thanks a lot in advance,
Boris
======================================================
"Boris Lokhvitsky" <msexpert@community.nospam> wrote in message
news:u9asCgT7EHA.2156@TK2MSFTNGP10.phx.gbl...
We have a problem concerning Exchange mail routing, and I hope to be
able
to
find some advises here.
We use multiple parallel mail systems in the company, with messages
being
delivered to all systems simultaneously. Users can connect to either
system
(depending on the client, e.g. desktop, laptop, or PDA) and still read
their
messages.
To accomplish this, we use an internal SMTP namespace
@exchange.company.com
for our Exchange environment, and different external namespace
@company.com
for general e-mail. There is an SMTP connector configured pointing to
an
external smart host. The underlying reason is - we need _all_ messages,
even
those addressed to another existing Exchange users, be routed to the
smart
host in order to reach parallel mail systems.
Currently we use the simple but inconvenient mechanism having users to
type
explicit user@company.com address instead of using the GAL, when
sending
e-mails. Since Exchange does not have this suffix in its recipient
policy,
it treats recipients as remote and routes all messages to the smart
host.
It
works, but users are not happy, especially those who have the
@exchange.company.com addresses somehow in their local Outlook address
cache.
I thought there could be a solution based on creating another (higher
priority) recipient policy with @company.com address in it and
"authoritative" flag cleared, so that GAL will receive the @company.com
suffix but Exchange will not consider itself authoritative for these
addresses, hence routing to the smart host. However, it doesn't work in
my
test environment, since - in accordance with MS KB articles I could
find -
Exchange does not care about being authoritative or not as soon as it
finds
a recipient in AD (btw I think this is odd).
A hardly acceptable workaround is to create a Contacts public folder
with
all @company.com addresses in it and reconfigure all clients to use
this
folder as an address book. Another (very cumbersome) way is to create a
(hidden) contact for each user with the @company.com address and
forward
messages to this contact. But we are looking for a better solution.
Is there something we are missing when trying the recipient policies
trick?
Is there another solution that we could implement to accomplish our
routing
goal?
I would greatly appreciate any help.
Best regards and Christmas / New Year wishes,
Boris
P.S.
Some details how I tried the policies trick basing on the description
in
KB
823158, 319759, 822943, and 321721:
1. Default policy defines the primary @something.com SMTP suffix;
"responsible" flag is set for it.
2. Another (higher priority) policy defines the primary @company.com
suffix;
"responsible" flag is not set for it.
3. SMTP connector is configured for * namespace to send all messages to
the
outside smart host.
Now I see in the GAL the proper @company.com addresses. However, when I
send
a message to user@company.com, it reaches the local user's mailbox and
is
not routed outside. I think it's because Exchange checks the AD (and
not
a
particular recipient policy) for a user's address.
|
|
|
| Back to top |
|
|
Victor Ivanidze
Guest
|
| Posted:
Thu Dec 30, 2004 8:50 pm Post subject:
Re: Exchange mail routing question |
|
|
I'm not sure that's elegant solution but you could create a custom
application (store event sink) that will redirect each locally delivered
message to the appropriate external SMTP address.
--
Regards,
Victor Ivanidze,
software developer
www.ivasoft.biz
"Boris Lokhvitsky" <msexpert@community.nospam> wrote in message
news:eDo4Y8f7EHA.1452@TK2MSFTNGP11.phx.gbl...
| Quote: | Thanks for your suggestion Peter,
This solution is described in my initial post, where I call it
"cumbersome".
Imagine this task for several thousand users... not even talking about
making the AD unmanageable with those thousands of contacts...
Another point is that in some cases we need to forward teh messages to
more
than 1 external address. I can only configure 1 for frowarding... Hence, I
will need tio create a Windows group for each user (!!!), create necessary
number of contacts, put them into this group and set up forwarding to teh
group alias... This is an administrative suicide :)
Any other suggestions?
Thanks,
Boris
"Peter Johnson" <peterj@mailzone.co.za> wrote in message
news:cqusjb$5k7$1@ctb-nnrp2.saix.net...
Have you tried creating an external contact for each mailbox and making
each
external contact an alternative mail recipient for the requisite mailbox
and
then hiding the contact? You could probably script this via vbscript and
ldif.
Regards
Peter Johnson
"Boris Lokhvitsky" <msexpert@community.nospam> wrote in message
news:%23vf9Zvc7EHA.4040@TK2MSFTNGP14.phx.gbl...
Hmmm. No reaction yet. Too bad :(
Let me try to reformulate the question making it shorter:
I have Exchange 2003 SP1. I need to forward _ALL_ e-mail messages to
the
external smart host.
ALL. Even messages addressed to the internal Exchange/AD recipients.
How can I accomplish this?
Thanks a lot in advance,
Boris
======================================================
"Boris Lokhvitsky" <msexpert@community.nospam> wrote in message
news:u9asCgT7EHA.2156@TK2MSFTNGP10.phx.gbl...
We have a problem concerning Exchange mail routing, and I hope to be
able
to
find some advises here.
We use multiple parallel mail systems in the company, with messages
being
delivered to all systems simultaneously. Users can connect to either
system
(depending on the client, e.g. desktop, laptop, or PDA) and still
read
their
messages.
To accomplish this, we use an internal SMTP namespace
@exchange.company.com
for our Exchange environment, and different external namespace
@company.com
for general e-mail. There is an SMTP connector configured pointing to
an
external smart host. The underlying reason is - we need _all_
messages,
even
those addressed to another existing Exchange users, be routed to the
smart
host in order to reach parallel mail systems.
Currently we use the simple but inconvenient mechanism having users
to
type
explicit user@company.com address instead of using the GAL, when
sending
e-mails. Since Exchange does not have this suffix in its recipient
policy,
it treats recipients as remote and routes all messages to the smart
host.
It
works, but users are not happy, especially those who have the
@exchange.company.com addresses somehow in their local Outlook
address
cache.
I thought there could be a solution based on creating another (higher
priority) recipient policy with @company.com address in it and
"authoritative" flag cleared, so that GAL will receive the
@company.com
suffix but Exchange will not consider itself authoritative for these
addresses, hence routing to the smart host. However, it doesn't work
in
my
test environment, since - in accordance with MS KB articles I could
find -
Exchange does not care about being authoritative or not as soon as it
finds
a recipient in AD (btw I think this is odd).
A hardly acceptable workaround is to create a Contacts public folder
with
all @company.com addresses in it and reconfigure all clients to use
this
folder as an address book. Another (very cumbersome) way is to create
a
(hidden) contact for each user with the @company.com address and
forward
messages to this contact. But we are looking for a better solution.
Is there something we are missing when trying the recipient policies
trick?
Is there another solution that we could implement to accomplish our
routing
goal?
I would greatly appreciate any help.
Best regards and Christmas / New Year wishes,
Boris
P.S.
Some details how I tried the policies trick basing on the description
in
KB
823158, 319759, 822943, and 321721:
1. Default policy defines the primary @something.com SMTP suffix;
"responsible" flag is set for it.
2. Another (higher priority) policy defines the primary @company.com
suffix;
"responsible" flag is not set for it.
3. SMTP connector is configured for * namespace to send all messages
to
the
outside smart host.
Now I see in the GAL the proper @company.com addresses. However, when
I
send
a message to user@company.com, it reaches the local user's mailbox
and
is
not routed outside. I think it's because Exchange checks the AD (and
not
a
particular recipient policy) for a user's address.
|
|
|
| Back to top |
|
|
Boris Lokhvitsky
Guest
|
| Posted:
Fri Dec 31, 2004 12:15 am Post subject:
Re: Exchange mail routing question |
|
|
Thank you Victor,
We were thinking about this, too. Not enough experience here... and I still
have some concern... like, in this case each Exchange user will receive a
duplicate of each message (the initial one plus the message that had been
forwarded, passed through external SMTP hosts and returned back to the
recipient).
We'll keep thinking in this direction, though.
Thanks,
Boris
P.S. Taking the opportunity, I wish to thank you personally for your
wonderful site and lots of useful Exchange utilities. Your selective
journaling tool, as to my belief, still remains out of competition. Bolshoye
spasibo!
"Victor Ivanidze" <no@spam.please> wrote in message
news:e4GOE6n7EHA.1452@TK2MSFTNGP11.phx.gbl...
| Quote: | I'm not sure that's elegant solution but you could create a custom
application (store event sink) that will redirect each locally delivered
message to the appropriate external SMTP address.
--
Regards,
Victor Ivanidze,
software developer
www.ivasoft.biz
"Boris Lokhvitsky" <msexpert@community.nospam> wrote in message
news:eDo4Y8f7EHA.1452@TK2MSFTNGP11.phx.gbl...
Thanks for your suggestion Peter,
This solution is described in my initial post, where I call it
"cumbersome".
Imagine this task for several thousand users... not even talking about
making the AD unmanageable with those thousands of contacts...
Another point is that in some cases we need to forward teh messages to
more
than 1 external address. I can only configure 1 for frowarding... Hence,
I
will need tio create a Windows group for each user (!!!), create
necessary
number of contacts, put them into this group and set up forwarding to
teh
group alias... This is an administrative suicide :)
Any other suggestions?
Thanks,
Boris
"Peter Johnson" <peterj@mailzone.co.za> wrote in message
news:cqusjb$5k7$1@ctb-nnrp2.saix.net...
Have you tried creating an external contact for each mailbox and
making
each
external contact an alternative mail recipient for the requisite
mailbox
and
then hiding the contact? You could probably script this via vbscript
and
ldif.
Regards
Peter Johnson
"Boris Lokhvitsky" <msexpert@community.nospam> wrote in message
news:%23vf9Zvc7EHA.4040@TK2MSFTNGP14.phx.gbl...
Hmmm. No reaction yet. Too bad :(
Let me try to reformulate the question making it shorter:
I have Exchange 2003 SP1. I need to forward _ALL_ e-mail messages to
the
external smart host.
ALL. Even messages addressed to the internal Exchange/AD recipients.
How can I accomplish this?
Thanks a lot in advance,
Boris
======================================================
"Boris Lokhvitsky" <msexpert@community.nospam> wrote in message
news:u9asCgT7EHA.2156@TK2MSFTNGP10.phx.gbl...
We have a problem concerning Exchange mail routing, and I hope to
be
able
to
find some advises here.
We use multiple parallel mail systems in the company, with messages
being
delivered to all systems simultaneously. Users can connect to
either
system
(depending on the client, e.g. desktop, laptop, or PDA) and still
read
their
messages.
To accomplish this, we use an internal SMTP namespace
@exchange.company.com
for our Exchange environment, and different external namespace
@company.com
for general e-mail. There is an SMTP connector configured pointing
to
an
external smart host. The underlying reason is - we need _all_
messages,
even
those addressed to another existing Exchange users, be routed to
the
smart
host in order to reach parallel mail systems.
Currently we use the simple but inconvenient mechanism having users
to
type
explicit user@company.com address instead of using the GAL, when
sending
e-mails. Since Exchange does not have this suffix in its recipient
policy,
it treats recipients as remote and routes all messages to the smart
host.
It
works, but users are not happy, especially those who have the
@exchange.company.com addresses somehow in their local Outlook
address
cache.
I thought there could be a solution based on creating another
(higher
priority) recipient policy with @company.com address in it and
"authoritative" flag cleared, so that GAL will receive the
@company.com
suffix but Exchange will not consider itself authoritative for
these
addresses, hence routing to the smart host. However, it doesn't
work
in
my
test environment, since - in accordance with MS KB articles I could
find -
Exchange does not care about being authoritative or not as soon as
it
finds
a recipient in AD (btw I think this is odd).
A hardly acceptable workaround is to create a Contacts public
folder
with
all @company.com addresses in it and reconfigure all clients to use
this
folder as an address book. Another (very cumbersome) way is to
create
a
(hidden) contact for each user with the @company.com address and
forward
messages to this contact. But we are looking for a better solution.
Is there something we are missing when trying the recipient
policies
trick?
Is there another solution that we could implement to accomplish our
routing
goal?
I would greatly appreciate any help.
Best regards and Christmas / New Year wishes,
Boris
P.S.
Some details how I tried the policies trick basing on the
description
in
KB
823158, 319759, 822943, and 321721:
1. Default policy defines the primary @something.com SMTP suffix;
"responsible" flag is set for it.
2. Another (higher priority) policy defines the primary
@company.com
suffix;
"responsible" flag is not set for it.
3. SMTP connector is configured for * namespace to send all
messages
to
the
outside smart host.
Now I see in the GAL the proper @company.com addresses. However,
when
I
send
a message to user@company.com, it reaches the local user's mailbox
and
is
not routed outside. I think it's because Exchange checks the AD
(and
not
a
particular recipient policy) for a user's address.
|
|
|
| Back to top |
|
|
Ben Winzenz [Exchange MVP
Guest
|
| Posted:
Fri Dec 31, 2004 12:41 am Post subject:
Re: Exchange mail routing question |
|
|
Well, that kind of depends on how you write the event sink. If you
configure your event sink to catch the messages before they are delivered to
the Store, then there will not be duplicates.
--
Ben Winzenz
Exchange MVP
"Boris Lokhvitsky" <msexpert@community.nospam> wrote in message
news:uC3NKup7EHA.2540@TK2MSFTNGP09.phx.gbl...
| Quote: | Thank you Victor,
We were thinking about this, too. Not enough experience here... and I
still
have some concern... like, in this case each Exchange user will receive a
duplicate of each message (the initial one plus the message that had been
forwarded, passed through external SMTP hosts and returned back to the
recipient).
We'll keep thinking in this direction, though.
Thanks,
Boris
P.S. Taking the opportunity, I wish to thank you personally for your
wonderful site and lots of useful Exchange utilities. Your selective
journaling tool, as to my belief, still remains out of competition.
Bolshoye
spasibo!
"Victor Ivanidze" <no@spam.please> wrote in message
news:e4GOE6n7EHA.1452@TK2MSFTNGP11.phx.gbl...
I'm not sure that's elegant solution but you could create a custom
application (store event sink) that will redirect each locally delivered
message to the appropriate external SMTP address.
--
Regards,
Victor Ivanidze,
software developer
www.ivasoft.biz
"Boris Lokhvitsky" <msexpert@community.nospam> wrote in message
news:eDo4Y8f7EHA.1452@TK2MSFTNGP11.phx.gbl...
Thanks for your suggestion Peter,
This solution is described in my initial post, where I call it
"cumbersome".
Imagine this task for several thousand users... not even talking about
making the AD unmanageable with those thousands of contacts...
Another point is that in some cases we need to forward teh messages to
more
than 1 external address. I can only configure 1 for frowarding...
Hence,
I
will need tio create a Windows group for each user (!!!), create
necessary
number of contacts, put them into this group and set up forwarding to
teh
group alias... This is an administrative suicide :)
Any other suggestions?
Thanks,
Boris
"Peter Johnson" <peterj@mailzone.co.za> wrote in message
news:cqusjb$5k7$1@ctb-nnrp2.saix.net...
Have you tried creating an external contact for each mailbox and
making
each
external contact an alternative mail recipient for the requisite
mailbox
and
then hiding the contact? You could probably script this via vbscript
and
ldif.
Regards
Peter Johnson
"Boris Lokhvitsky" <msexpert@community.nospam> wrote in message
news:%23vf9Zvc7EHA.4040@TK2MSFTNGP14.phx.gbl...
Hmmm. No reaction yet. Too bad :(
Let me try to reformulate the question making it shorter:
I have Exchange 2003 SP1. I need to forward _ALL_ e-mail messages
to
the
external smart host.
ALL. Even messages addressed to the internal Exchange/AD
recipients.
How can I accomplish this?
Thanks a lot in advance,
Boris
======================================================
"Boris Lokhvitsky" <msexpert@community.nospam> wrote in message
news:u9asCgT7EHA.2156@TK2MSFTNGP10.phx.gbl...
We have a problem concerning Exchange mail routing, and I hope to
be
able
to
find some advises here.
We use multiple parallel mail systems in the company, with
messages
being
delivered to all systems simultaneously. Users can connect to
either
system
(depending on the client, e.g. desktop, laptop, or PDA) and still
read
their
messages.
To accomplish this, we use an internal SMTP namespace
@exchange.company.com
for our Exchange environment, and different external namespace
@company.com
for general e-mail. There is an SMTP connector configured pointing
to
an
external smart host. The underlying reason is - we need _all_
messages,
even
those addressed to another existing Exchange users, be routed to
the
smart
host in order to reach parallel mail systems.
Currently we use the simple but inconvenient mechanism having
users
to
type
explicit user@company.com address instead of using the GAL, when
sending
e-mails. Since Exchange does not have this suffix in its recipient
policy,
it treats recipients as remote and routes all messages to the
smart
host.
It
works, but users are not happy, especially those who have the
@exchange.company.com addresses somehow in their local Outlook
address
cache.
I thought there could be a solution based on creating another
(higher
priority) recipient policy with @company.com address in it and
"authoritative" flag cleared, so that GAL will receive the
@company.com
suffix but Exchange will not consider itself authoritative for
these
addresses, hence routing to the smart host. However, it doesn't
work
in
my
test environment, since - in accordance with MS KB articles I
could
find -
Exchange does not care about being authoritative or not as soon as
it
finds
a recipient in AD (btw I think this is odd).
A hardly acceptable workaround is to create a Contacts public
folder
with
all @company.com addresses in it and reconfigure all clients to
use
this
folder as an address book. Another (very cumbersome) way is to
create
a
(hidden) contact for each user with the @company.com address and
forward
messages to this contact. But we are looking for a better
solution.
Is there something we are missing when trying the recipient
policies
trick?
Is there another solution that we could implement to accomplish
our
routing
goal?
I would greatly appreciate any help.
Best regards and Christmas / New Year wishes,
Boris
P.S.
Some details how I tried the policies trick basing on the
description
in
KB
823158, 319759, 822943, and 321721:
1. Default policy defines the primary @something.com SMTP suffix;
"responsible" flag is set for it.
2. Another (higher priority) policy defines the primary
@company.com
suffix;
"responsible" flag is not set for it.
3. SMTP connector is configured for * namespace to send all
messages
to
the
outside smart host.
Now I see in the GAL the proper @company.com addresses. However,
when
I
send
a message to user@company.com, it reaches the local user's mailbox
and
is
not routed outside. I think it's because Exchange checks the AD
(and
not
a
particular recipient policy) for a user's address.
|
|
|
| Back to top |
|
|
Victor Ivanidze
Guest
|
| Posted:
Thu Jan 06, 2005 3:38 pm Post subject:
Re: Exchange mail routing question |
|
|
Boris,
I think it's possible to mark a forwarded message and then
delete an original one to prevent duplicates.
Thank you for your kind words about our products.
--
Regards,
Victor Ivanidze,
software developer
www.ivasoft.biz
"Boris Lokhvitsky" <msexpert@community.nospam> wrote in message
news:uC3NKup7EHA.2540@TK2MSFTNGP09.phx.gbl...
| Quote: | Thank you Victor,
We were thinking about this, too. Not enough experience here... and I
still
have some concern... like, in this case each Exchange user will receive a
duplicate of each message (the initial one plus the message that had been
forwarded, passed through external SMTP hosts and returned back to the
recipient).
We'll keep thinking in this direction, though.
Thanks,
Boris
P.S. Taking the opportunity, I wish to thank you personally for your
wonderful site and lots of useful Exchange utilities. Your selective
journaling tool, as to my belief, still remains out of competition.
Bolshoye
spasibo!
"Victor Ivanidze" <no@spam.please> wrote in message
news:e4GOE6n7EHA.1452@TK2MSFTNGP11.phx.gbl...
I'm not sure that's elegant solution but you could create a custom
application (store event sink) that will redirect each locally delivered
message to the appropriate external SMTP address.
--
Regards,
Victor Ivanidze,
software developer
www.ivasoft.biz
"Boris Lokhvitsky" <msexpert@community.nospam> wrote in message
news:eDo4Y8f7EHA.1452@TK2MSFTNGP11.phx.gbl...
Thanks for your suggestion Peter,
This solution is described in my initial post, where I call it
"cumbersome".
Imagine this task for several thousand users... not even talking about
making the AD unmanageable with those thousands of contacts...
Another point is that in some cases we need to forward teh messages to
more
than 1 external address. I can only configure 1 for frowarding...
Hence,
I
will need tio create a Windows group for each user (!!!), create
necessary
number of contacts, put them into this group and set up forwarding to
teh
group alias... This is an administrative suicide :)
Any other suggestions?
Thanks,
Boris
"Peter Johnson" <peterj@mailzone.co.za> wrote in message
news:cqusjb$5k7$1@ctb-nnrp2.saix.net...
Have you tried creating an external contact for each mailbox and
making
each
external contact an alternative mail recipient for the requisite
mailbox
and
then hiding the contact? You could probably script this via vbscript
and
ldif.
Regards
Peter Johnson
"Boris Lokhvitsky" <msexpert@community.nospam> wrote in message
news:%23vf9Zvc7EHA.4040@TK2MSFTNGP14.phx.gbl...
Hmmm. No reaction yet. Too bad :(
Let me try to reformulate the question making it shorter:
I have Exchange 2003 SP1. I need to forward _ALL_ e-mail messages
to
the
external smart host.
ALL. Even messages addressed to the internal Exchange/AD
recipients.
How can I accomplish this?
Thanks a lot in advance,
Boris
======================================================
"Boris Lokhvitsky" <msexpert@community.nospam> wrote in message
news:u9asCgT7EHA.2156@TK2MSFTNGP10.phx.gbl...
We have a problem concerning Exchange mail routing, and I hope to
be
able
to
find some advises here.
We use multiple parallel mail systems in the company, with
messages
being
delivered to all systems simultaneously. Users can connect to
either
system
(depending on the client, e.g. desktop, laptop, or PDA) and still
read
their
messages.
To accomplish this, we use an internal SMTP namespace
@exchange.company.com
for our Exchange environment, and different external namespace
@company.com
for general e-mail. There is an SMTP connector configured
pointing
to
an
external smart host. The underlying reason is - we need _all_
messages,
even
those addressed to another existing Exchange users, be routed to
the
smart
host in order to reach parallel mail systems.
Currently we use the simple but inconvenient mechanism having
users
to
type
explicit user@company.com address instead of using the GAL, when
sending
e-mails. Since Exchange does not have this suffix in its
recipient
policy,
it treats recipients as remote and routes all messages to the
smart
host.
It
works, but users are not happy, especially those who have the
@exchange.company.com addresses somehow in their local Outlook
address
cache.
I thought there could be a solution based on creating another
(higher
priority) recipient policy with @company.com address in it and
"authoritative" flag cleared, so that GAL will receive the
@company.com
suffix but Exchange will not consider itself authoritative for
these
addresses, hence routing to the smart host. However, it doesn't
work
in
my
test environment, since - in accordance with MS KB articles I
could
find -
Exchange does not care about being authoritative or not as soon
as
it
finds
a recipient in AD (btw I think this is odd).
A hardly acceptable workaround is to create a Contacts public
folder
with
all @company.com addresses in it and reconfigure all clients to
use
this
folder as an address book. Another (very cumbersome) way is to
create
a
(hidden) contact for each user with the @company.com address and
forward
messages to this contact. But we are looking for a better
solution.
Is there something we are missing when trying the recipient
policies
trick?
Is there another solution that we could implement to accomplish
our
routing
goal?
I would greatly appreciate any help.
Best regards and Christmas / New Year wishes,
Boris
P.S.
Some details how I tried the policies trick basing on the
description
in
KB
823158, 319759, 822943, and 321721:
1. Default policy defines the primary @something.com SMTP suffix;
"responsible" flag is set for it.
2. Another (higher priority) policy defines the primary
@company.com
suffix;
"responsible" flag is not set for it.
3. SMTP connector is configured for * namespace to send all
messages
to
the
outside smart host.
Now I see in the GAL the proper @company.com addresses. However,
when
I
send
a message to user@company.com, it reaches the local user's
mailbox
and
is
not routed outside. I think it's because Exchange checks the AD
(and
not
a
particular recipient policy) for a user's address.
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in