Inline:
-Cliff
"yousaid" <> wrote in message
news:57158CE5-8E42-4741-AB0A-...
> Thanks Cliff for responding. Actually I have a few books on this and the
> one
> I used is SBS2008 Unleashed. I used all the default settings.
> (1) Well like I send, emails to Internal users work ok. For external
> users,
> the emails just sit in the QUE. Then after a while I get a message
> Delayed
> message. then the next day, I get an NDR message.
Exchange 2007 has tools to get more information on what is happening with
the messages in the queue. Your SBS 2008 book should cover these tools. A
message sitting in a queue isn't much information to go on.
http://technet.microsoft.com/en-us/l.../aa997892.aspx
In particular, the message flow troubleshooter and queue viewer will be
helpful. You can see WHY a message is still in the queue. A very different
error is logged when a server fails to do a DNS lookup, for example, than
when a remote SMTP server answers and then gives a rejection code because
the email determined to be invalid. Even the rejection code would be a
significantly important detail.
> (2) When I use Pop3 client, Exchange downloads the messages and places
> them
> in the appropriate mailbox. HOWEVER, I don't want to use POP3. I want SBS
> to
> send and receive the messages.
As well you should, but you missed my larger point. DNS is used for the
*sending* server to find your server. Right now, for incoming mail, the
sending servers are obviously finding your ISP's email server and not yours.
That is strictly a DNS record issue and not at all related to SBS.
mxtoolbox checks to see that you have an MX record (which you do) and that a
server is there (which your ISPs server is) so your mxtoolbox test passing
has NO bearing on this being an SBS issue. It is still a DNS issue. You
said in your initial post that you weren't familiar with SBS but that you
were familiar with networking. So I don't know how to explain it more
easily that this *is* a basic networking issue.
> (3)The only error I see in pop3clientlog is "unable to relay
> .
POP3 is only used for receiving emails, never for sending. So, as we've
established, your incoming mail issue is DNS related. Your outgoing email
issue will involve pop3 or its logs.
> (4)I have used wireshack and other tools to verify that traffic is
> flowing
> thru the ports and even my ISP have also tested. The problem is definetely
> a
> configuration issue having to do with one of the connectors NOT being
> properly configured.
wireshark is of limited value here. Your SBS server can send and receive on
port 25 all day, but if your router is not properly forwarding traffic from
the external IP to your SBS server then you'll still get no joy. Similarly
if your router passes traffic on port 25 outbound but your ISP is blocking
it (common on residential connection) then wireshark shows good, but your
outgoing mail will still fail.
In short? You can't trust your ISP to do this. You need to take pro-active
troubleshooting steps. The mailflow troubleshooter mentioned above will
help. But in short, you should be able to at least verify outgoing SMTP
connectivity by picking a random server (gmail works) and do what any mail
server would. nslookup and telnet. If you can't manually send an SMTP
message to a gmail or hotmail account via telnet then you can't expect SBS
to do its thing either. And again, this isn't SBS specific. Testing SMTP
is generic network troubleshooting.
> (5)Sure If you are available, I will pay you to walk me OVER THE PH to
> get
> it working. This is a Test environment that will be used as a proof of
> concept
> Email me: (replace no spam with .com)
> thanks for posting
I don't solicit business in the newsgroups. More importantly, I'd recommend
trying to find somebody local to you. SBS definitely *does* have quirks,
and if...for example...you go from test to live and then later need to
restore a backup in a timely fashion, having a pre-existing relationship
with an SBS expert could be invaluable. ...someone who can show up and help
you get the restore gong as quickly as possible. Certainly a scenario where
phone support simply wouldn't be enough.
Start here.
http://www.microsoft.com/smallbusiness/hub.mspx
MS offers a great tool for helping find specialists familiar with small
businesses and SBS. Treat this like you would any contracting relationship.
If you were building a new office, you wouldn't just take any contractor and
architect. You'd meet a few, get some bids, and form a relationship with
someone you are comfortable. You should treat your technology investment
with similar reverence.
Hope this helps,
-Cliff
>
> --
> yousaid
>
>
> "Cliff Galiher" wrote:
>
>> Your issues aren't SBS specific in any way.
>>
>> 1) The fact that you are able to receive emails via pop3 implies that
>> your
>> MX record is incorrect. mxtoolbox only goes so far. It can check that
>> the
>> records exist, are properly formatted, and that *A* server responds, but
>> it
>> can't verify that the server responding is the one you WANT responding.
>> This is, in short, basic DNS networking and not specific to SBS or even
>> Windows.
>>
>> 2) For sending, you need to provide more information. Errors,
>> troubleshooting steps taken, etc. Could be an SBS issue, could be a
>> firewall issue, could be a router issue, could be a DNS issue. AGain,
>> far
>> more likely a networking issue than an SBS issue, considering the
>> statement
>> above.
>>
>> As far as an idiot's guide, far too many moving parts here. You can't
>> call
>> a mechanic over the phone and tell him your car is not running right and
>> expect him to fix it over the phone with no details. Similarly, a
>> functioning network is a myriad of complementary systems coordinating and
>> working together to pass traffic. It takes on-site observances or very
>> detailed information to even begin troubleshooting problems.
>>
>> Your best bet is to buy some books (amazon has several on SBS) and/or
>> call
>> in a consultant familiar with SBS to help you. It is probably a good
>> idea,
>> if you aren't familiar with SBS, to build a relationship with an SBS
>> specialist anyways. That way you know and trust the person *before* you
>> need their expertise and you already have a working relationship if you
>> need
>> to call them in a pinch.
>>
>> -Cliff
>>
>>
>> "yousaid" <> wrote in message
>> news:A7824C8B-1B06-4D29-B6CB-...
>> > Greetings,
>> > I have just installed SBS 2008 and everything seems to work fine
>> > EXCEPT,
>> > we
>> > can not get emails out to external adresses.( Internal users get their
>> > mails
>> > OK) Also, we can only retrieve mails from our webhoster if we use POP3
>> > connector. Our preference is NOT to use POP3 connector. So essentially
>> > receive only works with POP3 and send does NOT work at all to EXTERNAL
>> > users.
>> > Our test environment is like this:
>> > Server name = Testserve. Ip address = 192.168.2.200. Internal Domain =
>> > Testdomain. Our mailserver with webhoster = mail.ourdomain.com
>> > (mail.agingcarenet.com).
>> > Using Outlook, we connect and download and send mails.
>> > I have checked with our webhoster, webhost4life and even checked myself
>> > using mxtools.com website to verify and confirm that SPF, MX etc are
>> > all
>> > ok.
>> > (1) So how do I configure SBS2008 to both SEND and RECEIVE using
>> > EXCHANGE?
>> > (2) Do we need to have our hoster add our STATIC IP address to the MX
>> > records, and then change the SBS box to use STATIC adddress?
>> > NOTE: Currently, we are NOT using the static address. but we have one
>> > that
>> > can be used if need be.
>> > Thanks for your help and please and IDIOTS guide on how to configure
>> > the
>> > needed connectors for this to work. I am very familiar with networking,
>> > but
>> > not SBS 2008.
>> >
>> > --
>> > yousaid
>>
>> .
>>
Similar Threads
Linear Mode
