I understand exactly what it is you want to do. Exchange does not work that way.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brett Fernicola Posted At: Wednesday, November 14, 2007 9:38 AM Posted To: swynk Conversation: Exchange advanced SMTP Configuration ? Subject: RE: Exchange advanced SMTP Configuration ? Thanks for the good info but I still think your overcomplicating it. There would never be a loop in my scenario. If all email going to the external domain never got routed through exchange at all, and went strait to the internet pop3 linux host all would be perfect. The mail would not get delivered to the exchange mailbox at all. Instead it will travel the internet until received by the pop3 linux server. Then the pop3 linux server would forward a copy back to the Exchange servers local domain name where the email would finally reach the users mailbox only one time. Now there would be a copy on the pop3 server and the exchange server, which is what I need. No infinite loop or problems. Yes I see this will create a slight delay in delivery times but only a few seconds to minutes, a little extra bandwidth will be used to send out and back in but that's not a problem for this small company. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Scharff Sent: Wednesday, November 14, 2007 10:04 AM To: Exchange Discussions Subject: RE: Exchange advanced SMTP Configuration ? I'm sorry but I didn't miss the point or misunderstand the problem. What you want to happen Exchange doesn't do and my peers, in trying to be helpful were thinking out loud. Always a trait to be encouraged, but unfortunately the suggestion would introduce a mail loop. At best that would mean your users would receive multiple copies of every message and the senders would receive an NDR stating the message had been NDR'd because it had executed too many hops. That is both a loop and a problem in my experience. Your surety notwithstanding, when a company goes through an acquisition, the acquiring company generally goes through very deliberate steps to prevent exactly the type of behavior you describe rather than trying to encourage it. If you search on InterOrg you should find a series of Microsoft whitepapers on related topics. In all of those, there is deliberate care to delineate the processes whereby the mailbox is homed in one and only one organization. They do this because the alternative looks like that which is described above. As to what you actually want to achieve you're right of course, I opted for brevity over an exhaustive series of what are generally held to be untenable implementations which meet the requirements more broadly. But since you insist here are your options: Client: 1. Maintain 2 profiles: 1 for POP3 and one for Exchange. All sending must be done via the POP3 profile. If a user is in the Exchange profile and wants to send to or reply to a message, they need to close and reopen outlook in the correct profile. When the POP3 server is unavailable change its settings to use Exchange. 1a. Use 2 separate mail applications instead of 2 profiles. 2. Use POP3 for all mail related activities. Use OWA for calendaring and contacts. Yes, I know this is really 1b, and that all of these ignore that Exchange calendaring invites are mail messages but I already said they were untenable. 3. Add the POP3 service to the existing profile at time of disaster... sure you'll download a second copy of every message already in the POP3 mailbox but it a also technically meets the stated end goal of maintaining 2 mailboxes using the client to capture sent messages. Server: Here I have a great deal more insight having helped design a somewhat similar solution for a different problem. It's relatively straightforward. First you'll need to write a categorizer event sink which uses a hash table to remap all mail sent to the user to an alias you associate with the user's POP3 mailbox. Then you'll need to have the POP3 account forward to an alternate address on the Exchange server where your cat sink will rewrite the address to the primary. If you have more than one Exchange server it starts to get really complicated because now you'll need to maintain state information. Hopefully you won't need to do that as it will likely radically increase the time required to develop the solution. It's certainly possible I'm wrong. There are plenty of things I know more about than Exchange (e.g beer and the Dukes of Hazzard). But I've not come across an answer which was better than the original I posited. As to your desire for real help, I'm not sure what that means. I guess in this context it might mean you want someone to write the server solution for you I describe. I'm certainly willing to do that. I'd estimate it would take 8-10 weeks to develop and QA; I'd be happy to discuss your budget for the project offline. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brett Fernicola Posted At: Wednesday, November 14, 2007 7:30 AM Posted To: swynk Conversation: Exchange advanced SMTP Configuration ? Subject: RE: Exchange advanced SMTP Configuration ? I think you guys are missing the point, there is no loop or problem. First I don't care about the ISP Linux Pop3 server, its not my problem. Let me brake it down again... Lets call the small company books.com, books.com pays a 3rd party webhost a small fee for webhosting dns, and 30 pop3 mail accounts. The current users of this company all use pop3 to connect to the linux host to get their email. All is well here. Ok now the users of the company are interested in exchange. They have a small network with a domain controller, file servers etc. They also have an extra box which I installed exchange on. They have a semi decent static internet connection which I registered etc. There internal domain name is contoso.local. Now on the 3rd party webhosting admin panel each users pop3 email account is setup to forward a copy of all new incoming email to [EMAIL PROTECTED] this feature is working 100%. Now what I want to achieve. By adding the external live smtp address for each user in AD, ex. [EMAIL PROTECTED] the users at the company can log into exchange and send email; by setting the 2nd smtp address "@books.com" as primary, the recipients of those emails see @books.com as the sender. If the recipient emails [EMAIL PROTECTED] back the email will go to the Linux Pop3 server "again not under my control or problem" and once the email gets there it will be forwarded to [EMAIL PROTECTED] There the email will get to the proper exchange account etc. So now we have a copy of the email in 2 places. On the linux host and on their exchange server. The only problem I have is this. Using this setup if a user logs into exchange on the lan and sends an email to another co-worker using the real external domain, @books.com, so lets say [EMAIL PROTECTED] emails [EMAIL PROTECTED] using their exchange profile, then the email will not go out to the internet, instead it gives delivered instantly to their mailbox via exchange. I can not have this right now. I need exchange to not deliver mail going to the domain @books.com to its local storage group. Instead I need it to strictly use a Smart Host or something to force exchange to send the email out to the internet where it will reach the Linux Pop3 server only. Now once that email reaches the linux pop3 server it will be forwared to [EMAIL PROTECTED] Thus no duplicate emails, one exchange server not doing that much work, and the linux server I don't care one bit about. So now if exchange fails or they do not like it, they can switch Outlook profiles and fall back to their Linux Pop3 account, where low and behold an exact copy of %100 of their email will be sitting waiting for them. I know this can be done, its got to be very similar to when one company purchases another company and they start a merger. Please any real help is appreciated this setup has to work as described. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dean Cunningham Sent: Tuesday, November 13, 2007 8:52 PM To: Exchange Discussions Subject: RE: Exchange advanced SMTP Configuration ? Probably agree with your comment on your last line :-) Journalling may be another option, or perhaps each excahnge mailbox has an alternate recipient that is a mailbox on the linux server?? Would not cached outlook give them similar feature to what they have now? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brett Fernicola Sent: Wednesday, 14 November 2007 06:35 To: Exchange Discussions Subject: RE: Exchange advanced SMTP Configuration ? The copy of email on the pop3 linux host is for backup and failsafe purposes, these users right now do not want to switch to exchange because they fear failure is destined on the exchange server. They want to be able to fall back to the hosting provider they already pay for incase exchange goes down. They also do not have an exchange admin, but they do have the hardware and bandwidth in place. Since the pop3 is so cheap they don't mind paying them for this type of backup and service until they feel they can manage exchange. However they are interested in exchange because they want to be able to share calendars and inbox's etc, which means using exchange. So what will happen right now with the current setup is their pop3 and exchange accounts will all have the same exact email except for any emails sent from outlook via exchange to another user in the company. This mail sees the smtp address in AD and sends the mail to the storage group. So if exchange fails and they have to temporarily switch profiles to pop3 they will be missing all the emails the users sent to each other. Can anyone think of any solution to this problem, or am I nuts for even trying. ********************************************************************** Have you clicked on yet? www.nrc.govt.nz ********************************************************************** NORTHLAND REGIONAL COUNCIL This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify [EMAIL PROTECTED] ********************************************************************** _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange To subscribe: http://e-newsletters.internet.com/discussionlists.html/ To unsubscribe send a blank email to [EMAIL PROTECTED] t.com Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange To subscribe: http://e-newsletters.internet.com/discussionlists.html/ To unsubscribe send a blank email to [EMAIL PROTECTED] t.com Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange To subscribe: http://e-newsletters.internet.com/discussionlists.html/ To unsubscribe send a blank email to [EMAIL PROTECTED] t.com Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange To subscribe: http://e-newsletters.internet.com/discussionlists.html/ To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange To subscribe: http://e-newsletters.internet.com/discussionlists.html/ To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
