[Dovecot] Problem setting up dovecot on Debian: "telnet: Unable to connect to remote host: Connection refused"
I would like to get dovecot running on my laptop so I can transfer a lot of old Email from Thunderbird mailbox files to a hosted zimbra service. However I'm falling at the first hurdle. I'm running Debian squeeze i386 (kernel 2.6.32-5-686) and have installed dovecot-imapd and dovecot-common with synaptic and edited /etc/dovecot/dovecot.conf to make sure it has the right protocols and listen instructions. Here's dovecot -n
root@delldeb:/etc/dovecot# dovecot -n # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-686 i686 Debian 6.0.6 log_timestamp: %Y-%m-%d %H:%M:%S listen: 143 993 disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_privileged_group: mail mbox_write_locks: fcntl dotlock auth default: passdb: driver: pam userdb: driver: passwd
Here's ps:
root@delldeb:/etc/dovecot# ps aux | grep dove root 10353 0.0 0.0 3944 792 ? Ss 15:32 0:00 /usr/sbin/dovecot -c /etc/dovecot/dovecot.conf root 10356 0.0 0.0 10008 2420 ? S 15:32 0:00 dovecot-auth root 10360 0.0 0.0 10008 2372 ? S 15:32 0:00 dovecot-auth -w dovecot 10361 0.0 0.0 5412 2024 ? S 15:32 0:00 imap-login dovecot 10362 0.0 0.0 5412 2024 ? S 15:32 0:00 imap-login dovecot 10363 0.0 0.0 5412 2028 ? S 15:32 0:00 imap-login root 10393 0.0 0.0 3304 772 pts/2 S+ 15:33 0:00 grep dove
Here's netstat: root@delldeb:/etc/dovecot# netstat -tap | grep 143 tcp 0 0 0.0.0.143:imap2 *:* LISTEN 9178/dovecot tcp 0 0 0.0.0.143:imaps *:* LISTEN 9178/dovecot
I can telnet into SMTP OK with telnet localhost 25 but telnet localhost 143 gets me the "Connection refused" message. I've changed auth_debug to "yes" and now /var/log/mail.info says:
Jan 5 15:32:13 delldeb dovecot: Dovecot v1.2.15 starting up (core dumps disabled) Jan 5 15:32:14 delldeb dovecot: auth(default): new auth connection: pid=10361 Jan 5 15:32:14 delldeb dovecot: auth(default): new auth connection: pid=10362 Jan 5 15:32:14 delldeb dovecot: auth(default): new auth connection: pid=10363
That doesn't change after I try the telnet login again so I think that's just telling me that the dovecot daemon started and launched it's listeners (but I know I don't know how to read this so correction welcome).
My reading of all of this is that the dovecot daemon is up and running, that it's listening correctly on 143 and 993 and that I have to do something else to get authorisation even to start the IMAP dialogue with the server. I would like to get it working and locked to SSL only but thought I should start with both unencrypted and encrypted.
Can someone help me or point me to the bits of documentation or good web howto or the like that I've missed?
TIA,
Chris (long term Debian user but it's some years since I last ran my own mail server and I'm a total newby to imap and dovecot)
Am 05.01.2013 16:48, schrieb Chris Evans:
root@delldeb:/etc/dovecot# ps aux | grep dove root 10353 0.0 0.0 3944 792 ? Ss 15:32 0:00 /usr/sbin/dovecot -c /etc/dovecot/dovecot.conf root 10356 0.0 0.0 10008 2420 ? S 15:32 0:00 dovecot-auth root 10360 0.0 0.0 10008 2372 ? S 15:32 0:00 dovecot-auth -w dovecot 10361 0.0 0.0 5412 2024 ? S 15:32 0:00 imap-login dovecot 10362 0.0 0.0 5412 2024 ? S 15:32 0:00 imap-login dovecot 10363 0.0 0.0 5412 2028 ? S 15:32 0:00 imap-login root 10393 0.0 0.0 3304 772 pts/2 S+ 15:33 0:00 grep dove
Here's netstat: root@delldeb:/etc/dovecot# netstat -tap | grep 143 tcp 0 0 0.0.0.143:imap2 *:* LISTEN 9178/dovecot tcp 0 0 0.0.0.143:imaps *:* LISTEN 9178/dovecot
I can telnet into SMTP OK with telnet localhost 25 but telnet localhost 143 gets me the "Connection refused"
as you can see you daemon ist listening on IP 0.0.0.143 instead 0.0.0.0
1.2.x is really really old but i think you missunderstood a listen-option
listen: 143 993 seems to be translated to 0.0.0.143, means you specified the ADDRESS the daemon should listen to instead the port
root@delldeb:/etc/dovecot# dovecot -n # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-686 i686 Debian 6.0.6 log_timestamp: %Y-%m-%d %H:%M:%S listen: 143 993
[SOLVED] - thanks to Harald Reindl - [SOLVED]
----- Original Message -----
From: "Reindl Harald" h.reindl@thelounge.net To: dovecot@dovecot.org Sent: Saturday, 5 January, 2013 4:01:09 PM Subject: Re: [Dovecot] Problem setting up dovecot on Debian: "telnet: Unable to connect to remote host: Connection refused" ... some snipped ...
as you can see you daemon ist listening on IP 0.0.0.143 instead 0.0.0.0
1.2.x is really really old
Aha. That's the version that's packaged for Debian squeeze. I assume that's OK for now. I'm not planning to keep it running long.
but i think you missunderstood a listen-option
listen: 143 993 seems to be translated to 0.0.0.143, means you specified the ADDRESS the daemon should listen to instead the port
Aargh!! Idiot me: and the answer was there staring me in the face.
OK. Sorted!
I think I may be back to the list with questions about the best simple way to authenticate logging in. Is there an obvious guide? The documentation that comes with the Debian package seems pretty minimal. I'm just looking to switch on only the encrypted listening on 993 and then use a plain text password. But I'm getting off this thread which is closed and solved.
[SOLVED] - thanks to Harald Reindl - [SOLVED]
Very best to all whose inboxes were burdened!
Chris
On Sat, 2013-01-05 at 17:01 +0100, Reindl Harald wrote:
1.2.x is really really old
It might be old (only deprecated 12 months ago though so not THAT old) but it is very, very, stable (and widely used in large installations and likely will be for some time to come) That said, it is pointless reporting a bug for it if one is found.
Am 06.01.2013 04:47, schrieb Noel Butler:
On Sat, 2013-01-05 at 17:01 +0100, Reindl Harald wrote:
1.2.x is really really old
It might be old (only deprecated 12 months ago though so not THAT old)
i do not know here you work but where i work is a no longer maintained software a no-go
but it is very, very, stable (and widely used in large installations and likely will be for some time to come)
oh yeah, "large installations" is anotehr word for "nobody cares"
That said, it is pointless reporting a bug for it if one is found
that is the point
On Sun, 2013-01-06 at 04:54 +0100, Reindl Harald wrote:
1.2.x is really really old
It might be old (only deprecated 12 months ago though so not THAT old)
i do not know here you work but where i work is a no longer maintained software a no-go
Most places prefer known stability over tinkering techs, the track history of the projects dictates what happens with updates, I stay up to day on stable productions like httpd, php, bind, and postfix, I had that faith in dovecot 1.x, but following the constant near weekly patches in the 2 series early on - no, I don't at this point in time, have faith in 2.0|1's maturity.
That's not a swipe at Timo, trust me, I'll apply the same forensic review on all major version bumps, like bind 10, postfix 3, php 6, mysql 6, and so on.
but it is very, very, stable (and widely used in large installations and likely will be for some time to come)
oh yeah, "large installations" is anotehr word for "nobody cares"
really, I thought it meant SP's with hundreds of thousands, or millions, of users, plenty of them out there ya know who do actually care, and its because they care, they stick with what they consider mature versions of the software.
That said, it is pointless reporting a bug for it if one is found
that is the point
I dont get your point, if it is mature and stable and aint broke, who actually cares?
Personally, I consider 2.1.x more of a risk then 1.2 so I'm sticking with 1.2.17 until there is an urgent and compelling reason to move to 2.1, that's much the same attitude with other admins I speak to on IRC.
Just because something is a current release, does not make it mature software, mature software is stable software that doesn't release often nor need to have patches issued every other week - THAT is what RC's and betas are for.
Noel Butler skrev den 2013-01-06 05:56:
[snip]
Personally, I consider 2.1.x more of a risk then 1.2 so I'm sticking with 1.2.17 until there is an urgent and compelling reason to move to 2.1, that's much the same attitude with other admins I speak to on IRC. [snip]
i have added 1.2.17 to fidonet overlay if others like to keep it in funtoo/gentoo, and i agree dont remove it just becurse of policy
Noel are you using gentoo/funtoo or another problem ?
On Sun, 2013-01-06 at 14:14 +0100, Benny Pedersen wrote:
Noel Butler skrev den 2013-01-06 05:56:
[snip]
Personally, I consider 2.1.x more of a risk then 1.2 so I'm sticking with 1.2.17 until there is an urgent and compelling reason to move to 2.1, that's much the same attitude with other admins I speak to on IRC. [snip]
i have added 1.2.17 to fidonet overlay if others like to keep it in funtoo/gentoo, and i agree dont remove it just becurse of policy
Noel are you using gentoo/funtoo or another problem ?
Nope, all severs are slackware (and I dont have any problem which was my point in earlier thread, no reason why 1.2.17 can't still be suitable for years to come) used to have some gentoo as well, but phased them out to keep everything uniform, and desktops are almost now all opensuse, and once ubuntu stop supporting 10.04 those couple will be converted to opensuse as well (and thats only "then" because I'm too lazy to do it "now" LOL)
I build from sources all key daemon software anyway, package maintainers can only account for so many configurations. Its not so critical with dovecot now since v2, because, regrettably, Timo removed a lot of fine tune config options that allowed us to only build in what we wanted, now, tuff, most the auth methods and stuff must be built even if we dont want them.
But if we absolutely must need a new feature that is in 2.1.x and we can no longer live without it, then and only then will I consider moving to it, otherwise, I'm happy to sit on 1.2 until I consider 2.1 mature and stable enough.
Cheers
Noel Butler skrev den 2013-01-07 03:18:
Nope, all severs are slackware (and I dont have any problem which was my point in earlier thread, no reason why 1.2.17 can't still be suitable for years to come) used to have some gentoo as well, but phased them out to keep everything uniform, and desktops are almost now all opensuse, and once ubuntu stop supporting 10.04 those couple will be converted to opensuse as well (and thats only "then" because I'm too lazy to do it "now" LOL)
:)
i just prefer opensource that is not precompiled as server platform, mostly what is precompiled needs to be recompiled to support what i need anyway, thats why i use gentoo/funtoo/freebsd :=)
and yes i found that opensuse is more nice one to keep as desktop os aswell
I build from sources all key daemon software anyway, package maintainers can only account for so many configurations. Its not so critical with dovecot now since v2, because, regrettably, Timo removed a lot of fine tune config options that allowed us to only build in what we wanted, now, tuff, most the auth methods and stuff must be built even if we dont want them.
shit happens, he does not like opensource then ?, what was a major show stopper for me was the splited config that needs whole new layout to keep the old 1.x style config to work in 2.x, and gentoo infra just ignored my call for help geting it back as long Timo keeps wiki for 1.x
hope it makes sense to other why
But if we absolutely must need a new feature that is in 2.1.x and we can no longer live without it, then and only then will I consider moving to it, otherwise, I'm happy to sit on 1.2 until I consider 2.1 mature and stable enough.
same here, but i try to see how 2.x works here if i get succed with it i properly change to dovecot 2.1 when i build a new server, but change the stable one, no thanks
Noel Butler skrev den 2013-01-06 04:47:
1.2.x is really really old
It might be old (only deprecated 12 months ago though so not THAT old)
it was removed in gentoo recently so now its only 2.x if one still like to use dovecot, for stabalise it could aswell just change to cyrus imapd :=)
with is still in gentoo and opensuse atleast, fun part of opensource is that it gets removed imho to fast just becurse there is no ongoing devolopment, not since its contains bugs or are old, why cant stable software continue to work ?
i have readded dovecot 1.2.17 into local overlay so my mailserver does not break of laziness admins that just want to clean up trees :(
participants (4)
-
Benny Pedersen
-
Chris Evans
-
Noel Butler
-
Reindl Harald