[Dovecot] dovecot 2.x via xinetd
Hello,
I was using dovecot 1.2.x via xinetd with a setup like http://wiki.dovecot.org/InetdInstall
Since I upgraded to Debian Wheezy, shipping dovecot 2.x, it no longer works. At best, I end up with stuff like
Error: net_connect_unix(anvil) failed: No such file or directory
Fatal: Couldn't connect to anvil
Any clues? Regards,
(add me in Cc in replies, I'm not suscribed to the list)
# doveconf -n # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-3-amd64 x86_64 Debian wheezy/sid ext4 mail_location = maildir:/home/%n/.Maildir:LAYOUT=fs mail_privileged_group = mail namespace inbox { inbox = yes location = prefix = } passdb { driver = pam } protocols = " imap" ssl_cert =
-- Mathieu Roy
On 22.7.2012, at 14.46, Mathieu Roy wrote:
Hello,
I was using dovecot 1.2.x via xinetd with a setup like http://wiki.dovecot.org/InetdInstall
Since I upgraded to Debian Wheezy, shipping dovecot 2.x, it no longer works. At best, I end up with stuff likeError: net_connect_unix(anvil) failed: No such file or directory Fatal: Couldn't connect to anvil
Any clues? Regards,
(add me in Cc in replies, I'm not suscribed to the list)
Doesn't work anymore. No plans to make it work anymore. Way too much trouble.
Le dimanche 22 juillet 2012, Timo Sirainen a écrit :
On 22.7.2012, at 14.46, Mathieu Roy wrote:
Hello,
I was using dovecot 1.2.x via xinetd with a setup like http://wiki.dovecot.org/InetdInstall
Since I upgraded to Debian Wheezy, shipping dovecot 2.x, it no longer works. At best, I end up with stuff likeError: net_connect_unix(anvil) failed: No such file or directory Fatal: Couldn't connect to anvil
Any clues? Regards,
(add me in Cc in replies, I'm not suscribed to the list)
Doesn't work anymore. No plans to make it work anymore. Way too much trouble.
Is there any way to make dovecot aware of hosts.deny and hosts.allow?
Thanks for your reply, Regards,
-- Mathieu Roy
On 23.7.2012, at 4.37, Mathieu Roy wrote:
I was using dovecot 1.2.x via xinetd with a setup like http://wiki.dovecot.org/InetdInstall
Since I upgraded to Debian Wheezy, shipping dovecot 2.x, it no longer works. At best, I end up with stuff likeDoesn't work anymore. No plans to make it work anymore. Way too much trouble.
Is there any way to make dovecot aware of hosts.deny and hosts.allow?
If you've compiled with tcpwrappers, you can do:
login_access_sockets = tcpwrap
On 7/23/2012 5:54 AM, Mathieu Roy wrote:
Le lundi 23 juillet 2012, Timo Sirainen a écrit :
If you've compiled with tcpwrappers, you can do:
login_access_sockets = tcpwrap
I use debian stock version, I'll check that and recompile if need be.
Debian stable has Dovecot 1.2.15, and I don't see 2.x in backports. Yet you're discussing 2.x. You must be using testing which has 2.1.7. In which case using the word "stock" isn't quite appropriate, as it implies the stable branch. You should have explicitly stated which branch you're using to avoid confusion.
-- Stan
On 23.07.2012 13:23, wrote Stan Hoeppner:
On 7/23/2012 5:54 AM, Mathieu Roy wrote:
Le lundi 23 juillet 2012, Timo Sirainen a écrit :
If you've compiled with tcpwrappers, you can do:
login_access_sockets = tcpwrap
I use debian stock version, I'll check that and recompile if need be.
Debian stable has Dovecot 1.2.15, and I don't see 2.x in backports. Yet you're discussing 2.x. You must be using testing which has 2.1.7. In which case using the word "stock" isn't quite appropriate, as it implies the stable branch. You should have explicitly stated which branch you're using to avoid confusion.
2.1.7 is indeed in backports
On 7/23/2012 6:52 AM, e-frog wrote:
On 23.07.2012 13:23, wrote Stan Hoeppner:
On 7/23/2012 5:54 AM, Mathieu Roy wrote:
Le lundi 23 juillet 2012, Timo Sirainen a écrit :
If you've compiled with tcpwrappers, you can do:
login_access_sockets = tcpwrap
I use debian stock version, I'll check that and recompile if need be.
Debian stable has Dovecot 1.2.15, and I don't see 2.x in backports. Yet you're discussing 2.x. You must be using testing which has 2.1.7. In which case using the word "stock" isn't quite appropriate, as it implies the stable branch. You should have explicitly stated which branch you're using to avoid confusion.
2.1.7 is indeed in backports
Good catch e-frog. I stand (partially) corrected. Indeed it is in backports. I hadn't done an aptitude update for a while, though it hasn't been more than a month, so this is very new. Debian doesn't provide a package inclusion date...
I say "partially" because Backports packages don't really fall under the term "stock" either.
-- Stan
participants (4)
-
e-frog
-
Mathieu Roy
-
Stan Hoeppner
-
Timo Sirainen