Re: SMTP Receipient Policy for Intranet email only

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Bob Genestet (bob_genestet_at_computernetorkservice.com)
Date: 02/18/04 

Date: Tue, 17 Feb 2004 23:14:02 -0600

Thanks Javier,

Thanks for interpreting my problem correctly and for the suggestion for
limiting e-mail to .local only. This is what the client is looking for. They
are almost entirely Windows 98 (10 or 12 users) and will need to take one
step at a time towards total domain functionally. As of now, they wish to
remain a workgroup. They will need to authenticate to the SBS server only
through their email clients for now, which is Windows Messaging. I hope to
be able to at least move them to Outlook 2003. My main concern is with the
large .wav files and Exchange. They are not concerned with periodically
backing up the SBS server. Can I keep these .wav files out of the Exchange
database or should I just enable "circular logging" and let it run?

I was initially going to recommend MS Server 2003 to this client, but it
would be hard to beat the value of SBS2003 Standard Edition. I have
discovered the flexibility of SBS's Exchange for accommodating any e-mail
protocol, including POP3, IMAP, HTTP, and SMTP, which makes it possible to
use Outlook Express with SBS2003 if needed.

Thank you,
Bob Genestet

"Javier Gomez [SBS MVP]" <javier_gomez@remove.this.engineer.com> wrote in
message news:uFFl4nc9DHA.4080@tk2msftngp13.phx.gbl...
> You are saying that you have a linux box that would reside on the SBS lan
> and it will send .wav files to different intranet email accounts by
relaying
> them to the SBS box using SMTP? I think SBS would work on your scenario.
>
> See inline...
>
> > Using SBS2003, what else is needed for a user to receive intranet email
> > other than an email address space created in the receipient policy in
> > Exchange? Or for that matter, any individual FQDN email address created
> for
> > any individual user in their user profile?
>
> You need to have a mailbox in Exchange for each user and if you would have
> to delete the FQDN addresses so they only have their intranet ones
(.local)
> in order not to receive external mail. If you want also to restrict them
to
> send external mail... you can do it using delivery restrictions.
>
> > Does SBS2003 include a POP3 service as in Windows Server 2003, or just a
> > connector?
>
> Yes. It is disabled by default... but it's there.
>
> --
> Javier [SBS MVP]
>
> << SBS ROCKS !!! >>
>
>

Relevant Pages

  • Re: Two email domains
    ... The client decided to order new server. ... You can take them from a barely functioning SBS to fully functional ... HQ may or may not be storing data in Exchange regardless ...
    (microsoft.public.windows.server.sbs)
  • Re: Two email domains
    ... The client decided to order new server. ... You can take them from a barely functioning SBS to fully functional ... HQ may or may not be storing data in Exchange regardless of ...
    (microsoft.public.windows.server.sbs)
  • Re: Install new hardware for SBS 2003
    ... I used Swing on about half my transitions from SBS or Windows 2000 to SBS 2003, and can recommend it without reservation. ... I just want to do it the right way for this client. ... AFAIK, neither method (complete independent rebuild off line, or the SWING kit) would result in leaving the client "without a working system". ... Other than simply copying the data over I will have to get the current Exchange mail over too. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS EXchange Server not send to @aol.com.
    ... Signup for Mailhop Outbound ... Open Exchange System Manager and go to Connectors. ... is it possible in SBS exchange? ... We have a client that was issued a fixed IP address only to find out ...
    (microsoft.public.windows.server.sbs)
  • Re: best way to recreate a mailbox
    ... >> some changes in PSS recently, so please take advantage of any request to ... I exhausted what I could do by phone and told the client, ... data loss can occur from running utilities against your Exchange ... >>> There is also a problem, likely related, with Backup Exec. ...
    (microsoft.public.windows.server.sbs)