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
