Displaying 20 results from an estimated 3000 matches similar to: "RHEL7/CentOS7 RPM of dovecot 2.3.11.3-3 seems to have dropped tcpwrap support"
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
>
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
2020 Aug 21
0
RHEL7/CentOS7 RPM of dovecot 2.3.11.3-3 seems to have dropped tcpwrap support
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
2020 Aug 21
0
RHEL7/CentOS7 RPM of dovecot 2.3.11.3-3 seems to have dropped tcpwrap support
>>>> 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?
2020 Aug 21
0
RHEL7/CentOS7 RPM of dovecot 2.3.11.3-3 seems to have dropped tcpwrap support
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
2017 Dec 29
2
dovecot-pigeonhole problems after upgrade to v2.3.0
Am 29.12.2017 um 15:08 schrieb Fabian A. Santiago:
> December 28, 2017 6:38 PM, "Peter" <peter at pajamian.dhs.org> wrote:
>
>> On 29/12/17 10:00, Fabian A. Santiago wrote:
>>
>>> i've now completely uninstalled all traces of dovecot and reinstalled
>>> from your repo and still the same issue persists with the same
>>> errors.
2013 Mar 03
1
tcpwrap: Fatal: master: service(tcpwrap): child $PID killed with signal 11
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
2017 Dec 28
5
dovecot-pigeonhole problems after upgrade to v2.3.0
December 28, 2017 2:52 PM, "Fabian A. Santiago" <fsantiago at garbage-juice.com> wrote:
> December 28, 2017 1:21 PM, "Aki Tuomi" <aki.tuomi at dovecot.fi> wrote:
>
>>> On December 28, 2017 at 7:43 PM "Fabian A. Santiago" <fsantiago at garbage-juice.com> wrote:
>>>
>>> December 28, 2017 12:14 PM, "Aki
2020 Aug 23
2
doveadm/doveconf as user tries and fails to read host key
Distro: OpenSuSE Tumbleweed for x86_64
Failing version: dovecot23-2.3.11.3-1.1.x86_64 Install Date: 2020-08-18
Reverting to previous version works: dovecot23-2.3.10.1-2.3.x86_64
(Packages downgraded coordinately: dovecot23 dovecot23-backend-sqlite)
How to make it fail: As the user, execute
doveadm expunge mailbox Spam37 savedbefore 3day #User's actual cmd
doveadm who #The simplest
2020 Jul 08
6
Urgent Help required
Thank you for the reply.
As per our current infrastructure, I can go maximum of the redhat 7.7
version. Not more than that. Am I able to install or upgrade to dovecot 2.3
version in redhat 7.7?
I have another question. I understand redhat 6.10 will go out of support in
november 2020. But this is a test environment. Am i able to install dovecot
2.3 version on redhat 6.10? For the Live support, I
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
2020 Aug 13
2
2.3.11.3 on 32bit platforms
HI!
I'm trying to update openSUSE package on OBS [1] which builds for
various OS versions and hardware platforms. To me it seems that a test
fails on 32bit platforms:
Info: invalid token 3: structure length disagrees with data size
test rpa ..................................... : ok
Info: invalid NTLM response: buffer length out of bounds
test ntlm ............................: ok
1 / 86
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
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:
2011 Aug 29
1
dovecot w/ libwrap on fbsd
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
2010 Mar 25
1
Dovecot 2.0beta4
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 solve by touching and
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
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
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
2017 Jan 05
4
CDB tables in Centos7 Postfix ?
Hi,
It seems the default binaries don't have CDB tables compiled into them ?
Now, I know Centos isn't Ubuntu, but on Ubuntu there is an optional
package in the main distribution "postfix-cdb - CDB map support for
Postfix". I can't find anything similar using "yum search", so I'm
guessing that's not an option.
Unless anyone else here corrects me