"Oliver Moazzezi [MVP]" <o.moazzezino@spamfreenet.co.uk> wrote in message
news:uNmbG3YHJHA.3456@TK2MSFTNGP04.phx.gbl...
> Hi Nick,
>
> The easy way would be to configure the b***@ourdomain.com user to access
> their mail via your Exchange infrastructure.
>
> Either OWA, Outlook Anywhere (RPC over HTTPs) or POP3/IMAP4 and SMTP.
>
> What you are asking is possible, but it requires you to make your domain
> non-authoritative - which I think is pretty crazy when you can implement a
> better solution via one of the options above.
>
> Oliver
>
>

"Bharat Suneja [MSFT]" wrote:

> In addition to what Oliver said, it would be really hard to justify adding
> this complexity (of address space sharing) to your Exchange deployment for a
> single mailbox.
> --
> Bharat Suneja
> Microsoft Corporation
> blog: exchangepedia.com/blog
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights. Please do not send email directly to this alias. This alias is for
> newsgroup purposes only.
> ----------------------------
>
>
>
>
> "Oliver Moazzezi [MVP]" <o.moazzezino@spamfreenet.co.uk> wrote in message
> news:uNmbG3YHJHA.3456@TK2MSFTNGP04.phx.gbl...
> > Hi Nick,
> >
> > The easy way would be to configure the b***@ourdomain.com user to access
> > their mail via your Exchange infrastructure.
> >
> > Either OWA, Outlook Anywhere (RPC over HTTPs) or POP3/IMAP4 and SMTP.
> >
> > What you are asking is possible, but it requires you to make your domain
> > non-authoritative - which I think is pretty crazy when you can implement a
> > better solution via one of the options above.
> >
> > Oliver
> >
> >
>
>

"nick reed" <nickr***@discussions.microsoft.com> wrote in message
news:79976AE1-DD87-406B-B6D7-AF92D31DE92D@microsoft.com...
> Hi All,
>
> I have a funny little one here to ponder over. We are running exchange
> 2003,
>
> We have an address set up with our ISP that captures b***@ourdomain.com,
> this is a POP account so a home user can pick up the mail. All other mail
> sent to anyth***@ourdomain.com still gets routed to us,
>
> However, if you try and send the mail form the office whilst obviously on
> the domain, the exchange server throws back a report saying no user.
>
> What i require is that exchange Ignores this one address and lets it be
> sent
> to our ISP, therefor being kept on their server for POP access.
>
> We do not really want to create a user on our domain for this account and
> do
> not want to open pop on our servers either. Is their an easy way of doing
> this??
>
> Cheers All
> Nick Reed