Lanwench
Mon Jul 14 07:55:50 PDT 2008
hijack <hijack@discussions.microsoft.com> wrote:
> Thanks for your reply. I know I have to implement SBS as described in
> this post but I am still confused about the MX record and other
> issues. The possibility that I may be using incorrect terminology or
> descriptions may be high.
>
> The difficulty I experienced in replying to this post was always from
> a different PC not in any way connected to the SBS, but my off site
> personel PC.
>
> I have spoken to the ISP personal. Each person at the ISP gives a
> different story about my account. Tha latest is that I have a pop3
> domain registered account with an MX record MX1.ISPname.net. Further
> this consultant told me that I do need a MX record.
Yes - your domain has one now in its public DNS.
> (The ISP personal
> are not familiar with SBS)
SBS has nothing to do with this...this is basic SMTP :-)
Did you read the tutorial/link I posted to msexchange.org?
>
> Assuming that my server is setup with an MX record
It isn't. Your *domain* is, in its DNS. What is your public domain name?
> where in the SBS
> setting can I confirm this ? or If I am using the dreaded pop
> connection how do I confirm this on SBS ?
When you ran the CEICW you would've chosen the POP3 connector. You can run
it again and see (without making changes).
>
> Please help me take this one step at a time.
Again, check out the link I posted originally.
Change your domain's public DNS - you need an A record, or "address" record,
that specifies your network's public IP. Many people use mail.mydomain.com.
Your domain's primary MX record should then be changed to mail.mydomain.com
You should re-run the CEICW to stop using the POP connector, and make sure
your firewall is configured to direct port 25 traffic to your SBS server's
LAN IP.
Make sure your ISP doesn't block port 25 inbound!
Note that you can do this even with a dynamic public IP if you don't have a
static, but it's a little more complex....you will need a dynamic DNS host
such as www.dyndns.com or www.no-ip.com
>
>> hijack <hijack@discussions.microsoft.com> wrote:
>>> I seem to be having a problem with my replies. This is the fifth
>>> attempt.
>>>
>>> Thanks for your informative link.
>>> I ponder whether I require a MX record.
>>
>> Of course you do, if you want to get any mail at all. Your domain
>> most likely has an MX record now, remember. ;-)
>>
>>
>>> All my email users have a
>>> separate email account with the ISP
>>
>> Yep.
>>
>>> and not a spooled email account.
>>
>> There isn't any such thing - without POP at the ISP, all your
>> senders will deliver mail directly to the Exchange server. The ISP
>> isn't involved.
>>
>>> This decision was taken before my involvement with SBS at this site
>>> and hence I use the pop3 connection. The reasoning for this decision
>>> was that in the event of the server going down an alternative method
>>> for email retrieval was possible from the ISP as individual
>>> accounts.
>>
>> Yes. But your server really shouldn't be going down!
>>
>>> With a spooled account all email users can see all email on the ISP
>>> side.
>>
>> Nope. Nobody can see squat. Your ISP has nothing to do with this,
>> remember. You *can* get someone else to act as a backup ("store &
>> forward") - a lower-priority MX record in your domain's DNS - but
>> that isn't mandatory.
>>
>>> Would this be true ? I need to give convincing argument to the
>>> benifits of a spooled email account with sbs in mind.
>>
>> Use good hardware, good maintenance, and a good internet connection,
>> and ensure that your server does not go down regularly. You can
>> configure a backup (I usually use dyndns - MailHop BackupMX) if you
>> like, too. But remember, your senders should automatically retry
>> delivery for 3 to 5 days if your server is unavailable for any
>> reason.
>>
>> See
http://www.swinc.com/resource/exch_smtp_diatribe.htm
>>>
>>>
>>>> hijack <hijack@discussions.microsoft.com> wrote:
>>>>> Thanks for the reply.
>>>>> My server is not on a fixed static IP address to the server (I
>>>>> will setup a free one with no-ip.com etc later)
>>>>
>>>> I personally prefer www.dyndns.com, but they're all good. Set this
>>>> up now.
>>>>>
>>>>> You mentioned that my MX records directly send mail through the
>>>>> server
>>>>
>>>> Not exactly. There's a good SMTP delivery outline here:
>>>>
http://www.msexchange.org/tutorials/MF002.html. It's not written
>>>> for SBS (or E2003) specifixally - but it should help. And you
>>>> don't need a static IP to do it, although it's recommended.
>>>>
>>>>> and using RPC over HTTPS.
>>>>
>>>>> Please expand on the benifits of
>>>>> these concept as I feel I am under utilising my SBS.
>>>>
>>>> Yes, that's possible. This stuff is pretty easy to setup, though.
>>>>
>>>> POP connectors are a kluge and are not recommended. RPC over HTTP
>>>> gives your remote users access to their full mailboxes, public
>>>> folders, GAL, etc. - and all data remains on your server, sync'd to
>>>> an local OST file in Outlook via cached mode.
>>>>>
>>>>>
>>>>>> Is there a reason why you haven't changed your MX records
>>>>>> directly to send mail through your SBS box
>>>>>> and Are not using RPC over HTTPS?
>>>>>>
>>>>>> Then you wouldn't have to worry about any of this?
>>>>>>
>>>>>> Russ
>>>>>>
>>>>>> --
>>>>>> Russell Grover - SBITS.Biz
>>>>>> Microsoft Gold Certified Partner
>>>>>> Microsoft Small Business Specialist
>>>>>> World Wide Remote SBS2003 Support -
http://www.SBITS.Biz
>>>>>> Get Help Now!
http://www.crossloop.com/SBITSdotBiz
>>>>>>
>>>>>>
>>>>>> "hijack" <hijack@discussions.microsoft.com> wrote in message
>>>>>> news:55F019CE-4826-4F39-8B28-315B8DEA08B0@microsoft.com...
>>>>>>> I have SBS2003 std with 15 local clients on site attached to the
>>>>>>> server. The
>>>>>>> clients use MS Outlook 2007 for email. All client email
>>>>>>> accounts are held with an ISP. the server downloads email from
>>>>>>> the ISP using pop3 and smtp automatically.
>>>>>>>
>>>>>>> One of my client notebooks will be out of the office and
>>>>>>> requires email access using a wireless connection to the ISP.
>>>>>>>
>>>>>>> 1. How do I prevent the server from downloading email from the
>>>>>>> ISP automatically for this client notebook when the notebook is
>>>>>>> not in the office?
>>>>>>>
>>>>>>> 2. How do I set up a notification message informing the senders
>>>>>>> that the recipient is out of the office.
>>>>>>>
>>>>>>> 3. When MS Outlook sets up the email account via the server on
>>>>>>> client PCs, the server details appear in outlook and is greyed
>>>>>>> out. Do I create a new profile specifically for this client
>>>>>>> notebook?
>>>>>>>
>>>>>>> 4. The client notebook can RWW into the server but I will not
>>>>>>> consider this
>>>>>>> option for this specific application.
>>>>>>> --
>>>>>>> Thanks for the help
>>>>>>> Jack