RE: Future plans 2

2002-02-14 Thread Neil Hobson

The reason I mentioned OWA in the first place is because I've done this
for a customer of mine in the UK.  They've got several people from a
small corner-shop outfit in the USA (called WalMart I think...!)
accessing mailboxes on their system via OWA.  Using SSL of course... :-)


Neil Hobson

Silversands
http://www.silversands.co.uk
Microsoft Gold Certified Partner
For Enterprise Systems
For Collaborative Solutions
 
-Original Message-
From: Matthew Carpenter [mailto:[EMAIL PROTECTED]] 
Posted At: 13 February 2002 21:09
Posted To: Sunbelt Exchange List
Conversation: Future plans 2
Subject: RE: Future plans 2


That is the best answer I have received, and you are right. I have no
idea how to implement this without dropped mail to nonhomed recipients
here OR there. I will discuss with them the different options that truly
seem available:
They home the mailboxes and we use OWA to use their domain 
there is a LEGAL partnership in which we act as connected sites, only
passing THEIR address book
I have not found another way around this, nor have I heard a good
alternative otherwise
-Original Message-
From: Benjamin Winzenz [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 13, 2002 1:08 PM
To: MS-Exchange Admin Issues
Subject: RE: Future plans 2


I'm just saying that you may want to consult with your legal department.
Having the permission of the owner of the domain doesn't mean squat in
the legal world.  You are talking about basically interchanging internal
company information.  That, plus you don't have a plan in place how you
want to accomplish this.  The owner of the domain may not realize the
scope of a project like this, which may not even be possible.  In your
given scenario below, if you were to add an MX record for their domain
and accept it as inbound, you would HAVE to have a way to route the
messages destined for their employees.  Otherwise, mail is going to
bounce.  Why?  Because the way that MX records work is that the server
with the lowest cost gets most of the messages sent to it.  There will
be some messages that get sent to the other server.  There isn't any way
around this.  That means that you will be receiving mail for possibly
ANY person working at the other company.  You get a message for a person
at the other company, and your Exchange server doesn't know what the
hell to do with it.  You don't have any recipients with that name set
up.  Ends up being very messy.

I was thinking earlier about setting up custom recipients for them, but
that too would end up being messy, and I don't think it would work.
They could, however, set up some mailboxes and custom recipients for
you, have the mailbox deliver mail to the custom recipient and have
those custom recipients forward the mail to your server.  That, or
setting up some mailboxes for you and you using OWA, would be by far the
easiest, if not the only, solutions to what you are asking.  Anything
else is sounding more like a consulting gig to find a solution to your
problem.

If they are so insistent on you using their e-mail, why don't they
provide the solution?  Otherwise, tell them to go with the
above-mentioned OWA, or forward your mail via CR's, and let you reply
using your own addy's.

Ben Winzenz, MCSE 
Network/Systems Administrator 
Peregrine Systems 

-Original Message-
From: Matthew Carpenter [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 13, 2002 1:25 PM
To: MS-Exchange Admin Issues
Subject: RE: Future plans 2

What do you mean legally? If we have the permission of the owner of the
domain, there is no issue. 
-Original Message- 
From: Benjamin Winzenz [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 13, 2002 10:48 AM 
To: MS-Exchange Admin Issues 
Subject: RE: Future plans 2 

Other than this type of plan, there will be nothing that will not take a
large amount of time and effort to do.  You may not even legally be able
to do more than this.  Check with your legal department.
Ben Winzenz, MCSE 
Network/Systems Administrator 
Peregrine Systems 

-Original Message- 
From: Neil Hobson [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 13, 2002 11:30 AM 
To: MS-Exchange Admin Issues 
Subject: RE: Future plans 2 
Get them to create you a few mailboxes on their system, and access them
via OWA. 

Neil Hobson 
Silversands 
http://www.silversands.co.uk 
Microsoft Gold Certified Partner 
For Enterprise Systems 
For Collaborative Solutions 
-Original Message- 
From: Matthew Carpenter [mailto:[EMAIL PROTECTED]] 
Posted At: 13 February 2002 15:21 
Posted To: Sunbelt Exchange List 
Conversation: Future plans 2 
Subject: Future plans 2 

I am going to try this one more time. I think some of you can help me on
this. TIA -Original Message- 
From: Matthew Carpenter 
Sent: Tuesday, February 12, 2002 2:52 PM 
To: 'MS-Exchange Admin Issues' 
Subject: Future plans 

We have future plans to work with another company on a few projects, and
they want some of us to use THEIR email

RE: Future plans 2

2002-02-14 Thread Neil Hobson

The reason I mentioned OWA in the first place is because I've done this
for a customer of mine in the UK.  They've got several people from a
small corner-shop outfit in the USA (called WalMart I think...!)
accessing mailboxes on their system via OWA.  Using SSL of course... :-)


Neil Hobson

Silversands
http://www.silversands.co.uk
Microsoft Gold Certified Partner
For Enterprise Systems
For Collaborative Solutions
 
-Original Message-
From: Matthew Carpenter [mailto:[EMAIL PROTECTED]] 
Posted At: 13 February 2002 21:09
Posted To: Sunbelt Exchange List
Conversation: Future plans 2
Subject: RE: Future plans 2


That is the best answer I have received, and you are right. I have no
idea how to implement this without dropped mail to nonhomed recipients
here OR there. I will discuss with them the different options that truly
seem available:
They home the mailboxes and we use OWA to use their domain 
there is a LEGAL partnership in which we act as connected sites, only
passing THEIR address book
I have not found another way around this, nor have I heard a good
alternative otherwise
-Original Message-
From: Benjamin Winzenz [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 13, 2002 1:08 PM
To: MS-Exchange Admin Issues
Subject: RE: Future plans 2


I'm just saying that you may want to consult with your legal department.
Having the permission of the owner of the domain doesn't mean squat in
the legal world.  You are talking about basically interchanging internal
company information.  That, plus you don't have a plan in place how you
want to accomplish this.  The owner of the domain may not realize the
scope of a project like this, which may not even be possible.  In your
given scenario below, if you were to add an MX record for their domain
and accept it as inbound, you would HAVE to have a way to route the
messages destined for their employees.  Otherwise, mail is going to
bounce.  Why?  Because the way that MX records work is that the server
with the lowest cost gets most of the messages sent to it.  There will
be some messages that get sent to the other server.  There isn't any way
around this.  That means that you will be receiving mail for possibly
ANY person working at the other company.  You get a message for a person
at the other company, and your Exchange server doesn't know what the
hell to do with it.  You don't have any recipients with that name set
up.  Ends up being very messy.

I was thinking earlier about setting up custom recipients for them, but
that too would end up being messy, and I don't think it would work.
They could, however, set up some mailboxes and custom recipients for
you, have the mailbox deliver mail to the custom recipient and have
those custom recipients forward the mail to your server.  That, or
setting up some mailboxes for you and you using OWA, would be by far the
easiest, if not the only, solutions to what you are asking.  Anything
else is sounding more like a consulting gig to find a solution to your
problem.

If they are so insistent on you using their e-mail, why don't they
provide the solution?  Otherwise, tell them to go with the
above-mentioned OWA, or forward your mail via CR's, and let you reply
using your own addy's.

Ben Winzenz, MCSE 
Network/Systems Administrator 
Peregrine Systems 

-Original Message-
From: Matthew Carpenter [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 13, 2002 1:25 PM
To: MS-Exchange Admin Issues
Subject: RE: Future plans 2

What do you mean legally? If we have the permission of the owner of the
domain, there is no issue. 
-Original Message- 
From: Benjamin Winzenz [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 13, 2002 10:48 AM 
To: MS-Exchange Admin Issues 
Subject: RE: Future plans 2 

Other than this type of plan, there will be nothing that will not take a
large amount of time and effort to do.  You may not even legally be able
to do more than this.  Check with your legal department.
Ben Winzenz, MCSE 
Network/Systems Administrator 
Peregrine Systems 

-Original Message- 
From: Neil Hobson [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 13, 2002 11:30 AM 
To: MS-Exchange Admin Issues 
Subject: RE: Future plans 2 
Get them to create you a few mailboxes on their system, and access them
via OWA. 

Neil Hobson 
Silversands 
http://www.silversands.co.uk 
Microsoft Gold Certified Partner 
For Enterprise Systems 
For Collaborative Solutions 
-Original Message- 
From: Matthew Carpenter [mailto:[EMAIL PROTECTED]] 
Posted At: 13 February 2002 15:21 
Posted To: Sunbelt Exchange List 
Conversation: Future plans 2 
Subject: Future plans 2 

I am going to try this one more time. I think some of you can help me on
this. TIA -Original Message- 
From: Matthew Carpenter 
Sent: Tuesday, February 12, 2002 2:52 PM 
To: 'MS-Exchange Admin Issues' 
Subject: Future plans 

We have future plans to work with another company on a few projects, and
they want some of us to use THEIR email

RE: Future plans 2

2002-02-14 Thread William Lefkovics

I've never been inside one of these 'WalMart' places you refer.  I don't
think they exist.  Are you sure you have the name right?

-Original Message-
From: Neil Hobson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 14, 2002 12:44 AM
To: MS-Exchange Admin Issues
Subject: RE: Future plans 2


The reason I mentioned OWA in the first place is because I've done this
for a customer of mine in the UK.  They've got several people from a
small corner-shop outfit in the USA (called WalMart I think...!)
accessing mailboxes on their system via OWA.  Using SSL of course... :-)


Neil Hobson

Silversands
http://www.silversands.co.uk
Microsoft Gold Certified Partner
For Enterprise Systems
For Collaborative Solutions
 
-Original Message-
From: Matthew Carpenter [mailto:[EMAIL PROTECTED]] 
Posted At: 13 February 2002 21:09
Posted To: Sunbelt Exchange List
Conversation: Future plans 2
Subject: RE: Future plans 2


That is the best answer I have received, and you are right. I have no
idea how to implement this without dropped mail to nonhomed recipients
here OR there. I will discuss with them the different options that truly
seem available:
They home the mailboxes and we use OWA to use their domain 
there is a LEGAL partnership in which we act as connected sites, only
passing THEIR address book
I have not found another way around this, nor have I heard a good
alternative otherwise
-Original Message-
From: Benjamin Winzenz [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 13, 2002 1:08 PM
To: MS-Exchange Admin Issues
Subject: RE: Future plans 2


I'm just saying that you may want to consult with your legal department.
Having the permission of the owner of the domain doesn't mean squat in
the legal world.  You are talking about basically interchanging internal
company information.  That, plus you don't have a plan in place how you
want to accomplish this.  The owner of the domain may not realize the
scope of a project like this, which may not even be possible.  In your
given scenario below, if you were to add an MX record for their domain
and accept it as inbound, you would HAVE to have a way to route the
messages destined for their employees.  Otherwise, mail is going to
bounce.  Why?  Because the way that MX records work is that the server
with the lowest cost gets most of the messages sent to it.  There will
be some messages that get sent to the other server.  There isn't any way
around this.  That means that you will be receiving mail for possibly
ANY person working at the other company.  You get a message for a person
at the other company, and your Exchange server doesn't know what the
hell to do with it.  You don't have any recipients with that name set
up.  Ends up being very messy.

I was thinking earlier about setting up custom recipients for them, but
that too would end up being messy, and I don't think it would work.
They could, however, set up some mailboxes and custom recipients for
you, have the mailbox deliver mail to the custom recipient and have
those custom recipients forward the mail to your server.  That, or
setting up some mailboxes for you and you using OWA, would be by far the
easiest, if not the only, solutions to what you are asking.  Anything
else is sounding more like a consulting gig to find a solution to your
problem.

If they are so insistent on you using their e-mail, why don't they
provide the solution?  Otherwise, tell them to go with the
above-mentioned OWA, or forward your mail via CR's, and let you reply
using your own addy's.

Ben Winzenz, MCSE 
Network/Systems Administrator 
Peregrine Systems 

-Original Message-
From: Matthew Carpenter [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 13, 2002 1:25 PM
To: MS-Exchange Admin Issues
Subject: RE: Future plans 2

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm




RE: Future plans 2

2002-02-14 Thread Steve Ens

Lucky you...I wish I hadn't ever heard of Walmart either...

-Original Message-
From: William Lefkovics [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, February 14, 2002 10:34 AM
To: MS-Exchange Admin Issues
Subject: RE: Future plans 2


I've never been inside one of these 'WalMart' places you refer.  I don't
think they exist.  Are you sure you have the name right?

-Original Message-
From: Neil Hobson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 14, 2002 12:44 AM
To: MS-Exchange Admin Issues
Subject: RE: Future plans 2


The reason I mentioned OWA in the first place is because I've done this for
a customer of mine in the UK.  They've got several people from a small
corner-shop outfit in the USA (called WalMart I think...!) accessing
mailboxes on their system via OWA.  Using SSL of course... :-)


Neil Hobson

Silversands
http://www.silversands.co.uk
Microsoft Gold Certified Partner
For Enterprise Systems
For Collaborative Solutions
 
-Original Message-
From: Matthew Carpenter [mailto:[EMAIL PROTECTED]] 
Posted At: 13 February 2002 21:09
Posted To: Sunbelt Exchange List
Conversation: Future plans 2
Subject: RE: Future plans 2


That is the best answer I have received, and you are right. I have no idea
how to implement this without dropped mail to nonhomed recipients here OR
there. I will discuss with them the different options that truly seem
available: They home the mailboxes and we use OWA to use their domain 
there is a LEGAL partnership in which we act as connected sites, only
passing THEIR address book I have not found another way around this, nor
have I heard a good alternative otherwise -Original Message-
From: Benjamin Winzenz [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 13, 2002 1:08 PM
To: MS-Exchange Admin Issues
Subject: RE: Future plans 2


I'm just saying that you may want to consult with your legal department.
Having the permission of the owner of the domain doesn't mean squat in the
legal world.  You are talking about basically interchanging internal company
information.  That, plus you don't have a plan in place how you want to
accomplish this.  The owner of the domain may not realize the scope of a
project like this, which may not even be possible.  In your given scenario
below, if you were to add an MX record for their domain and accept it as
inbound, you would HAVE to have a way to route the messages destined for
their employees.  Otherwise, mail is going to bounce.  Why?  Because the way
that MX records work is that the server with the lowest cost gets most of
the messages sent to it.  There will be some messages that get sent to the
other server.  There isn't any way around this.  That means that you will be
receiving mail for possibly ANY person working at the other company.  You
get a message for a person at the other company, and your Exchange server
doesn't know what the hell to do with it.  You don't have any recipients
with that name set up.  Ends up being very messy.

I was thinking earlier about setting up custom recipients for them, but that
too would end up being messy, and I don't think it would work. They could,
however, set up some mailboxes and custom recipients for you, have the
mailbox deliver mail to the custom recipient and have those custom
recipients forward the mail to your server.  That, or setting up some
mailboxes for you and you using OWA, would be by far the easiest, if not the
only, solutions to what you are asking.  Anything else is sounding more like
a consulting gig to find a solution to your problem.

If they are so insistent on you using their e-mail, why don't they provide
the solution?  Otherwise, tell them to go with the above-mentioned OWA, or
forward your mail via CR's, and let you reply using your own addy's.

Ben Winzenz, MCSE 
Network/Systems Administrator 
Peregrine Systems 

-Original Message-
From: Matthew Carpenter [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 13, 2002 1:25 PM
To: MS-Exchange Admin Issues
Subject: RE: Future plans 2

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm




RE: Future plans 2

2002-02-14 Thread Andrew Philips

you must not be married.

-Original Message-
From: William Lefkovics [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 14, 2002 10:34 AM
To: MS-Exchange Admin Issues
Subject: RE: Future plans 2


I've never been inside one of these 'WalMart' places you refer.  I don't
think they exist.  Are you sure you have the name right?

-Original Message-
From: Neil Hobson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 14, 2002 12:44 AM
To: MS-Exchange Admin Issues
Subject: RE: Future plans 2


The reason I mentioned OWA in the first place is because I've done this
for a customer of mine in the UK.  They've got several people from a
small corner-shop outfit in the USA (called WalMart I think...!)
accessing mailboxes on their system via OWA.  Using SSL of course... :-)


Neil Hobson

Silversands
http://www.silversands.co.uk
Microsoft Gold Certified Partner
For Enterprise Systems
For Collaborative Solutions
 
-Original Message-
From: Matthew Carpenter [mailto:[EMAIL PROTECTED]] 
Posted At: 13 February 2002 21:09
Posted To: Sunbelt Exchange List
Conversation: Future plans 2
Subject: RE: Future plans 2


That is the best answer I have received, and you are right. I have no
idea how to implement this without dropped mail to nonhomed recipients
here OR there. I will discuss with them the different options that truly
seem available:
They home the mailboxes and we use OWA to use their domain 
there is a LEGAL partnership in which we act as connected sites, only
passing THEIR address book
I have not found another way around this, nor have I heard a good
alternative otherwise
-Original Message-
From: Benjamin Winzenz [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 13, 2002 1:08 PM
To: MS-Exchange Admin Issues
Subject: RE: Future plans 2


I'm just saying that you may want to consult with your legal department.
Having the permission of the owner of the domain doesn't mean squat in
the legal world.  You are talking about basically interchanging internal
company information.  That, plus you don't have a plan in place how you
want to accomplish this.  The owner of the domain may not realize the
scope of a project like this, which may not even be possible.  In your
given scenario below, if you were to add an MX record for their domain
and accept it as inbound, you would HAVE to have a way to route the
messages destined for their employees.  Otherwise, mail is going to
bounce.  Why?  Because the way that MX records work is that the server
with the lowest cost gets most of the messages sent to it.  There will
be some messages that get sent to the other server.  There isn't any way
around this.  That means that you will be receiving mail for possibly
ANY person working at the other company.  You get a message for a person
at the other company, and your Exchange server doesn't know what the
hell to do with it.  You don't have any recipients with that name set
up.  Ends up being very messy.

I was thinking earlier about setting up custom recipients for them, but
that too would end up being messy, and I don't think it would work.
They could, however, set up some mailboxes and custom recipients for
you, have the mailbox deliver mail to the custom recipient and have
those custom recipients forward the mail to your server.  That, or
setting up some mailboxes for you and you using OWA, would be by far the
easiest, if not the only, solutions to what you are asking.  Anything
else is sounding more like a consulting gig to find a solution to your
problem.

If they are so insistent on you using their e-mail, why don't they
provide the solution?  Otherwise, tell them to go with the
above-mentioned OWA, or forward your mail via CR's, and let you reply
using your own addy's.

Ben Winzenz, MCSE 
Network/Systems Administrator 
Peregrine Systems 

-Original Message-
From: Matthew Carpenter [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 13, 2002 1:25 PM
To: MS-Exchange Admin Issues
Subject: RE: Future plans 2

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm


List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm




RE: Future plans 2

2002-02-14 Thread Matthew Carpenter
Title: RE: Future plans 2





He may be. My wife won't set foot in WalMart. Actually, neither will I...


-Original Message-
From: Andrew Philips [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, February 14, 2002 11:13 AM
To: MS-Exchange Admin Issues
Subject: RE: Future plans 2



you must not be married.


-Original Message-
From: William Lefkovics [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 14, 2002 10:34 AM
To: MS-Exchange Admin Issues
Subject: RE: Future plans 2



I've never been inside one of these 'WalMart' places you refer. I don't think they exist. Are you sure you have the name right?

-Original Message-
From: Neil Hobson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 14, 2002 12:44 AM
To: MS-Exchange Admin Issues
Subject: RE: Future plans 2



The reason I mentioned OWA in the first place is because I've done this for a customer of mine in the UK. They've got several people from a small corner-shop outfit in the USA (called WalMart I think...!) accessing mailboxes on their system via OWA. Using SSL of course... :-)


Neil Hobson


Silversands
http://www.silversands.co.uk
Microsoft Gold Certified Partner
For Enterprise Systems
For Collaborative Solutions

-Original Message-
From: Matthew Carpenter [mailto:[EMAIL PROTECTED]] 
Posted At: 13 February 2002 21:09
Posted To: Sunbelt Exchange List
Conversation: Future plans 2
Subject: RE: Future plans 2



That is the best answer I have received, and you are right. I have no idea how to implement this without dropped mail to nonhomed recipients here OR there. I will discuss with them the different options that truly seem available: They home the mailboxes and we use OWA to use their domain 

there is a LEGAL partnership in which we act as connected sites, only passing THEIR address book I have not found another way around this, nor have I heard a good alternative otherwise -Original Message-

From: Benjamin Winzenz [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 13, 2002 1:08 PM
To: MS-Exchange Admin Issues
Subject: RE: Future plans 2



I'm just saying that you may want to consult with your legal department. Having the permission of the owner of the domain doesn't mean squat in the legal world. You are talking about basically interchanging internal company information. That, plus you don't have a plan in place how you want to accomplish this. The owner of the domain may not realize the scope of a project like this, which may not even be possible. In your given scenario below, if you were to add an MX record for their domain and accept it as inbound, you would HAVE to have a way to route the messages destined for their employees. Otherwise, mail is going to bounce. Why? Because the way that MX records work is that the server with the lowest cost gets most of the messages sent to it. There will be some messages that get sent to the other server. There isn't any way around this. That means that you will be receiving mail for possibly ANY person working at the other company. You get a message for a person at the other company, and your Exchange server doesn't know what the hell to do with it. You don't have any recipients with that name set up. Ends up being very messy.

I was thinking earlier about setting up custom recipients for them, but that too would end up being messy, and I don't think it would work. They could, however, set up some mailboxes and custom recipients for you, have the mailbox deliver mail to the custom recipient and have those custom recipients forward the mail to your server. That, or setting up some mailboxes for you and you using OWA, would be by far the easiest, if not the only, solutions to what you are asking. Anything else is sounding more like a consulting gig to find a solution to your problem.

If they are so insistent on you using their e-mail, why don't they provide the solution? Otherwise, tell them to go with the above-mentioned OWA, or forward your mail via CR's, and let you reply using your own addy's.

Ben Winzenz, MCSE 
Network/Systems Administrator 
Peregrine Systems 


-Original Message-
From: Matthew Carpenter [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 13, 2002 1:25 PM
To: MS-Exchange Admin Issues
Subject: RE: Future plans 2


List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm



List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm



List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm





RE: Future plans 2

2002-02-14 Thread Martin Blackstone
Title: Message



I'm the same with 
KMart. I have never been in a WalMart and have on intention of doing 
so.
I'm a Target kind 
of guy.

Just to be on 
topic, Do you think Kmart or Wal-Mart use Exchange? 

  
  -Original Message-From: Matthew Carpenter 
  [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 14, 2002 
  9:16 AMTo: MS-Exchange Admin IssuesSubject: RE: Future 
  plans 2
  He may be. My wife won't set foot in WalMart. Actually, 
  neither will I... 
  -Original Message- From: 
  Andrew Philips [mailto:[EMAIL PROTECTED]] 
  Sent: Thursday, February 14, 2002 11:13 AM 
  To: MS-Exchange Admin Issues Subject: 
  RE: Future plans 2 
  you must not be married. 
  -Original Message- From: 
  William Lefkovics [mailto:[EMAIL PROTECTED]] 
  Sent: Thursday, February 14, 2002 10:34 AM To: MS-Exchange Admin Issues Subject: RE: 
  Future plans 2 
  I've never been inside one of these 'WalMart' places you 
  refer. I don't think they exist. Are you sure you have the name 
  right?
  -Original Message- From: Neil 
  Hobson [mailto:[EMAIL PROTECTED]] 
  Sent: Thursday, February 14, 2002 12:44 AM To: MS-Exchange Admin Issues Subject: RE: 
  Future plans 2 
  The reason I mentioned OWA in the first place is because I've 
  done this for a customer of mine in the UK. They've got several people 
  from a small corner-shop outfit in the USA (called WalMart I think...!) 
  accessing mailboxes on their system via OWA. Using SSL of course... 
  :-)
  Neil Hobson 
  Silversands http://www.silversands.co.uk Microsoft Gold Certified Partner For Enterprise 
  Systems For Collaborative Solutions  -Original Message- 
  From: Matthew Carpenter [mailto:[EMAIL PROTECTED]] 
  Posted At: 13 February 2002 21:09 Posted To: Sunbelt Exchange List Conversation: 
  Future plans 2 Subject: RE: Future plans 2 
  
  That is the best answer I have received, and you are right. I 
  have no idea how to implement this without dropped mail to nonhomed recipients 
  here OR there. I will discuss with them the different options that truly seem 
  available: They home the mailboxes and we use OWA to use their domain 
  
  there is a LEGAL partnership in which we act as connected 
  sites, only passing THEIR address book I have not found another way around 
  this, nor have I heard a good alternative otherwise -Original 
  Message-
  From: Benjamin Winzenz [mailto:[EMAIL PROTECTED]] 
  Sent: Wednesday, February 13, 2002 1:08 PM 
  To: MS-Exchange Admin Issues Subject: 
  RE: Future plans 2 
  I'm just saying that you may want to consult with your legal 
  department. Having the permission of the owner of the domain doesn't mean 
  squat in the legal world. You are talking about basically interchanging 
  internal company information. That, plus you don't have a plan in place 
  how you want to accomplish this. The owner of the domain may not realize 
  the scope of a project like this, which may not even be possible. In 
  your given scenario below, if you were to add an MX record for their domain 
  and accept it as inbound, you would HAVE to have a way to route the messages 
  destined for their employees. Otherwise, mail is going to bounce. 
  Why? Because the way that MX records work is that the server with the 
  lowest cost gets most of the messages sent to it. There will be some 
  messages that get sent to the other server. There isn't any way around 
  this. That means that you will be receiving mail for possibly ANY person 
  working at the other company. You get a message for a person at the 
  other company, and your Exchange server doesn't know what the hell to do with 
  it. You don't have any recipients with that name set up. Ends up 
  being very messy.
  I was thinking earlier about setting up custom recipients for 
  them, but that too would end up being messy, and I don't think it would work. 
  They could, however, set up some mailboxes and custom recipients for you, have 
  the mailbox deliver mail to the custom recipient and have those custom 
  recipients forward the mail to your server. That, or setting up some 
  mailboxes for you and you using OWA, would be by far the easiest, if not the 
  only, solutions to what you are asking. Anything else is sounding more 
  like a consulting gig to find a solution to your problem.
  If they are so insistent on you using their e-mail, why don't 
  they provide the solution? Otherwise, tell them to go with the 
  above-mentioned OWA, or forward your mail via CR's, and let you reply using 
  your own addy's.
  Ben Winzenz, MCSE Network/Systems 
  Administrator Peregrine Systems 
  -Original Message- From: 
  Matthew Carpenter [mailto:[EMAIL PROTECTED]] 
  Sent: Wednesday, February 13, 2002 1:25 PM 
  To: MS-Exchange Admin Issues Subject: 
  RE: Future plans 2 
  List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm 
  
  List Charter and FAQ at: http://www.sunbelt-software.com

RE: Future plans 2

2002-02-14 Thread Erik Sojka
Title: Message



KMart 
does; There is a KMart employee on the Swynk list.

  
  -Original Message-From: Martin 
  Blackstone [mailto:[EMAIL PROTECTED]] Sent: Thursday, 
  February 14, 2002 12:23 PMTo: MS-Exchange Admin 
  IssuesSubject: RE: Future plans 2
  I'm the same 
  with KMart. I have never been in a WalMart and have on intention of doing 
  so.
  I'm a Target 
  kind of guy.
  
  Just to be on 
  topic, Do you think Kmart or Wal-Mart use Exchange? 
  

-Original Message-From: Matthew Carpenter 
[mailto:[EMAIL PROTECTED]] Sent: Thursday, February 14, 2002 
9:16 AMTo: MS-Exchange Admin IssuesSubject: RE: Future 
plans 2
He may be. My wife won't set foot in WalMart. Actually, 
neither will I... 
-Original Message- From: 
Andrew Philips [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, February 14, 2002 11:13 AM 
To: MS-Exchange Admin Issues Subject: RE: Future plans 2 
you must not be married. 
-Original Message- From: 
William Lefkovics [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, February 14, 2002 10:34 AM To: MS-Exchange Admin Issues Subject: RE: 
Future plans 2 
I've never been inside one of these 'WalMart' places you 
refer. I don't think they exist. Are you sure you have the name 
right?
-Original Message- From: 
Neil Hobson [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, February 14, 2002 12:44 AM To: MS-Exchange Admin Issues Subject: RE: 
Future plans 2 
The reason I mentioned OWA in the first place is because 
I've done this for a customer of mine in the UK. They've got several 
people from a small corner-shop outfit in the USA (called WalMart I 
think...!) accessing mailboxes on their system via OWA. Using SSL of 
course... :-)
Neil Hobson 
Silversands http://www.silversands.co.uk Microsoft Gold Certified Partner For 
Enterprise Systems For Collaborative 
Solutions  -Original Message- From: Matthew 
Carpenter [mailto:[EMAIL PROTECTED]] 
Posted At: 13 February 2002 21:09 Posted To: Sunbelt Exchange List Conversation: Future plans 2 Subject: RE: 
Future plans 2 
That is the best answer I have received, and you are right. 
I have no idea how to implement this without dropped mail to nonhomed 
recipients here OR there. I will discuss with them the different options 
that truly seem available: They home the mailboxes and we use OWA to use 
their domain 
there is a LEGAL partnership in which we act as connected 
sites, only passing THEIR address book I have not found another way around 
this, nor have I heard a good alternative otherwise -Original 
Message-
From: Benjamin Winzenz [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 13, 2002 1:08 PM 
To: MS-Exchange Admin Issues Subject: RE: Future plans 2 
I'm just saying that you may want to consult with your legal 
department. Having the permission of the owner of the domain doesn't mean 
squat in the legal world. You are talking about basically 
interchanging internal company information. That, plus you don't have 
a plan in place how you want to accomplish this. The owner of the 
domain may not realize the scope of a project like this, which may not even 
be possible. In your given scenario below, if you were to add an MX 
record for their domain and accept it as inbound, you would HAVE to have a 
way to route the messages destined for their employees. Otherwise, 
mail is going to bounce. Why? Because the way that MX records 
work is that the server with the lowest cost gets most of the messages sent 
to it. There will be some messages that get sent to the other 
server. There isn't any way around this. That means that you 
will be receiving mail for possibly ANY person working at the other 
company. You get a message for a person at the other company, and your 
Exchange server doesn't know what the hell to do with it. You don't 
have any recipients with that name set up. Ends up being very 
messy.
I was thinking earlier about setting up custom recipients 
for them, but that too would end up being messy, and I don't think it would 
work. They could, however, set up some mailboxes and custom recipients for 
you, have the mailbox deliver mail to the custom recipient and have those 
custom recipients forward the mail to your server. That, or setting up 
some mailboxes for you and you using OWA, would be by far the easiest, if 
not the only, solutions to what you are asking. Anything else is 
sounding more like a consulting gig to find a solution to your 
problem.
If they are so insistent on you using their e-mail, why 
don't they provide the solution? Otherwise, tell them to go with the 
above-mentioned OWA, or forward your mail via CR's, and let you reply using 
your own addy's

RE: Future plans 2

2002-02-14 Thread William Lefkovics
Title: Message



You 
know the answer Mr B. They both use Exchange. WalMart, based in 
Arkansas, may well be the largest Exchange2000 deployment at around 300,000 
mailboxes.

William

  -Original Message-From: Martin Blackstone 
  [mailto:[EMAIL PROTECTED]]Sent: Thursday, February 14, 
  2002 9:23 AMTo: MS-Exchange Admin IssuesSubject: RE: 
  Future plans 2
  I'm the same 
  with KMart. I have never been in a WalMart and have on intention of doing 
  so.
  I'm a Target 
  kind of guy.
  
  Just to be on 
  topic, Do you think Kmart or Wal-Mart use Exchange? 
  

-Original Message-From: Matthew Carpenter 
[mailto:[EMAIL PROTECTED]] Sent: Thursday, February 14, 2002 
9:16 AMTo: MS-Exchange Admin IssuesSubject: RE: Future 
plans 2
He may be. My wife won't set foot in WalMart. Actually, 
neither will I... 
-Original Message- From: 
Andrew Philips [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, February 14, 2002 11:13 AM 
To: MS-Exchange Admin Issues Subject: RE: Future plans 2 
you must not be married. 
-Original Message- From: 
William Lefkovics [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, February 14, 2002 10:34 AM To: MS-Exchange Admin Issues Subject: RE: 
Future plans 2 
I've never been inside one of these 'WalMart' places you 
refer. I don't think they exist. Are you sure you have the name 
right?
-Original Message- From: 
Neil Hobson [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, February 14, 2002 12:44 AM To: MS-Exchange Admin Issues Subject: RE: 
Future plans 2 
The reason I mentioned OWA in the first place is because 
I've done this for a customer of mine in the UK. They've got several 
people from a small corner-shop outfit in the USA (called WalMart I 
think...!) accessing mailboxes on their system via OWA. Using SSL of 
course... :-)
Neil Hobson 
Silversands http://www.silversands.co.uk Microsoft Gold Certified Partner For 
Enterprise Systems For Collaborative 
Solutions  -Original Message- From: Matthew 
Carpenter [mailto:[EMAIL PROTECTED]] 
Posted At: 13 February 2002 21:09 Posted To: Sunbelt Exchange List Conversation: Future plans 2 Subject: RE: 
Future plans 2 
That is the best answer I have received, and you are right. 
I have no idea how to implement this without dropped mail to nonhomed 
recipients here OR there. I will discuss with them the different options 
that truly seem available: They home the mailboxes and we use OWA to use 
their domain 
there is a LEGAL partnership in which we act as connected 
sites, only passing THEIR address book I have not found another way around 
this, nor have I heard a good alternative otherwise -Original 
Message-
From: Benjamin Winzenz [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 13, 2002 1:08 PM 
To: MS-Exchange Admin Issues Subject: RE: Future plans 2 
I'm just saying that you may want to consult with your legal 
department. Having the permission of the owner of the domain doesn't mean 
squat in the legal world. You are talking about basically 
interchanging internal company information. That, plus you don't have 
a plan in place how you want to accomplish this. The owner of the 
domain may not realize the scope of a project like this, which may not even 
be possible. In your given scenario below, if you were to add an MX 
record for their domain and accept it as inbound, you would HAVE to have a 
way to route the messages destined for their employees. Otherwise, 
mail is going to bounce. Why? Because the way that MX records 
work is that the server with the lowest cost gets most of the messages sent 
to it. There will be some messages that get sent to the other 
server. There isn't any way around this. That means that you 
will be receiving mail for possibly ANY person working at the other 
company. You get a message for a person at the other company, and your 
Exchange server doesn't know what the hell to do with it. You don't 
have any recipients with that name set up. Ends up being very 
messy.
I was thinking earlier about setting up custom recipients 
for them, but that too would end up being messy, and I don't think it would 
work. They could, however, set up some mailboxes and custom recipients for 
you, have the mailbox deliver mail to the custom recipient and have those 
custom recipients forward the mail to your server. That, or setting up 
some mailboxes for you and you using OWA, would be by far the easiest, if 
not the only, solutions to what you are asking. Anything else is 
sounding more like a consulting gig to find a solution to your 
problem.
If they are so insistent on you using their e-mail, why 
don't they provide the solution? Otherwise, tell them to go

RE: Future plans 2

2002-02-14 Thread Matthew Carpenter
Title: Message



What 
the hell do WalMart employees need mailboxes for? To let each other know that 
the Dale Earnhardt bandanas are on sale this week?

  
  -Original Message-From: William 
  Lefkovics [mailto:[EMAIL PROTECTED]] Sent: Thursday, 
  February 14, 2002 11:26 AMTo: MS-Exchange Admin 
  IssuesSubject: RE: Future plans 2
  You 
  know the answer Mr B. They both use Exchange. WalMart, based in 
  Arkansas, may well be the largest Exchange2000 deployment at around 300,000 
  mailboxes.
  
  William
  
-Original Message-From: Martin Blackstone 
[mailto:[EMAIL PROTECTED]]Sent: Thursday, February 
14, 2002 9:23 AMTo: MS-Exchange Admin IssuesSubject: 
RE: Future plans 2
I'm the same 
with KMart. I have never been in a WalMart and have on intention of doing 
so.
I'm a Target 
kind of guy.

Just to be on 
topic, Do you think Kmart or Wal-Mart use Exchange? 

  
  -Original Message-From: Matthew Carpenter 
  [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 14, 2002 
  9:16 AMTo: MS-Exchange Admin IssuesSubject: RE: 
  Future plans 2
  He may be. My wife won't set foot in WalMart. Actually, 
  neither will I... 
  -Original Message- From: 
  Andrew Philips [mailto:[EMAIL PROTECTED]] 
  Sent: Thursday, February 14, 2002 11:13 AM 
  To: MS-Exchange Admin Issues Subject: RE: Future plans 2 
  you must not be married. 
  -Original Message- From: 
  William Lefkovics [mailto:[EMAIL PROTECTED]] 
  Sent: Thursday, February 14, 2002 10:34 AM 
  To: MS-Exchange Admin Issues Subject: RE: Future plans 2 
  I've never been inside one of these 'WalMart' places you 
  refer. I don't think they exist. Are you sure you have the 
  name right?
  -Original Message- From: 
  Neil Hobson [mailto:[EMAIL PROTECTED]] 
  Sent: Thursday, February 14, 2002 12:44 AM 
  To: MS-Exchange Admin Issues Subject: RE: Future plans 2 
  The reason I mentioned OWA in the first place is because 
  I've done this for a customer of mine in the UK. They've got several 
  people from a small corner-shop outfit in the USA (called WalMart I 
  think...!) accessing mailboxes on their system via OWA. Using SSL of 
  course... :-)
  Neil Hobson 
  Silversands http://www.silversands.co.uk 
  Microsoft Gold Certified Partner For Enterprise Systems For Collaborative 
  Solutions  -Original Message- From: Matthew 
  Carpenter [mailto:[EMAIL PROTECTED]] 
  Posted At: 13 February 2002 21:09 Posted To: Sunbelt Exchange List Conversation: Future plans 2 Subject: RE: 
  Future plans 2 
  That is the best answer I have received, and you are 
  right. I have no idea how to implement this without dropped mail to 
  nonhomed recipients here OR there. I will discuss with them the different 
  options that truly seem available: They home the mailboxes and we use OWA 
  to use their domain 
  there is a LEGAL partnership in which we act as connected 
  sites, only passing THEIR address book I have not found another way around 
  this, nor have I heard a good alternative otherwise -Original 
  Message-
  From: Benjamin Winzenz [mailto:[EMAIL PROTECTED]] 
  Sent: Wednesday, February 13, 2002 1:08 PM 
  To: MS-Exchange Admin Issues Subject: RE: Future plans 2 
  I'm just saying that you may want to consult with your 
  legal department. Having the permission of the owner of the domain doesn't 
  mean squat in the legal world. You are talking about basically 
  interchanging internal company information. That, plus you don't 
  have a plan in place how you want to accomplish this. The owner of 
  the domain may not realize the scope of a project like this, which may not 
  even be possible. In your given scenario below, if you were to add 
  an MX record for their domain and accept it as inbound, you would HAVE to 
  have a way to route the messages destined for their employees. 
  Otherwise, mail is going to bounce. Why? Because the way that 
  MX records work is that the server with the lowest cost gets most of the 
  messages sent to it. There will be some messages that get sent to 
  the other server. There isn't any way around this. That means 
  that you will be receiving mail for possibly ANY person working at the 
  other company. You get a message for a person at the other company, 
  and your Exchange server doesn't know what the hell to do with it. 
  You don't have any recipients with that name set up. Ends up being 
  very messy.
  I was thinking earlier about setting up custom recipients 
  for them, but that too would end up being messy, and I don't think it 
  would work. They could, however, set up some mailboxes and custom 
  recipients for you, have

RE: Future plans 2

2002-02-14 Thread Jeremiah Watson
Title: Message



You 
need the Earnhardt bandanna, and some country and western 
music.

  -Original Message-From: Matthew Carpenter 
  [mailto:[EMAIL PROTECTED]]Sent: Thursday, February 14, 2002 
  12:52 PMTo: MS-Exchange Admin IssuesSubject: RE: Future 
  plans 2
  What 
  the hell do WalMart employees need mailboxes for? To let each other know that 
  the Dale Earnhardt bandanas are on sale this week?
  

-Original Message-From: William 
Lefkovics [mailto:[EMAIL PROTECTED]] Sent: Thursday, 
February 14, 2002 11:26 AMTo: MS-Exchange Admin 
IssuesSubject: RE: Future plans 2
You know the answer Mr B. They both use 
Exchange. WalMart, based in Arkansas, may well be the largest 
Exchange2000 deployment at around 300,000 mailboxes.

William

  -Original Message-From: Martin Blackstone 
  [mailto:[EMAIL PROTECTED]]Sent: Thursday, February 
  14, 2002 9:23 AMTo: MS-Exchange Admin IssuesSubject: 
  RE: Future plans 2
  I'm the 
  same with KMart. I have never been in a WalMart and have on intention of 
  doing so.
  I'm a 
  Target kind of guy.
  
  Just to be 
  on topic, Do you think Kmart or Wal-Mart use Exchange? 

  

-Original Message-From: Matthew Carpenter 
[mailto:[EMAIL PROTECTED]] Sent: Thursday, February 14, 
2002 9:16 AMTo: MS-Exchange Admin IssuesSubject: 
RE: Future plans 2
He may be. My wife won't set foot in WalMart. Actually, 
neither will I... 
-Original Message- From: 
Andrew Philips [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, February 14, 2002 11:13 
AM To: MS-Exchange Admin Issues Subject: RE: Future plans 2 
you must not be married. 
-Original Message- From: 
William Lefkovics [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, February 14, 2002 10:34 AM 
To: MS-Exchange Admin Issues Subject: RE: Future plans 2 
I've never been inside one of these 'WalMart' places you 
refer. I don't think they exist. Are you sure you have the 
name right?
-Original Message- From: 
Neil Hobson [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, February 14, 2002 12:44 AM 
To: MS-Exchange Admin Issues Subject: RE: Future plans 2 
The reason I mentioned OWA in the first place is because 
I've done this for a customer of mine in the UK. They've got 
several people from a small corner-shop outfit in the USA (called 
WalMart I think...!) accessing mailboxes on their system via OWA. 
Using SSL of course... :-)
Neil Hobson 
Silversands http://www.silversands.co.uk Microsoft Gold Certified Partner For 
Enterprise Systems For Collaborative 
Solutions  -Original Message- From: Matthew 
Carpenter [mailto:[EMAIL PROTECTED]] 
Posted At: 13 February 2002 21:09 
Posted To: Sunbelt Exchange List Conversation: Future plans 2 Subject: RE: 
Future plans 2 
That is the best answer I have received, and you are 
right. I have no idea how to implement this without dropped mail to 
nonhomed recipients here OR there. I will discuss with them the 
different options that truly seem available: They home the mailboxes and 
we use OWA to use their domain 
there is a LEGAL partnership in which we act as 
connected sites, only passing THEIR address book I have not found 
another way around this, nor have I heard a good alternative otherwise 
-Original Message-
From: Benjamin Winzenz [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 13, 2002 1:08 
PM To: MS-Exchange Admin Issues Subject: RE: Future plans 2 
I'm just saying that you may want to consult with your 
legal department. Having the permission of the owner of the domain 
doesn't mean squat in the legal world. You are talking about 
basically interchanging internal company information. That, plus 
you don't have a plan in place how you want to accomplish this. 
The owner of the domain may not realize the scope of a project like 
this, which may not even be possible. In your given scenario 
below, if you were to add an MX record for their domain and accept it as 
inbound, you would HAVE to have a way to route the messages destined for 
their employees. Otherwise, mail is going to bounce. 
Why? Because the way that MX records work is that the server with 
the lowest cost gets most of the messages sent to it. There will 
be some messages that get sent to the other server. There isn't 
any way around this. That means that you will be receiving mail 
for possibly ANY person working at the other company. You get

Re: Future plans 2

2002-02-14 Thread David N. Precht
Title: Message



how many servers ?

  - Original Message - 
  From: 
  William Lefkovics 
  To: MS-Exchange Admin 
  Issues 
  Sent: Thursday, February 14, 2002 12:25 
  
  Subject: RE: Future plans 2
  
  You 
  know the answer Mr B. They both use Exchange. WalMart, based in 
  Arkansas, may well be the largest Exchange2000 deployment at around 300,000 
  mailboxes.
  
  William
  
-Original Message-From: Martin Blackstone 
[mailto:[EMAIL PROTECTED]]Sent: Thursday, February 
14, 2002 9:23 AMTo: MS-Exchange Admin IssuesSubject: 
RE: Future plans 2
I'm the same 
with KMart. I have never been in a WalMart and have on intention of doing 
so.
I'm a Target 
kind of guy.

Just to be on 
topic, Do you think Kmart or Wal-Mart use Exchange? 

  
  -Original Message-From: Matthew Carpenter 
  [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 14, 2002 
  9:16 AMTo: MS-Exchange Admin IssuesSubject: RE: 
  Future plans 2
  He may be. My wife won't set foot in WalMart. Actually, 
  neither will I... 
  -Original Message- From: 
  Andrew Philips [mailto:[EMAIL PROTECTED]] 
  Sent: Thursday, February 14, 2002 11:13 AM 
  To: MS-Exchange Admin Issues Subject: RE: Future plans 2 
  you must not be married. 
  -Original Message- From: 
  William Lefkovics [mailto:[EMAIL PROTECTED]] 
  Sent: Thursday, February 14, 2002 10:34 AM 
  To: MS-Exchange Admin Issues Subject: RE: Future plans 2 
  I've never been inside one of these 'WalMart' places you 
  refer. I don't think they exist. Are you sure you have the 
  name right?
  -Original Message- From: 
  Neil Hobson [mailto:[EMAIL PROTECTED]] 
  Sent: Thursday, February 14, 2002 12:44 AM 
  To: MS-Exchange Admin Issues Subject: RE: Future plans 2 
  The reason I mentioned OWA in the first place is because 
  I've done this for a customer of mine in the UK. They've got several 
  people from a small corner-shop outfit in the USA (called WalMart I 
  think...!) accessing mailboxes on their system via OWA. Using SSL of 
  course... :-)
  Neil Hobson 
  Silversands http://www.silversands.co.uk Microsoft Gold Certified Partner For 
  Enterprise Systems For Collaborative 
  Solutions  -Original Message- From: Matthew 
  Carpenter [mailto:[EMAIL PROTECTED]] 
  Posted At: 13 February 2002 21:09 Posted To: Sunbelt Exchange List Conversation: Future plans 2 Subject: RE: 
  Future plans 2 
  That is the best answer I have received, and you are 
  right. I have no idea how to implement this without dropped mail to 
  nonhomed recipients here OR there. I will discuss with them the different 
  options that truly seem available: They home the mailboxes and we use OWA 
  to use their domain 
  there is a LEGAL partnership in which we act as connected 
  sites, only passing THEIR address book I have not found another way around 
  this, nor have I heard a good alternative otherwise -Original 
  Message-
  From: Benjamin Winzenz [mailto:[EMAIL PROTECTED]] 
  Sent: Wednesday, February 13, 2002 1:08 PM 
  To: MS-Exchange Admin Issues Subject: RE: Future plans 2 
  I'm just saying that you may want to consult with your 
  legal department. Having the permission of the owner of the domain doesn't 
  mean squat in the legal world. You are talking about basically 
  interchanging internal company information. That, plus you don't 
  have a plan in place how you want to accomplish this. The owner of 
  the domain may not realize the scope of a project like this, which may not 
  even be possible. In your given scenario below, if you were to add 
  an MX record for their domain and accept it as inbound, you would HAVE to 
  have a way to route the messages destined for their employees. 
  Otherwise, mail is going to bounce. Why? Because the way that 
  MX records work is that the server with the lowest cost gets most of the 
  messages sent to it. There will be some messages that get sent to 
  the other server. There isn't any way around this. That means 
  that you will be receiving mail for possibly ANY person working at the 
  other company. You get a message for a person at the other company, 
  and your Exchange server doesn't know what the hell to do with it. 
  You don't have any recipients with that name set up. Ends up being 
  very messy.
  I was thinking earlier about setting up custom recipients 
  for them, but that too would end up being messy, and I don't think it 
  would work. They could, however, set up some mailboxes and custom 
  recipients for you, have the mailbox deliver mail to the custom recipient 
  and have those custom recipients forward the mail to your server

RE: Future plans 2

2002-02-14 Thread Martin Blackstone
Title: Message



ROFL

  
  -Original Message-From: Matthew Carpenter 
  [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 14, 2002 
  9:52 AMTo: MS-Exchange Admin IssuesSubject: RE: Future 
  plans 2
  What 
  the hell do WalMart employees need mailboxes for? To let each other know that 
  the Dale Earnhardt bandanas are on sale this week?
  

-Original Message-From: William 
Lefkovics [mailto:[EMAIL PROTECTED]] Sent: Thursday, 
February 14, 2002 11:26 AMTo: MS-Exchange Admin 
IssuesSubject: RE: Future plans 2
You know the answer Mr B. They both use 
Exchange. WalMart, based in Arkansas, may well be the largest 
Exchange2000 deployment at around 300,000 mailboxes.

William

  -Original Message-From: Martin Blackstone 
  [mailto:[EMAIL PROTECTED]]Sent: Thursday, February 
  14, 2002 9:23 AMTo: MS-Exchange Admin IssuesSubject: 
  RE: Future plans 2
  I'm the 
  same with KMart. I have never been in a WalMart and have on intention of 
  doing so.
  I'm a 
  Target kind of guy.
  
  Just to be 
  on topic, Do you think Kmart or Wal-Mart use Exchange? 

  

-Original Message-From: Matthew Carpenter 
[mailto:[EMAIL PROTECTED]] Sent: Thursday, February 14, 
2002 9:16 AMTo: MS-Exchange Admin IssuesSubject: 
RE: Future plans 2
He may be. My wife won't set foot in WalMart. Actually, 
neither will I... 
-Original Message- From: 
Andrew Philips [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, February 14, 2002 11:13 
AM To: MS-Exchange Admin Issues Subject: RE: Future plans 2 
you must not be married. 
-Original Message- From: 
William Lefkovics [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, February 14, 2002 10:34 AM 
To: MS-Exchange Admin Issues Subject: RE: Future plans 2 
I've never been inside one of these 'WalMart' places you 
refer. I don't think they exist. Are you sure you have the 
name right?
-Original Message- From: 
Neil Hobson [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, February 14, 2002 12:44 AM 
To: MS-Exchange Admin Issues Subject: RE: Future plans 2 
The reason I mentioned OWA in the first place is because 
I've done this for a customer of mine in the UK. They've got 
several people from a small corner-shop outfit in the USA (called 
WalMart I think...!) accessing mailboxes on their system via OWA. 
Using SSL of course... :-)
Neil Hobson 
Silversands http://www.silversands.co.uk Microsoft Gold Certified Partner For 
Enterprise Systems For Collaborative 
Solutions  -Original Message- From: Matthew 
Carpenter [mailto:[EMAIL PROTECTED]] 
Posted At: 13 February 2002 21:09 
Posted To: Sunbelt Exchange List Conversation: Future plans 2 Subject: RE: 
Future plans 2 
That is the best answer I have received, and you are 
right. I have no idea how to implement this without dropped mail to 
nonhomed recipients here OR there. I will discuss with them the 
different options that truly seem available: They home the mailboxes and 
we use OWA to use their domain 
there is a LEGAL partnership in which we act as 
connected sites, only passing THEIR address book I have not found 
another way around this, nor have I heard a good alternative otherwise 
-Original Message-
From: Benjamin Winzenz [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 13, 2002 1:08 
PM To: MS-Exchange Admin Issues Subject: RE: Future plans 2 
I'm just saying that you may want to consult with your 
legal department. Having the permission of the owner of the domain 
doesn't mean squat in the legal world. You are talking about 
basically interchanging internal company information. That, plus 
you don't have a plan in place how you want to accomplish this. 
The owner of the domain may not realize the scope of a project like 
this, which may not even be possible. In your given scenario 
below, if you were to add an MX record for their domain and accept it as 
inbound, you would HAVE to have a way to route the messages destined for 
their employees. Otherwise, mail is going to bounce. 
Why? Because the way that MX records work is that the server with 
the lowest cost gets most of the messages sent to it. There will 
be some messages that get sent to the other server. There isn't 
any way around this. That means that you will be receiving mail 
for possibly ANY person working at the other company. You get a 
message for a person at the other company, and your Exchange

RE: Future plans 2

2002-02-14 Thread William Lefkovics
Title: Message



I wish 
I knew. I lacked the enterprise experience to join their deployment 
team. That number includes thousands of resource mailboxes and may not be 
as many as I quoted.

William 

  -Original Message-From: David N. Precht 
  [mailto:[EMAIL PROTECTED]]Sent: Thursday, February 14, 2002 
  10:00 AMTo: MS-Exchange Admin IssuesSubject: Re: Future 
  plans 2
  how many servers ?
  
- Original Message - 
From: 
William Lefkovics 
To: MS-Exchange Admin Issues 

Sent: Thursday, February 14, 2002 12:25 

Subject: RE: Future plans 2

You know the answer Mr B. They both use 
Exchange. WalMart, based in Arkansas, may well be the largest 
Exchange2000 deployment at around 300,000 mailboxes.

William

  -Original Message-From: Martin Blackstone 
  [mailto:[EMAIL PROTECTED]]Sent: Thursday, February 
  14, 2002 9:23 AMTo: MS-Exchange Admin IssuesSubject: 
  RE: Future plans 2
  I'm the 
  same with KMart. I have never been in a WalMart and have on intention of 
  doing so.
  I'm a 
  Target kind of guy.
  
  Just to be 
  on topic, Do you think Kmart or Wal-Mart use Exchange? 

  

-Original Message-From: Matthew Carpenter 
[mailto:[EMAIL PROTECTED]] Sent: Thursday, February 14, 
2002 9:16 AMTo: MS-Exchange Admin IssuesSubject: 
RE: Future plans 2
He may be. My wife won't set foot in WalMart. Actually, 
neither will I... 
-Original Message- From: 
Andrew Philips [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, February 14, 2002 11:13 
AM To: MS-Exchange Admin Issues Subject: RE: Future plans 2 
you must not be married. 
-Original Message- From: 
William Lefkovics [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, February 14, 2002 10:34 AM 
To: MS-Exchange Admin Issues Subject: RE: Future plans 2 
I've never been inside one of these 'WalMart' places you 
refer. I don't think they exist. Are you sure you have the 
name right?
-Original Message- From: 
Neil Hobson [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, February 14, 2002 12:44 AM 
To: MS-Exchange Admin Issues Subject: RE: Future plans 2 
The reason I mentioned OWA in the first place is because 
I've done this for a customer of mine in the UK. They've got 
several people from a small corner-shop outfit in the USA (called 
WalMart I think...!) accessing mailboxes on their system via OWA. 
Using SSL of course... :-)
Neil Hobson 
Silversands http://www.silversands.co.uk Microsoft Gold Certified Partner For 
Enterprise Systems For Collaborative 
Solutions  -Original Message- From: Matthew 
Carpenter [mailto:[EMAIL PROTECTED]] 
Posted At: 13 February 2002 21:09 
Posted To: Sunbelt Exchange List Conversation: Future plans 2 Subject: RE: 
Future plans 2 
That is the best answer I have received, and you are 
right. I have no idea how to implement this without dropped mail to 
nonhomed recipients here OR there. I will discuss with them the 
different options that truly seem available: They home the mailboxes and 
we use OWA to use their domain 
there is a LEGAL partnership in which we act as 
connected sites, only passing THEIR address book I have not found 
another way around this, nor have I heard a good alternative otherwise 
-Original Message-
From: Benjamin Winzenz [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 13, 2002 1:08 
PM To: MS-Exchange Admin Issues Subject: RE: Future plans 2 
I'm just saying that you may want to consult with your 
legal department. Having the permission of the owner of the domain 
doesn't mean squat in the legal world. You are talking about 
basically interchanging internal company information. That, plus 
you don't have a plan in place how you want to accomplish this. 
The owner of the domain may not realize the scope of a project like 
this, which may not even be possible. In your given scenario 
below, if you were to add an MX record for their domain and accept it as 
inbound, you would HAVE to have a way to route the messages destined for 
their employees. Otherwise, mail is going to bounce. 
Why? Because the way that MX records work is that the server with 
the lowest cost gets most of the messages sent to it. There will 
be some messages that get sent to the other server. There isn't 
any way around this. That means that you will be receiving mail 
for possibly ANY person working at the other company. You get a 
message

RE: Future plans 2

2002-02-14 Thread Diane Beckham
Title: Message



They're loss

  -Original Message-From: William Lefkovics 
  [mailto:[EMAIL PROTECTED]]Sent: Thursday, February 14, 2002 
  10:09 AMTo: MS-Exchange Admin IssuesSubject: RE: Future 
  plans 2
  I 
  wish I knew. I lacked the enterprise experience to join their deployment 
  team. That number includes thousands of resource mailboxes and may not 
  be as many as I quoted.
  
  William 
  
-Original Message-From: David N. Precht 
[mailto:[EMAIL PROTECTED]]Sent: Thursday, February 14, 2002 
10:00 AMTo: MS-Exchange Admin IssuesSubject: Re: 
Future plans 2
how many servers ?

  - Original Message - 
  From: 
  William Lefkovics 
  To: MS-Exchange Admin 
  Issues 
  Sent: Thursday, February 14, 2002 
  12:25 
  Subject: RE: Future plans 2
  
  You know the answer Mr B. They both use 
  Exchange. WalMart, based in Arkansas, may well be the largest 
  Exchange2000 deployment at around 300,000 mailboxes.
  
  William
  
-Original Message-From: Martin Blackstone 
[mailto:[EMAIL PROTECTED]]Sent: Thursday, 
February 14, 2002 9:23 AMTo: MS-Exchange Admin 
IssuesSubject: RE: Future plans 2
I'm the 
same with KMart. I have never been in a WalMart and have on intention of 
doing so.
I'm a 
Target kind of guy.

Just to 
be on topic, Do you think Kmart or Wal-Mart use Exchange? 


  
  -Original Message-From: Matthew Carpenter 
  [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 14, 
  2002 9:16 AMTo: MS-Exchange Admin IssuesSubject: 
  RE: Future plans 2
  He may be. My wife won't set foot in WalMart. 
  Actually, neither will I... 
  -Original Message- From: Andrew Philips [mailto:[EMAIL PROTECTED]] 
  Sent: Thursday, February 14, 2002 11:13 
  AM To: MS-Exchange Admin Issues 
  Subject: RE: Future plans 2 
  you must not be married. 
  -Original Message- From: William Lefkovics [mailto:[EMAIL PROTECTED]] 
  Sent: Thursday, February 14, 2002 10:34 AM 
  To: MS-Exchange Admin Issues Subject: RE: Future plans 2 
  I've never been inside one of these 'WalMart' places 
  you refer. I don't think they exist. Are you sure you have 
  the name right?
  -Original Message- From: Neil Hobson [mailto:[EMAIL PROTECTED]] 
  Sent: Thursday, February 14, 2002 12:44 AM 
  To: MS-Exchange Admin Issues Subject: RE: Future plans 2 
  The reason I mentioned OWA in the first place is 
  because I've done this for a customer of mine in the UK. They've 
  got several people from a small corner-shop outfit in the USA (called 
  WalMart I think...!) accessing mailboxes on their system via 
  OWA. Using SSL of course... :-)
  Neil Hobson 
  Silversands http://www.silversands.co.uk 
  Microsoft Gold Certified Partner For Enterprise Systems For 
  Collaborative Solutions  
  -Original Message- From: Matthew Carpenter [mailto:[EMAIL PROTECTED]] 
  Posted At: 13 February 2002 21:09 
  Posted To: Sunbelt Exchange List Conversation: Future plans 2 Subject: 
  RE: Future plans 2 
  That is the best answer I have received, and you are 
  right. I have no idea how to implement this without dropped mail to 
  nonhomed recipients here OR there. I will discuss with them the 
  different options that truly seem available: They home the mailboxes 
  and we use OWA to use their domain 
  there is a LEGAL partnership in which we act as 
  connected sites, only passing THEIR address book I have not found 
  another way around this, nor have I heard a good alternative otherwise 
  -Original Message-
  From: Benjamin Winzenz [mailto:[EMAIL PROTECTED]] 
  Sent: Wednesday, February 13, 2002 1:08 
  PM To: MS-Exchange Admin Issues 
  Subject: RE: Future plans 2 
  I'm just saying that you may want to consult with your 
  legal department. Having the permission of the owner of the domain 
  doesn't mean squat in the legal world. You are talking about 
  basically interchanging internal company information. That, plus 
  you don't have a plan in place how you want to accomplish this. 
  The owner of the domain may not realize the scope of a project like 
  this, which may not even be possible. In your given scenario 
  below, if you were to add an MX record for their domain and accept it 
  as inbound, you would HAVE to have a way to route the messages 
  destined for their employees. Otherwise, mail is going

Future plans 2

2002-02-13 Thread Matthew Carpenter
Title: Message



I am 
going to try this one more time. I think some of you can help me on this. 
TIA

  
  -Original Message-From: Matthew 
  Carpenter Sent: Tuesday, February 12, 2002 2:52 PMTo: 
  'MS-Exchange Admin Issues'Subject: Future 
plans
  We have future 
  plans to work with another company on a few projects, and they want some of us 
  to use THEIR email domain. ie:
  
  We are abc.com, 
  and they want us to be able to send mail also as xyz.com without handling mail 
  for the rest of xyz.com. Can I just add an MX record for xyz.com, as well as 
  that company doing so (since they are authoritative) and then accept xyz.com 
  as inbound? I am pretty sure I missed something since I just lost myself in 
  this example!! Anyone have experience with this? That is the best way to 
  approach it.
  
  EXCH 5.5 SP4 
  NT4
  Matthew Carpenter, MCP, CNA, A+Network Engineer and 
  Exchange AdministratorSARMA1801 
  BroadwaySan Antonio, TX 78215
  
List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm





RE: Future plans 2

2002-02-13 Thread Neil Hobson

Get them to create you a few mailboxes on their system, and access them
via OWA.


Neil Hobson

Silversands
http://www.silversands.co.uk
Microsoft Gold Certified Partner
For Enterprise Systems
For Collaborative Solutions 

-Original Message-
From: Matthew Carpenter [mailto:[EMAIL PROTECTED]] 
Posted At: 13 February 2002 15:21
Posted To: Sunbelt Exchange List
Conversation: Future plans 2
Subject: Future plans 2


I am going to try this one more time. I think some of you can help me on
this. TIA
-Original Message-
From: Matthew Carpenter 
Sent: Tuesday, February 12, 2002 2:52 PM
To: 'MS-Exchange Admin Issues'
Subject: Future plans


We have future plans to work with another company on a few projects, and
they want some of us to use THEIR email domain. ie:

We are abc.com, and they want us to be able to send mail also as xyz.com
without handling mail for the rest of xyz.com. Can I just add an MX
record for xyz.com, as well as that company doing so (since they are
authoritative) and then accept xyz.com as inbound? I am pretty sure I
missed something since I just lost myself in this example!! Anyone have
experience with this? That is the best way to approach it.

EXCH 5.5 SP4 NT4
Matthew Carpenter, MCP, CNA, A+
Network Engineer and Exchange Administrator
SARMA
1801 Broadway
San Antonio, TX 78215


List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm
**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual to whom it is addressed.
Any view or opinions presented are solely those of the author and do
not necessarily represent those of Silversands, or any of its
subsidiary companies.
If you have received this email in error, please contact our Support
Desk immediately by telephone on 01202-36 or via email at
[EMAIL PROTECTED]
**

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm




RE: Future plans 2

2002-02-13 Thread Benjamin Winzenz

Other than this type of plan, there will be nothing that will not take a
large amount of time and effort to do.  You may not even legally be able to
do more than this.  Check with your legal department.

Ben Winzenz, MCSE 
Network/Systems Administrator 
Peregrine Systems 


-Original Message-
From: Neil Hobson [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 13, 2002 11:30 AM
To: MS-Exchange Admin Issues
Subject: RE: Future plans 2

Get them to create you a few mailboxes on their system, and access them
via OWA.


Neil Hobson

Silversands
http://www.silversands.co.uk
Microsoft Gold Certified Partner
For Enterprise Systems
For Collaborative Solutions 

-Original Message-
From: Matthew Carpenter [mailto:[EMAIL PROTECTED]] 
Posted At: 13 February 2002 15:21
Posted To: Sunbelt Exchange List
Conversation: Future plans 2
Subject: Future plans 2


I am going to try this one more time. I think some of you can help me on
this. TIA
-Original Message-
From: Matthew Carpenter 
Sent: Tuesday, February 12, 2002 2:52 PM
To: 'MS-Exchange Admin Issues'
Subject: Future plans


We have future plans to work with another company on a few projects, and
they want some of us to use THEIR email domain. ie:

We are abc.com, and they want us to be able to send mail also as xyz.com
without handling mail for the rest of xyz.com. Can I just add an MX
record for xyz.com, as well as that company doing so (since they are
authoritative) and then accept xyz.com as inbound? I am pretty sure I
missed something since I just lost myself in this example!! Anyone have
experience with this? That is the best way to approach it.

EXCH 5.5 SP4 NT4
Matthew Carpenter, MCP, CNA, A+
Network Engineer and Exchange Administrator
SARMA
1801 Broadway
San Antonio, TX 78215


List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm
**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual to whom it is addressed.
Any view or opinions presented are solely those of the author and do 
not necessarily represent those of Silversands, or any of its 
subsidiary companies.
If you have received this email in error, please contact our Support 
Desk immediately by telephone on 01202-36 or via email at
[EMAIL PROTECTED]
**

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm




RE: Future plans 2

2002-02-13 Thread Steve Wyman
Title: Message



as you 
saying they want you to send as [EMAIL PROTECTED] for 
example but not receive on the XYZ domain.

Whereas you will continue to send and receive on 
abc.com

  -Original Message-From: Matthew Carpenter 
  [mailto:[EMAIL PROTECTED]]Sent: 13 February 2002 
  15:21To: MS-Exchange Admin IssuesSubject: Future plans 
  2
  I am 
  going to try this one more time. I think some of you can help me on this. 
  TIA
  

-Original Message-From: Matthew 
Carpenter Sent: Tuesday, February 12, 2002 2:52 PMTo: 
'MS-Exchange Admin Issues'Subject: Future 
plans
We have future 
plans to work with another company on a few projects, and they want some of 
us to use THEIR email domain. ie:

We are abc.com, 
and they want us to be able to send mail also as xyz.com without handling 
mail for the rest of xyz.com. Can I just add an MX record for xyz.com, as 
well as that company doing so (since they are authoritative) and then accept 
xyz.com as inbound? I am pretty sure I missed something since I just lost 
myself in this example!! Anyone have experience with this? That is the best 
way to approach it.

EXCH 5.5 SP4 
NT4
Matthew Carpenter, MCP, CNA, A+Network Engineer 
and Exchange AdministratorSARMA1801 BroadwaySan Antonio, TX 78215
List Charter and FAQ 
  at:http://www.sunbelt-software.com/exchange_list_charter.htm
List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm





RE: Future plans 2

2002-02-13 Thread Matthew Carpenter
Title: Message



I am 
saying that they basically want the functionality of having 2 domain addresses 
so that they can go back and forth and send and receive mail as xyz.com OR 
abc.com. Another company owns the new domain, and we will just be using 10-12 
mailboxes completely separate from them.

  
  -Original Message-From: Steve Wyman 
  [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 13, 2002 
  10:56 AMTo: MS-Exchange Admin IssuesSubject: RE: Future 
  plans 2
  as 
  you saying they want you to send as [EMAIL PROTECTED] for 
  example but not receive on the XYZ domain.
  
  Whereas you will continue to send and receive on 
  abc.com
  
-Original Message-From: Matthew Carpenter 
[mailto:[EMAIL PROTECTED]]Sent: 13 February 2002 
15:21To: MS-Exchange Admin IssuesSubject: Future plans 
2
I 
am going to try this one more time. I think some of you can help me on this. 
TIA

  
  -Original Message-From: Matthew 
  Carpenter Sent: Tuesday, February 12, 2002 2:52 
  PMTo: 'MS-Exchange Admin Issues'Subject: Future 
  plans
  We have future 
  plans to work with another company on a few projects, and they want some 
  of us to use THEIR email domain. ie:
  
  We are 
  abc.com, and they want us to be able to send mail also as xyz.com without 
  handling mail for the rest of xyz.com. Can I just add an MX record for 
  xyz.com, as well as that company doing so (since they are authoritative) 
  and then accept xyz.com as inbound? I am pretty sure I missed something 
  since I just lost myself in this example!! Anyone have experience with 
  this? That is the best way to approach it.
  
  EXCH 5.5 SP4 
  NT4
  Matthew Carpenter, MCP, CNA, A+Network Engineer 
  and Exchange AdministratorSARMA1801 BroadwaySan Antonio, TX 
  78215
  List Charter and FAQ 
at:http://www.sunbelt-software.com/exchange_list_charter.htmList 
  Charter and FAQ 
  at:http://www.sunbelt-software.com/exchange_list_charter.htm
List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm





RE: Future plans 2

2002-02-13 Thread Benjamin Winzenz
Title: RE: Future plans 2









I'm just saying that you may want to
consult with your legal department. Having the permission of the owner of
the domain doesn't mean squat in the legal world. You are talking
about basically interchanging internal company information. That, plus
you don't have a plan in place how you want to accomplish this. The
owner of the domain may not realize the scope of a project like this, which may
not even be possible. In your given scenario below, if you were to add an
MX record for their domain and accept it as inbound, you would HAVE to have a
way to route the messages destined for their employees. Otherwise, mail
is going to bounce. Why? Because the way that MX records work is
that the server with the lowest cost gets most of the messages sent to
it. There will be some messages that get sent to the other server.
There isn't any way around this. That means that you will be
receiving mail for possibly ANY person working at the other company. You
get a message for a person at the other company, and your Exchange server doesn't
know what the hell to do with it. You don't have any recipients
with that name set up. Ends up being very messy.



I was thinking earlier about setting up
custom recipients for them, but that too would end up being messy, and I don't
think it would work. They could, however, set up some mailboxes and custom
recipients for you, have the mailbox deliver mail to the custom recipient and
have those custom recipients forward the mail to your server. That, or
setting up some mailboxes for you and you using OWA, would be by far the
easiest, if not the only, solutions to what you are asking. Anything else
is sounding more like a consulting gig to find a solution to your problem.



If they are so insistent on you using
their e-mail, why don't they provide the solution? Otherwise, tell
them to go with the above-mentioned OWA, or forward your mail via CR's,
and let you reply using your own addy's.









Ben Winzenz,
MCSE 
Network/Systems Administrator 
Peregrine Systems 









-Original Message-
From: Matthew Carpenter
[mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 13, 2002
1:25 PM
To: MS-Exchange Admin Issues
Subject: RE: Future plans 2



What do
you mean legally? If we have the permission of the owner of the domain, there
is no issue. 

-Original
Message- 
From: Benjamin Winzenz [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 13, 2002
10:48 AM 
To: MS-Exchange Admin Issues

Subject: RE: Future plans 2




Other
than this type of plan, there will be nothing that will not take a large amount
of time and effort to do. You may not even legally be able to do more
than this. Check with your legal department.

Ben
Winzenz, MCSE 
Network/Systems Administrator 
Peregrine Systems 



-Original
Message- 
From: Neil Hobson [mailto:[EMAIL PROTECTED]]

Sent: Wednesday, February 13, 2002
11:30 AM 
To: MS-Exchange Admin Issues

Subject: RE: Future plans 2


Get them
to create you a few mailboxes on their system, and access them via OWA.




Neil
Hobson 

Silversands

http://www.silversands.co.uk

Microsoft Gold Certified Partner

For Enterprise Systems

For Collaborative Solutions 

-Original
Message- 
From: Matthew Carpenter [mailto:[EMAIL PROTECTED]] 
Posted At: 13 February 2002 15:21

Posted To: Sunbelt Exchange List

Conversation: Future plans 2

Subject: Future plans 2




I am going
to try this one more time. I think some of you can help me on this. TIA
-Original Message- 
From: Matthew Carpenter 
Sent: Tuesday, February 12, 2002
2:52 PM 
To: 'MS-Exchange Admin Issues'

Subject: Future plans




We have
future plans to work with another company on a few projects, and they want some
of us to use THEIR email domain. ie:

We are
abc.com, and they want us to be able to send mail also as xyz.com without
handling mail for the rest of xyz.com. Can I just add an MX record for xyz.com,
as well as that company doing so (since they are

authoritative)
and then accept xyz.com as inbound? I am pretty sure I missed something since I
just lost myself in this example!! Anyone have experience with this? That is
the best way to approach it.

EXCH 5.5
SP4 NT4 
Matthew Carpenter, MCP, CNA, A+

Network Engineer and Exchange
Administrator 
SARMA 
1801 Broadway 
San Antonio, TX 78215




List
Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm

**

This email and any files
transmitted with it are confidential and intended solely for the use of the
individual to whom it is addressed. Any view or opinions presented are solely
those of the author and do 

not
necessarily represent those of Silversands, or any of its 
subsidiary companies.

If you have received this email in
error, please contact our Support 
Desk immediately by telephone on
01202-36 or via email at [EMAIL PROTECTED

RE: Future plans 2

2002-02-13 Thread Vincent Britton
Title: Message











I am a little confused!



But if I understand you correctly! 



Have the administrators of xyz company create an alternate recipient for the people in
your abc company. Have there main email
address listed as the [EMAIL PROTECTED] on there
server. Then on the Addresses tab of
there server add the name they wish that user to receive mail from [EMAIL PROTECTED].
When they receive an incoming request for [EMAIL PROTECTED],
there server will accept it and then redirect it to [EMAIL PROTECTED].
Then on your servers have there reply addresses set to [EMAIL PROTECTED] if necessary.



Will this do what you need? 



-Original Message-
From: Matthew Carpenter
[mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 13, 2002 10:21 AM
To: MS-Exchange Admin Issues
Subject: Future plans 2





I am going to try this
one more time. I think some of you can help me on this. TIA





-Original Message-
From: Matthew Carpenter 
Sent: Tuesday, February 12, 2002 2:52 PM
To: 'MS-Exchange Admin Issues'
Subject: Future plans



We have future plans to work with
another company on a few projects, and they want some of us to use THEIR email
domain. ie:











We are abc.com, and they want us to
be able to send mail also as xyz.com without handling mail for the rest of
xyz.com. Can I just add an MX record for xyz.com, as well as that company doing
so (since they are authoritative) and then accept xyz.com as inbound? I am
pretty sure I missed something since I just lost myself in this example!!
Anyone have experience with this? That is the best way to approach it.











EXCH 5.5 SP4 NT4





Matthew Carpenter, MCP, CNA, A+
Network
Engineer and Exchange Administrator
SARMA
1801
Broadway
San Antonio, TX 78215









List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm




List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm







RE: Future plans 2

2002-02-13 Thread Matthew Carpenter
Title: Message



That 
is the best answer I have received, and you are right. I have no idea how to 
implement this without dropped mail to nonhomed recipients here OR there. I will 
discuss with them the different options that truly seem 
available:

  They home the mailboxes and we use OWA to use 
  their domain
  there 
  is a LEGAL partnership in which we act as connected sites, only passing THEIR 
  address book
I have 
not found another way around this, nor have I heard a good alternative 
otherwise

  
  -Original Message-From: Benjamin Winzenz 
  [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 13, 
  2002 1:08 PMTo: MS-Exchange Admin IssuesSubject: RE: 
  Future plans 2
  
  I'm just saying that 
  you may want to consult with your legal department. Having the 
  permission of the owner of the domain doesn't mean squat in the legal 
  world. You are talking about basically interchanging internal company 
  information. That, plus you don't have a plan in place how you want to 
  accomplish this. The owner of the domain may not realize the scope of a 
  project like this, which may not even be possible. In your given 
  scenario below, if you were to add an MX record for their domain and accept it 
  as inbound, you would HAVE to have a way to route the messages destined for 
  their employees. Otherwise, mail is going to bounce. Why? 
  Because the way that MX records work is that the server with the lowest cost 
  gets most of the messages sent to it. There will be some messages that 
  get sent to the other server. There isn't any way around this. 
  That means that you will be receiving mail for possibly ANY person working at 
  the other company. You get a message for a person at the other company, 
  and your Exchange server doesn't know what the hell to do with it. You 
  don't have any recipients with that name set up. Ends up being very 
  messy.
  
  I was thinking 
  earlier about setting up custom recipients for them, but that too would end up 
  being messy, and I don't think it would work. They could, however, set 
  up some mailboxes and custom recipients for you, have the mailbox deliver mail 
  to the custom recipient and have those custom recipients forward the mail to 
  your server. That, or setting up some mailboxes for you and you using 
  OWA, would be by far the easiest, if not the only, solutions to what you are 
  asking. Anything else is sounding more like a consulting gig to find a 
  solution to your problem.
  
  If they are so 
  insistent on you using their e-mail, why don't they provide the 
  solution? Otherwise, tell them to go with the above-mentioned OWA, or 
  forward your mail via CR's, and let you reply using your own 
  addy's.
  
  
  
  
  Ben 
  Winzenz, MCSE Network/Systems 
  Administrator 
  Peregrine Systems 
  
  -Original 
  Message-From: Matthew 
  Carpenter [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 13, 2002 1:25 
  PMTo: MS-Exchange Admin 
  IssuesSubject: RE: Future 
  plans 2
  
  What do 
  you mean legally? If we have the permission of the owner of the domain, there 
  is no issue. 
  -Original Message- From: Benjamin Winzenz [mailto:[EMAIL PROTECTED]] 
  Sent: Wednesday, 
  February 13, 2002 10:48 AM To: MS-Exchange Admin Issues Subject: RE: Future plans 2 
  
  
  Other 
  than this type of plan, there will be nothing that will not take a large 
  amount of time and effort to do. You may not even legally be able to do 
  more than this. Check with your legal department.
  Ben 
  Winzenz, MCSE Network/Systems Administrator Peregrine Systems 
  
  -Original Message- From: Neil Hobson [mailto:[EMAIL PROTECTED]] 
  Sent: Wednesday, 
  February 13, 2002 11:30 AM To: MS-Exchange Admin Issues Subject: RE: Future plans 2 
  
  Get them 
  to create you a few mailboxes on their system, and access them via 
  OWA. 
  
  Neil 
  Hobson 
  Silversands http://www.silversands.co.uk 
  Microsoft Gold Certified 
  Partner For 
  Enterprise Systems For Collaborative Solutions 
  -Original Message- From: Matthew Carpenter [mailto:[EMAIL PROTECTED]] 
  Posted At: 13 
  February 2002 15:21 Posted To: Sunbelt Exchange List 
  Conversation: Future plans 
  2 Subject: Future 
  plans 2 
  
  I am 
  going to try this one more time. I think some of you can help me on this. TIA 
  -Original Message- From: Matthew Carpenter Sent: Tuesday, February 12, 2002 2:52 
  PM To: 
  'MS-Exchange Admin Issues' Subject: Future plans 
  
  We have 
  future plans to work with another company on a few projects, and they want 
  some of us to use THEIR email domain. ie:
  We are 
  abc.com, and they want us to be able to send mail also as xyz.com without 
  handling mail for the rest of xyz.com. Can I just add an MX record for 
  xyz.com, as well as that company doing so (since they are
  authoritative) and then accept xyz.com as inbound? I 
  am pretty sure I missed something since I just lost myself in this example

RE: Future plans 2

2002-02-13 Thread Vincent Britton
Title: Message









Changing the MX records on your domain
will not affect mail going to them unless coming from your domain! No one will ever query your DNS Servers
for there mail server?









-Original Message-
From: Matthew Carpenter
[mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 13, 2002
4:09 PM
To: MS-Exchange Admin Issues
Subject: RE: Future plans 2





That is the best answer I
have received, and you are right. I have no idea how to implement this without
dropped mail to nonhomed recipients here OR there. I will discuss with them the
different options that truly seem available:




They
home the mailboxes and we use OWA to use their domain


there is
a LEGAL partnership in which we act as connected sites, only passing THEIR
address book



I have not found another
way around this, nor have I heard a good alternative otherwise





-Original Message-
From: Benjamin Winzenz
[mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 13, 2002
1:08 PM
To: MS-Exchange Admin Issues
Subject: RE: Future plans 2

I'm just saying that you
may want to consult with your legal department. Having the permission of
the owner of the domain doesn't mean squat in the legal world. You are
talking about basically interchanging internal company information. That,
plus you don't have a plan in place how you want to accomplish this. The
owner of the domain may not realize the scope of a project like this, which may
not even be possible. In your given scenario below, if you were to add an
MX record for their domain and accept it as inbound, you would HAVE to have a
way to route the messages destined for their employees. Otherwise, mail
is going to bounce. Why? Because the way that MX records work is
that the server with the lowest cost gets most of the messages sent to
it. There will be some messages that get sent to the other server.
There isn't any way around this. That means that you will be receiving
mail for possibly ANY person working at the other company. You get a
message for a person at the other company, and your Exchange server doesn't
know what the hell to do with it. You don't have any recipients with that
name set up. Ends up being very messy.



I was thinking earlier
about setting up custom recipients for them, but that too would end up being
messy, and I don't think it would work. They could, however, set up some
mailboxes and custom recipients for you, have the mailbox deliver mail to the
custom recipient and have those custom recipients forward the mail to your server.
That, or setting up some mailboxes for you and you using OWA, would be by far
the easiest, if not the only, solutions to what you are asking. Anything
else is sounding more like a consulting gig to find a solution to your problem.



If they are so insistent
on you using their e-mail, why don't they provide the solution?
Otherwise, tell them to go with the above-mentioned OWA, or forward your mail
via CR's, and let you reply using your own addy's.









Ben Winzenz, MCSE 
Network/Systems Administrator 
Peregrine Systems 









-Original Message-
From: Matthew Carpenter
[mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 13, 2002
1:25 PM
To: MS-Exchange Admin Issues
Subject: RE: Future plans 2



What do you mean legally? If we have the permission of
the owner of the domain, there is no issue. 

-Original Message- 
From: Benjamin Winzenz [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 13, 2002
10:48 AM 
To: MS-Exchange Admin Issues

Subject: RE: Future plans 2




Other than this type of plan, there will be nothing
that will not take a large amount of time and effort to do. You may not
even legally be able to do more than this. Check with your legal
department.

Ben Winzenz, MCSE 
Network/Systems Administrator 
Peregrine Systems 



-Original Message- 
From: Neil Hobson [mailto:[EMAIL PROTECTED]]

Sent: Wednesday, February 13, 2002
11:30 AM 
To: MS-Exchange Admin Issues

Subject: RE: Future plans 2


Get them to create you a few mailboxes on their
system, and access them via OWA. 



Neil Hobson 

Silversands 
http://www.silversands.co.uk

Microsoft Gold Certified Partner

For Enterprise Systems

For Collaborative Solutions 

-Original Message- 
From: Matthew Carpenter [mailto:[EMAIL PROTECTED]] 
Posted At: 13 February 2002 15:21

Posted To: Sunbelt Exchange List

Conversation: Future plans 2

Subject: Future plans 2




I am going to try this one more time. I think some of
you can help me on this. TIA -Original Message- 
From: Matthew Carpenter 
Sent: Tuesday, February 12, 2002
2:52 PM 
To: 'MS-Exchange Admin Issues'

Subject: Future plans




We have future plans to work with another company on a
few projects, and they want some of us to use THEIR email domain. ie:

We are abc.com, and they want us to be able to send
mail also as xyz.com without handling mail for the rest of xyz.com. Can I just
add an MX record for xyz.com, as well as that company doing so