On Wed, 2011-07-27 at 15:39 +0200, Kees Lemmens wrote:
> I think I sorted it out : I also had to add a service section to
> dovecot.conf and I had to change the old "imap-login" settings in
> /etc./hosts.allow to be simply "imap" now.
..
> Timo : maybe this could be documented a little better ?
Hi,
I think I sorted it out : I also had to add a service section to
dovecot.conf and I had to change the old "imap-login" settings in
/etc./hosts.allow to be simply "imap" now.
service tcpwrap {
Hi Timo,others,
Adding login_access_sockets = tcpwrap wasn't enough : I also had to
recompile dovecot 2.0.13 with the --with-libwrap option. Then linking
failed as it didn't link with libnsl.so but that was easily fixed.
However, if I try to connect now with tcpwrap switched on I still have a
Hi Timo,
Thanks for the prompt answer ! This solves a large security for me ;-)
Any idea why the inetd path is not working anymore in 2.x or is that
already somewhere else in the list ?
On Wednesday, July 27, 2011, Timo Sirainen wrote:
> On Wed, 2011-07-27 at 14:16 +0200, Kees Lemmens wrote:
>
Hi,
I used dovecot 1.x for quite a while and it worked fine. However, I used it
through inetd and used hosts.allow/deny to restrict access to only certain
groups of systems.
Since yesterday I have dovecot 2.0.13. But in version 2.0.13 it seems that
starting using inetd doesn't work anymore : I
On Wed, 2011-07-27 at 14:16 +0200, Kees Lemmens wrote:
> Since yesterday I have dovecot 2.0.13. But in version 2.0.13 it seems
> that starting using inetd doesn't work anymore : I only get a strange
> error message if I try to connect using telnet :
Yeah, won't work.
> Is dovecot indeed ignoring
