Displaying 20 results from an estimated 1000 matches similar to: "dovecot w/ libwrap on fbsd"
2016 Nov 14
2
dovecot / tcp-wrappers / FBSD 10.3
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:
2016 Dec 30
1
FreeBSD / dovecot 2.2.27 / libwrap
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
2016 Dec 30
1
FreeBSD / dovecot 2.2.27 / libwrap
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
2008 May 25
4
inetd & corrupt environment
Hello. I'm having the following problem with dovecot 1.0.12 and above,
on a FreeBSD 7.0 system - I'm trying to run pop3-login from inetd and I
keep getting this error after authentication:
May 25 09:46:19 charlie dovecot: POP3(gelu): /libexec/ld-elf.so.1:
environment corrupt; missing value for no-nuls oe-ns-eoh
The problem persists if I uncomment the lines with no-nuls oe-ns-eoh in
2010 Mar 07
1
2.0 beta 3 w/o libwrap?
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
2016 Nov 14
0
dovecot / tcp-wrappers / FBSD 10.3
# 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
2013 Jul 03
1
tcpwrappers
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
2020 Aug 21
2
RHEL7/CentOS7 RPM of dovecot 2.3.11.3-3 seems to have dropped tcpwrap support
> On 21/08/2020 08:48 Peter <peter at pajamian.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
>
2013 Apr 05
3
Configuring dovecot to use tcp wrappers
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 =
2013 Apr 05
3
Configuring dovecot to use tcp wrappers
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 =
2011 Feb 09
4
Domain blacklisting
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
2020 Aug 21
2
RHEL7/CentOS7 RPM of dovecot 2.3.11.3-3 seems to have dropped tcpwrap support
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
2017 Jul 13
5
passwd-file, getting invalid uid 0
Per my earlier post about system and virtual users, I have everything working, but I'm seeing the
following message, and wondering:
1) does it matter?
2) is there a way to suppress it?
I have an Exim /etc/aliases entry that sends root to me.
Jul 13 14:38:47 thebighonker dovecot: auth-worker(13055): Error: passwd-file /etc/passwd: User root has invalid UID '0'
doveconf -n:
# 2.2.31
2017 Dec 25
2
Sieve 0.5.0/Dovecot 2.3.0
Using 2.3.0/0.5 and the below scripts/config, why doesn?t a mail addressed to ler_freebsd at lerctr.org get the FreeBSD flag?
.dovecot.sieve points to master.sieve.
Scripts:
http://www.lerctr.org/~ler/sieve/
doveconf -n:
thebighonker.lerctr.org /home/ler/sieve $ doveconf -n
# 2.3.0 (c8b89eb): /usr/local/etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.0 (d68c23a1)
# OS: FreeBSD
2017 Dec 25
3
Sieve 0.5.0/Dovecot 2.3.0
Updated (current) doveconf -n attached....
On Mon, Dec 25, 2017 at 04:33:16PM -0600, Larry Rosenman wrote:
> FTR, this is being delivered via LMTP from Exim using the recommended transport / director.
>
> headers from one of my tests:
> Return-Path: <ler at lerctr.org>
> Delivered-To: ler at lerctr.org
> Received: from thebighonker.lerctr.org
> by
2020 Aug 20
2
RHEL7/CentOS7 RPM of dovecot 2.3.11.3-3 seems to have dropped tcpwrap support
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
2010 Feb 25
2
dovecot-2.0.beta3 tcpwrapper support in Solaris
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
2019 Sep 08
1
Subscribe to a fileinto :create mailbox?
Is it possible in pigeonhole?
I.E. I do a fileinto :create "some/mail/box"
How can I make it autosubscribe?
doveconf -n:
# 2.3.7.2 (3c910f64b): /usr/local/etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.7.2 (7372921a)
# OS: FreeBSD 12.0-STABLE amd64
# Hostname: thebighonker.lerctr.org
auth_default_realm = lerctr.org
auth_mechanisms = plain login
auth_realms = lerctr.org
2017 Jul 18
1
passwd-file, getting invalid uid 0
Did you miss the part about 0 also being hardcoded?
On Tue, Jul 18, 2017 at 1:34 PM Larry Rosenman <larryrtx at gmail.com> wrote:
> 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
2017 Jul 18
1
passwd-file, getting invalid uid 0
# Valid UID range for users, defaults to 500 and above. This is mostly
# to make sure that users can't log in as daemons or other system users.
# Note that denying root logins is hardcoded to dovecot binary and can't
# be done even if first_valid_uid is set to 0.
#first_valid_uid = 500
#last_valid_uid = 0
Aki
> On July 18, 2017 at 9:23 PM Larry Rosenman <larryrtx at gmail.com>