Re: Handeling Multiple SMTP Email Messages via one Exchange Mailbo

From: Weinie (Weinie_at_discussions.microsoft.com)
Date: 03/27/05


Date: Sun, 27 Mar 2005 07:37:02 -0800

Thanks for the answer. I was kinda expecting the third party answer from my
lack of finding an answer elsewhere.

However, I realize I failed to define my OWA thought properly. What prompted
this whole search is that I have the users "Exchange" profile configured with
POP3 accounts, and of course the mail goes into the mail Inbox. However,
someone needs to be at the client and open it up, or hit "Send/Receive" to
get the mail. When they log into OWA from a remote location, you can see the
email that was gathered from that Outlook client previously, but there
doesn’t seem to be a way to get new mail as those POP3 additions to that
clients profile are local to that machine, so not accessible via OWA.

This caused me to try and get email for these domains routed directly into
their Inbox, but then my previously stated observation and dilemma came about.

Then again, perhaps I'm approaching this the wrong way, I don't know.

"Lanwench [MVP - Exchange]" wrote:

> Weinie wrote:
> > All,
> >
> > Ok, here is the situation I have. I have one W3K server running
> > Exchange server 2003. I have 4 Internet domains (4 separate
> > companies, housed in the same building) that I need to receive email
> > from. Currently these are on a UNIX server in a co-lo, with people
> > connecting to these accounts via IMAP or POP3 with their Outlook 2003
> > clients.
> >
> > I have setup a little Linux box in a DMZ running Postfix, and have
> > configured it to accept only email for the four domains I need, i.e.
> > dom1.com, dom2.com, dom3.com, dom4.com. This bastion host/front end
> > server is happily sitting there and receiving email and forwarding it
> > onto the Exchange server on the Intranet. (The Exchange server has
> > it's own internal private domain name that has nothing to do with the
> > Internet) The Exchange server happily receives this email, and
> > delivers this email to the mailbox's it's supposed to as I have
> > configured the default recipient policy with these domain names,
> > naming one of them as the default (@dom1.com).
> >
> > Ok, so far so good. Now, when a user connects to the Exchange server
> > using his "Exchange" profile (as opposed to the one they are using
> > for IMAP/POP3 access) so they can use common calendaring, tasks, etc
> > they see this email in their mailbox. Now comes the part that I need
> > help with in understanding, and hopefully coming to a resolution.
> >
> > When you open an email in this profile, you see the senders name in
> > From:, but no matter what email domain the message was sent to, the
> > To: address is the local Active Directory name, not the email address
> > (user@dom3.com) it was originally sent to.
>
> Yep.
>
> > This poses a problem as
> > these users need to know what company this email was sent to, and
> > they need to reply to that email and have it sent out with the From:
> > address from that company/domains address.
>
> You'll need third party stuff - www.ivasoft.biz. ChooseFrom - and maybe
> WhichAddress. Nothing native will do this - unless you want to set up
> multiple mailboxes, assign permissions, etc....which is a pain.
> >
> > Outlook 2003 does this just fine in it's non-exchange profile of
> > course, but I can't seem to figure out how to get this accomplished
> > in an Exchange profile. Another reason I would like to do this is so
> > people can access their email box, with email from all 4 domains,
> > from OWA.
>
> They can do that now, actually. They just can't see
> who/what/which/where/what. Even if you get the 3rd party stuff, as far as I
> know.
> >
> > I have been looking thorough these support forums for a day now and
> > have not run across an answer to this, yet. Could someone please
> > point me to a relevant article, or provide me with the (I'm sure)
> > simple answer I am overlooking?
> >
> > Thanks,
>
>
>



Relevant Pages

  • Re: Hoping for a response this time
    ... simply testing OWA) from inside the network. ... their mail from another workstation PC using OWA inside ... I do believe the problem is on the client ... Roaming profile problems? ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange + Entourage
    ... But the main problem remains the LDAP related 3268 port. ... And yes I believe if OWA works fine then Entourage ... >> I'd like the Exchange server to be accessible over the Internet, ... >> client is in US and the server is in Europe. ...
    (microsoft.public.exchange.admin)
  • Re: Exchange + Entourage
    ... But the main problem remains the LDAP related 3268 port. ... And yes I believe if OWA works fine then Entourage ... >> I'd like the Exchange server to be accessible over the Internet, ... >> client is in US and the server is in Europe. ...
    (microsoft.public.mac.office.entourage)
  • Re: Exchange + Entourage
    ... But the main problem remains the LDAP related 3268 port. ... And yes I believe if OWA works fine then Entourage ... >> I'd like the Exchange server to be accessible over the Internet, ... >> client is in US and the server is in Europe. ...
    (microsoft.public.exchange.clients)
  • Re: Exchange + Entourage
    ... But the main problem remains the LDAP related 3268 port. ... And yes I believe if OWA works fine then Entourage ... >> I'd like the Exchange server to be accessible over the Internet, ... >> client is in US and the server is in Europe. ...
    (microsoft.public.exchange.connectivity)