search for: tcpwrap

Using the Repo http://repo.dovecot.org/ce-2.3-latest after upgrading from 2.3.10.1-3 to 2.3.11.3-3 we get numerous error messages like: dovecot: imap-login: Error: connect(tcpwrap) failed: No such file or directory We use tcpwrap support in dovecot, which worked flawlessly in the older version. I can see that the socket /var/run/dovecot/login/tcpwrap is not created anymore. And comparing with RPMs, the new one seems to be missing the file: /usr/libexec/dovecot/tcpwrap whi...

Hi Timo, today I've started Dovecot v2.2.rc2 (976bf9e69367) for the first time. /var/log/mail.log: Mar 3 14:28:33 mail dovecot: master: Dovecot v2.2.rc2 (976bf9e69367) starting up Mar 3 14:28:38 mail dovecot: master: Error: service(tcpwrap): command startup failed, throttling for 2 secs Mar 3 14:28:38 mail dovecot: tcpwrap: Fatal: master: service(tcpwrap): child $PID killed with signal 11 (core dumped) Mar 3 14:28:38 mail dovecot: imap-login: Error: read(tcpwrap) failed: Connection reset by peer Mar 3 14:28:38 mail dovecot: imap-l...

...n.dhs.org> wrote: > > > On 20/08/20 11:02 pm, Thomas Scheunemann wrote: > > Using the Repo http://repo.dovecot.org/ce-2.3-latest after upgrading from > > 2.3.10.1-3 to 2.3.11.3-3 we get numerous error messages like: > > > > dovecot: imap-login: Error: connect(tcpwrap) failed: No such file or directory > > > > We use tcpwrap support in dovecot, which worked flawlessly in the older version. > > I can see that the socket /var/run/dovecot/login/tcpwrap is not created anymore. > > And comparing with RPMs, the new one seems to be missing the...

It works ! It was THAT easy ! Can you suggest how to replace the hair I pulled out ? :-) On 2016-12-29 5:27 PM, Larry Rosenman wrote: > login_access_sockets = tcpwrap > > service tcpwrap { > unix_listener login/tcpwrap { > group = $default_login_user > mode = 0600 > user = $default_login_user > } > } > > > > On Thu, Dec 29, 2016 at 7:21 PM, Jim Pazarena <dovecot at paz.bz> wrote: > >> I have...

On 20/08/20 11:02 pm, Thomas Scheunemann wrote: > Using the Repo http://repo.dovecot.org/ce-2.3-latest after upgrading from > 2.3.10.1-3 to 2.3.11.3-3 we get numerous error messages like: > > dovecot: imap-login: Error: connect(tcpwrap) failed: No such file or directory > > We use tcpwrap support in dovecot, which worked flawlessly in the older version. > I can see that the socket /var/run/dovecot/login/tcpwrap is not created anymore. > And comparing with RPMs, the new one seems to be missing the file: > > /us...

...get wrappers working in dovecot on FreeBSD? The dovecot examples do not seem to work, and I thought perhaps FBSD needs slightly different configs. I've compiled with: -DHAVE_LIBWRAP which I presume is the first step. The example for dovecot.conf in uncommenting: login_access_sockets = tcpwrap merely causes a log error of "imap-login: Error: connect(tcpwrap) failed: No such file or directory" Suggestions/Direction much appreciated.

On Fri, Aug 21, 2020 at 06:02:49PM +1200, Peter wrote: > On 21/08/20 5:55 pm, Aki Tuomi wrote: > > > At a guess it was removed from the spec for el8 (which does not support > > > tcpwrap) and somehow got removed from el7 by accident. The ghettoforge > > > dovecot23 packages have tcpwrap support for el7: So is el8 truly incompatible with tcpwrap? Or is it just too much effort to continue suport for every feature that was ever in the system? If the former, might it be r...

I have compiled dovecot2 for FreeBSD with the tcpwrap option. A tcpwrap binary gets built and resides in the FreeBSD directory /usr/local/libexec/dovecot an examination of the compiled options (using the FreeBSD pkg install dovecot2) confirms: LIBWRAP : on yet, when I adjust dovecot.conf with: login_access_sockets = tcpwrap I get the followin...

Hello, I run dovecot-2/Maildir/LDAP user/passdb and would like to be able to deny acess to users who connect from certain domains/IP (google.com for instance since in that case they gave their credentials to a third party). My understanding is that I cannot use some negative form of "allow_nets". The only mechanism I can think of is tcp_wrappers. However, dovecot documentation mention

>>>> At a guess it was removed from the spec for el8 (which does not support >>>> tcpwrap) and somehow got removed from el7 by accident. The ghettoforge >>>> dovecot23 packages have tcpwrap support for el7: > > So is el8 truly incompatible with tcpwrap? Or is it just too much > effort to continue suport for every feature that was ever in the system? https://acc...

On 21/08/20 5:55 pm, Aki Tuomi wrote: >> At a guess it was removed from the spec for el8 (which does not support >> tcpwrap) and somehow got removed from el7 by accident. The ghettoforge >> dovecot23 packages have tcpwrap support for el7: > > We are looking into this, it was indeed removed from el7 by accident. RPM macros can be quite tricky sometimes. I have: %if 0%{?rhel} < 8 BuildRequires: tcp_wrap...

I'm trying to kickstart 2.0b3 on my NetBSD system (where 1.2.x works great!), and keep hitting: Fatal: service(tcpwrap) access(/software/dovecot-2.0beta3/libexec/dovecot/tcpwrap) failed: No such file or directory Indeed, that file doesn't exist...but I don't have nor want libwrap. It appears that doveconf includes tcpwrap... service tcpwrap { chroot = client_limit = 1 drop_priv_before_exec =...

Hello, It seems dovecot 2.0 beta4 still behave strangely without tcpwrap. I still get the errors: 2010-03-25_17:26:59.33848 Fatal: service(tcpwrap) access(/opt/dovecot/libexec/dovecot/tcpwrap) failed: No such file or directory 2010-03-25_17:27:00.36108 Fatal: service(tcpwrap) access(/opt/dovecot/libexec/dovecot/tcpwrap) failed: Permission denied It's easy to sol...

...libwrap doesn't work on FreeBSD for some reason or another. I have these lines in my /etc/hosts.allow: ALL: LOCAL 127.0.0.1: allow pop3: ALL: allow ALL: ALL: deny Yet when you try to telnet to localhost, port 110 this is what happens: Aug 29 22:48:38 dodo dovecot: pop3-login: Error: connect(tcpwrap) failed: Permission denied I also tried auth_debug=yes to see what's wrong but it only shows the processes which handled the connection, no extra info with the reason why it failed. Here's the config: # 2.0.13: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 7.4-RELEASE i386? auth_mec...

# Space separated list of login access check sockets (e.g. tcpwrap) #login_access_sockets = login_access_sockets = tcpwrap service tcpwrap { unix_listener login/tcpwrap { group = $default_login_user mode = 0600 user = $default_login_user } } I believe that's all. I had placed it all in /usr/local/etc/dovecot/dovecot.conf. On Mon, Nov 14,...

hi everybody having I believe sort of plain-vanilla config with section in 10-tcpwrapper.conf as per docs login_access_sockets = tcpwrap service tcpwrap { unix_listener login/tcpwrap { group = $default_login_user mode = 0600 user = $default_login_user } } /etc/hosts.deny contains: ALL: given_host and yet dovecot logins IMAP client in whereas other tcpwrapper...

Hi, 2.0 compiles fine in Solaris but and I've found only one glitch so far. Tcpwapper support needs some tweaks. I need to add CPPFLAGS=/usr/sfw/include because tcpd.h is in there. Then also LDFLAGS='-R/usr/sfw/lib -L/usr/sfw/lib' is needed. It would be nice to have --with-tcpwrap-dir or something. After this linking gives an error Undefined first referenced symbol in file deny_severity /usr/sfw/lib//libwrap.so allow_severity /usr/sfw/lib//libwrap.so These are not defined but application itself should define these globally so I've added these to configure and src/util...

Hello, Using the TCP Wrapper Dovecot could control access to IMAP and POP3 servers. Is it also possible to controll access to an LMTP Server listening on Port 24? Andreas

...links as guides to configuration: http://blog.acsystem.sk/linux/brute-force-attack-dovecot-imap-server-blocking-ip-with-tcp-wrappers http://wiki2.dovecot.org/LoginProcess (you need to go to the very bottom) I'm concerned in making the configuration correctly. If you set login_access_sockets = tcpwrap in /etc/dovecot/dovecot.conf Then everything accessing ports controlled by dovecot (and open by iptables) is blocked. So my question relates to the second part of the configuration examples in the links above: service tcpwrap { unix_listener login/tcpwrap { group = $default_login_user...

...links as guides to configuration: http://blog.acsystem.sk/linux/brute-force-attack-dovecot-imap-server-blocking-ip-with-tcp-wrappers http://wiki2.dovecot.org/LoginProcess (you need to go to the very bottom) I'm concerned in making the configuration correctly. If you set login_access_sockets = tcpwrap in /etc/dovecot/dovecot.conf Then everything accessing ports controlled by dovecot (and open by iptables) is blocked. So my question relates to the second part of the configuration examples in the links above: service tcpwrap { unix_listener login/tcpwrap { group = $default_login_user...