LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Server
User Name
Password
Linux - Server This forum is for the discussion of Linux Software used in a server related context.

Notices


Reply
  Search this Thread
Old 08-11-2012, 04:18 PM   #1
acasaviellesg
LQ Newbie
 
Registered: Jul 2012
Posts: 6

Rep: Reputation: Disabled
Wink S.O.S.: Squirrelmail access problem!!


Hello!

I've a Centos 5.8 as mail server (sendmail+exim+dovecot) and I need to provide my users the service of checking their emails via web. So I've decided to install squirrelmail. After finishing the instalation of apache+mysql+php+squirrelmail I tried to access the main page: myserver/webmail and guess: it works!!

The problem occurs when I try to login with my user and passwd. I read the following error in my screen: Error connecting to IMAP server: localhost.111:Connection refused.

I've been searching on Internet, but the solutions I've found are not recommended when using dovecot.

I'll appreciate any help. Thanks for your attention.

Best regards.
 
Old 08-11-2012, 05:09 PM   #2
bathory
LQ Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 13,163
Blog Entries: 1

Rep: Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032
Quote:
The problem occurs when I try to login with my user and passwd. I read the following error in my screen: Error connecting to IMAP server: localhost.111:Connection refused.
Check if dovecot is running and listening on port 143:
Code:
netstat -tanpl|grep 143
If it's running but you can't connect, I guess it's SELinux that denies access to the imap server for the apache user. In this case you can run:
Code:
setsebool -P httpd_can_network_connect 1

BTW, you should tell squirrelmail about the imap server you're running. See this for details

Regards

Last edited by bathory; 08-11-2012 at 05:13 PM.
 
Old 08-13-2012, 08:24 AM   #3
acasaviellesg
LQ Newbie
 
Registered: Jul 2012
Posts: 6

Original Poster
Rep: Reputation: Disabled
Unhappy Hard to find a solution!

Thanks for your time giving me the light to solve my problem. I did what you suggested:

1 The netstat gave me this: "tcp 0 0 192.168.0.1:143 0.0.0.0:* LISTEN 5294/dovecot". So, can I conclude that dovecot is listening from port 143?

2 SELinux is disabled.

3 I read the article about the squirrelmail configuration and I did everything they say.

But something is missing because the error still alive.

Any other suggestions?

Regards
 
Old 08-13-2012, 09:36 AM   #4
bathory
LQ Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 13,163
Blog Entries: 1

Rep: Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032
Quote:
1 The netstat gave me this: "tcp 0 0 192.168.0.1:143 0.0.0.0:* LISTEN 5294/dovecot". So, can I conclude that dovecot is listening from port 143?
Yes, but it's not listening on the local loopback interface (127.0.0.1), that is why you get that error
I guess you have to use in diovecot.conf the following:
Code:
imap_listen = *
Regards
 
Old 08-13-2012, 12:07 PM   #5
acasaviellesg
LQ Newbie
 
Registered: Jul 2012
Posts: 6

Original Poster
Rep: Reputation: Disabled
Question

Thanks again!

I did what you said:

imap_listen = * was not valid. After some research I used instead:

protocol imap { listen = *:143 }

Nothing happened but the same error.

What else should I check??
 
Old 08-13-2012, 12:56 PM   #6
bathory
LQ Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 13,163
Blog Entries: 1

Rep: Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032
Quote:
imap_listen = * was not valid. After some research I used instead:

protocol imap { listen = *:143 }
Oups I forgot that some of the dovecot.conf options are changed. Anyway the above is wrong. Either use (the deprecated)
Code:
protocol imap {
listen = *:143
}
or just
Code:
listen = *
You can also comment out the whole protocol/listen part, so dovecot listens on all available interfaces.
And don't forget to restart the service after making changes in the configuration

Regards
 
Old 08-13-2012, 04:09 PM   #7
acasaviellesg
LQ Newbie
 
Registered: Jul 2012
Posts: 6

Original Poster
Rep: Reputation: Disabled
Talking

Hi!

It worked!! thanks for all your help and patience..

Regards.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Troubles with postfix and Squirrelmail but not Outlook- relay access denied DKLeader Linux - Server 2 10-01-2011 02:15 PM
how to access squirrelmail by using port 3333 pawan_lal Linux - Server 1 07-31-2009 02:36 AM
Restrict access per user with Squirrelmail and postfix ? id_viorel Linux - Server 0 05-30-2008 08:09 AM
squirrelmail access problem help needed soroccoheaven Linux - Server 2 08-21-2007 10:20 AM
access denied on squirrelmail / dovecot / SE Linux policy rioguia Linux - Security 2 07-06-2005 11:25 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Server

All times are GMT -5. The time now is 12:02 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration