Steve Ingraham wrote: > > I want to thank Jake, Andrew, George, Eric, Loren, Jimmy and anyone > else who has sent information to help me with my email problems the > last couple of days. Despite all of your good advice our domain is > still having email problems. I am not exactly sure what the root of > the problem is exactly. > > I received an email to [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]> that appears to have only gone to > that account so Jake may be the only one reading this aware of his > comments. In it he states that he was unable to connect to remote host > when he digs our MX okcca.net. I have included the contents of his > message here: > > Jake Vickers wrote: > > Hey Steve. I've been in those shoes before.... To get email working, > for now take out all of your SA rules. Then run spamassassin -D --lint > to parse everything and make sure all is okay. > I am trying to do as much trouble shooting without actually logging > into your machine as I can from here. Here is my first problem.... > Your DNS is wrong, or you have a network problem somewhere: > <snip> > > > [EMAIL PROTECTED] ~]# telnet 204.87.111.225 > Trying 204.87.111.225... > telnet: connect to address 204.87.111.225: No route to host > telnet: Unable to connect to remote host: No route to host > > > As you can see, I cannot get to your IP address at all. > > As Jake suggested, I moved everything except local.cf and init.pre out > of /etc/mail/spamassassin and ran spamassassin –D –lint. I am not sure > what I am looking for in the returns from this action. > Stop looking at your spamassassin configuration. Stop looking at your email configuration. Start looking at routers and firewalls.
The "no route to host" can only be caused by a router or firewall somewhere in the path from Jake's machine to 204.87.111.225. Possibly even a router on Jake's end. First, I'd have Jake try his telnet again, but this time use port 25 to connect to: (note the extra 25 on the end) telnet 204.87.111.225 25 *I* can do this just fine. I get back: 220 dellapp02.occa.state.ok.us ESMTP Jake should to. If he can't, the problem isn't in your network, it is in his.
