SMTP problem to Yahoo and AOL

Discussion regarding the Standard version.
Post Reply
jess
Posts: 4
Joined: Sun Aug 29, 2004 2:39 am

SMTP problem to Yahoo and AOL

Post by jess »

Ok, so I switch ISP's from time warner to this crappy little company called Grande. I still have a static IP but all of a sudden, now I can't send to Yahoo or AOL. ARIN doesn't say it's dynamic so what might be going wrong? Arin says:

Code: Select all

Search results for: 216.188.250.*** 

Grande Communications Networks, Inc. GRANDECOM-02 (NET-216-188-224-0-1)
                                  216.188.224.0 - 216.188.255.255
Grande Communications AUSTIN GRANDECOM-MARKET02 (NET-216-188-250-0-1)
                                  216.188.250.0 - 216.188.253.255

# ARIN WHOIS database, last updated 2004-09-07 19:10
# Enter ? for additional hints on searching ARIN's WHOIS database.
reverse DNS says:

Code: Select all

216-188-250-***.dyn.grandenetworks.net 
(Even though I have a static IP)

ME says:

Code: Select all

MailEnable: Message delivery has been delayed.

Message is waiting at mydomain.com for delivery to mx4.mail.yahoo.com.

Reason: Mail Server for yahoo.com could not be contacted at this time. MailEnable will keep trying to deliver this message and will notify you of any progress.
it did work for a couple of days after I updated the DNS in ME and updated from 1.73 to 1.8 but now has stopped again. I'm using a netopia 3386 router with port 110 and 25 UDP and TCP open both ways. Suggestions anyone?

bill

same problem

Post by bill »

I was using MailEnable successfully with Grande in Austin for quite some time, but now, I am experiencing the same problem you are describing. I can't figure it out. Something had to change. I cannot send or receive emails outside of my domain.

jess
Posts: 4
Joined: Sun Aug 29, 2004 2:39 am

Post by jess »

got dns changed to 216-188-250-***.ip.grandenetworks.net now can't send OR recieve. HELP!

jess
Posts: 4
Joined: Sun Aug 29, 2004 2:39 am

Post by jess »

Ok. the DNS change helped. Had to have them take the stupid port 25 filter off again because they put it back on when they changed the reverse DNS. Try this and is should work for you.

Post Reply