View Full Version : Warning: fsockopen(): unable to connect to localhost:25 in Deliver_SMTP.class.php on

05-14-2005, 12:37 AM
I have installed Debian, and I am using dovecot imap and squirrelmail. When I try to send a letter in squirrelmail, I get this error:

Warning: fsockopen(): unable to connect to localhost:25 in Deliver_SMTP.class.php on line 57

Any ideas???

06-16-2005, 05:06 PM
I have also observed this problem with Tiki Wiki (when using "Mailin" and "Webmail" features).

There's very little (none?) discussion of this problem in the Tiki Wiki community.

I've observed the same problem (ie fsockopen is "unable to connect") with two different versions of Tiki Wiki (1.84 and 1.85) and I can see that it's been reported (in Tiki Wiki) back in 2003 as well. It appears to work fine for many users at the moment. I can't find any current reports of this problem with Tiki Wiki.

So I've all but concluded that the problem likes elsewhere -- not in Tiki Wiki, but perhaps in PHP itself.

In my case, Tiki Wiki is using POP, not IMAP -- but I think this message appears before we get that far along...

The problem occurs when attempting to connect to EACH OF TWO different POP3 Servers.

Frankly, I don't expect any help... I hope that just writing something coherent about it will help me figure it out... Hmmm... I'm still blank...

By the way, squirrel mail is configured on this system and works fine when accessing the same email servers that Tiki Wiki fails on. I should inspect the SM code... that might shed some light.

Here's the (slightly MODIFIED) output from Tiki's mailin.php:
Warning: fsockopen(): unable to connect to mail.SERVER.ABC:110 in /home/LINUXUSER/public_html/TIKI/lib/webmail/pop3.php on line 79

Notice: Undefined offset: 1 in /home/LINUXUSER/public_html/TIKI/lib/webmail/pop3.php on line 153

Notice: Undefined offset: 2 in /home/LINUXSER/public_html/TIKI/lib/webmail/pop3.php on line 154

An examination of Tiki's mailin.php file seems to reveal that that mailin.php has poor error handling and shouldn't even have got to lines 153 and 154 -- so those messages can be regarded as spurious, I believe (1 and 2 are simply array indices which are invalid because the array doesn't seem to exist ... not surprisingly since the call to fsockopen failed). I include these here only so that a search engine will find them...

Now to check the SM code...