Email access setup problems

[reuben]

I have just had DA installed on my server and have multiple domains. I have just got round to setting up the email accounts for the domains. But when I try to use squirrel mail to access the email I get the following error message for every email account I have regardless of the domain setup on the server.

Does any one know what this problem is and how I can fix it?


Warning: fsockopen(): unable to connect to localhost:143 in /var/www/html/squirrelmail-1.4.2/functions/imap_general.php on line 454

SquirrelMail version 1.4.2
By the SquirrelMail Development Team
ERROR
Error connecting to IMAP server: localhost.
111 : Connection refused
Go to the login page

[ProWebUK]

Ensure imap is running (can you connect to it using another mail client?)

If you have a firewall try turning it off temporarily also.

Chris

[DirectAdmin Support]

You can test if/when you get it running by typing:
telnet localhost 143Also, imap is run via the xinetd daemon, so you have to make sure that's running.

John

[ProWebUK]

Is xinetd now being monitored by DA John?

Chris

[DirectAdmin Support]

No it isn't.

John

[ProWebUK]

OK I will add that to the SIM how-to ;)

Chris

[reuben]

This fixed my problem - great advice.

[ProHS]

I am having the same problem, what is the imap service called?

[ProWebUK]

Originally posted by ProHS
I am having the same problem, what is the imap service called?

it runs under the xinet daemon which can be restarted:

service xinetd {options}

restart, stop start etc being the options.

Chris

[ProHS]

That command does not work what would the command be in FreeBSD i tryed service inetd restart and did not work.

[DirectAdmin Support]

Hello,

"service" doesn't exist on FreeBSD. To restart it on FreeBSD, you'll probably have to do something like:

killall inetd
inetdJohn

[ProHS]

I tryed that and i am still having issues with imap so is there anything else i should check?

[DirectAdmin Support]

Hello,

1) is inetd runing?
When I type "ps -ax |grep inetd", i get:

-bash-2.05b# ps -ax |grep inetd
564 ?? Is 0:00.00 /usr/sbin/inetd -wW
so maybe try killing it, and starting it with the -wW option

2) check your /etc/inetd.conf file to make sure imap is setup. Mine has a line :
imap4 stream tcp nowait root /usr/sbin/imapd imapd

3) Give inetd an hup:killall -HUP inetd

4) check if it's working:telnet localhost 143... also, make sure that the imapd binary exists at /usr/sbin/imapd

If anything doesn't work, check the /var/log/messages file after a restart/reload of inetd.

John