Error connecting to IMAP server: localhost 111 Connection Refused, Squirrel mail?

Advertisement

May 17, 2008 03:21am pdt

Experts Exchange

Announcements Feedback

Advertisement

1. shakoush... 156,946
2. ravenpl 129,100
3. omarfarid 121,926
4. duncan_roe 97,920
5. Tintin 86,485
6. Nopius 61,619
7. PeturIng... 51,424
8. arnold 34,527
9. Rance_Hall 29,605
10. Kdo 28,950
11. ozo 26,630
12. MicheleM... 24,660
13. uetian1707 23,800
14. rindi 23,025
15. ahoffmann 21,469

1. jlevie 742,191
2. wesly_chen 643,537
3. ravenpl 606,959
4. Gns 468,980
5. rindi 423,055
6. duncan_roe 407,742
7. pjedmond 396,065
8. Tintin 361,696
9. xDamox 344,723
10. slyong 245,583
11. nedvis 224,350
12. ahoffmann 221,435
13. Tim_Utschig 207,074
14. khkremer 202,287
15. Mysidia 199,498

01.17.2008 at 08:45AM PST, ID: 23090679

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

Error connecting to IMAP server: localhost 111 Connection Refused, Squirrel mail?

Zones: Linux, Linux Networking, Qmail Email Server

Hey all

Ive installed QMAIL and all should be good, used the installation from QMAIL rocks.

Now ive got to the point where im using the Squirrel mail Web mail, and I get the error that ive provided.

It seems something to do with IMAPD perhaps, so was just seeing if anything had the issues with this before?

Please let me know your ideas and thoughts.

Cheers

Curt

Start your free trial to view this solution

Question Stats

Zone: OS

Question Asked By: thechase22

Solution Provided By: Bibliophage

Participating Experts: 3

Solution Grade: B

Views: 318

Translate:

Loading Advertisement...

Internet Protocols
Applications

Development
OS

Hardware
Windows Security

Operating Systems
Hardware

Programming
Networking

Software

Search Engines
File Sharing
WebTrends / Stats
Spy / Ad Blockers

Web Browsers
New Net Users
Web Development
Chat / IM

Anti Spam
Web Servers
Anti-Virus
Email Clients

Tips
Online / MMORPG
Puzzle
Emulators

Action / Adventure
Role Playing
Consoles
Game Programming

Strategy
Sports
Misc
Computer Games

Hardware
New Net Users
New Users

Software
Digital Music
Gaming World

Home Security
Apple
Networking Hardware

Virus & Spyware

Vulnerabilities
IDS
Encryption
Anti-Virus

Operating Systems Security
Software Firewalls
WebApplications
Cell Phones

Operating Systems
Internet
Hardware Firewalls

Handhelds / PDAs
Displays / Monitors
Components
Networking Hardware

Peripherals
Laptops/Notebooks
Storage
Servers

Desktops
New Users
Misc
Apple

System Utilities
Industry Specific
Network Management
Photos / Graphics
Page Layout
VMWare
Misc
Web Development

OS
CYGWIN
Voice Recognition
Message Queue
Quality Assurance
Security
Firewalls
MultiMedia Applications

Development
Database
Office / Productivity
Business Management
OS/2 Apps
Server Software
Internet / Email

OS
Storage
Encryption
Operating Systems Security
Apple Hardware
Laptops & Notebooks
Servers
Networking Hardware
Peripherals

Devices
Displays / Monitors
WebTrends / Stats
Search Engines
Firewalls
WebApplications
IDS
Vulnerabilities
Email Clients

File Sharing
Spy / Ad Blockers
Web Browsers
Web Servers
Networking
Anti-Virus
Chat / IM
Anti Spam

Web Servers
Web Browsers
Game Programming
Dev Tools
Industry Specific
Office / Productivity

Database
CYGWIN
Web Development
Search Engines
File Sharing
WebTrends / Stats

Programming
Content Management
Application Servers
Protocols

Removable Backup Media
Storage Technology
Servers

Grid
Remote Access
Backup / Restore

Misc
Hard Drives

Miscellaneous
Security
Development
Linux
VMWare

MainFrame OS
Unix
Apple
OS / 2
AS / 400

BeOS
Microsoft
VMS / OpenVMS

Oracle
Miscellaneous
MySQL
Software
Sybase
Contact Management
PostgreSQL
Data Manipulation
Clarion
InterSystems Cache

Siebel
MUMPS
OLAP
SQLBase
SAS
GIS & GPS
4GL
Berkeley DB
DB2
Informix

Interbase / Firebird
FoxPro
Reporting
LDAP
Filemaker Pro
MS SQL Server
dBase
MS Access

Misc
Web Browsers
Software Firewalls
Operating Systems Security
File Sharing

Spy / Ad Blockers
Vulnerabilities
WebApplications
IDS
Anti-Virus

Encryption
Anti Spam
Email Clients
VPN
Chat / IM

Editors IDEs
Installation
Handhelds / PDAs
Multimedia Programming
System / Kernel

Algorithms
Game
Signal Processing
Project Management
Open Source

Database
Misc
Languages
Processor Platforms
Theory

Web Development

Scripting
Blogs
Web Servers
Software
Search Engines
Web Graphics
Images

Internet Marketing
Images and Photos
Components
Document Imaging
Web Languages/Standards
Illustration
WebApplications

Fonts
WebTrends / Stats
Authoring
Digital Camera Software
Miscellaneous

Protocols
Apple Networking
Network Management
Message Queue
Application Servers
Content Management
File Servers
Email Servers
Misc
Java Editors & IDEs

Wireless
Networking Hardware
Backup / Restore
System Utilities
ISPs & Hosting
Web Servers
Storage Technology
Removable Backup Media
Servers
Broadband

Grid
OS / 2
Novell Netware
Unix Networking
Windows Networking
Security
Telecommunications
Operating Systems
Linux Networking

Community Advisor
Lounge
Community Support
New Net Users

Philosophy / Religion
Math / Science
Miscellaneous
URLs

Expert Lounge
Politics
Puzzles / Riddles

Community Support

Suggestions
New to EE
New Topics
Community Advisor

CleanUp
Announcements
General

Feedback
Input
EE Bugs

01.17.2008 at 10:54AM PST, ID: 20684155

It means that the Courier-IMAP settings aren't quite right.

Now, just so you know, the QMR instructions are sadly out of date. I would recommend that you stop now, go to qmail.jms1.net, and read through some of the information there. for example, the patch set that's in the QMR install is almost two years old, and correspondingly buggy - especially since several of the patches in the 'set' aren't necessary (or have been rolled into John Simpson's large patch)

One of the problems with the QMR site, and it's not a huge problem in some ways, is that it doesn't explain enough, and just gives you too many 'run this script' tools. I'm not against run this script tools, but they should be offered after you've run through the entire site, not as part of the main thing.

You should also join the mailing list - which is linked directly off of the QMR site itself.

As for your error? It's common yes. Usually it means that the IMAPD or AUTHD isn't running properly. Don't ask for help from Sam Varshavik of Courier, he'd give you short shrift for not researching it thoroughly.

Find the archives for the qmr mailing list, scan through them, and you'll probably find a better explanation than I could give you in a couple of minutes.

Accepted Solution

01.17.2008 at 11:02AM PST, ID: 20684224

Heya

Well this doesnt help me very much lol

The qmail part runs fine, I will read through the site you mentioned for the patches though.

I was hoping someone could go through some things with me, even if I have to wait a while.

Ive been pondering around this error for a few weeks and havent got much further.

01.17.2008 at 11:05AM PST, ID: 20684251

You need to check that website you showed me again, not unless you intended me to goto a spamming site?

01.17.2008 at 05:07PM PST, ID: 20687132

http://qmail.jms1.net/

It may only work correctly in firefox. No spammer site there. I don't use IE on this machine at all, so I can't remember if he has it set the same way as delete.net (which is also owned by him)

Actually, it should work any _any_ browser but IE, if he put his site that way.

01.18.2008 at 10:58AM PST, ID: 20693085

Qmail doesn't do IMAP on its own. Have you installed Courier too ?

01.18.2008 at 01:06PM PST, ID: 20694181

Heya
ofcourse ive installed Courier.

anything else I could try?

01.18.2008 at 01:26PM PST, ID: 20694342

ok good just checking :)

You can check to see if courier has started with

ps aux| grep courier

and if so then check to see which ports if any its listening on with

netstat -tupan |grep courier

you'll need to be root for that last one. I'd expect to see either
127.0.0.1:143 0.0.0.0:* LISTEN
or
0.0.0.0:143 0.0.0.0:* LISTEN

Either of those would allow connections from localhost.

If you get neither then I think the config file to edit is /etc/courier/imapd and check the ADDRESS= and PORT= lines.

If courier is already listening on port 143 then squirrelmail is probably connecting to the wrong port, and something needs changing in squirrelmails config.

actually you could just "telnet localhost 143" to test courier.

Good luck.

01.18.2008 at 05:34PM PST, ID: 20695602

Tomun - you're misunderstanding part of the root of his problem.

The QMR installation was written for older versions of the distributions (I should know, I wrote most of the Slackware instructions), and is sadly out of date for almost every piece of software in the main package.

The real fix isn't going to be to try to patch what he has, but to go back to the starting point, and realize what he needs to do to upgrade it to a more 'current' version. Thus the link I sent him to. John Simpson has very good information on that.

There are also a couple of mailing lists, including the QmailRocks mailing list itself, which I'm a member of.

01.19.2008 at 10:57AM PST, ID: 20698507

Heya and thanks for the replys

Heres what I got from the first command:

[root@s15260266 ~]# ps aux | grep courier
root 8759 0.0 0.0 1736 500 ? S Jan13 0:00 /usr/local/libe xec/couriertcpd -address=0 -stderrlogger=/usr/local/sbin/courierlogger -stderrlo ggername=imapd-ssl -maxprocs=40 -maxperip=4 -pid=/var/run/imapd-ssl.pid -nodnslo okup -noidentlookup 993 /usr/local/bin/couriertls -server -tcpd /usr/local/sbin/ imaplogin /usr/local/bin/imapd Maildir
root 8763 0.0 0.0 1504 316 ? S Jan13 0:00 /usr/local/sbin /courierlogger imapd-ssl
root 26106 0.0 0.0 3888 672 pts/0 R+ 18:46 0:00 grep courier
root 28956 0.0 0.0 1732 500 ? S Jan15 0:00 /usr/local/libe xec/couriertcpd -address=87.106.73.54 -stderrlogger=/usr/local/sbin/courierlogge r -stderrloggername=imapd -maxprocs=40 -maxperip=4 -pid=/var/run/imapd.pid -nodn slookup -noidentlookup 143 /usr/local/sbin/imaplogin /usr/local/bin/imapd Maildi r
root 28958 0.0 0.0 1504 316 ? S Jan15 0:00 /usr/local/sbin /courierlogger imapd

and second command

:[root@s15260266 ~]# netstat -tupan | grep courier
tcp 0 0 0.0.0.0:993 0.0.0.0:* LISTEN 8759/couriertcpd
tcp 0 0 87.106.73.54:143 0.0.0.0:*

That what you needed to know?

01.19.2008 at 09:55PM PST, ID: 20700254

I may have to go back and look at the instructions. I don't recall if the courier version that is with QMR is the all in one, or the one with courier-authlib separate from courier-imap. If it is, part of your issue might be that you don't have the authlib enabled properly.

Specifically it has to be running, and have 'vchkpw' as it's only option.

Assisted Solution

01.20.2008 at 01:57AM PST, ID: 20700648

Either way he'll need to fix that connection refused error, and to do that means either editing the imapd config file and adding ADDRESS=127.0.0.1 or alternatively editing squirrelmail's config and telling it to connect to 87.106.73.54 instead of localhost.

If he still can't log in, then courier-authlib would be a good place to start investigating.

01.21.2008 at 07:41AM PST, ID: 20706777

Hey guys

I did what you said Tomun, about the ADDRESS=127.0.0.1

I orignally changed it to my external address.

I changed this settting in

vi /usr/local/etc/imapd

a few things I should point out, is that the startup scripts dont work, I have to start imapd, and imaps myself:

/etc/rc.d/init.d/imap stop

/etc/rc.d/init.d/imaps stop

/etc/rc.d/init.d/imap start

/etc/rc.d/init.d/imaps start

The last thing I wanted to mention, was that when I tried to telnet to 110 I think it was, wouldnt have it, but I was lookin in /etc/services to this line:

courierpassd 106/tcp #for /etc/xinetd.d/courierpassd

and I remember that when I entered this manually like /etc/xinetd.d/courierpassd start

It would ask me to enter the password and stuff, bingo, so it works manually but not as a service, strange.

Just wanted to add some info as I need this fixed, and these are the things I came across.

Let me know what you think

Curt

01.21.2008 at 07:42AM PST, ID: 20706790

I wanted to add this quickly, very strange:

[root@s15260266 ~]# /etc/xinetd.d/courierpassd start
-bash: /etc/xinetd.d/courierpassd: Permission denied
[root@s15260266 ~]# /etc/xinetd.d/courierpassd status
-bash: /etc/xinetd.d/courierpassd: Permission denied
[root@s15260266 ~]# cd /etc/xinetd.d/
[root@s15260266 xinetd.d]# ls
chargen-dgram daytime-dgram discard-stream tcpmux-server
chargen-stream daytime-stream echo-dgram time-dgram
courierpassd discard-dgram echo-stream time-stream
[root@s15260266 xinetd.d]# courierpassd start
200 courierpassd v1.1.0-RC1 hello, who are you?

01.21.2008 at 08:14AM PST, ID: 20707079

Well if it now says ADDRESS=127.0.0.1 and you've restarted courier can squirrelmail now connect ? or do you get a new error ?

What happens if you telnet localhost 143 ?

As for the services not starting automatically, try "/sbin/chkconfig imap reset" which would fix it if your system has chkconfig, do the same for imaps and anything else that should be running.

It's starting to sound like there is indeed more wrong than simply the configuration of imapd.

Assisted Solution

01.21.2008 at 08:22AM PST, ID: 20707145

Silly me, I was so caught up with giving you information, I forgot to restart courier, and try and connect.

ok so im gonan try the webmail part and try login again and see how far I get.

As for the telnet localhost 143, its strange when I start the daemons manually I USED to be able to get a response. but look now, imaps is ok, but no imap?

[root@s15260266 xinetd.d]# nmap localhost

Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2008-01-21 16:20 GMT
Interesting ports on localhost.localdomain (127.0.0.1):
Not shown: 1671 closed ports
PORT STATE SERVICE
21/tcp open ftp
22/tcp open ssh
25/tcp open smtp
80/tcp open http
110/tcp open pop3
443/tcp open https
993/tcp open imaps
3306/tcp open mysql
10000/tcp open snet-sensor-mgmt

Ill get back to you in a sec about the other stuff

01.21.2008 at 08:27AM PST, ID: 20707205

Well you'll need to have port 143 open on localhost before squirrelmail will connect.

01.21.2008 at 08:48AM PST, ID: 20707392

Same thing: Error connecting to IMAP server: localhost.

Im thinking, it says server localhost, somewhere in a config, there is localhost, I reckon we find this entry and change to 127.0.0.1 perhaps, or maybe the dns IP.

I had this hunch before and I bet im not too far off.

01.21.2008 at 08:53AM PST, ID: 20707456

127.0.0.1 is localhost, they are the same thing.

Check your config again, and make sure imap is running.

try
netstat -tupan|grep LISTEN

and when its working you'll see 127.0.0.1:143 in the output.

Assisted Solution

01.21.2008 at 09:15AM PST, ID: 20707625

I know 127.0.0.1 is localhost, but it should say 127.0.0.1 instead of localhost, I get the impression that its looking at "localhost" text, I dunno just a theory anyways.

[root@s15260266 etc]# netstat -tupan|grep LISTEN
tcp 0 0 0.0.0.0:993 0.0.0.0:* LISTEN 8759/couriertcp d
tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN 2833/mysqld
tcp 0 0 0.0.0.0:110 0.0.0.0:* LISTEN 2987/tcpserver
tcp 0 0 87.106.73.54:143 0.0.0.0:* LISTEN 28956/couriertc pd
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 789/httpd
tcp 0 0 0.0.0.0:10000 0.0.0.0:* LISTEN 874/perl
tcp 0 0 0.0.0.0:10001 0.0.0.0:* LISTEN 2707/xinetd
tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 32194/vsftpd
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 2694/sshd
tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 2986/tcpserver
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 789/httpd

No Imap there sir

01.21.2008 at 09:18AM PST, ID: 20707663

Ok now im getting:

ERROR: Connection dropped by IMAP server.

We have progress it seems, I think ur thing about the 127.0.0.1 worked.

But now we have the connection dropped

01.21.2008 at 09:24AM PST, ID: 20707726

You might now have to go back to what Bibliophage said about 'vchkpw'.

01.21.2008 at 09:32AM PST, ID: 20707793

Yea I can see what he wrote, it doesnt help much, I hope he comes back soon.

I did find this page on google though, with same problem as myself:

http://www.oreillynet.com/cs/user/view/cs_msg/26360

Let me know what you think

01.27.2008 at 07:46PM PST, ID: 20756721

After trying to start imapd, have a look in the syslog and see if anything appears about it failing to start. Post your imapd conf file too. I believe its usually in /usr/local/etc

Squirrelmail connects to Courier-IMAP via Courier-Authlib I believe so that needs to be running. Depending on the mailbox structure you use, it needs to support the correct authentication setup (vchkpw for Vpopmail if that's what you use) Ensure that vchkpw is enabled in the COrier-IMAP config file in the location metioned above.

Assisted Solution

02.08.2008 at 10:58AM PST, ID: 20852898

Actually, i think that should read AUTHvchkpw. That's the actual name of the authentication module. Vchkpw is what it authenticates against.

Assisted Solution

02.11.2008 at 02:18AM PST, ID: 20865132

Heya thanks so much for your reply.

Im currently opening /usr/local/etc/imapd:

##VERSION: $Id: imapd.dist.in,v 1.33 2005/02/21 04:05:53 mrsam Exp $
#
# imapd created from imapd.dist by sysconftool
#
# Do not alter lines that begin with ##, they are used when upgrading
# this configuration.
#
# Copyright 1998 - 2004 Double Precision, Inc. See COPYING for
# distribution information.
#
# This configuration file sets various options for the Courier-IMAP server
# when used with the couriertcpd server.
# A lot of the stuff here is documented in the manual page for couriertcpd.
#
# NOTE - do not use \ to split long variable contents on multiple lines.
# This will break the default imapd.rc script, which parses this file.
#
##NAME: ADDRESS:0
#
# Address to listen on, can