no route to host

classic Classic list List threaded Threaded
44 messages Options
123
Reply | Threaded
Open this post in threaded view
|

no route to host

Engin qwert
Hello again. About one month later I decided to make a clean Debian 6 install. This time I did'nt do much modification to the system. Only installed OS and ehcp control panel.

But the new installation suffers the same problem, I cannot send mail ( no route to host error). Before clean install I can send mail connectiong to the server with a client machine using Icedove. From now on I cannot send from local server nor relaying from outside clients. 

The  ISP still claims they are not blocking any port.  Any help would be apprecriated. Thanks :)
   
Reply | Threaded
Open this post in threaded view
|

Re: no route to host

Reindl Harald-2


Am 29.07.2012 22:32, schrieb Engin qwert:
> Hello again. About one month later I decided to make a clean Debian 6 install. This time I did'nt do much
> modification to the system. Only installed OS and ehcp control panel.
>
> But the new installation suffers the same problem, I cannot send mail ( no route to host error). Before clean
> install I can send mail connectiong to the server with a client machine using Icedove. From now on I cannot send
> from local server nor relaying from outside clients.
>
> The  ISP still claims they are not blocking any port.  Any help would be apprecriated. Thanks :)

you have to provide a FULL log of a specific message and
output of "postconf -n" - our crystal bill is broken


signature.asc (270 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: no route to host

Benny Pedersen
In reply to this post by Engin qwert
Den 2012-07-29 22:32, Engin qwert skrev:

> The ISP still claims they are not blocking any port. Any help would
> be
> apprecriated. Thanks :)

show postconf -n to resolve this problem if you belive postfix users
care of no spam to maillist with no route to host :=)

you already reinstalled debian, why not try windows 7 ?

you did not post relevant info, thats why i keep the fun going



Reply | Threaded
Open this post in threaded view
|

RE: no route to host

Engin qwert
In reply to this post by Reindl Harald-2
Hey, :) I am sorry not sending the output message in advance. Should I also send all my configuration files regarding to networking such as /etc/networking/interfaces?

I also tested my ip address from canyouseeme.org and the test result is "Your ISP is not blocking your port 25", this  information may also provide a clue although I don't have any problem getting mails from outside.
---------------------------------------------------
root@xn--hadibakalm-5ub:~# postconf -n
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
append_dot_mydomain = no
biff = no
broken_sasl_auth_clients = yes
config_directory = /etc/postfix
debug_peer_level = 1
debug_peer_list = 
html_directory = /usr/share/doc/postfix/html
inet_interfaces = all
mailbox_command = procmail -a "$EXTENSION"
mailbox_size_limit = 0
mydestination = localhost, 31.44.198.247
myhostname = xn--hadibakalm-5ub
mynetworks = 127.0.0.0/8, 192.168.0.0/16, 172.16.0.0/16, 10.0.0.0/8,  31.44.198.0/24
myorigin = xn--hadibakalm-5ub.com
proxy_read_maps = $local_recipient_maps $mydestination $virtual_alias_maps $virtual_alias_domains $virtual_mailbox_maps $virtual_mailbox_domains $relay_recipient_maps $canonical_maps $sender_canonical_maps $recipient_canonical_maps $relocated_maps $mynetworks $virtual_mailbox_limit_maps $transport_maps
readme_directory = /usr/share/doc/postfix
recipient_delimiter = +
relayhost = 
sender_canonical_maps = 
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
smtp_use_tls = yes
smtpd_banner = $myhostname ESMTP $mail_name powered by Easy Hosting Control Panel (ehcp) on Ubuntu, www.ehcp.net
smtpd_recipient_restrictions = permit_mynetworks,permit_sasl_authenticated,check_client_access hash:/var/lib/pop-before-smtp/hosts,reject_unauth_destination
smtpd_sasl_auth_enable = yes
smtpd_sasl_security_options = noanonymous
smtpd_tls_CAfile = /etc/postfix/cacert.pem
smtpd_tls_auth_only = no
smtpd_tls_cert_file = /etc/postfix/smtpd.cert
smtpd_tls_key_file = /etc/postfix/smtpd.key
smtpd_tls_loglevel = 1
smtpd_tls_received_header = yes
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtpd_tls_session_cache_timeout = 3600s
smtpd_use_tls = yes
tls_random_source = dev:/dev/urandom
transport_maps = proxy:mysql:/etc/postfix/mysql-virtual_transports.cf
virtual_alias_domains = 
virtual_alias_maps = proxy:mysql:/etc/postfix/mysql-virtual_forwardings.cf, proxy:mysql:/etc/postfix/mysql-virtual_email2email.cf
virtual_gid_maps = static:5000
virtual_mailbox_base = /home/vmail
virtual_mailbox_domains = proxy:mysql:/etc/postfix/mysql-virtual_domains.cf
virtual_mailbox_maps = proxy:mysql:/etc/postfix/mysql-virtual_mailboxes.cf
virtual_uid_maps = static:5000
---------------------------------------------------

> Date: Sun, 29 Jul 2012 22:53:25 +0200

> From: [hidden email]
> To: [hidden email]
> Subject: Re: no route to host



> Am 29.07.2012 22:32, schrieb Engin qwert:
> > Hello again. About one month later I decided to make a clean Debian 6 install. This time I did'nt do much
> > modification to the system. Only installed OS and ehcp control panel.
> > 
> > But the new installation suffers the same problem, I cannot send mail ( no route to host error). Before clean
> > install I can send mail connectiong to the server with a client machine using Icedove. From now on I cannot send
> > from local server nor relaying from outside clients. 
> > 
> > The ISP still claims they are not blocking any port. Any help would be apprecriated. Thanks :)

> you have to provide a FULL log of a specific message and
> output of "postconf -n" - our crystal bill is broken
Reply | Threaded
Open this post in threaded view
|

Re: no route to host

Michael J Wise
In reply to this post by Engin qwert

On Jul 29, 2012, at 1:32 PM, Engin qwert wrote:

> But the new installation suffers the same problem, I cannot send mail ( no route to host error).

That means … that the server is attempting to get to a host IP address that doesn't exist.
Somehow, I suspect this isn't as such a Postfix problem.

> The  ISP still claims they are not blocking any port.

If they were blocking ports, it would be a time-out.
There's no way to connect to the destination, it would seem, let alone an arbitrary port.

I suspect either your router config, or a typo in what you think is your local network.

But without a lot more details than just postconf, like … what is the IP address of your mail server … this will be a bit of a poser.

Aloha,
Michael.
--
"Please have your Internet License            
 and Usenet Registration handy..."

Reply | Threaded
Open this post in threaded view
|

RE: no route to host

Engin qwert
Hello, sorry for sending too  many information which may be irrelevant but I want to post anything I think it causes the problem.

-------------------------------------------------------------
Hostname: xn--hadibakalm-5ub.com
The Static IP, that ISP provided me is : 31.44.198.247.
The internal IP address of the Server PC: 10.138.9.201
Netmask: 255.255.255.0
The gateway: 10.138.9.254
-------------------------------------------------------------


nano /etc/network/interfaces
-------------------------------------------------------------
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

auto eth0
# The primary network interface
allow-hotplug eth0
#NetworkManager#iface eth0 inet dhcp
iface eth0 inet static
address 10.138.9.201
netmask 255.255.255.0
gateway 10.138.9.254
-------------------------------------------------------------


root@xn--hadibakalm-5ub:~# iptables -L
-------------------------------------------------------------
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
-------------------------------------------------------------


root@xn--hadibakalm-5ub:~# tail /var/log/mail.err 
-------------------------------------------------------------
Jul 29 20:47:33 xn--hadibakalm-5ub postfix/trivial-rewrite[3818]: fatal: proxy:mysql:/etc/postfix/mysql-virtual_domains.cf(0,lock|fold_fix): table lookup problem
Jul 29 20:48:34 xn--hadibakalm-5ub postfix/trivial-rewrite[4571]: fatal: proxy:mysql:/etc/postfix/mysql-virtual_domains.cf(0,lock|fold_fix): table lookup problem
Jul 29 20:49:35 xn--hadibakalm-5ub postfix/trivial-rewrite[4788]: fatal: proxy:mysql:/etc/postfix/mysql-virtual_domains.cf(0,lock|fold_fix): table lookup problem
Jul 29 20:50:36 xn--hadibakalm-5ub postfix/trivial-rewrite[4973]: fatal: proxy:mysql:/etc/postfix/mysql-virtual_domains.cf(0,lock|fold_fix): table lookup problem
Jul 29 20:51:37 xn--hadibakalm-5ub postfix/trivial-rewrite[5155]: fatal: proxy:mysql:/etc/postfix/mysql-virtual_domains.cf(0,lock|fold_fix): table lookup problem
Jul 29 20:52:38 xn--hadibakalm-5ub postfix/trivial-rewrite[5340]: fatal: proxy:mysql:/etc/postfix/mysql-virtual_domains.cf(0,lock|fold_fix): table lookup problem
Jul 29 20:53:39 xn--hadibakalm-5ub postfix/trivial-rewrite[5525]: fatal: proxy:mysql:/etc/postfix/mysql-virtual_domains.cf(0,lock|fold_fix): table lookup problem
Jul 29 20:54:40 xn--hadibakalm-5ub postfix/trivial-rewrite[5712]: fatal: proxy:mysql:/etc/postfix/mysql-virtual_domains.cf(0,lock|fold_fix): table lookup problem
Jul 29 20:55:41 xn--hadibakalm-5ub postfix/trivial-rewrite[5925]: fatal: proxy:mysql:/etc/postfix/mysql-virtual_domains.cf(0,lock|fold_fix): table lookup problem
Jul 29 22:34:12 xn--hadibakalm-5ub postfix/master[3131]: fatal: /etc/postfix/master.cf: line 23: field "unprivileged": bad value: "???"
-------------------------------------------------------------


root@xn--hadibakalm-5ub:~# tail /var/log/mail.warn 
-------------------------------------------------------------
Jul 29 20:55:41 xn--hadibakalm-5ub postfix/proxymap[2091]: warning: connect to mysql server localhost: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
Jul 29 20:55:41 xn--hadibakalm-5ub postfix/proxymap[2091]: warning: connect to mysql server localhost: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
Jul 29 20:55:41 xn--hadibakalm-5ub postfix/trivial-rewrite[5925]: fatal: proxy:mysql:/etc/postfix/mysql-virtual_domains.cf(0,lock|fold_fix): table lookup problem
Jul 29 20:55:42 xn--hadibakalm-5ub postfix/qmgr[2075]: warning: problem talking to service rewrite: Interrupted system call
Jul 29 20:55:42 xn--hadibakalm-5ub postfix/cleanup[2082]: warning: problem talking to service rewrite: Connection reset by peer
Jul 29 20:55:42 xn--hadibakalm-5ub postfix/master[2064]: warning: process /usr/lib/postfix/trivial-rewrite pid 5925 exit status 1
Jul 29 20:55:42 xn--hadibakalm-5ub postfix/master[2064]: warning: /usr/lib/postfix/trivial-rewrite: bad command startup -- throttling
Jul 29 21:28:51 xn--hadibakalm-5ub postfix/smtpd[6954]: warning: 64.20.227.133: address not listed for hostname recover.mxtoolbox.com
Jul 29 21:55:56 xn--hadibakalm-5ub postfix/smtpd[7612]: warning: TLS library problem: 7612:error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca:s3_pkt.c:1102:SSL alert number 48:
Jul 29 22:34:12 xn--hadibakalm-5ub postfix/master[3131]: fatal: /etc/postfix/master.cf: line 23: field "unprivileged": bad value: "???"
-------------------------------------------------------------


root@xn--hadibakalm-5ub:~# tail /var/log/mail.log
-------------------------------------------------------------
Jul 30 00:53:59 xn--hadibakalm-5ub postfix/smtp[3075]: connect to mx2.hotmail.com[65.55.37.120]:25: No route to host
Jul 30 00:54:02 xn--hadibakalm-5ub postfix/smtp[3075]: connect to mx4.hotmail.com[65.55.37.88]:25: No route to host
Jul 30 00:54:02 xn--hadibakalm-5ub postfix/smtp[3075]: D8FD5189887C: to=<[hidden email]>, relay=none, delay=10655, delays=10627/0.04/28/0, dsn=4.4.1, status=deferred (connect to mx4.hotmail.com[65.55.37.88]:25: No route to host)
Jul 30 00:58:33 xn--hadibakalm-5ub postfix/qmgr[1852]: 87AE71898884: from=<[hidden email]>, size=744, nrcpt=1 (queue active)
Jul 30 00:58:34 xn--hadibakalm-5ub postfix/smtp[3082]: connect to mx2.hotmail.com[65.55.92.136]:25: No route to host
Jul 30 00:58:37 xn--hadibakalm-5ub postfix/smtp[3082]: connect to mx3.hotmail.com[65.55.92.136]:25: No route to host
Jul 30 00:58:40 xn--hadibakalm-5ub postfix/smtp[3082]: connect to mx4.hotmail.com[65.54.188.72]:25: No route to host
Jul 30 00:58:43 xn--hadibakalm-5ub postfix/smtp[3082]: connect to mx3.hotmail.com[65.55.37.88]:25: No route to host
Jul 30 00:58:46 xn--hadibakalm-5ub postfix/smtp[3082]: connect to mx4.hotmail.com[65.55.92.168]:25: No route to host
Jul 30 00:58:46 xn--hadibakalm-5ub postfix/smtp[3082]: 87AE71898884: to=<[hidden email]>, relay=none, delay=6920, delays=6907/0.04/13/0, dsn=4.4.1, status=deferred (connect to mx4.hotmail.com[65.55.92.168]:25: No route to host)
-------------------------------------------------------------

> Subject: Re: no route to host

> From: [hidden email]
> Date: Sun, 29 Jul 2012 14:43:19 -0700
> To: [hidden email]
>
>
> On Jul 29, 2012, at 1:32 PM, Engin qwert wrote:
>
> > But the new installation suffers the same problem, I cannot send mail ( no route to host error).
>
> That means … that the server is attempting to get to a host IP address that doesn't exist.
> Somehow, I suspect this isn't as such a Postfix problem.
>
> > The ISP still claims they are not blocking any port.
>
> If they were blocking ports, it would be a time-out.
> There's no way to connect to the destination, it would seem, let alone an arbitrary port.
>
> I suspect either your router config, or a typo in what you think is your local network.
>
> But without a lot more details than just postconf, like … what is the IP address of your mail server … this will be a bit of a poser.
>
> Aloha,
> Michael.
> --
> "Please have your Internet License
> and Usenet Registration handy..."
>
Reply | Threaded
Open this post in threaded view
|

Re: no route to host

Michael J Wise

On Jul 29, 2012, at 3:03 PM, Engin qwert wrote:

> Hello, sorry for sending too  many information which may be irrelevant but I want to post anything I think it causes the problem.

220 xn--hadibakalm-5ub ESMTP Postfix powered by Easy Hosting Control Panel (ehcp) on Ubuntu, www.ehcp.net

Well, it does appear to be reachable from the outside world, so THAT's good….

Aloha,
Michael.
--
"Please have your Internet License            
 and Usenet Registration handy..."

Reply | Threaded
Open this post in threaded view
|

Re: no route to host

Wietse Venema
Michael J Wise:
>
> On Jul 29, 2012, at 3:03 PM, Engin qwert wrote:
>
> > Hello, sorry for sending too  many information which may be irrelevant but I want to post anything I think it causes the problem.
>
> 220 xn--hadibakalm-5ub ESMTP Postfix powered by Easy Hosting Control Panel (ehcp) on Ubuntu, www.ehcp.net
>
> Well, it does appear to be reachable from the outside world, so THAT's good?.

Confirmed. Inbound SMTP connectivity appears to work.  You may need
a network sniffer to find out why outbound SMTP fails.

        Wietse
Reply | Threaded
Open this post in threaded view
|

RE: no route to host

Engin qwert
In reply to this post by Michael J Wise
Yes,  I can receive mails :) I also want to add an additional information that. "On the server machine I can reach the internet. (web browsing, can ping hotmail etc.)"

> Subject: Re: no route to host

> From: [hidden email]
> Date: Sun, 29 Jul 2012 15:08:25 -0700
> To: [hidden email]
>
>
> On Jul 29, 2012, at 3:03 PM, Engin qwert wrote:
>
> > Hello, sorry for sending too many information which may be irrelevant but I want to post anything I think it causes the problem.
>
> 220 xn--hadibakalm-5ub ESMTP Postfix powered by Easy Hosting Control Panel (ehcp) on Ubuntu, www.ehcp.net
>
> Well, it does appear to be reachable from the outside world, so THAT's good….
>
> Aloha,
> Michael.
> --
> "Please have your Internet License
> and Usenet Registration handy..."
>
Reply | Threaded
Open this post in threaded view
|

Re: no route to host

Michael J Wise
In reply to this post by Engin qwert

On Jul 29, 2012, at 2:13 PM, Engin qwert wrote:

> transport_maps = proxy:mysql:/etc/postfix/mysql-virtual_transports.cf

… any from other logs, yer MySQL is pooched in some way.

I think I see the problem.
I have no idea how to fix it, sorry.

Aloha,
Michael.
--
"Please have your Internet License            
 and Usenet Registration handy..."

Reply | Threaded
Open this post in threaded view
|

Re: no route to host

Wietse Venema
In reply to this post by Engin qwert
Engin qwert:
> Yes,  I can receive mails :) I also want to add an additional information that. "On the server machine I can reach the internet. (web browsing, can ping hotmail etc.)"
>

What happens when you type this command on the server with the problem:

    telnet 168.100.189.2 25

That's my SMTP server.

(if telnet does not exist, try: nc 168.100.189.2 25).

        Wietse
Reply | Threaded
Open this post in threaded view
|

RE: no route to host

Engin qwert
In reply to this post by Wietse Venema
The nmap program outputs the result below.


root@xn--hadibakalm-5ub:~# nmap -p 25 hotmail.com
-------------------------------------------
Starting Nmap 5.00 ( http://nmap.org ) at 2012-07-30 01:27 EEST
Warning: Hostname hotmail.com resolves to 4 IPs. Using 65.55.72.183.
Interesting ports on origin.sn134w.snt134.mail.live.com (65.55.72.183):
PORT   STATE    SERVICE
25/tcp filtered smtp

Nmap done: 1 IP address (1 host up) scanned in 0.97 seconds
-------------------------------------------

> Subject: Re: no route to host

> To: [hidden email]
> Date: Sun, 29 Jul 2012 18:20:04 -0400
> From: [hidden email]
>
> Michael J Wise:
> >
> > On Jul 29, 2012, at 3:03 PM, Engin qwert wrote:
> >
> > > Hello, sorry for sending too many information which may be irrelevant but I want to post anything I think it causes the problem.
> >
> > 220 xn--hadibakalm-5ub ESMTP Postfix powered by Easy Hosting Control Panel (ehcp) on Ubuntu, www.ehcp.net
> >
> > Well, it does appear to be reachable from the outside world, so THAT's good?.
>
> Confirmed. Inbound SMTP connectivity appears to work. You may need
> a network sniffer to find out why outbound SMTP fails.
>
> Wietse
Reply | Threaded
Open this post in threaded view
|

RE: no route to host

Engin qwert
In reply to this post by Wietse Venema
root@xn--hadibakalm-5ub:~# telnet 168.100.189.2 25
Trying 168.100.189.2...
telnet: Unable to connect to remote host: No route to host


> Subject: Re: no route to host

> To: [hidden email]
> Date: Sun, 29 Jul 2012 18:30:20 -0400
> From: [hidden email]

> Engin qwert:
> > Yes, I can receive mails :) I also want to add an additional information that. "On the server machine I can reach the internet. (web browsing, can ping hotmail etc.)"
> > 

> What happens when you type this command on the server with the problem:

> telnet 168.100.189.2 25

> That's my SMTP server.

> (if telnet does not exist, try: nc 168.100.189.2 25).

> Wietse
> Subject: Re: no route to host

> To: [hidden email]
> Date: Sun, 29 Jul 2012 18:30:20 -0400
> From: [hidden email]
>
> Engin qwert:
> > Yes, I can receive mails :) I also want to add an additional information that. "On the server machine I can reach the internet. (web browsing, can ping hotmail etc.)"
> >
>
> What happens when you type this command on the server with the problem:
>
> telnet 168.100.189.2 25
>
> That's my SMTP server.
>
> (if telnet does not exist, try: nc 168.100.189.2 25).
>
> Wietse
Reply | Threaded
Open this post in threaded view
|

RE: no route to host

Engin qwert
In reply to this post by Michael J Wise
If the problem cannot resolved I will re run the echp script. It may solve the mysql problem.

> Subject: Re: no route to host

> From: [hidden email]
> Date: Sun, 29 Jul 2012 15:25:27 -0700
> To: [hidden email]
>
>
> On Jul 29, 2012, at 2:13 PM, Engin qwert wrote:
>
> > transport_maps = proxy:mysql:/etc/postfix/mysql-virtual_transports.cf
>
> … any from other logs, yer MySQL is pooched in some way.
>
> I think I see the problem.
> I have no idea how to fix it, sorry.
>
> Aloha,
> Michael.
> --
> "Please have your Internet License
> and Usenet Registration handy..."
>
Reply | Threaded
Open this post in threaded view
|

Re: no route to host

Wietse Venema
In reply to this post by Engin qwert
Engin qwert:
> root@xn--hadibakalm-5ub:~# telnet 168.100.189.2 25Trying 168.100.189.2...telnet: Unable to connect to remote host: No route to host

Then your ISP is blocking your outbound SMTP connections.

I was able to connect to your server's SMTP port from 168.100.189.2
(you should see that in your maillog file).


        Wietse
Reply | Threaded
Open this post in threaded view
|

Re: no route to host

Reindl Harald-2


Am 30.07.2012 01:29, schrieb Wietse Venema:
> Engin qwert:
>> root@xn--hadibakalm-5ub:~# telnet 168.100.189.2 25Trying 168.100.189.2...telnet: Unable to connect to remote host: No route to host
>
> Then your ISP is blocking your outbound SMTP connections.

as said a month ago

-------- Original-Nachricht --------
Betreff: Re: "no route to host"  error message
Datum: Fri, 13 Jul 2012 16:58:06 +0200
Von: Reindl Harald <[hidden email]>
Organisation: the lounge interactive design
An: [hidden email]

BOAH DO NOT SWITCH TO TOP-POSTING

Am 13.07.2012 16:33, schrieb Engin qwert:

> --------------
>> Date: Fri, 13 Jul 2012 16:25:54 +0200
>> From: [hidden email]
>> To: [hidden email]
>> Subject: Re: "no route to host" error message
>>
>>
>>
>> Am 13.07.2012 16:20, schrieb Engin qwert:
>> > Hello and sorry for asking again.
>> >
>> > I telnet'ted the hotmail.com from both port 25 and port 587 when I telnet directly from server or any other
>> > location in Istanbul
>> > ----------
>> > engin@xn--hadibakalm-5ub:~$ telnet hotmail.com 25
>> > Trying 65.55.72.183...
>> > Trying 65.55.72.135...
>> > Trying 65.55.72.151...
>> > Trying 65.55.72.167...
>> > telnet: Unable to connect to remote host: No route to host
>>
>> contact your ISP after made sure you are not
>> blocking something via iptables your own
>>
>> this is simply a firewall-rejecting
>>
>> "-j REJECT --reject-with icmp-host-unreachable" will exactly
>> trigger this repsones regardless if it is done outgoing
>> in your firewall or somewehere in the network
>> ___________________
>>
>> http://www.linuxtopia.org/Linux_Firewall_iptables/x4550.html
>>
>> The following reject types are currently valid:
>> icmp-net-unreachable
>> icmp-host-unreachable
>> icmp-port-unreachable
>> icmp-proto-unreachable
>> icmp-net-prohibited
>> icmp-host-prohibited.
>>
>> The default error message is to send a port-unreachable to the host

> Sorry for asking everything but I want to make sure there isn't any rejection. I run the  command you told me.
> To my weak understanding ther is no restrictions at all in the iptables isn't it?
> --------------
> root@xn--hadibakalm-5ub:~# iptables -L -n
> Chain INPUT (policy ACCEPT)
> target     prot opt source               destination
>
> Chain FORWARD (policy ACCEPT)
> target     prot opt source               destination
>
> Chain OUTPUT (policy ACCEPT)
> target     prot opt source               destination

no, so call your ISP and scream loud in the phone


signature.asc (270 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

RE: no route to host

Engin qwert
In reply to this post by Wietse Venema
Thank you all clarifiyng that my ISP is blocking port 25. This way I can insist that they are blocking port 25. Due to my weak knowledge  I had to accept what they claimed that it is not blocked. 

> Subject: Re: no route to host

> To: [hidden email]
> Date: Sun, 29 Jul 2012 19:29:10 -0400
> From: [hidden email]
>
> Engin qwert:
> > root@xn--hadibakalm-5ub:~# telnet 168.100.189.2 25Trying 168.100.189.2...telnet: Unable to connect to remote host: No route to host
>
> Then your ISP is blocking your outbound SMTP connections.
>
> I was able to connect to your server's SMTP port from 168.100.189.2
> (you should see that in your maillog file).
>
>
> Wietse
Reply | Threaded
Open this post in threaded view
|

Re: no route to host

Reindl Harald-2
before you insist make sure that you are allowed to
run a server and that your NAT-gateway is not broken

> The internal IP address of the Server PC: 10.138.9.201

says there is a NAT-router in front of your box


Am 30.07.2012 01:36, schrieb Engin qwert:

> Thank you all clarifiyng that my ISP is blocking port 25. This way I can insist that they are blocking port 25. Due
> to my weak knowledge  I had to accept what they claimed that it is not blocked.
>
>> Subject: Re: no route to host
>> To: [hidden email]
>> Date: Sun, 29 Jul 2012 19:29:10 -0400
>> From: [hidden email]
>>
>> Engin qwert:
>> > root@xn--hadibakalm-5ub:~# telnet 168.100.189.2 25Trying 168.100.189.2...telnet: Unable to connect to remote
> host: No route to host
>>
>> Then your ISP is blocking your outbound SMTP connections.
>>
>> I was able to connect to your server's SMTP port from 168.100.189.2
>> (you should see that in your maillog file).


signature.asc (270 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: no route to host

Wietse Venema
Reindl Harald:
> before you insist make sure that you are allowed to
> run a server and that your NAT-gateway is not broken
>
> > The internal IP address of the Server PC: 10.138.9.201
>
> says there is a NAT-router in front of your box

Reindl has a good point. If the NAT router maps only inbound traffic,
then you'd also have the result that we see.

        Wietse
Reply | Threaded
Open this post in threaded view
|

RE: no route to host

Engin qwert
In reply to this post by Reindl Harald-2
>

> as said a month ago
>
> -------- Original-Nachricht --------
> Betreff: Re: "no route to host" error message
> Datum: Fri, 13 Jul 2012 16:58:06 +0200
> Von: Reindl Harald <[hidden email]>
> Organisation: the lounge interactive design
> An: [hidden email]
>
> BOAH DO NOT SWITCH TO TOP-POSTING
>

Sorry for top postings again but the hotmail posting screen automatically puts the cursor to top so that I missed the warning I was made against top posting.  This make me forget and repeat the same wrong postings again.

I think my ISP won't care my situation. Changing it may be better.

But now I 've left with configuration that even cannot send mail even outside the network :(
123