Al
Thu Jul 21 20:31:26 CDT 2005
Did you say something again? ;)
Here's a few thoughts:
1) delivery to multiple mailboxes can be incredibly confusing. Consider TCP
443 to allow for the services you want to publish vs. dual-homing.
Dual-homing is not going to provide any other added benefit and it always
causes issues.
2) Consider using ISA server for the above as resources allow.
3) Until then, if you MUST and I mean really MUST allow for messages to be
delivered to two locations the best way to do that would be to assign an
alternate recipient. The downside to this is that all messages will be
delivered to both mailboxes similar to journaling (which would be another
option if you so choose). To accomplish this, it would be something like:
a) Exchange is authoritative for the MYDOM.local domain only (again, I have
to assume here. The delivery of other messages from outside does not occur
here right? Or does your ISP send mail to your Exchange server? It sounds
like not, but that instead that is completely internal only; let me know if
this is incorrect on my part)
b) create a mail-enabled contact with the target address of
CEO@MYNONPROFIT.org
c) assign the contact as the alternate delivery mailbox of the CEO's mailbox
(remember it should be a copy so you want to specify that it should deliver
to both recipient and target)
d) verify it's working as expected.
Expected results: all mail sent to the CEO should be bifurcated and sent to
the ISP server
Does that solve the problem? Or did I misunderstand something in the
description?
Al
"Flayton" <Flayton@discussions.microsoft.com> wrote in message
news:18994607-731C-4817-B70E-8C833C0F90DE@microsoft.com...
> Well, that sure is a good question!
>
> I've suggested that the company just get the multi-home config working so
> workers who are out of the building and using their laptops can just VPN
> in
> and check their email on the Exchange Server (and use the Sharepoint
> services, network resources, etc.) But there are security concerns and
> money
> concerns, so that must wait.
>
> Mostly this is to cater to the CEO, who is often out at a conference and
> needs to check email. She can get email from all external sources, as
> those
> messages reside on the ISP's POP3 server. Messages from her employees in
> our
> office-building never make it out of the building, however. Those
> messages
> are only in the local Exchange Mailbox.
>
> I've recommended that we disable Exchange Server and ONLY use the POP3
> accounts in our Outlook profiles, but that removes our shared Contacts and
> Calendar functionality, does it not? It also hinders use of the internal
> Sharepoint services, I've been told. I'm only volunteering my services
> for a
> relative who's head is on the block for this. I thought it would be a
> quick
> fix. Now I'm knee-deep. Thank you for helping!
>
> As for SMTP servers, we have the Exchange Virtual SMTP server, of course,
> hosted on the internal MYDOM.local domain. We have the smart host server
> from our ISP of MAIL.OURISP.NET (for example) that we are using. We have
> the
> MAIL.MYNONPROFIT.org server assigned to us by our ISP for SMTP and POP3
> services.
>
> I'm thinking that if our internal domain had been correctly set up as
> MYNONPROFIT.local, to match the domain namespace of MYNONPROFIT.org that
> the
> rest of the world sees, that the method given in KB article #300681 or
> #319759 would have worked, but I'm not sure.
>
> Any ideas?
>
> Thanks,
> Ian
>
> "Al Mulnick" wrote:
>
>> Did you say something?
>>
>> Why does the mail need to go to the ISP server for mobile comm? Give us
>> more
>> information such as why? what the smtp addresses are that are being used
>> (not real ones, but if the ISP and your SMTP addresses are the same we
>> need
>> to know). Let us know any other pertinent information as well, such as
>> what
>> you mean by mobile? Is this a mobile device?
>>
>> It's been my experience that it's always best to follow the "there is
>> only
>> one" method of addressing and not try this dual delivery method. If
>> you're
>> using multiple addresses, you could forward messages to the ISP, but that
>> could get messy as well.
>>
>> I'm mostly interested in why you want mail in more than one location at a
>> time.
>>
>> Al
>>
>>
>>
>> "Flayton" <Flayton@discussions.microsoft.com> wrote in message
>> news:68AB8D8C-0251-444A-822F-8292EAA5D262@microsoft.com...
>> > Apparently, my question from 6 days ago was too old to get a response.
>> > Anybody know how I can achieve this? Am I talking only to myself? Who
>> > said
>> > that? ;) Here's my problem, and my non-solutions so far. Original
>> > message
>> > is at the bottom.
>> >
>> > Thanks for any and all help.
>> > Ian
>> >
>> > Flayton wrote >>
>> >
>> > No Luck. My local domain is, for example, MYDOM.local, whereas my POP3
>> > domain is MYNONPROFIT.org. Is this the problem? I've followed the
>> > instructions in METHOD #1 and #2, but my internal Exchange Server (or
>> > internal DNS, I'm not sure which) is still grabbing any
>> > internal-to-internal
>> > email and delivering it. It does NOT pass it on to my ISP for
>> > delivery,
>> > which is what I want.
>> >
>> > I realize that I'm trying to do something unorthodox, from Microsoft's
>> > perspective, but it should be possible.
>> >
>> > Please help!
>> >
>> > I have my Default recipient policy (has 2 smtp addresses, one
>> > MYDOM.local
>> > and one MYNONPROFIT.org, and an X400 address; and the internal one is
>> > primary) set. I selected the MYNONPROFIT.org address and de-selected
>> > the
>> > "This Exchange Organization is not responsible for all email delivery
>> > to
>> > this
>> > address."
>> > I have an additional recipient policy that is applied to all Users with
>> > an
>> > Exchange Mailbox. It has the same 3 addresses listed, except the
>> > MYNONPROFIT.org is set as the primary. I chose Yes on the following 2
>> > dialog
>> > boxes, and did an Apply this Policy Now... for good measure.
>> >
>> > My test user flayton is set to Automatically Update Email Addresses
>> > based
>> > on
>> > Recipient Policy, and I have tried sending email from this user TO this
>> > user
>> > with the local address ad primary AND with the external address as
>> > primary.
>> > Both times, the email was delivered instantly to my Exchange inbox and
>> > never
>> > made it out to the external POP3 server.
>> >
>> > Ian
>> >
>> >
>> > "Flayton" wrote:
>> >
>> >> In reviewing another post regarding a similar issue, I found a pointer
>> >> to
>> >> the
>> >> following Knowledge Base article:
>> >>
>> >>
http://support.microsoft.com/kb/300681
>> >>
>> >> I believe that Method #2 contained in that article will solve my
>> >> problem.
>> >> I
>> >> want the external (ISP host) mail server to be responsible for
>> >> handling
>> >> ALL email,
>> >> whether it originates from an internal or external source. That way
>> >> we
>> >> can
>> >> access all of our email remotely. This is a temporary fix until we
>> >> get
>> >> our
>> >> Multi-Home configuration up and running, but that has some security
>> >> considerations that we still need to address.
>> >>
>> >> I'll follow up with another reply after I've applied recipient
>> >> policies
>> >> to
>> >> all of our email users. Luckily there aren't hundreds!
>> >>
>> >> Ian
>> >>
>> >> "Flayton" wrote:
>> >>
>> >> > We're running SBS 2003, and we don't have a multihome configuration,
>> >> > yet.
>> >> > When sending email to co-workers on our same domain, Exchange server
>> >> > resolves
>> >> > the email address and places the email in the user's mailbox. We
>> >> > want
>> >> > to
>> >> > make all such emails go past the Exchange Server and out to the
>> >> > ISP's
>> >> > SMTP
>> >> > server, so that mobile users can access ALL of their email. How do
>> >> > I
>> >> > force
>> >> > Exchange Server to pass on all emails to the external ISP's SMTP
>> >> > server?
>> >> >
>> >> > Thanks,
>> >> > Ian
>> >
>>
>>
>>