Open GoogleCodeExporter opened 8 years ago
[deleted comment]
Warning: fsockopen() [function.fsockopen]: unable to connect to
gmail-smtp-in.l.google.com:25 (Connection refused)
how to solve this problem. any buddy can help me.
Earlier it was working!!!!!!!!!
Original comment by adarsh...@yahoo.com
on 23 Jun 2009 at 7:23
I have the same as this, seems to be something not working as intended here.
Original comment by steinh...@gmail.com
on 9 Jul 2009 at 11:13
I think google prevents this check.
Original comment by Hudson.A...@gmail.com
on 9 Jul 2009 at 4:46
Did you manage to solve this problem? I also have the same...
Original comment by sophie.boulanger1@gmail.com
on 5 Aug 2009 at 2:49
Could this be a blocked port? Error message shows up almost instanious.
Original comment by knowlecu...@gmail.com
on 27 Oct 2009 at 1:59
Bump
I've tried multiple domains, and even verified that I can telnet to port 25 at
the
mx servers that are telling me connection refused.
Original comment by illush...@gmail.com
on 14 Nov 2009 at 1:05
it work on my developpement srv but not on the production one...
perhaps hostmonster block them, or it's blacklisted...
Original comment by 1000feui...@gmail.com
on 9 Dec 2010 at 3:33
i works on localhost but not online
Original comment by bikashch...@gmail.com
on 26 Dec 2011 at 3:58
It happens when you run this script in shared hosting like hostgator or
hostmonster, you need to open port 25 in iptables. Most shared hosts won't
allow this to protect their ip from blacklist
Original comment by axvac...@gmail.com
on 1 May 2012 at 12:18
It works on my development local server but not working on production live
server...
Please help me to out of this problem
Original comment by mailvikr...@gmail.com
on 19 Apr 2013 at 2:31
hi,
Array
(
[gmail-smtp-in.l.google.com] => 5
[alt1.gmail-smtp-in.l.google.com] => 10
[alt2.gmail-smtp-in.l.google.com] => 20
[alt3.gmail-smtp-in.l.google.com] => 30
[alt4.gmail-smtp-in.l.google.com] => 40
[gmail.com] => 0
)
try gmail-smtp-in.l.google.com:25
try alt1.gmail-smtp-in.l.google.com:25
try alt2.gmail-smtp-in.l.google.com:25
try alt3.gmail-smtp-in.l.google.com:25
try alt4.gmail-smtp-in.l.google.com:25
try gmail.com:25
fetch this problem plz solved this for
http://ciudadanoahora.com/
Original comment by sanjeev....@thefreshersworld.net
on 2 Nov 2013 at 8:13
[deleted comment]
Array
(
[gmail-smtp-in.l.google.com] => 5
[alt1.gmail-smtp-in.l.google.com] => 10
[alt2.gmail-smtp-in.l.google.com] => 20
[alt3.gmail-smtp-in.l.google.com] => 30
[alt4.gmail-smtp-in.l.google.com] => 40
[gmail.com] => 0
)
try gmail-smtp-in.l.google.com:25
Warning: fsockopen(): unable to connect to gmail-smtp-in.l.google.com:25
(Connection timed out) in
/home/hemsprop/public_html/new/mail/smtp_validateEmail.class.php on line 154
try alt1.gmail-smtp-in.l.google.com:25
Warning: fsockopen(): unable to connect to alt1.gmail-smtp-in.l.google.com:25
(Connection timed out) in
/home/hemsprop/public_html/new/mail/smtp_validateEmail.class.php on line 154
try alt2.gmail-smtp-in.l.google.com:25
Warning: fsockopen(): unable to connect to alt2.gmail-smtp-in.l.google.com:25
(Connection timed out) in
/home/hemsprop/public_html/new/mail/smtp_validateEmail.class.php on line 154
try alt3.gmail-smtp-in.l.google.com:25
Warning: fsockopen(): unable to connect to alt3.gmail-smtp-in.l.google.com:25
(Connection timed out) in
/home/hemsprop/public_html/new/mail/smtp_validateEmail.class.php on line 154
try alt4.gmail-smtp-in.l.google.com:25
have any solution for this ?
Original comment by sachin11...@gmail.com
on 3 Jul 2014 at 11:42
I have same problem.. the code is working on localhost, but not working on my
production server. How to fix ?
Original comment by iamva...@gmail.com
on 20 Jan 2015 at 4:33
It works on localhost, but not working on live server. I try to change
nameservers in smtp class. Still didn't have sucess.
Original comment by kaleem.s...@gmail.com
on 22 Jan 2015 at 11:16
fsockopen(): unable to connect to gmail-smtp-in.l.google.com:25
try alt1.gmail-smtp-in.l.google.com:25 Warning showing....
Original comment by MAHIVIT...@gmail.com
on 28 Feb 2015 at 10:45
Original issue reported on code.google.com by
Hudson.A...@gmail.com
on 14 Jun 2009 at 6:22