Can send e-mails out to internet except aol, yahoo, and earthlink 1

[cardinalkid]

I can send emails out to almost all email accounts except for aol, yahoo, and earthlink. These are really the only ones I'm concered with. We are running exchange 2000 and host our own website and exchange server. We migrated from 5.5 to 2000 about a year and a half ago. I wasn't here then so I don't know if they ever were able to send to these sites. I'm assuming so because people are shocked when I tell them they can't send to these sites. I'm looking for any advice. I can give more information if requested. Please HELP!!

 

[Zelandakh]

you are probably on a dhcp address not a fixed ip. Try using a smart host out to your isp.

 

[cardinalkid]

I have a static ip address on the web/exchange server. The emails sit in the smtp queue. Here is the message I get when I try to send to these sites

Your message did not reach some or all of the intended recipients.

Subject: Trouble emailing aol addresses
Sent: 12/1/2004 10:46 AM

The following recipient(s) could not be reached:

address@aol.com on 12/3/2004 11:02 AM
Could not deliver the message in the time limit specified. Please retry or contact your administrator.
<(domain name) #4.4.7>

 

[Zelandakh]

4.4.7 is usually a DNS error.

 

[zigcoors]

Does your MX record for your mail domain point to your SBS Server?

I believe that AOL do a rDNS lookup on the sending SMTP server, you may to either use a smarthost to relay your mail , or better have a proper rDNS record created for your static IP, that resolves to your domain.

 

[zigcoors]

See this thread:

http://www.tek-tips.com/viewthread.cfm?qid=950924&page=1

for more info.

 

[cardinalkid]

I have read this thread all ready. I'm not sure what you are trying to say when you are talking about the sbs server. I know what it is I'm just not sure what you are referring to. We are using two servers for DNS our server with exchange and data server. I should also mention that we can receive mail from people with these addresses, just not send.

 

[zigcoors]

if i did a NSLOOKUP on your domain - would it return your SBS servers external IP address as the MX record.

for example
H:\>nslookup
Default Server: fred.domain.co.uk
Address: 192.168.10.105

> set q=mx
> mydomain.com
Server: fred.domain.co.uk
Address: 192.168.10.105

Non-authoritative answer:
mydomain.com MX preference = 0, mail exchanger = m.dnsix.com

m.dnsix.com internet address = 63.251.171.165
m.dnsix.com internet address = 63.251.171.167
m.dnsix.com internet address = 63.251.171.166
m.dnsix.com internet address = 63.251.171.164
Then if I did a ,lookup on the IP would it resolve back to the same FQDN?

 

[cardinalkid]

I know a little about DNS but not a lot.

Here is what I get when I do nslookup, I did it twice once with just my domain name and then with the exchange server name and this one is the second ouput:

H:\>nslookup
Default Server: data.domain.com
Address: 172.20.0.8

> set q=mx
> domain.com
Server: data.domain.com
Address: 172.20.0.8

DNS request timed out.
timeout was 2 seconds.
domain.com MX preference = 10, mail exchanger = cardinals




Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

H:\>nslookup
Default Server: data.domain.com
Address: 172.20.0.8

> set q=mx
> cardinals.domain.com
Server: data.domain.com
Address: 172.20.0.8

domain.com
primary name server = data.domain.com
responsible mail addr = hostmaster
serial = 4701
refresh = 900 (15 mins)
retry = 600 (10 mins)
expire = 86400 (1 day)
default TTL = 3600 (1 hour)

 

[zigcoors]

OK - you really need to do the lookup against an external DNS server for your domain. The info that you have is your internal DNS info - not the same as the rest of the world sees.

Change the DNS server in the properties of your network connection to an external server, try 212.1.128.156

Ian

 

[cardinalkid]

Here is what I get when I do it from external DNS, some stuff edited out for security. Not completely sure how this will help me, hopefully you can help.

Non-authoritative answer:
myDomain.com MX preference = 10, mail exchanger = mydomain.com

mydomain.com nameserver = dns.uw-mil.wiscnet.net
mydomain.com nameserver = dns.uw-mad.wiscnet.net
mydomain.com internet address = 216.56.16.x
dns.uw-mil.wiscnet.net internet address = 205.213.163.100
dns.uw-mad.wiscnet.net internet address = 205.213.108.100

 

[NinthBit]

Out of curiousity, did you upgrade Server OS recently?

I ran into this same situation when I upgraded from 2000 server to 2003 server. There's an issue with EDNS allowing larger than 512k DNS packets, and it's defaulted to ON in 2003. Some sites aren't able to accept larger DNS packets.

I only bring this up because it sounds identical to the problem I was having - MX records were correct, we weren't blacklisted, etc. This was the final attempt and disabling EDNS allowed immediate mail transfer to the big sites like AOL/Yahoo!/Earthlink.

 

[cardinalkid]

We went from 5.5 exchange to 2000. I just want to mention that I have gone out to dnsstuff.com,

http://www.mxtoolbox.com,

and another to make sure I'm not on a blacklist and all reports are good. I will try the EDNS.

 

[cardinalkid]

I forgot to mention that we do have two dns servers, our exchange/web server and the data server which is 2k3 server and this was added the same time the exchange was updated. When I ran all the ip/domain lookup stuff it all came back to the correct location.

 

[NinthBit]

That could be your problem, CK. The Server 2k3 is what handles the EDNS. Minutes after I brought my 2k3 forest live, DNS pooped out.

All of my DNS resolved appropriately (hence being able to email to any domain but the big three) but it wasn't until I turned EDNS off that the queues for AOL/Yahoo/etc. started clearing out.

 

[cardinalkid]

This is how I solved the problem, after I did this registry edit I could send mail to the email addresses.

I would give the EDNS fix a try. If you don't have dnscmd.exe installed (and you really should), just open the registry and go to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters

and add this name/value pair:

EnableEDNSProbes DWORD 0x0

and stop and restart your DNS service.

This solved all my problems.

 

[NinthBit]

Great! Glad you're all set. I know I was pulling my hair out about this same problem. Happy holidays to ya.