Ubuntu
sendmail package

No route to host sendmail

Asked by Robert Johnson

I've had this problem in the past, but have always been able to resolve...

I installed the Ubuntu updates my mail server on the 18th... Email stopped getting sent... No route to host...

I can telnet to port 25

I can receive email "i know pop server"

Traceroute looks ok at first... Then traceroute -T -p 25 host "stops in about 4 hops with a !X"

Mail inside works fine... Web server uses the email server and sent me a message this morning...

I know this is a common problem and most of the time it is easy fixes... I've been doing this for a long time... This one has me stumped...

I think it might be a qwest filter and was just a fluke I seen it after the updates... But I need to be sure before I call them...

Thanks!

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu sendmail Edit question
Assignee:
No assignee Edit question
Solved by:
Robert Johnson
Solved:
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#1

When you have issues are you outside of the network of which the server you are trying to emai from is connected (That is awkward grammar but couldn't word it better)?

when you say 'host' is that a name or an IP?

Revision history for this message
Robert Johnson (wo-ai-xiao-yu) said : 		#2

no I'm on the network when sending mail...
Host is server that should be getting the mail...

Grasping at straws because everything else worked fine but needed to check...
First thought maybe my resolve.conf files got changed... But no...
Then I thought maybe my internal DNS server had problems... But no...

I even set-up sendmail on a different server and changed the NAT to point to it... Same issue, however then I realized it had the same update installed.

So on the machine in question I installed postfix just--crossing fingers... No change still no route to host... I'm really sure it has to do with port 25... just not sure where to look... 25 is open on the machine in question...

Revision history for this message
Robert Johnson (wo-ai-xiao-yu) said : 		#3

Just as I thought... It was Qwest! They removed the filter...
Why would they block a static IPs mail without saying anything?
Wow! If I didn't have a backup plan with Gmail... Maybe it's time to rethink Qwest as an ISP...