Sandy Drobic wrote:
I'd rather like to know what happens if you enter the command telnet mx2.epicuria.be 25 in your console. As I wrote you should be able to see the lines I mentioned.
Sandy
Here's what i get : telnet mx2.epicuria.be 25 Trying 204.200.196.67... telnet: connect to address 204.200.196.67: Connection timed out -- Laurent Renard
Laurent wrote regarding 'Re: [SLE] Postfix error' on Fri, Jan 21 at 11:03:
Sandy Drobic wrote:
I'd rather like to know what happens if you enter the command telnet mx2.epicuria.be 25 in your console. As I wrote you should be able to see the lines I mentioned.
Sandy
Here's what i get : telnet mx2.epicuria.be 25 Trying 204.200.196.67... telnet: connect to address 204.200.196.67: Connection timed out
There's your problem - DNS works, but the connection's dropped. Blame your ISP. You probably just need to set your smart_relay to point at your ISP's smtp host, rather than letting your machine directly deliver itself. --Danny
Danny Sauer wrote:
Here's what i get : telnet mx2.epicuria.be 25 Trying 204.200.196.67... telnet: connect to address 204.200.196.67: Connection timed out
There's your problem - DNS works, but the connection's dropped. Blame your ISP.
You probably just need to set your smart_relay to point at your ISP's smtp host, rather than letting your machine directly deliver itself.
It is indeed possible that the ISP has enforced a policy to allow smtp client connections only to his own mail server. That is the reason I asked you to connect via telnet to port 110 (pop3) as well. That should work in any case because you have to be able to get your mail via pop from any server you might need. In that case you need to set the parameter relayhost = [mail server of isp] in /etc/postfix/main.cf. Alternatively you could use another ISP to connect to the internet. (^-^) Sandy
Fri, 21 Jan 2005, by suse-linux-e.suselists@danny.teleologic.net:
Laurent wrote regarding 'Re: [SLE] Postfix error' on Fri, Jan 21 at 11:03:
Sandy Drobic wrote:
I'd rather like to know what happens if you enter the command telnet mx2.epicuria.be 25 in your console. As I wrote you should be able to see the lines I mentioned.
Sandy
Here's what i get : telnet mx2.epicuria.be 25 Trying 204.200.196.67... telnet: connect to address 204.200.196.67: Connection timed out
There's your problem - DNS works, but the connection's dropped. Blame your ISP.
I came to that conclusion two days ago in X-Message-Number-for-archive: 223195 :-P Theo -- Theo v. Werkhoven Registered Linux user# 99872 http://counter.li.org ICBM 52 13 26N , 4 29 47E. + ICQ: 277217131 SUSE 9.2 + Jabber: muadib@jabber.xs4all.nl Kernel 2.6.8 + MSN: twe-msn@ferrets4me.xs4all.nl See headers for PGP/GPG info. +
Theo wrote regarding 'Re: [SLE] Postfix error' on Fri, Jan 21 at 16:24:
Fri, 21 Jan 2005, by suse-linux-e.suselists@danny.teleologic.net:
Laurent wrote regarding 'Re: [SLE] Postfix error' on Fri, Jan 21 at 11:03:
Sandy Drobic wrote:
I'd rather like to know what happens if you enter the command telnet mx2.epicuria.be 25 in your console. As I wrote you should be able to see the lines I mentioned.
Sandy
Here's what i get : telnet mx2.epicuria.be 25 Trying 204.200.196.67... telnet: connect to address 204.200.196.67: Connection timed out
There's your problem - DNS works, but the connection's dropped. Blame your ISP.
I came to that conclusion two days ago in X-Message-Number-for-archive: 223195 :-P
I typed X-Message-Number-for-archive: 223273 before I had received any other responses in that thread, but the machine I typed the response on masqueraded my address, and the message didn't get posted until I fixed the problem and resent. Unfortunately, that particular message must've been missed even after it was finally posted, as neither the postconf -n results or the telnet test were run until much later in the thread. :) So there. :) --Danny, in second grade again
participants (4)
-
Danny Sauer -
Laurent Renard -
Sandy Drobic -
Theo v. Werkhoven