Re: Email Quagmire
- From: Frank <Frank@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 3 Dec 2007 17:31:00 -0800
"Brian Cryer" wrote:
"Frank" <Frank@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:234EEF00-6B9A-4721-A05F-AE743371B820@xxxxxxxxxxxxxxxx
I've been using SBS 2003 at home for a few years. I've also used Outlook
2003, but I had the client setup as POP3 accounts on the couple of
computers
I own.
Now, I'm trying to switch to use Outlook as an Exchange client on SBS and
I'm having some issues. Initally, I couldn't get mail to send until I
placed
my ISP's (Comcast) DNS servers in:
Default SMTP Virtual Server | Properties | Advanced Delivery | Configure.
I inserted comcast.net for the FQDN, left Smart Host blank, and in
Configure, I put in the Comcast DNS servers.
I know you've already resolved this one, but the reason is simply that many
email servers use blacklists which automatically reject ip addresses which
are allocated to home broadband or dial-up accounts. Hence the need to send
via your ISP because hopefully their servers aren't blacklisted.
The mail works now, with two exceptions: email sent to AOL accounts is NOT
accepted and I have this little quirk with my own domain name.
What error do you get back when trying to send to AOL accounts? (Its always
possible that your ISP is blacklisted somewhere, some ISPs are.)
Let's say your domain is abc.local and you try to send email to an ISP
that
has abc.com pop3 accounts for you, but your ISP at the server is Comcast.
Try
to send an email to frank@xxxxxxx and the server won't even send it
because
it won't recognize the address when the server is .local.
This isn't a problem on any of the servers I'm responsible for. It could be
a DNS issue. If you open up a command prompt window and do "nslookup
abc.com" then what IP address comes back? (Do both the nslookup I just said
and also "nslookup -type=mx abc.com" the latter looks up where mail should
be sent which may be different to the destination of other traffic.) Is this
the correct (external) IP address or is it the IP address of your server? If
its the IP address of your server then its a DNS issue.
I don't have a static IP and I suspect that complicates matters.
Not having a static IP adds something to the mix, but not much. If you
haven't already then I'd suggest signing up with one of the dynamic-dns
providers such as www.no-ip.com or www.dyndns.com and then be sure to use
that DNS name everywhere instead of your IP address. But you probably know
that already.
Hope this helps.
--
Brian Cryer
www.cryer.co.uk/brian
Thank you everyone for your response....
Just some follow-ups...
I did get the email to work sending and receiving. I think this came after
putting comcast's DNS servers in the Advanced Delivery-Configure of the
Default SMTP Virtual Server.
However, I still cannot send email to AOL and I had email rejected by one
other ISP.
I puzzle as to why this is the case when I'm still sending mail using
Comcast's DNS servers as I was when my email was configured as a "standalone"
Outlook client pointing to smtp.comcast.net. By the way, I have added that to
the Smart Host.
I do own a domain name and I have setup an account with DynDNS to simulate a
static IP. I have not set an MX record with the DynDNS account, but that
won't help me get that mail out to AOL anyway.
Thanks again. Any followup thoughts would be appreciated.
.
- Follow-Ups:
- Re: Email Quagmire
- From: Daveinfla
- Re: Email Quagmire
- Prev by Date: Re: employee monitoring
- Next by Date: Re: AD Replication
- Previous by thread: Re: AD Replication
- Next by thread: Re: Email Quagmire
- Index(es):
Relevant Pages
|
