Les
Sun Apr 09 07:30:40 PDT 2006
http://support.microsoft.com/search/default.aspx?qu=share+smtp+name+space+exchange+2003
It's going to be an issue no matter what you do with the email addresses on
the box, exchange doesn't need to use the .com email address to find a match
and deliver the message locally.
The bottom line is that they're just not using their resources as they're
designed to be used, so you are being forced to find a work around to
something that would normally work properly and with low administration
cost.
They may as well turn off exchange and use external mail hosting
exclusively - it's hard to be half-in half-out.
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius
"Adrian Marsh (NNTP)" <news@_removeme_adrianmarsh.me.uk> wrote in message
news:4438D836.9040501@_removeme_adrianmarsh.me.uk...
> Hi Les,
>
> You won't find me disagreeing!!
>
> Unfortunately, this is a small company with no local IT support on site,
> and they want to access their email when not in the office from mobiles
> etc over POP3, but they don't want to open up their main server to the
> net. Thats where I'm trying to re-educate..
>
> User accounts are still needed for the NT domain.
>
> Sounds like the MS KB is the most likely solution, I'll go search and
> come back if I can't find anything.
>
> Would deleting the users mailbox force SBS to send the email on
> externally, even if the account has a matching SMTP/Email address?
>
> My current solution is to change those specific users email address
> account to @somewhere.local, and then hide those users from the GAB.
>
> Adrian
>
> Les Connor [SBS Community Member - SBS MVP] wrote:
>> Hi Adrian,
>>
>> So, you're sharing the name space, then. If Joe never logs onto the SBS;
>> doesn't need a user account - then his mailbox is at the ISP. Because the
>> ISP's mail server is authoratative for the domain, your exchange can't
>> be -
>> hence the sharing.
>>
>> It is possible to share the namespace in such a way by removing Joe's
>> mailbox from the SBS, and telling Exchange to forward all mail witn
>> unresolved addresses to the ISP, where Joe's mailbox is. You can search
>> the
>> MS KB for sharing email name space.
>>
>> But honestly, you are making this way too hard. Wouldn't it just be
>> simpler
>> for Joe to pick his email up from Exchange instead of the ISP? He won't
>> know
>> the difference - it's exactly the same mechanism, just a different
>> server.
>> Further, the users don't need to pick up *any* mail from the ISP via
>> Outlook, and then store it in Exchange. That's backwards. Exchange should
>> pick the email from the ISP, and store it in the users mailboxes. The
>> users
>> then use Outlook to connect to their Exchange mailbox for email (and much
>> more). Further, even - email becomes more accessible as you now have
>> multiple ways for users to connect to their mailboxes - Outlook on the
>> lan,
>> web browser (OWA) from any internet connected computer, Outlook over the
>> Web
>> (RPC/HTTP), POP, IMAP.
>>
>> It's a trivial task to run the CEICW and configure the Exchange pop3
>> connector to bring all the ISP hosted mail into Exchange, 24x7, and have
>> the
>> users connect to Exchange. At the same time, get your DNS records in
>> order
>> so you can host the email yourself, and in a matter of a day or two you
>> won't need the pop3 connector any more.
>>