Displaying 20 results from an estimated 10000 matches similar to: "Running dovecot proxy as different user"
2019 Dec 04
2
Rootless wiki page is not up to date?
If I run a docker image with the mesos containerizer and altering the
dovecot config mentioned here[1]
I think the root detection is incorrect because it looks like dovecot is
still thinking it is root. I still get errors like:
>> log(829825): Fatal: We couldn't drop root group privileges
(wanted=10053(dovecot), gid=0(root), egid=0(root))
Why does it want to drop to root, if we
2019 Dec 30
0
Issue running Dovecot in Docker Container
I'm not using internal logging. I'm running the docker with the logging to
the host.
I have used the same options you have specified.
The problem is that the below processes are not running inside docker
container whereas the standalone dovecot is running these processes(meaning
without container)
dovecot-Dovecot/auth
dovecot-Dovecot/ssl-params
dovecot-Director/lmtp
2009 Jul 07
0
rsync-3.0.6 regression test problems
Hi,
I've build rsync-3.0.6 on a number of legacy unix systems, and on a few
systems the regression tests showed up with some errors:
HP-UX 11.11 and 11.23 (ia64):
FAIL chown
FAIL dir-sgid
FAIL fuzzy
FAIL itemize
IRIX 6.5.13m:
FAIL chown
FAIL fuzzy
FAIL itemize
MacOS-X 10.4:
FAIL chgrp
the errors on "fuzzy" and "itemize" are
2019 Dec 30
0
Issue running Dovecot in Docker Container
Aki, This image doesn't have a director service, just the dovecot is
running.
Marc, I'm running the docker container in a privileged mode and it doesn't
seem to have any issues reaching out to the outside network. I will try
running with default config and see what fails.
Thanks & Regards,
Naveen
On Mon, Dec 30, 2019 at 4:16 PM Aki Tuomi <aki.tuomi at open-xchange.com>
2019 Nov 11
2
Login/director not created
But if in the configuration of the director is stated login/director.
Than I assume this socket should be in the login dir not? You have also
the director activate with executable = imap-login director?
-----Original Message-----
Subject: Re: Login/director not created
On my install the login/ dir is:
drwxr-x--- 2 root dovenull 8 Nov 10 18:14:00 login/
srw-rw-rw- 1 root
2019 Dec 30
2
Issue running Dovecot in Docker Container
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
You could also try our docker images, see
<a href="https://hub.docker.com/u/dovecot">https://hub.docker.com/u/dovecot</a>
</div>
<div>
<br>
</div>
<div>
Aki
</div>
<blockquote
2019 Dec 30
0
Issue running Dovecot in Docker Container
If you are running your container as root. You will not have the issues
I encountered. Dovecot is dropping to the 'dovecot' and 'dovenull'(?)
when needed, this is fine.
PS. I would not recommend using internal logging, use something like
this to log to the host or remote syslog.
docker run -v /dev/log:/dev/log -it dovecot-proxy
-----Original Message-----
Subject: Re: Issue
2001 Apr 22
1
relaxing access rights verifications
Hello,
I was trying to build a chrooted sftp account when I faced a problem. The
chroot is done with the patch present in the contrib subdirectory in the
portable version (I'm under linux slackware current).
My problem is that verifying access rights on directories and files are too
tight and then I couldn't have the following things :
The user sftp, with primary group sftp, is chrooted
2001 Jun 05
2
a bug? (PR#968)
--T4sUOijqQbZv57TR
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Dear R,
I would like to report what I think is a bug in R. I am running R
within emacs on a Digital AlphaStation. See the version information
at the end of my R session for details. I also attach a copy of the
file that is read in the `read.table' command.
Here's my R session, with a few
2019 Nov 11
0
Login/director not created
I too assume this socket should be in the login dir.
I am suggesting that maybe the socket is not being created because of
permissions.
Therefore if you explicitly set { group = dovenull } you may fix the
permissions issue.
I am not running director in my setup, just pointing out what jumped out
at me.
On 11/11/2019 1:24 PM, Marc Roos via dovecot wrote:
>
> But if in the configuration
2018 Oct 16
0
Fatal: setgid, imap connections dropped.
I'm still trying to fix this problem. Hopefully someone can help.
I've upgraded dovecot to 2.3.3
# dovecot --version
2.3.3 (dcead646b)
That didn't help.
Next I switched 10-auth.conf to use a local password file (instead of LDAP)
=======================================
# cache all authentication results for one hour
auth_cache_size = 10M
auth_cache_ttl = 1 hour
2019 Nov 22
1
chown(/var/dovecot/login/ipc-proxy
Can we remove/change this in the source? So we do not have to add the
CAP_CHOWN with containers.
chown(/var/dovecot/login/ipc-proxy)
When run as root this has user dovenull, maybe this can be resolved by
using a group dovenull?
bash-5.0# ls -arlt
total 4
srw-rw-rw- 1 root root 0 Nov 21 22:27 pop3
srw-rw-rw- 1 root root 0 Nov 21 22:27 login
srw-------
2012 Sep 07
1
dovecot/log not running
I'm running 2.1.7 as downloaded/installed by Debian (and
then appropriately setup for my config, ...). It almost
works. I can send/receive email from thunderbird, squirrelmail, ...
However there are two anomalies:
1. dovecot/log is not running. After restarting dovecot (and waiting
30 seconds), I have this in the log files:
Sep 6 17:42:16 hinch4 dovecot: master: Dovecot v2.1.7 starting up
2020 Jan 02
0
dovecot cannot drop privileges inside singularity container
Have you tried setting linux capabilities, like
NET_BIND_SERVICE,CHOWN,SYS_CHROOT,SETGID? Have you checked the
permissions of paths? I had to relocate the run dir with things like
these
&& mkdir /var/dovecot \
&& mkdir /var/lib/dovecot \
&& (umask 027 ; mkdir /var/dovecot/login) \
&& (umask 022 ; mkdir /var/dovecot/empty) \
&& (umask
2011 Jan 12
2
Problem after migration dovecot 1.2 -> dovecot 2.0
I have migrated from dovecot 1.2 to dovecot 2.0. When I connect via
telnet to 110 port of the dovecot server the client hangs:
telnet 192.168.4.80 110
Trying 192.168.4.80...
/Connected to 192.168.4.80.
Escape character is '^]'./
In syslog I got the following error:
/Jan 12 12:14:44 buzon dovecot: imap-login: Error: auth: connect(login)
in directory / failed: Permission denied
2019 Aug 26
0
non-terminating processes
On 23.8.2019 17.19, Randy Bush via dovecot wrote:
> FreeBSD psg.com 11.3-RELEASE-p3 FreeBSD 11.3-RELEASE-p3
> dovecot 2.3.6 (7eab80676) (latest from binary package system)
>
> symptom: multiple imap4s users complain that they can not fetch mail
>
> stopping and restarting dovecot is a temporary workaround
>
> dovenull 3713 0.0 0.0 11036 6816 - I 02:27
2018 Sep 28
2
Fatal: setgid, imap connections dropped.
Hi,
I'm getting errors with my IMAP setup.
Basically, everything seems to work.
Mail is delivered nicely from Postfix to Dovecot via LMTP. Dovecot does
the authentication to LDAP (also for Postfix). Users are able to send mail
via authenticated submission (Postfix) and login into IMAP and POP.
However, IMAP connections are dropped frequently with an "ERROR:
Connection dropped by IMAP
2020 Jan 14
0
Upgrade 2.2.27 to 2.3.9.2: master(imap): net_connect_unix(imap) failed: Resource temporarily unavailable
We are unfortunately still seeing a lot of these errors once the machine
reaches a high number of concurrent users/logins (just below 20k
simultaneous IMAP connections on a powerful 24 core machine with 128GB RAM):
2020-01-14T09:18:58.661349+01:00 dovecot: imap-login: Warning:
net_connect_unix(imap) succeeded only after retrying - took 140330 us
2020-01-14T09:18:58.854692+01:00 dovecot:
2020 Jan 08
0
Upgrade 2.2.27 to 2.3.9.2: master(imap): net_connect_unix(imap) failed: Resource temporarily unavailable
With proctitles below.
Strangely, Dovecot is reporting 12679 imap-login sockets in "pre-login"
state, which is about 50% more than there are active TCP connections to
the server (8271, of which 7546 are in "imap-login" process according to
`ss -tp`).
On another server, not currently experiencing this issue, the number of
TCP sockets appears to more closely match the
2019 Nov 11
0
Login/director not created
On my install the login/ dir is:
drwxr-x--- 2 root dovenull 8 Nov 10 18:14:00 login/
srw-rw-rw- 1 root dovenull 0 Nov 10 18:14:00 login/dns-client=
srw-rw-rw- 1 root dovenull 0 Nov 10 18:14:00 login/imap=
srw------- 1 dovenull dovenull 0 Nov 10 18:14:00 login/ipc-proxy=
srw-rw-rw- 1 root dovenull 0 Nov 10 18:14:00 login/login=
srw-rw-rw- 1 root dovenull 0 Nov