79 replies
by dash242
I've had this problem before, but it was so long ago, I can't remember exactly what caused it. Some things to try though: telnet to 205.188.156.164 on port 25 from your mail server. If you get a connection, try the following:
helo nameofyourmailserver.yourdomain.com
mail from: root@yourdomain.com
rcpt to: postmaster@aol.com
data
Subject: Having trouble sending e-mail to your server.
If you get this message, please respond.
.
quit
If the message goes through, postmaster should respond. (They did for me) This means your domain isn't being blocked.
That is where I'd start. AOL actually helped me fix the problem, but it was years ago.
Good luck.
by mcpken
Seems to me that an SMTP connection to AOL.COM will not work since AOL uses proprietary email and news servers.
Can you forward outgoing mail to an ISP mail host or use DNS? How is your internet mail currently being delivered? DOes the error indicate that your server is an internet mail host and that you create an smtp conection directly with each INternet email mailhost destination? I think it does, but I'm no Exchange expert...
If all else fails and you can't get an answer, contact AOL, maybe there is an Exchange connector program so that their mail servers will work wtih Exchange...
Some things i've found:
Because AOL does not offer e-mail services to customers beyond its proprietary client, the SBSETRN and ETRN commands do not function with AOL software. To use the ETRN command, a local ISP is required
AOL does not support POP3 clients. AOL does support Simple Mail Transfer Protocol (SMTP) through its e-mail servers, but only for Winsock programs originating from theinternal proxy IP ad
by mcpken
by trurod70
by mcpken
by clpadmin
by mcpken
by insatiable
You didn't mention your system setups ie the version of Exchange Server and the OS, but it just sounds like you need to upgrade. I've never had this problem and didn't have to do anything special to sent or receive to AOL or any other ISP.
The person who answered #1 even indicated it was something they saw a long time ago -- possibly before new versions???
Good luck!!
by mcpken
I have had this problem before. It is frustrating, but then again so is AOhelL
Okay first all make sure you are on the current version and service pack, not that that is your problem but it will quite the people that think it is. Then try the suggestion in Answer number one, more than likley and this was the case for me, AOL is blocking/filtering your domain or your ISPs blobk of IP addreses. I was using Verio/Best at the time. I don't think that this problem is with your Exchange server but there is a way to test that, there is a tool out there that allows you to send relay mail through your ISPs (and your ISP only) mail servers. Complete the above and if AOL or you ISP won't help you find out your ISPs mail server addresses and send me an e-mail.
by mcpken
Thank you all who put in your input on this problem. Your suggestions helped me to find the solve the problem. I changed ISP from Cox Communications, which has horrible customer service and prices, to Telepacific. Thereby changing the IP of my mail server, and assureing that I had the DNS reverse mapping set up correctly. AOL accounts are now getting email consistantly.
THANK YOU
Ken
by tulsa
by mcpken
by mcrowley
by mcpken
by aekland
by mcpken
by steve cody
Here are some other SMTP servers that AOL has. You can specify that all mail destined for AOL.COM be forwarded to one of these servers. Try them until you find a working one for you.
152.163.224.33 through 152.163.224.37 and
152.163.224.65 through 152.163.224.69
This may not fix your problem, but it might help.
Steve
by mcpken
I would just like to add that I think that it was funny that the an AOL user is giving you advise on this question. Sorry, trurod70@aol.com, but couldn't you have used another username for this question.
LOL
ALSO:
Steve Cody, who is norammly pretty good, has given you more IP address to telnet and check out, do those too before you resort to using the e-mail tool I was talking about.
by mcpken
by davew
by mcpken
by corky132
by mcpken
by roka427
by mcpken
by resmith
Sounds like everything is working fine as far as sending mail to AOL. AOL has been known in the past as deleting incoming mail from "black listed" sources. AOL maintains a database of possible spam domains. If they receive mail from these, instead of sending a reject, they delete the mail. We have discussed this at several conferences where others have had this problem. Sometimes AOL misinterprets spam and blacklists the wrong source. I have no way of confirming this, but I would definitely contact AOL to find out if your domain is listed in any of their "lists".
Hope this helps.
by mcpken
by ian.campbell
First check the 'Administrator' mailbox on Exchange Server. Are there any messages in there that refer to rejections from AOL which may give clues as to why mail is not being delivered to the AOL recipient ?
You do not mention the size of the e-mail being sent. Some mail hosts limit the size of mails that can be recieved - Exchange server can be configured on both in-bound and out-bound to reject mails which exceed the sizes set. I believe AOL may have a 2Mb or 5Mb limit. I am not certain how this is calcualted, but when Exchange Server sends a mail with attachment the mail is UU or MIME coded which increases (~150%) the total size of the data being sent.
The log event indicating that a new SMTP connection has been made is in itselfnothing to be too concerned about (IMHO). I expect there will be similar items for other domains.
by mcpken
by loug
Can you send mail to other domains? If so there may be an issue with AOL. Do you have a reverse address record for your mail server? Some Mail servers will do a reverse address lookup to verify who is connecting and that the fully qualified host name matches the dns reverse address record. Your NT Server may be using a host name when connecting such as Exchange rather than exchange.domain.com.
HTH
Loug@designsystemsinc.com MCP
by mcpken
by dmiles
I am thinking that maybe a Inbox rule to foward email to an Internet account.The rule is not working.The ability to foward mail to an Internet account has been disabled on Exchange Server,or your Exhange Server was upgraded to 5.5
Exchange Server administrator has the ability to foward mail.
Remove the restriction to foward email to an Internet account.
by mcpken
by starkc
I had this problem once. Check you IMC (Internet Mail Connector) settings. Make sure all mail is using DNS for domain name resolution for ALL outbound e-mail. I have seen if you pint all mail to a specific host, they sometimes have filters on specific domain names.
Also, check you router. Make sure you don't have any access lists that are blocking this traffic.
Good Luck
by mcpken
by tony berni
by mcpken
by tony hogan
Add a reverse DNS lookup record to your DNS servers for your mail server.
The site which the message is destined for is possibly using reverse zone lookups for security purposes. The Fully Qualified Domain Name (FQDN) of the Exchange Server computer does not match its InterNic-registered IP address; hence, the telnet session to the destination mail server is refused.
From MS Article Q198981:
Certain mail servers require specific additional Domain Name Service (DNS) records before allowing mail transfer. A Reverse Zone record needs to be created on the DNS server responsible for the source mail server's e-mail domain.
You can look up the reverse routing on the following link (first find out the IP address for the Exchange Servercomputer):
http://network-tools.com/2/
Put the IP address in the text box, and click the DNS Records radio button. This will give the result for the reverse lookup.
-Adding reverse DNS record:
The DNS server requires a PTR record in its in-addr.arpa domain, wh
by mcpken
by s_pat_p
America Online (AOL) uses its own e-mail system which does not comply with the Internet standards supported by Outlook. For additional information about this limitation, click the article number below to view the article in the Microsoft Knowledge Base:
Q243336 OL2000: AOL E-mail Service Is Not Available for Outlook Users
by mcpken
by fred_e944
by mcpken
Your messages are akmost 99% likely being blocked AOL's extensive spam filters. Two main possibilities:
1. If your mail server is 'open relay' (www.orbs.org for info) then AOL will consider your domain's messages spam. Ip restricted servers sometimes still come up appearing to be open rel. However, I don't think this is the issue in this case, since you're on an Exchange server. To test, try telnetting to your SMTP port and spoofing a message command-line like explained in the first post on the thread. If you can get it to go, then you're open, and that's what's blocking you.
2. Assuming that's not the problem, and if the domain is the one in your email address, there's a definite issue with the name server association. (sechristind.com fails NSLOOKUP, only www.sechristind.com or mail.sechristind.com come up with name server info. AOL does the reverse lookup based on the domain.com part of the email address. Contact your service provider or domain registrant.) If I was right about the domain,
by mcpken
The mail delivery system is a connection based protocol (SMTP/POP). That means that before doing anything else the message sender needs to create a connection with destination system. In some cases (huge mail systems) have mail routers that disseminate the bulk of mail to different servers.
MS Exchange is a relay server (it needs a SMTP connection with DNS based SMTP server).
So, if AOL is your ISP (the SMTP connection is to your ISP usually) they may have another port for this mail-router so you should ask them about this.
If AOL is not your ISP then I don't see why you have that SMTP connection. Call your ISP and tell them your problem.
If you tried to use more than one Internet connections on Exchange that might cause some problems too.
Anyway the best way is to call you ISP and explain them your problem.
Luck.
by mcpken
by pschmied
Aol.com can receive internet (smtp) mail from any sender, if aol.com is not blocking your domain or particular users in your domain - unusual.
When your mail is sent out, it is going somewhere. If your mail server can't deliver the message to aol, or it's refused, it will generate an error message back to the recipient.
Have your Exchange admin or consultant crank up the level of error logging for the internet mta to maximum. Also configure the sending client to request delivery and read receipts. You should be able to track a particular message, and see exactly what's happening. In particular, after the SMTP connection is made, you should be able to see if the message was delivered. SMTP uses a "handshake" protocol for checking the receiving address, sending the message body, and sending the attachments.
If there is not indication that the mail is being rejected by the receiving post office or delivered (transferred), you should check to be sure that your Exchange serverhas the latest servi
by mcpken
by jmann46
by mcpken
by stemarie
AOL does what's called REVERSE domain identification.
The process is quite simple: it takes the IP of the computer that's attempting to send mail to it and does a reverse-DNS query to determine that it's really located within the domain that it claims to be. Because of spam and system overhead, AOL no longuer sends out warning messages that your sending mail system can't send mail to AOL.
the FIX:
You DNS database should have an entry for your domain name and also a reverse ARP file. The entries in this file are simply the IP addresses of all your public-ip network appliances and their names.
Therefore if i'm trying to determine what's 205.188.156.164 then the DNS tells me it's xxx.aol.com
Another possible problem:
Make sure that sechristind.com has an address, a most common problem it to put mail.domain.com and www.domain.com in the DNS, a common mistake is not to put domain.com itself. simply give domain.com the address of your e-mail server (or your webserver) and the problem will be fi
by mcpken
by ntnetmgr
Greetings!
Providing you haven't been blacklisted...
Using the Administrator program, check to see if there is alternate Routing information for AOL.COM Under Configuration | Site Addressing | Routing. Check type under SMTP
Did e-mail to AOL ever work? If so, you could have a filter in your Router.
Hope this helps! david
by mcpken
by mjervis
by mcpken
by hackz
by mcpken
by rws
I saw a number of good answers to your problem. What it boils down to is that your mail server is not identifying itself with the same DNS name as the reverse lookup of the IP address resolves to.
This is actually a fairly common problem with "tight" mail servers.
Be sure that the IP address that your mail server is using has a reverse DNS PTR record that matches the DNS name it uses.
by mcpken
by mcpken
by figment
The simplest way to fix this (while this isn't an answer, it's a way to get one) is to use a separate email carrier... i.e. Your personal ISP. and send an email to "postmaster@aol.com" tell them what your problem is and they should be able to help you to repair the problem.
Good luck and fair hunting...
Jeremy
by mcpken
by alphageek
Been there done that.
AOL is most likely rejecting your email due to header/DNS problems. AOL's servers do a lookup on the email server name that is passed in the mail header. When it does this it must find a DNS MX record for the server named inthe header.
Most likely your ISP has your MX record set for mail.yourdomain.com. Exchange however passes ntservername.yourdomain.com in the headers.
For example server was named exchange01. Exchange will put exchange01.yourdomain.com in the header. AOL does a lookup for that server name and comes up empty becuase there is no DNS listing for it.
Easy fix? Sure thing! Just open up your network properties and in the DNS tab change the host name to mail or whatever your ISP has set for your MX record. When you do this NT will whine that it doesn't match the actual NT server name. So what. Not a big deal. But now exchange will pass mail.yourdomain.com in the headers.
The above works fine for Exchange 5.5 SP3. Any other version I can't attest for it to
by mcpken
by tony k
I've seen this many times before, and it's got nothing to do with your Exchange server.
This usually occurs in August/September during AOL's push for new membership, but it does happen to some limited degree in June when the kids are just out of school.
It's a simple case of AOL's servers being unable to handle the load. I've tried telneting into their mail servers and it's taken up to 2 minutes for a response. Most servers will stop trying to send well before that.
The only solution I ever found was to create a canned email to send to my users reminding them that it was "AOL push" time and they may not be able to send mail there. Usually around the end of September beginning of October it goes back to normal.
It did have one positive side-effect, though...all the users on my network who were AOLosers dropped that crappy service! :)
by mcpken
by slora
From the SLMail FAQ:
(begin quote)
Sending mail to America Online (AOL.COM) is currently very difficult. The problem is two-fold:
1. AOL's MX records (where mail servers should send mail to) are pointing to CNAMEs in violation of RFC1123 (5.2.2).
2. Although AOL lists nearly a dozen mail servers (MX records), only one responds at any given time. Worse, that server 'moves' (changes IP address) every 4 hours.
(end quote)
This indicates that you will need to do an MX Lookup and programmatically verify which server is active if you want to send mail directly to AOL's MX server.
by mcpken
by slora
Another strong possibility:
If your site fails a reverse NS Lookup, AOL will refuse your mail. See
"http://www.graphicpower.com/techarticles/mailsvr.stm"
for a good description of the problem and the solution. The relevant information starts about halfway through the page.
Hope this is useful.
by mcpken
by boneil
by mcpken
by mcpken
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending