RE: Not even sure how to title this..

2001-12-13 Thread Exchange

Jeff...

I am intimately familiar with this issue and most of its mutations. I am
an Exchange / AD consultant and just completed a migration to E2K of
22,000 mailboxes where 3 mail systems all shared the same SMTP domain
name. It took a little work, but routing is efficient and works like a
charm.

It all depends on the exact details of your implementation, but in a
nutshell: you have to close the loop somewhere, and I suggest you let
outside mail come in to the E2K boxes (like you already are). These
servers will deliver the messages if the recipients are on E2K or the
5.5 boxes (they're in the same Org. right? So they'll know of ANY
Exchange recipient, not just the ones residing on the E2K boxes, and
they'll forward to the 5.5 boxes directly or based on routing group
connectors, or whatever you have joining your sites) and if they don't
see the recipient as having a mailbox on any of the Exchange servers,
they'll pass it on to the Sendmail box. The Sendmail box then needs to
either deliver locally, or NDR. The logic being, if Exchange passed it
on to it, the only other place the recipient can exist is on the
Sendmail box itself. So if Sendmail doesn't host the recipient, then it
is safe to NDR the message, and it shouldn't send it to any of the 5.5
boxes. To make all of this work, the other key is to have the E2K boxes,
which receive the outside mail, know of everyone on the inside of your
organization - whether they're on Exchange or not. This way, the E2K
boxes will accept mail for anyone on your internal mail systems
(listserv lists, etc.) There are a bunch of different options on how to
get Exchange to forward the messages to your smtp.domain.edu server, but
I've found the forward unresolved... not to be the best choice...

There's lots of little nuances in these scenarios, but it is possible,
and actually not all that hard (once you've beat your head against the
wall for a few weeks and found out a handful of undocumented things). I
feel your pain on this, and would be happy to have a quick chat with you
if you like. Send me an email at [EMAIL PROTECTED] and we can
arrange for phone call.

All the best,
Per 
 



-Original Message-
From: Edgington, Jeffrey [mailto:[EMAIL PROTECTED]] 
Posted At: Wednesday, December 12, 2001 4:00 PM
Posted To: Exchange
Conversation: Not even sure how to title this..
Subject: Not even sure how to title this..

Sorry, but long... (names have been changed)... any suggestions would be
greatly appreciated (and constructive criticism humbly accepted).



Environment:
Mixed Mode with 3 E5.5 Servers and 5 E2K servers. 
e55-mail01 - E5.5 - IMC, x.400 site connector 
e55-mail02 - E5.5 - mailbox server 
e55-mail03 - E5.5 - mailbox server 
e2k-mail1 - E2K - participating in accepting inbound SMTP for entire
site 
e2k-mail2 - E2K - participating in accepting inbound SMTP for entire
site 
umr-msxproto1 - E2K - currently just idling - will be a front-end server

umr-msxproto2 - E2K - SRS server 
umr-msxproto3 - E2K - currently just idling - will be a front-end server
 
--Inbound SMTP mail is flowing through e2k-mail1 and e2k-mail2 while
outbound is flowing through e55-mail01 just a transition state...
eventually all in/outbound will be handled by E2K. 

--e2k-mail1 and e2k-mail2 are configured to send all unresolved e-mail
to
smtp.domain.edu (Linux Sendmail box)... this is because domain.edu is
shared
by AD and Linux and we have listserv lists (like [EMAIL PROTECTED])
that
are on a Linux Listserv box. Additionally all  mailboxes in Exchange
have an
additional e-mail address of [EMAIL PROTECTED] (besides their
primary of
[EMAIL PROTECTED]).. this is so  mail routed through smtp.domain.edu can
route the smtp mail to either a sendmail box or exchange for example
if
[EMAIL PROTECTED] comes in  to smtp.domain.edu and he is on exchange, the
address is re-written to [EMAIL PROTECTED] ... if he is on the
Sendmail
box the address is  left unchanged. 

--In E5.5 we have CRs configured with a primary address of @domain.edu
and a
forwarding address of @domain.edu (before my time and I'm unsure as to
why
it's this way)... messages addressed to these  CRs flow out the IMC on
e55-mail01 



Problem: 
If I address a message to [EMAIL PROTECTED] this will route through
smtp.domain.edu (sendmail) and into e2k-mail1 or e2k-mail2 (E2K)...
these
servers will not find this address... they will then (because they are
configured to) route this to smtp.domain.edu (passing it  through
e55-mail01
on the way to smtp.domain.edu).. this is a mail loop and fills the
transaction log drive on e55-mail01 summary: 

1. email to: [EMAIL PROTECTED] (not a valid address in exchange) 
2. smtp.domain.edu (sendmail) receives it from the internet 
3. e2k-mail1  (or e2k-mail2) receives it from smtp.domain.edu 
4. E2K box does not resolve the name and so forwards it to
smtp.domain.edu
via e55-mail01 
5.  smtp.domain.edu receives it from e55-mail01 and sends it to
e2k-mail1 or
e2k-mail2 ... goto 4

Not even sure how to title this..

2001-12-12 Thread Edgington, Jeffrey

Sorry, but long... (names have been changed)... any suggestions would be
greatly appreciated (and constructive criticism humbly accepted).



Environment:
Mixed Mode with 3 E5.5 Servers and 5 E2K servers. 
e55-mail01 - E5.5 - IMC, x.400 site connector 
e55-mail02 - E5.5 - mailbox server 
e55-mail03 - E5.5 - mailbox server 
e2k-mail1 - E2K - participating in accepting inbound SMTP for entire site 
e2k-mail2 - E2K - participating in accepting inbound SMTP for entire site 
umr-msxproto1 - E2K - currently just idling - will be a front-end server 
umr-msxproto2 - E2K - SRS server 
umr-msxproto3 - E2K - currently just idling - will be a front-end server
 
--Inbound SMTP mail is flowing through e2k-mail1 and e2k-mail2 while
outbound is flowing through e55-mail01 just a transition state...
eventually all in/outbound will be handled by E2K. 

--e2k-mail1 and e2k-mail2 are configured to send all unresolved e-mail to
smtp.domain.edu (Linux Sendmail box)... this is because domain.edu is shared
by AD and Linux and we have listserv lists (like [EMAIL PROTECTED]) that
are on a Linux Listserv box. Additionally all  mailboxes in Exchange have an
additional e-mail address of [EMAIL PROTECTED] (besides their primary of
[EMAIL PROTECTED]).. this is so  mail routed through smtp.domain.edu can
route the smtp mail to either a sendmail box or exchange for example if
[EMAIL PROTECTED] comes in  to smtp.domain.edu and he is on exchange, the
address is re-written to [EMAIL PROTECTED] ... if he is on the Sendmail
box the address is  left unchanged. 

--In E5.5 we have CRs configured with a primary address of @domain.edu and a
forwarding address of @domain.edu (before my time and I'm unsure as to why
it's this way)... messages addressed to these  CRs flow out the IMC on
e55-mail01 



Problem: 
If I address a message to [EMAIL PROTECTED] this will route through
smtp.domain.edu (sendmail) and into e2k-mail1 or e2k-mail2 (E2K)...  these
servers will not find this address... they will then (because they are
configured to) route this to smtp.domain.edu (passing it  through e55-mail01
on the way to smtp.domain.edu).. this is a mail loop and fills the
transaction log drive on e55-mail01 summary: 

1. email to: [EMAIL PROTECTED] (not a valid address in exchange) 
2. smtp.domain.edu (sendmail) receives it from the internet 
3. e2k-mail1  (or e2k-mail2) receives it from smtp.domain.edu 
4. E2K box does not resolve the name and so forwards it to smtp.domain.edu
via e55-mail01 
5.  smtp.domain.edu receives it from e55-mail01 and sends it to e2k-mail1 or
e2k-mail2 ... goto 4 

The reason that I have 'Forward all mail with unresolved recipients to host'
configured (properties of 'default smtp virtual server'  then 'Messages'
tab) is because we have listserv addresses like [EMAIL PROTECTED] that are
hosted on a Linux Listserv box.. without this  configured e-mail to the
listserv lists bounce for users on E2K. 

Additionally, when and E5.5 mailbox sends to a Custom Recipient (configured
as above), the message is sent out the E5.5 IMC... a  mailbox on E2K sends
to this same CR and gets NDR stating  A configuration error in the e-mail
system caused the message to bounce  between two servers or to be forwarded
between two recipients. Contact your administrator. 
e2k-mail1.domain.edu #5.4.6 
 

Questions: 

1. Is there a way to tell E2K to forward the @domain.edu messages that don't
resolve to smtp.domain.edu without using the above configuration? 

2. Is there a way to tell E2K NOT to forward @msx.domain.edu messages when
they don't resolve? 

Things I'm after: 

1. Mail from exchange to @domain.edu - if addr matches a primary or proxy
address, deliver locally, otherwise send to smtp.domain.edu 

2. Mail from exchange to @msx.domain.edu - if addr matches a primary or
proxy address, deliver locally, otherwise bounce 

3. Mail from exchange to any other domain - send to smtp.domain.edu 

4. Mail from exchange - if addr matches a primary address for a custom
recipient that is forwarding to @domain.edu that is not resolvable  locally,
send it to smtp.domain.edu, do not treat it as a bounce. (Right now, it
bounces on e2k, but on E55 it dumps it out smtp.domain.edu.) 

5. The two e2k SMTP hosts should accept mail only for @domain.edu or
@msx.domain.edu (I believe we have this functional with recipient policy and
the setting for relay.) 

Thanks. 

---
Jeffrey Edgington
Systems Administrator
University of Missouri - Rolla
Are you a Spectator or a Participant?
--- 

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



RE: Not even sure how to title this..

2001-12-12 Thread Kevin Miller

200$ an hour..  You need a consultant. My brain hurt before getting to
the Question.

--Kevinm M, WLKMMAS, UCC+WCA, CKWSE, CKST, HWPHHIICP


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Edgington,
Jeffrey
Sent: Wednesday, December 12, 2001 2:00 PM
To: Exchange Discussions
Subject: Not even sure how to title this..


Sorry, but long... (names have been changed)... any suggestions would be
greatly appreciated (and constructive criticism humbly accepted).



Environment:
Mixed Mode with 3 E5.5 Servers and 5 E2K servers. 
e55-mail01 - E5.5 - IMC, x.400 site connector 
e55-mail02 - E5.5 - mailbox server 
e55-mail03 - E5.5 - mailbox server 
e2k-mail1 - E2K - participating in accepting inbound SMTP for entire
site 
e2k-mail2 - E2K - participating in accepting inbound SMTP for entire
site 
umr-msxproto1 - E2K - currently just idling - will be a front-end server

umr-msxproto2 - E2K - SRS server 
umr-msxproto3 - E2K - currently just idling - will be a front-end server
 
--Inbound SMTP mail is flowing through e2k-mail1 and e2k-mail2 while
outbound is flowing through e55-mail01 just a transition state...
eventually all in/outbound will be handled by E2K. 

--e2k-mail1 and e2k-mail2 are configured to send all unresolved e-mail
to smtp.domain.edu (Linux Sendmail box)... this is because domain.edu is
shared by AD and Linux and we have listserv lists (like
[EMAIL PROTECTED]) that are on a Linux Listserv box. Additionally all
mailboxes in Exchange have an additional e-mail address of
[EMAIL PROTECTED] (besides their primary of [EMAIL PROTECTED])..
this is so  mail routed through smtp.domain.edu can route the smtp mail
to either a sendmail box or exchange for example if [EMAIL PROTECTED]
comes in  to smtp.domain.edu and he is on exchange, the address is
re-written to [EMAIL PROTECTED] ... if he is on the Sendmail box the
address is  left unchanged. 

--In E5.5 we have CRs configured with a primary address of @domain.edu
and a forwarding address of @domain.edu (before my time and I'm unsure
as to why it's this way)... messages addressed to these  CRs flow out
the IMC on e55-mail01 



Problem: 
If I address a message to [EMAIL PROTECTED] this will route through
smtp.domain.edu (sendmail) and into e2k-mail1 or e2k-mail2 (E2K)...
these servers will not find this address... they will then (because they
are configured to) route this to smtp.domain.edu (passing it  through
e55-mail01 on the way to smtp.domain.edu).. this is a mail loop and
fills the transaction log drive on e55-mail01 summary: 

1. email to: [EMAIL PROTECTED] (not a valid address in exchange) 
2. smtp.domain.edu (sendmail) receives it from the internet 
3. e2k-mail1  (or e2k-mail2) receives it from smtp.domain.edu 
4. E2K box does not resolve the name and so forwards it to
smtp.domain.edu via e55-mail01 
5.  smtp.domain.edu receives it from e55-mail01 and sends it to
e2k-mail1 or e2k-mail2 ... goto 4 

The reason that I have 'Forward all mail with unresolved recipients to
host' configured (properties of 'default smtp virtual server'  then
'Messages'
tab) is because we have listserv addresses like [EMAIL PROTECTED] that
are hosted on a Linux Listserv box.. without this  configured e-mail to
the listserv lists bounce for users on E2K. 

Additionally, when and E5.5 mailbox sends to a Custom Recipient
(configured as above), the message is sent out the E5.5 IMC... a
mailbox on E2K sends to this same CR and gets NDR stating  A
configuration error in the e-mail system caused the message to bounce
between two servers or to be forwarded between two recipients. Contact
your administrator. 
e2k-mail1.domain.edu #5.4.6 
 

Questions: 

1. Is there a way to tell E2K to forward the @domain.edu messages that
don't resolve to smtp.domain.edu without using the above configuration? 

2. Is there a way to tell E2K NOT to forward @msx.domain.edu messages
when they don't resolve? 

Things I'm after: 

1. Mail from exchange to @domain.edu - if addr matches a primary or
proxy address, deliver locally, otherwise send to smtp.domain.edu 

2. Mail from exchange to @msx.domain.edu - if addr matches a primary or
proxy address, deliver locally, otherwise bounce 

3. Mail from exchange to any other domain - send to smtp.domain.edu 

4. Mail from exchange - if addr matches a primary address for a custom
recipient that is forwarding to @domain.edu that is not resolvable
locally, send it to smtp.domain.edu, do not treat it as a bounce. (Right
now, it bounces on e2k, but on E55 it dumps it out smtp.domain.edu.) 

5. The two e2k SMTP hosts should accept mail only for @domain.edu or
@msx.domain.edu (I believe we have this functional with recipient policy
and the setting for relay.) 

Thanks. 

---
Jeffrey Edgington
Systems Administrator
University of Missouri - Rolla
Are you a Spectator or a Participant