[Dovecot] Dovecot & SquirrelMail HELP!
Hi All,
I just installed Dovecot-Imap because uw-imap is awful... and Dovecot seems like a good Imap Server.
Anyway I am using a Debian Server and apt-get install dovecot Seems to be working... I can telnet to port 143 and run /var/run/dovecot/login
However SquirrelMail Config test cannot detect if, If anyone knows a guide to make Dovecot work with SquirrelMail please let me know...
THis is quite urgent matter and need to fix this ASAP! Thanks! Mark Smith
--On Thursday, August 11, 2005 9:06 PM +1000 admin@downend.org wrote:
However SquirrelMail Config test cannot detect if, If anyone knows a guide to make Dovecot work with SquirrelMail please let me know...
<http://www.squirrelmail.org/wiki/en_US/FedoraCore1Dovecot> <http://www.squirrelmail.org/wiki/en_US/SquirrelMailAndDovecotIMAP>
admin@downend.org wrote:
Which version of Dovecot?
Have you run Squirrelmail's conf.pl? You could chose "other" or "uw" (but if the latter, you'll probably need to modify the folder prefix).
Chris
-- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin@reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094
Hey, Somenoe gave me this link: http://www.squirrelmail.org/wiki/en_US/SquirrelMailAndDovecotIMAP
I followed it and completed it... so I assume SquirrelMail should work... I am recieving an issue trying to connect to the IMap server in squirrelmail.
Firstly I recieve no response when starting dovecot
aries:/var/www/mail/config# /etc/init.d/dovecot start aries:/var/www/mail/config#
Which is odd...
I can telnet to it: aries:/var/www/mail/config# telnet localhost 143 Trying 127.0.0.1... Connected to localhost.localdomain. Escape character is '^]'.
I have installed previous Imap Servers could that be it? How can I check if port 143 is being used by another imap server?
Regards, Quoting admin@downend.org:
On Fri, Aug 12, 2005 at 12:42:54AM +1000, admin@downend.org wrote:
http://www.squirrelmail.org/wiki/en_US/SquirrelMailAndDovecotIMAP
I followed it and completed it...
the 2 urls given in some email earlier gave different values for e.g. the imap-server field
so I assume SquirrelMail should work...
on a working mailserver (freebsd) with dovecot + squirrelmail i have :
IMAP Settings
- IMAP Server : 192.168.2.22
- IMAP Port : 143
- Authentication type : login
- Secure IMAP (TLS) : false
- Server software : other
- Delimiter : detect
B. Update SMTP Settings : 192.168.2.22:25 H. Hide IMAP Server Settings
try /etc/init.d/dovecot restart or /etc/init.d/dovecot stop ; /etc/init.d/dovecot start
I have installed previous Imap Servers could that be it? How can I check if port 143 is being used by another imap server?
netstat -tan|grep 143
try /etc/init.d/dovecot restart or /etc/init.d/dovecot stop ; /etc/init.d/dovecot start
I recieve not output whe running the command which is usually odd.
I recieved the following output:
aries:~# netstat -tan|grep 143 tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:37837 127.0.0.1:143 ESTABLISHED tcp 0 0 127.0.0.1:37839 127.0.0.1:143 FIN_WAIT2 tcp 32 0 127.0.0.1:143 127.0.0.1:37755 CLOSE_WAIT tcp 1 0 127.0.0.1:143 127.0.0.1:37759 CLOSE_WAIT tcp 1 0 127.0.0.1:143 127.0.0.1:37761 CLOSE_WAIT tcp 231 0 127.0.0.1:143 127.0.0.1:37762 CLOSE_WAIT tcp 1 0 127.0.0.1:143 127.0.0.1:37764 CLOSE_WAIT tcp 1 0 127.0.0.1:143 127.0.0.1:37768 CLOSE_WAIT tcp 1 0 127.0.0.1:143 127.0.0.1:37771 CLOSE_WAIT tcp 32 0 127.0.0.1:143 127.0.0.1:37774 CLOSE_WAIT tcp 1 0 127.0.0.1:143 127.0.0.1:37777 CLOSE_WAIT tcp 202 0 127.0.0.1:143 127.0.0.1:37779 CLOSE_WAIT tcp 251 0 127.0.0.1:143 127.0.0.1:37783 CLOSE_WAIT tcp 1 0 127.0.0.1:143 127.0.0.1:37785 CLOSE_WAIT tcp 1 0 127.0.0.1:143 127.0.0.1:37787 CLOSE_WAIT tcp 1 0 127.0.0.1:143 127.0.0.1:37790 CLOSE_WAIT tcp 1 0 127.0.0.1:143 127.0.0.1:37793 CLOSE_WAIT tcp 1 0 127.0.0.1:143 127.0.0.1:37797 CLOSE_WAIT tcp 1 0 127.0.0.1:143 127.0.0.1:37800 CLOSE_WAIT tcp 32 0 127.0.0.1:143 127.0.0.1:37803 CLOSE_WAIT tcp 32 0 127.0.0.1:143 127.0.0.1:37806 CLOSE_WAIT tcp 1 0 127.0.0.1:143 127.0.0.1:37808 CLOSE_WAIT tcp 1 0 127.0.0.1:143 127.0.0.1:37811 CLOSE_WAIT tcp 32 0 127.0.0.1:143 127.0.0.1:37814 CLOSE_WAIT tcp 28 0 127.0.0.1:143 127.0.0.1:37815 CLOSE_WAIT tcp 29 0 127.0.0.1:143 127.0.0.1:37819 CLOSE_WAIT tcp 29 0 127.0.0.1:143 127.0.0.1:37822 CLOSE_WAIT tcp 29 0 127.0.0.1:143 127.0.0.1:37825 CLOSE_WAIT tcp 1 0 127.0.0.1:143 127.0.0.1:37829 CLOSE_WAIT tcp 32 0 127.0.0.1:143 127.0.0.1:37832 CLOSE_WAIT tcp 1 0 127.0.0.1:143 127.0.0.1:37836 CLOSE_WAIT tcp 97 0 127.0.0.1:143 127.0.0.1:37837 ESTABLISHED tcp 1 0 127.0.0.1:143 127.0.0.1:37839 CLOSE_WAIT tcp6 0 0 :::143 :::* LISTEN
Any ideas what do do? Thanks,
Quoting albi <albi@scii.nl>:
--On Thursday, August 11, 2005 5:28 PM +0200 albi <albi@scii.nl> wrote:
It's a wiki, and the two links are two different users' experiences.
I like (as root) "lsof -i" to list all open files that are IPv4 sockets, and then grep the result for the port of interest (eg. "| grep imap", which assumes that imap is defined in /etc/services).
participants (6)
-
admin@downend.org
-
albi
-
Chris Wakelin
-
Johannes Berg
-
Kenneth Porter
-
Robert Cooper