similar to: tcpwraper errors with v2.3.9.3

My system was working fine with version 2.3.9.2.? I upgraded to 2.3.9.3 and I am getting tcpwraper errors: > imap-login: Error: connect(tcpwrap) failed: No such file or directory Here's my config: > login_access_sockets = tcpwrap > > service tcpwrap { > ? unix_listener login/tcpwrap { > ??? group = $default_login_user > ??? mode = 0600 > ??? user =

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

# 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, 2016 at 11:45 AM, Jim Pazarena

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 aware

I have auto-subscribe turned on, but I had to doveadm mailbox subscribe to a LDA/Sieve created mailbox today. Did something break? doveconf -n attached. FreeBSD dovecot-2.3.9.3 Secure, fast and powerful IMAP and POP3 server dovecot-pigeonhole-0.5.9_1 Sieve plugin for the Dovecot 'deliver' LDA and LMTP -- Larry Rosenman http://www.lerctr.org/~ler

Hello, we want to use dovecot LMTP for efficient mail delivery from our MX servers (running postfix 2.8) to our storage servers (dovecot 2.0.17). However, the one problem we see is the lack of access control when using LMTP. It apears that every client in our network who has access to the storage machines can drop a message in a Maildir of any user on that storage server. To prevent this

Dovecot with 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

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

Greetings, I am looking to implement tcp wrappers with dovecot; I am using the following two 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 =

Greetings, I am looking to implement tcp wrappers with dovecot; I am using the following two 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 =

Stupid copypaste... can you do the change manually, it fails on tabs vs. spaces errors now. We'll get the commit out bit later. Aki > On April 11, 2017 at 8:29 PM Bobber <bobber at kc0dxf.net> wrote: > > > Not working: > > > patching file userdb-vpopmail.c > > Hunk #1 FAILED at 54. > > 1 out of 1 hunk FAILED -- saving rejects to file

Not working: > patching file userdb-vpopmail.c > Hunk #1 FAILED at 54. > 1 out of 1 hunk FAILED -- saving rejects to file userdb-vpopmail.c.rej -------- Original Message -------- Subject: Re: Vpopmail Error From: Aki Tuomi <aki.tuomi at dovecot.fi> To: dovecot at dovecot.org, Bobber <bobber at kc0dxf.net> Date: 04/11/2017 12:13 PM > diff --git

I'm seeing the following: Jun 5 11:10:52 thebighonker dovecot: imap(ler): Error: fts_solr: received invalid uid '0' Is there something I can get for you to debug? doveconf -n: # 2.2.30.1 (eebd877): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.18 (29cc74d) # OS: FreeBSD 11.1-PRERELEASE amd64 auth_debug_passwords = yes auth_default_realm = lerctr.org auth_mechanisms

Can anyone share the proper config to 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:

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 following logged error message: 20161229 17:02:49

I'm getting lots of: Jun 30 14:41:34 thebighonker dovecot: imap(ler/14135): Error: fts_solr: received invalid uid '0' in my logs. Ideas? doveconf -n: # 2.2.31 (65cde28): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.19 (e5c7051) # OS: FreeBSD 11.1-BETA2 amd64 auth_default_realm = lerctr.org auth_mechanisms = plain login auth_realms = lerctr.org

I'm getting a lot of: Jun 16 11:40:40 thebighonker dovecot: imap(ler/58755): Error: fts_solr: received invalid uid '0' Jun 16 11:40:40 thebighonker dovecot: imap(ler/58755): Error: fts_solr: received invalid uid '0' in my logs. What can I supply to help get to the bottom of it? doveconf -n: # 2.2.30.2 (c0c463e): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version

On Tue, Jul 18, 2017 at 3:31 PM, Larry Rosenman <larryrtx at gmail.com> wrote: > That didn't change it :( > Jul 18 15:28:14 thebighonker dovecot: auth-worker(77908): Error: > passwd-file /etc/passwd: User root has invalid UID '0' > Jul 18 15:28:14 thebighonker dovecot: auth-worker(77908): Error: > passwd-file /etc/passwd: User toor has invalid UID '0' >

thebighonker.lerctr.org /home/ler $ doveadm -D -v index \#ARCHIVE/2015/01/INBOX doveadm(ler): Debug: Loading modules from directory: /usr/local/lib/dovecot doveadm(ler): Debug: Module loaded: /usr/local/lib/dovecot/lib20_fts_plugin.so doveadm(ler): Debug: Module loaded: /usr/local/lib/dovecot/lib21_fts_lucene_plugin.so doveadm(ler): Debug: Module loaded:

Anyone? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: larryrtx at gmail.com US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 On 7/13/17, 2:42 PM, "Larry Rosenman" <larryrtx at gmail.com> wrote: Per my earlier post about system and virtual users, I have everything working, but I'm seeing the