Usermin - Read Mail - Failed to connect

9 posts / 0 new

Topic locked

Last post

#1 Sun, 05/17/2009 - 04:53

reQuorter

Usermin - Read Mail - Failed to connect

Hello,

I am using:

OS: Debian 5.0 Lenny Virualmin: 3.68 gpl Usermin: 1.400

When I successfully login to Usermin (port :20000) and then Usermin -> Mail -> Read Mail I got an error "An error occurred listing mail in this folder : Failed to connect to localhost:143 : Connection refused" and it's the same for every other account (root, admin domains, user domains).

When I'm using email with programs like Windows Mail (Vista), everything works fine (incoming/outcoming).

I've check /var/log/mail.log and /var/log/dovecot.log and there is nothing about that error, even no connection log when trying to connect by Usermin interface.

#2 Sun, 05/17/2009 - 06:09

andreychek

Well, normally I'd suggest making sure that Dovecot is running -- but I suspect it will be if it works from other clients.

I'd be curious if anything at all shows up in /var/log/auth.log and /var/log/mail.log when you're attempting to connect. It might have a completely different error than what you're seeing in Usermin.

As a complete shot in the dark, it's possible that "disable_plaintext_auth = no" needs to be set in your /etc/dovecot/dovecot.conf. If you try that, be sure to restart Dovecot afterwards.
-Eric

#3 Sun, 05/17/2009 - 08:14 (Reply to #2)

reQuorter

<b>andreychek wrote:</b>
<div class='quote'>Well, normally I'd suggest making sure that Dovecot is running -- but I suspect it will be if it works from other clients.</div>
Dovecot is running.
<div class='quote'>I'd be curious if anything at all shows up in /var/log/auth.log and /var/log/mail.log when you're attempting to connect. It might have a completely different error than what you're seeing in Usermin.</div>
There is nothing about that connection I'm trying to make through Usermin.
<div class='quote'>As a complete shot in the dark, it's possible that "disable_plaintext_auth = no" needs to be set in your /etc/dovecot/dovecot.conf. If you try that, be sure to restart Dovecot afterwards.</div>
I did it, but the problem still remains.

#4 Sun, 05/17/2009 - 09:52

reQuorter

<b>OK, I solved problem just by turning on IAMP on dovecot.</b>
At the beginning I configured dovecot to use only IAMP (SSL).

#5 Sat, 06/19/2010 - 14:05 (Reply to #4)

midol

any info welcome

#6 Wed, 08/18/2010 - 15:19

mikerobinson

I had this same problem too. The problem is that imapproxy was not running after a server reboot (on CentOS).

# /etc/init.d/imapproxy restart
Shutting down up-imapproxy daemon:                         [FAILED]
Starting up-imapproxy daemon:                              [  OK  ]

Executing this command fixed it.

#7 Sun, 10/24/2010 - 19:04

whippy

Same error. May have been following a restart.

Ubuntu does not have imapproxy but working from the above, I fixed it with:

paul@ws1:~$ sudo service dovecot restart
 * Restarting IMAP/POP3 mail server dovecot                              [ OK ] 
paul@ws1:~$

#8 Fri, 03/22/2013 - 00:27

nexusguy59

However i had migrated from a 10.04to 12.04 after the install of virtualmin, I am not sure if it was cause I didn't reboot after the install. whippy's remedy worked for me as well.

Thanks for the info.

Michael Cooper Linux Certified Professional http://www.coopfire.com

#9 Fri, 03/22/2013 - 00:27

nexusguy59

However i had migrated from a 10.04 to 12.04 after the install of virtualmin, I am not sure if it was cause I didn't reboot after the install. whippy's remedy worked for me as well.

Thanks for the info.

Michael Cooper Linux Certified Professional http://www.coopfire.com

Topic locked