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 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-360000 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 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 ********************************************************************** 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-360000 or via email at [EMAIL PROTECTED] ********************************************************************** List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
