Re: Debug: open(/proc/self/io) failed: Permission denied

Hi, On Mon, Apr 24, 2023 at 1:34 PM Aki Tuomi wrote: > You can get rid of the debug message with > > import_environment = $import_environment PR_SET_DUMPABLE=2 > > or setting > > sysctl fs.suid_dumpable=2 > Thanks so much - that appears to have fixed it. What does that do, and any idea why it

Re: Debug: open(/proc/self/io) failed: Permission denied

<2977522>: Debug: Module loaded: > /usr/lib64/dovecot/lib20_listescape_plugin.so > imap(bcc-user)<2977522>: Debug: Effective uid=1001, > gid=1001, home=/home/bcc-user > imap(bcc-user)<2977522>: Debug: open(/proc/self/io) failed: > Permission denied > imap(bcc-user)<297

Debug: open(/proc/self/io) failed: Permission denied

t imap(bcc-user)<2977522>: Debug: Module loaded: /usr/lib64/dovecot/lib20_listescape_plugin.so imap(bcc-user)<2977522>: Debug: Effective uid=1001, gid=1001, home=/home/bcc-user imap(bcc-user)<2977522>: Debug: open(/proc/self/io) failed: Permission denied imap(bcc-user)<2977522>

Re: Error: Mailbox INBOX: file_dotlock_create in directory /var/mail failed: Permission denied

On Mon, Jan 16, 2023 at 1:34 PM manmatha wrote: > Hi All, > > We are running Round cube on top of dovecot and postfix as our email echo > system. Main problem we are facing is that, roundcube loads really slow for > big inboxes (~5000 emails). I found that, while it loads, imap process goes >

Error: Mailbox INBOX: file_dotlock_create in directory /var/mail failed: Permission denied

dovecot: imap(xyz)<361270>: Error: unlink(/var/mail/xyz.lock) failed: Permission denied (in file-dotlock.c:195) Jan 16 15:36:13 roundcube-internal-server-1 dovecot: imap(xyz)<361270>: Error: unlink(xyz.lock) failed: Permission denied (in file-dotlock.c:195) Jan 16 15:36:13 roundc

Re: Permission denied UNIX perms appear ok (ACL/MAC wrong?))

16><1NieGKPmuOdKwxVI>: Error: Mailbox INBOX: >>>> stat(/mnt/volume1/mailserver/plain/maildir/domain.com/user/dovecot.index.log >>>> <http://domain.com/user/dovecot.index.log> >>>> <http://domain.com/user/dovecot.index.log >>>> <h

Re: Permission denied UNIX perms appear ok (ACL/MAC wrong?))

If you are running gocryptfs with Dovecot, you need to ensure that Dovecot has access to the files even when you are not logged in. Perhaps gocryptfs is blocking access to processes not originating from your session? Aki > On 31/08/2022 07:14 EEST Austin Witmer wrote: > > > No, I am

Re: Permission denied UNIX perms appear ok (ACL/MAC wrong?))

No, I am manually mounting it when I start my server. I then start dovecot. Austin Witmer > On Aug 30, 2022, at 9:40 PM, pe...@chubb.wattle.id.au wrote: > >  >> >> "Austin" == Austin Witmer writes: > > > Austin> So, the location of my mail storage > Austin>

Re: Permission denied UNIX perms appear ok (ACL/MAC wrong?))

> "Austin" == Austin Witmer writes: Austin> So, the location of my mail storage Austin> (/mnt/volume1/mailserver/plain/maildir/%d/%n/) is a filesystem Austin> mounted by gocryptfs. Do you think gocryptfs could be at fault Austin> here? Is it automounted? I've seen issues where dovecot

Re: Permission denied UNIX perms appear ok (ACL/MAC wrong?))

See below . . . > On Aug 30, 2022, at 1:41 PM, spi wrote: > > > > Am 30.08.22 um 20:43 schrieb Austin Witmer: >> I’m am still getting the errors I mentioned previously. Maybe half a dozen >> of them per day . . . >> >> So, the location of my mail storage >>

Re: Permission denied UNIX perms appear ok (ACL/MAC wrong?))

Am 30.08.22 um 20:43 schrieb Austin Witmer: I’m am still getting the errors I mentioned previously. Maybe half a dozen of them per day . . . So, the location of my mail storage (/mnt/volume1/mailserver/plain/maildir/%d/%n/) is a filesystem mounted by gocryptfs. Do you think gocryptfs could be

Re: Permission denied UNIX perms appear ok (ACL/MAC wrong?))

;> On Aug 20, 2022, at 11:15 AM, spi >> <mailto:s...@nurfuerspam.de>> wrote: >>> >>>  >>>> Am 20.08.22 um 16:52 schrieb Austin Witmer: >>>> Hello all! >>>> >>>> Recently I upgraded my mail server to Ubuntu 22.04 LTS

Re: Permission denied UNIX perms appear ok (ACL/MAC wrong?))

user::rwx > group::rwx > other::r-- > > Austin Witmer > > On Aug 20, 2022, at 11:15 AM, spi wrote: > >  > > Am 20.08.22 um 16:52 schrieb Austin Witmer: > Hello all! > > Recently I upgraded my mail server to Ubuntu 22.04 LTS and ever since > then I am

Re: Permission denied UNIX perms appear ok (ACL/MAC wrong?))

gt;>> Aug 20 14:41:58 mail dovecot: >>> imap(u...@domain.com)<56316><1NieGKPmuOdKwxVI>: Error: Mailbox INBOX: >>> stat(/mnt/volume1/mailserver/plain/maildir/domain.com/user/dovecot.index.log >>> <http://domain.com/user/dovecot.index.log>) fail

Re: Permission denied UNIX perms appear ok (ACL/MAC wrong?))

t;1NieGKPmuOdKwxVI>: Error: Mailbox INBOX: >>> stat(/mnt/volume1/mailserver/plain/maildir/domain.com/user/dovecot.index.log >>> <http://domain.com/user/dovecot.index.log>) failed: Permission denied >>> (euid=1000(austin) egid=1000(austin) UNIX perms appear

Re: Permission denied UNIX perms appear ok (ACL/MAC wrong?))

: >> imap(u...@domain.com)<56316><1NieGKPmuOdKwxVI>: Error: Mailbox INBOX: >> stat(/mnt/volume1/mailserver/plain/maildir/domain.com/user/dovecot.index.log >> <http://domain.com/user/dovecot.index.log>) failed: Permission denied >> (euid=1000(austin) eg

Re: Permission denied UNIX perms appear ok (ACL/MAC wrong?))

<56316><1NieGKPmuOdKwxVI>: Error: Mailbox INBOX: >> stat(/mnt/volume1/mailserver/plain/maildir/domain.com/user/dovecot.index.log >> <http://domain.com/user/dovecot.index.log>) failed: Permission denied >> (euid=1000(austin) egid=1000(austin) UNIX perms appear ok (ACL/

Re: Permission denied UNIX perms appear ok (ACL/MAC wrong?))

1/mailserver/plain/maildir/domain.com/user/dovecot.index.log >> <http://domain.com/user/dovecot.index.log>) failed: Permission denied >> (euid=1000(austin) egid=1000(austin) UNIX perms appear ok (ACL/MAC >> wrong?)) >> >> And here is the listing showing the permissions

Re: Permission denied UNIX perms appear ok (ACL/MAC wrong?))

/mnt/volume1/mailserver/plain/maildir/domain.com/user/dovecot.index.log <http://domain.com/user/dovecot.index.log>) failed: Permission denied (euid=1000(austin) egid=1000(austin) UNIX perms appear ok (ACL/MAC wrong?)) And here is the listing showing the permissions for that file. *austin@mail*

Re: Permission denied UNIX perms appear ok (ACL/MAC wrong?))

mail dovecot: imap(u...@domain.com)<56316><1NieGKPmuOdKwxVI>: Error: Mailbox INBOX: stat(/mnt/volume1/mailserver/plain/maildir/domain.com/user/dovecot.index.log <http://domain.com/user/dovecot.index.log>) failed: Permission denied (euid=1000(austin) egid=1000(austin) UNIX perms

Re: Permission denied UNIX perms appear ok (ACL/MAC wrong?))

dovecot: >>> imap(u...@domain.com)<56316><1NieGKPmuOdKwxVI>: Error: Mailbox INBOX: >>> stat(/mnt/volume1/mailserver/plain/maildir/domain.com/user/dovecot.index.log >>> <http://domain.com/user/dovecot.index.log>) failed: Permission denied >&g

Re: Permission denied UNIX perms appear ok (ACL/MAC wrong?))

dovecot: >>> imap(u...@domain.com)<56316><1NieGKPmuOdKwxVI>: Error: Mailbox INBOX: >>> stat(/mnt/volume1/mailserver/plain/maildir/domain.com/user/dovecot.index.log >>> <http://domain.com/user/dovecot.index.log>) failed: Permission denied >&g

Re: Permission denied UNIX perms appear ok (ACL/MAC wrong?))

t/volume1/mailserver/plain/maildir/domain.com/user/dovecot.index.log >> <http://domain.com/user/dovecot.index.log>) failed: Permission denied >> (euid=1000(austin) egid=1000(austin) UNIX perms appear ok (ACL/MAC wrong?)) >> >> And here is the listing showing the permissio

Re: Permission denied UNIX perms appear ok (ACL/MAC wrong?))

:58 mail dovecot: imap(u...@domain.com)<56316><1NieGKPmuOdKwxVI>: Error: Mailbox INBOX: stat(/mnt/volume1/mailserver/plain/maildir/domain.com/user/dovecot.index.log <http://domain.com/user/dovecot.index.log>) failed: Permission denied (euid=1000(austin) egid=1000(austin) UN

Permission denied UNIX perms appear ok (ACL/MAC wrong?))

ain.com>)<56316><1NieGKPmuOdKwxVI>: Error: Mailbox INBOX: > stat(/mnt/volume1/mailserver/plain/maildir/domain.com/user/dovecot.index.log > <http://domain.com/user/dovecot.index.log>) failed: Permission denied > (euid=1000(austin) egid=1000(austin) UNIX perms a

Permission denied UNIX perms appear ok (ACL/MAC wrong?))

316><1NieGKPmuOdKwxVI>: Error: Mailbox INBOX: stat(/mnt/volume1/mailserver/plain/maildir/domain.com/user/dovecot.index.log) failed: Permission denied (euid=1000(austin) egid=1000(austin) UNIX perms appear ok (ACL/MAC wrong?)) And here is the listing showing the permissions for that file.

Re: Stats-writer permission denied

> On 04/01/2022 08:04 Ken Wright wrote: > > > I've got a new Dovecot error (well, new to me, at least)! > > I ran tail /var/log/mail.err and got the following: > > net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission > denied > > I checke

Stats-writer permission denied

I've got a new Dovecot error (well, new to me, at least)! I ran tail /var/log/mail.err and got the following: net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission denied I checked the file, and it's owned by www-data and the www-data group, with read and write permissions

Re: Permission denied

On Thu, 2021-12-30 at 00:20 +0100, Christian Kivalo wrote: > The override.conf goes to /etc/systemd/system/dovecot.service.d/ to > be included. > Issue systemctl daemon-reload before restarting dovecot. > systemctl cat dovecot.service shows you the content of the involved > conf files Tried this,

Re: Permission denied

On 2021-12-29 17:51, Ken Wright wrote: On Wed, 2021-12-29 at 18:34 +0200, Aki Tuomi wrote: > On 29/12/2021 18:09 Ken Wright wrote: >   > On Wed, 2021-12-29 at 09:51 +0200, Aki Tuomi wrote: > > > > > On 29/12/2021 05:22 Ken Wright wrote: > > > > > > Any further information available upon

Re: Permission denied

On Wed, 2021-12-29 at 18:34 +0200, Aki Tuomi wrote: > > > On 29/12/2021 18:09 Ken Wright wrote: > >   > > On Wed, 2021-12-29 at 09:51 +0200, Aki Tuomi wrote: > > > > > > > On 29/12/2021 05:22 Ken Wright wrote: > > > > > > > > Any further information available upon request! > > > > > > Maybe

Re: Permission denied

> On 29/12/2021 18:09 Ken Wright wrote: > > > On Wed, 2021-12-29 at 09:51 +0200, Aki Tuomi wrote: > > > > > On 29/12/2021 05:22 Ken Wright wrote: > > > > > > Any further information available upon request! > > > > Maybe systemd is blocking it? > > > > If systemd unit has

Re: Permission denied

On Wed, 2021-12-29 at 09:51 +0200, Aki Tuomi wrote: > > > On 29/12/2021 05:22 Ken Wright wrote: > > > > Any further information available upon request! > > Maybe systemd is blocking it? > > If systemd unit has ProtectSystem=strict or ProtectSystem=full, try > adding override.conf with > >

Re: Permission denied

t; Dec 28 22:05:02 grace dovecot: > lmtp(m...@mydomain.com)<910309>: Error: lmtp- > server: conn unix:pid=906625,uid=117 [6]: rcpt m...@mydomain.com: Mailbox > INBOX: > open(/var/mail/vmail/m...@mydomain.com/tmp/1640747102.M850878P910309.grac > ) failed: Permission denied >

Permission denied

id=117 [6]: rcpt m...@mydomain.com: Mailbox INBOX: open(/var/mail/vmail/m...@mydomain.com/tmp/1640747102.M850878P910309.grac ) failed: Permission denied Any further information available upon request!

Strange error on multiple recipent email - permission denied

lmtp(user2)<1518>: lmtp-server: conn unix:pid=1517,uid=0 [1]: rcpt user2: msgid=: saved mail to INBOX Mar 27 00:35:04 mx2 dovecot[1473]: lmtp(user1)<1518>: Error: lmtp-server: conn unix:pid=1517,uid=0 [1]: rcpt user2: stat(/var/spool/mail/user2/.imap/INBOX/dovecot.index.log) failed: Permis

Re: net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission denied

I just ignore it? Still makes me wonder way it would happen at all..? MJ On 10/22/20 12:53 PM, mj wrote: > Hi, > > We are getting very occasional messags from dovecot: > >> net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission denied > > Over the last we

Re: net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission denied

unning fine > otherwise, should I just ignore it? > > Still makes me wonder way it would happen at all..? > > MJ > > On 10/22/20 12:53 PM, mj wrote: > > Hi, > > > > We are getting very occasional messags from dovecot: > > > >> net_conne

Re: net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission denied

/dovecot/stats-writer) failed: Permission denied Over the last week, the message appeared five times. (on a mail server with over 100 users, to that's basically almost never) doveconf -n below # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.0-10

net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission denied

Hi, We are getting very occasional messags from dovecot: net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission denied Over the last week, the message appeared five times. (on a mail server with over 100 users, to that's basically almost never) doveconf -n below # 2.3.4.1

Re: Dovecot permission denied errors on NFS after upgrade to 2.2.17

It seems that upgrading kernel from 4.9.0 to 4.19.0 fixed the problem. Thanks for your help On 24/09/20 14:31, Claudio Corvino wrote: Hi, this sound correct, here is my fstab entry: /XXX.XXX.XXX.XXX:/mail-storage    /mnt/mail-storage nfs     defaults,timeo=30                0   0/

Re: Dovecot permission denied errors on NFS after upgrade to 2.2.17

Hi, this sound correct, here is my fstab entry: /XXX.XXX.XXX.XXX:/mail-storage    /mnt/mail-storage nfs defaults,timeo=30                0   0/ Here are my options when doing "mount":

Re: Dovecot permission denied errors on NFS after upgrade to 2.2.17

On 21 Sep 2020, at 01:48, Claudio Corvino wrote: > problem still occurring, I just noticed that if I do an "ls -l > /mnt/mail-storage//Maildir/cur/" from the Dovecot server I can unblock > the mailbox of the user and Thunderbird can receives all the e-mails. > > The problem occurs even with

Re: Dovecot permission denied errors on NFS after upgrade to 2.2.17

m) failed: Permission denied (euid=501(vmail) egid=501(vmail) missing +r perm: /mnt/mail-storage/XXX/Maildir/cur/1594641298.M607225P10899.XXX,S=4465,W=4534:2,m stat(/mnt/mail-storage/XXX/Maildir/cur/1594641298.M607225P10899.XXX,S=4465,W=4534:2,m) failed: Permission denied)/ SElinux is not

Re: Dovecot permission denied errors on NFS after upgrade to 2.2.17

.XXX,S=4465,W=4534:2,m) failed: Permission denied (euid=501(vmail) egid=501(vmail) missing +r perm: /mnt/mail-storage/XXX/Maildir/cur/1594641298.M607225P10899.XXX,S=4465,W=4534:2,m stat(/mnt/mail-storage/XXX/Maildir/cur/1594641298.M607225P10899.XXX,S=4465,W=4534:2,m) failed: Permission denied

Re: Dovecot permission denied errors on NFS after upgrade to 2.2.17

Strange behavior but after a reboot of the Dovecot server, the error disappeared from logs (like Windows style! :-)). I'll monitor the situation and take you updated in case it should come back. Thanks all! On 13/07/20 20:27, John Stoffel wrote: "Mark" == Mark Moseley writes: Mark> This

Re: Dovecot permission denied errors on NFS after upgrade to 2.2.17

> "Mark" == Mark Moseley writes: Mark> This is just me throwing things out to look at, but did the Mark> client mount on the old server use NFS3 and the new upgraded Mark> client uses NFS4? Sometimes that can cause weirdness with id Mark> mapping.  Another thing to check is selinux, is it

Re: Dovecot permission denied errors on NFS after upgrade to 2.2.17

d on the NFS client side on Debian, > but I don't think so as aptlistchanges didn't notify me about it, nor if > Dovecot 2.2.17 treat NFS in other way. > > I'm stuck. > > On 13/07/20 16:07, Jochen Bern wrote: > > On 07/13/2020 03:45 PM, Claudio Corvino wrote: > >> in ad

Re: Dovecot permission denied errors on NFS after upgrade to 2.2.17

about it, nor if Dovecot 2.2.17 treat NFS in other way. I'm stuck. On 13/07/20 16:07, Jochen Bern wrote: On 07/13/2020 03:45 PM, Claudio Corvino wrote: in addition the "permission denied" error is random, most of the time Dovecot works well. In *that* case, I'd say that UID/GID mappin

Re: Dovecot permission denied errors on NFS after upgrade to 2.2.17

Hi Jochen, the ID has not changed, in addition the "permission denied" error is random, most of the time Dovecot works well. How can I check the mappings NFS uses? After the Debian upgrade I was using these NFS mount options: rw,user,rsize=8192,wsize=8192,timeo=30,intr Now try

Dovecot permission denied errors on NFS after upgrade to 2.2.17

Hi everyone, we just upgraded our mail server from Debian 8 to Debian 9, so our dovecot packages just got upgraded from version 2.2.13 to 2.2.17. Now we have a lot of errors in our dovecot.log about permission denied (our Mailboxes are on NFS remote server since years without problems) like

lmtp report permission denied on delivery to multiple recipients

$MSGID$>: saved mail to INBOX May 22 11:06:11 sinon dovecot[44304]: lmtp($USER2$)<119718><2HnmOgIR5Vym0wEA22L5Rg:2>: Error: stat(/IMAP/mail/mailboxes/$USER1$/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache) failed: Permission denied (euid=$UID2$($USER2$) egid=$GID2$(rbg

Permission denied

mail dovecot: lda(user@domain)<955>: msgid=<4562sm6yyyzv...@mail.covisp.net>: save failed to INBOX: Mailbox INBOX: open(/usr/local/virtual/user@domain/tmp/1558293345.M130062P955.mail.covisp.net) failed: Permission denied The permissions on /usr/local/virual have not changed and ar

Re: ssl_cert: Can't open file permission denied

‐‐‐ Original Message ‐‐‐ On Wednesday, April 10, 2019 1:08 PM, Michael Orlitzky via dovecot wrote: > On 4/10/19 6:39 AM, Dmitry Donskih via dovecot wrote: > > > `chmod -R 655 /etc/foobar/ssl' drops x attribute from`ssl' itself. > > Use `chmod -R 755' or`chmod +x' or similar. > > Your

Re: ssl_cert: Can't open file permission denied

0.4.2019 12.36, Laura Smith via dovecot wrote: > > > > > > > Dovecot 2.3.3 (dcead646b) > > > > openSUSE Leap 15.0 > > > > I am getting a weird error message: > > > > Fatal: Error in configuration file /etc/dovecot/local.conf line 16: > > >

Re: /var/run/dovecot/stats-writer) failed: Permission denied

> On 10 Apr 2019, at 11:50, Aki Tuomi via dovecot wrote: > > >> On 10 April 2019 20:48 @lbutlr via dovecot wrote: >> >> >> On 10 Apr 2019, at 10:43, @lbutlr via dovecot wrote: >>> lso, the failed message strongly implies that the email was not delivered, >>> since it happens on the

Re: /var/run/dovecot/stats-writer) failed: Permission denied

> On 10 April 2019 20:48 @lbutlr via dovecot wrote: > > > On 10 Apr 2019, at 10:43, @lbutlr via dovecot wrote: > > lso, the failed message strongly implies that the email was not delivered, > > since it happens on the delivery log line and there is not indication in > > the log that

Re: /var/run/dovecot/stats-writer) failed: Permission denied

On 10 Apr 2019, at 10:43, @lbutlr via dovecot wrote: > lso, the failed message strongly implies that the email was not delivered, > since it happens on the delivery log line and there is not indication in the > log that delivery succeeded. However, the message is delivered. It might be > worth

Re: /var/run/dovecot/stats-writer) failed: Permission denied

On 10 Apr 2019, at 10:55, Remo Mattei via dovecot wrote: > This is what fixed mine > > service stats { > # unix_listener stats-reader { > # group = > # mode = 0666 > # user = > # } > unix_listener stats-writer { > group = dovecot > mode = 0666 > user = > } > }

Re: /var/run/dovecot/stats-writer) failed: Permission denied

This is what fixed mine service stats { # unix_listener stats-reader { # group = # mode = 0666 # user = # } unix_listener stats-writer { group = dovecot mode = 0666 user = } } > On Apr 10, 2019, at 09:43, @lbutlr via dovecot wrote: > > On 10 Apr 2019, at

Re: /var/run/dovecot/stats-writer) failed: Permission denied

On Wed, 10 Apr 2019 at 19:44, @lbutlr via dovecot wrote: > On 10 Apr 2019, at 09:06, @lbutlr via dovecot wrote: > > Should I add > > > > service stats { > > unix_listener stats-writer { > > user = dovecot > > } > > unix_listener stats-reader { > > user = dovecot > > } > > } > > >

Re: /var/run/dovecot/stats-writer) failed: Permission denied

On 10 Apr 2019, at 09:06, @lbutlr via dovecot wrote: > Should I add > > service stats { > unix_listener stats-writer { > user = dovecot > } > unix_listener stats-reader { > user = dovecot > } > } > > to my dovecot.conf file? I did this and it appears to have fixed the issue.

Re: /var/run/dovecot/stats-writer) failed: Permission denied

On Wed, 10 Apr 2019 at 18:06, @lbutlr via dovecot wrote: > > > > On 10 Apr 2019, at 08:57, Odhiambo Washington via dovecot < > dovecot@dovecot.org> wrote: > > > > > > > > On Wed, 10 Apr 2019 at 17:50, @lbutlr via dovecot > wrote: > > On 10 Apr 2019, at 08:36, @lbutlr via dovecot > wrote: > > >

Re: /var/run/dovecot/stats-writer) failed: Permission denied

> On 10 Apr 2019, at 08:57, Odhiambo Washington via dovecot > wrote: > > > > On Wed, 10 Apr 2019 at 17:50, @lbutlr via dovecot wrote: > On 10 Apr 2019, at 08:36, @lbutlr via dovecot wrote: > > net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission den)) > > One other detail:

Re: /var/run/dovecot/stats-writer) failed: Permission denied

On Wed, 10 Apr 2019 at 17:50, @lbutlr via dovecot wrote: > On 10 Apr 2019, at 08:36, @lbutlr via dovecot wrote: > > net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission den)) > > One other detail: > > /var/run/dovecot/stats-writer: > 0 srw-rw 1 root dovecot 0 Apr 10

Re: /var/run/dovecot/stats-writer) failed: Permission denied

On 10 April 2019 17:49 @lbutlr via dovecot < dovecot@dovecot.org> wrote: On 10 Apr 2019, at 08:36, @lbutlr via dovecot < dovecot@dovecot.org> wrote: net_connect_unix(/var/run/dovecot/stats-writer) failed:

Re: /var/run/dovecot/stats-writer) failed: Permission denied

On 10 Apr 2019, at 08:36, @lbutlr via dovecot wrote: > net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission den)) One other detail: /var/run/dovecot/stats-writer: 0 srw-rw 1 root dovecot 0 Apr 10 08:47 stats-writer -- "Back off, man. I'm a scientist."

/var/run/dovecot/stats-writer) failed: Permission denied

I am getting this error in logs net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission den)) and I looked around the google results and it seems to be related to using service stats, which I am not using. # doveconf -n | grep stat # doveconf -n | head -3 # 2.3.5.1 (7ec6d0ade):

Re: ssl_cert: Can't open file permission denied

On 4/10/19 6:39 AM, Dmitry Donskih via dovecot wrote: > `chmod -R 655 /etc/foobar/ssl' drops x attribute from `ssl' itself. > Use `chmod -R 755' or `chmod +x' or similar. > Your private keys should be... private. Use 750 instead.

Re: ssl_cert: Can't open file permission denied

Leap 15.0 >>> I am getting a weird error message: >>> Fatal: Error in configuration file /etc/dovecot/local.conf line 16: >>> ssl_cert: Can't open file /etc/foobar/ssl/certbot.pem: Permission denied >>> I have tried the following: >>> >>> - chmo

Re: ssl_cert: Can't open file permission denied

guration file /etc/dovecot/local.conf line 16: ssl_cert: > Can't open file /etc/foobar/ssl/certbot.pem: Permission denied > > I have tried the following: > - chmod -R 655 /etc/foobar/ssl (/etc/foobar is 755) > - create "ssl_users" group add dovecot to it chown -R dovecot:ssl_u

Re: ssl_cert: Can't open file permission denied

etc/dovecot/local.conf line 16: > > ssl_cert: Can't open file /etc/foobar/ssl/certbot.pem: Permission denied > > I have tried the following: > > > > - chmod -R 655 /etc/foobar/ssl (/etc/foobar is 755) > > - create "ssl_users" group add dovecot to it

Re: ssl_cert: Can't open file permission denied

On 10.4.2019 12.36, Laura Smith via dovecot wrote: > Dovecot 2.3.3 (dcead646b) > openSUSE Leap 15.0 > > I am getting a weird error message: > > Fatal: Error in configuration file /etc/dovecot/local.conf line 16: ssl_cert: > Can't open file /etc/foobar/ssl/certbot.pem: Pe

ssl_cert: Can't open file permission denied

Dovecot 2.3.3 (dcead646b) openSUSE Leap 15.0 I am getting a weird error message: Fatal: Error in configuration file /etc/dovecot/local.conf line 16: ssl_cert: Can't open file /etc/foobar/ssl/certbot.pem: Permission denied I have tried the following: - chmod -R 655 /etc/foobar/ssl (/etc/foobar

permission denied errors with INDEX=MEMORY and trees plugin

@octet.space)<21780>: Error: Mailbox INBOX: Saving mail: read(/var/vmail/octet.space/john/Maildir/tmp/1551030180.M508113P21780.toaster.octet.space) failed: Permission denied (read reason=header Subject (Cache file is unusable)) It's like it's trying to read the message after it's been del

Re: Troubles with Dovecot 2.3.3 - mkdir permission denied due to +w perm: /var, dir owned by 0:0 mode=0755)

a dovecot: > > > Error: mkdir(/var/vmail/ema...@example.com/Maildir) failed: Permission > > denied (euid=5000(vmail) egid=5000(vmail) missing +w perm: /var, dir > owned > > by 0:0 mode=0755) > > The error message seems pretty clear. User 'vmail' does not have write > per

Re: Troubles with Dovecot 2.3.3 - mkdir permission denied due to +w perm: /var, dir owned by 0:0 mode=0755)

* Kunal A. via dovecot: > Error: mkdir(/var/vmail/ema...@example.com/Maildir) failed: Permission > denied (euid=5000(vmail) egid=5000(vmail) missing +w perm: /var, dir owned > by 0:0 mode=0755) The error message seems pretty clear. User 'vmail' does not have write permissions for /v

Troubles with Dovecot 2.3.3 - mkdir permission denied due to +w perm: /var, dir owned by 0:0 mode=0755)

mputer dovecot[4872]: imap-login: Login: user=< ema...@example.com>, method=PLAIN, rip=::1, lip=::1, mpid=4878, secured, session= Feb 22 08:55:14 computer dovecot[4872]: imap(ema...@example.com)<4878>: Error: mkdir(/var/vmail/ema...@example.com/Maildir) failed: Permission denied (euid=500

Error: connect(ipc-proxy) failed: Permission denied

Hello: We have got 2 directors and three backend mailbox servers. I get the following error " Error: connect(ipc-proxy) failed: Permission denied". I have read the article https://www.dovecot.org/list/dovecot/2012-August/137349.html and we have done as signaled in the two direct

Doveadm sync: Can't create mailbox mail_public/public: Permission denied if synchronize all the available namespaces

ublic/public: Permission denied." Config dumps, logs in attaches. # 2.3.1 (c5a5c0c82): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.devel (61b47828) # OS: Linux 4.14.47-5.el7xen.x86_64 x86_64 CentOS Linux release 7.5.1804 (Core) auth_cache_negative_ttl = 0 auth_cache_size = 1 k auth_cach

Re: stats-writer failed: Permission denied

/run/dovecot/stats-writer) failed: Permission denied Feb 07 11:16:35 aldebaran dovecot[7455]: imap: Error: net_connect_unix(/usr/local/var/run/dovecot/stats-writer) failed: Permission denied I can change the owner and/or permissions of the file, than it works till the next reboot. How can i

stats-writer failed: Permission denied

Hi there! Since i compile my own dovecot (not using dovecot from debian), i get this error on each startup dovecot with systemd Feb 07 11:16:35 aldebaran dovecot[7455]: imap: Error: net_connect_unix(/usr/local/var/run/dovecot/stats-writer) failed: Permission denied Feb 07 11:16:35 aldebaran

Re: Initialization failed: Namespace '': mkdir(/var/www/mail) failed: Permission denied

t;: On October 26, 2017 at 5:40 PM tr...@skrilnetz.net wrote:   Quoting Steffen Kaiser <skdove...@smail.inf.fh-brs.de>: On Thu, 26 Oct 2017, tr...@skrilnetz.net wrote: /dovecot: lda(www-data): Error: user www-data: Initialization failed: Namespace '': MKDIR(/VAR/WWW/MAIL) failed: Permis

Re: Initialization failed: Namespace '': mkdir(/var/www/mail) failed: Permission denied

017, tr...@skrilnetz.net wrote: > >>> > >>> /dovecot: lda(www-data): Error: user www-data: Initialization > >>> failed: Namespace '': MKDIR(/VAR/WWW/MAIL) failed: Permission > >>> denied (euid=33(www-data) egid=33(www-data) missing +w p

Re: Initialization failed: Namespace '': mkdir(/var/www/mail) failed: Permission denied

2017 at 5:40 PM tr...@skrilnetz.net wrote:   Quoting Steffen Kaiser <skdove...@smail.inf.fh-brs.de>: On Thu, 26 Oct 2017, tr...@skrilnetz.net wrote: /dovecot: lda(www-data): Error: user www-data: Initialization failed: Namespace '': MKDIR(/VAR/WWW/MAIL) failed: Permission denied (euid=33(www-data) e

Re: Initialization failed: Namespace '': mkdir(/var/www/mail) failed: Permission denied

gt;> > >> On October 26, 2017 at 5:40 PM tr...@skrilnetz.net wrote: > >> > >>   Quoting Steffen Kaiser <skdove...@smail.inf.fh-brs.de>: > >> > >> On Thu, 26 Oct 2017, tr...@skrilnetz.net wrote: > >> > >> /dovecot: lda(www-data): E

Re: Initialization failed: Namespace '': mkdir(/var/www/mail) failed: Permission denied

l.inf.fh-brs.de>: On Thu, 26 Oct 2017, tr...@skrilnetz.net wrote: /dovecot: lda(www-data): Error: user www-data: Initialization failed: Namespace '': MKDIR(/VAR/WWW/MAIL) failed: Permission denied (euid=33(www-data) egid=33(www-data) missing +w perm: /var/www, dir owned by 1001:1001 mode=0755

Re: Initialization failed: Namespace '': mkdir(/var/www/mail) failed: Permission denied

u, 26 Oct 2017, tr...@skrilnetz.net wrote: /dovecot: lda(www-data): Error: user www-data: Initialization failed: Namespace '': MKDIR(/VAR/WWW/MAIL) failed: Permission denied (euid=33(www-data) egid=33(www-data) missing +w perm: /var/www, dir owned by 1001:1001 mode=0755//)  / I did some troublesh

Re: Initialization failed: Namespace '': mkdir(/var/www/mail) failed: Permission denied

t;: > >> > >> On Thu, 26 Oct 2017, tr...@skrilnetz.net wrote: > >> > >> /dovecot: lda(www-data): Error: user www-data: Initialization > >> failed: Namespace '': MKDIR(/VAR/WWW/MAIL) failed: Permission > >> denied (euid=33(www-data) e

Re: Initialization failed: Namespace '': mkdir(/var/www/mail) failed: Permission denied

d: Namespace '': MKDIR(/VAR/WWW/MAIL) failed: Permission denied (euid=33(www-data) egid=33(www-data) missing +w perm: /var/www, dir owned by 1001:1001 mode=0755//)  / I did some troubleshooting and I don't understand where the MKDIR(/VAR/WWW/MAIL) is coming from. Mailboxes are in /var/mail and ^^ /var/m

Re: Initialization failed: Namespace '': mkdir(/var/www/mail) failed: Permission denied

> >> failed: Namespace '': MKDIR(/VAR/WWW/MAIL) failed: Permission > >> denied (euid=33(www-data) egid=33(www-data) missing +w perm: > >> /var/www, dir owned by 1001:1001 mode=0755//)  / > >> > >> I did some troubleshooting and I don't unde

Re: Initialization failed: Namespace '': mkdir(/var/www/mail) failed: Permission denied

Quoting Steffen Kaiser <skdove...@smail.inf.fh-brs.de>: On Thu, 26 Oct 2017, tr...@skrilnetz.net wrote: /dovecot: lda(www-data): Error: user www-data: Initialization failed: Namespace '': MKDIR(/VAR/WWW/MAIL) failed: Permission denied (euid=33(www-data) egid=33(www-data) missing +

Re: Initialization failed: Namespace '': mkdir(/var/www/mail) failed: Permission denied

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 26 Oct 2017, tr...@skrilnetz.net wrote: /dovecot: lda(www-data): Error: user www-data: Initialization failed: Namespace '': MKDIR(/VAR/WWW/MAIL) failed: Permission denied (euid=33(www-data) egid=33(www-data) missing +w perm: /var/www, dir

Initialization failed: Namespace '': mkdir(/var/www/mail) failed: Permission denied

Hi, I'm running dovecot (v 2.2.9) on ubuntu 14.04 since a long time. I did not change any configuration lately and I'm getting the below error message. /dovecot: lda(www-data): Error: user www-data: Initialization failed: Namespace '': MKDIR(/VAR/WWW/MAIL) failed: Permission denied

Re: Permission denied error on private key...

rtificate for the replication server, and I cannot get >>>> dovecot to start up. Keep getting: >>>> >>>> doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf >>>> line 31: ssl_key: Can't open file /etc/pki/dovecot/private/mail

Re: Permission denied error on private key...

t open file /etc/pki/dovecot/private/mailserver.crt: Permission denied Different permissions on the mailserver.crt have no effect on the error. Maybe something I did in creating the file? I’m a little fuzzy when it comes to how you’re supposed to create the whole thing. Here are the steps

Re: Permission denied error on private key...

ed >> certificate for the replication server, and I cannot get dovecot to start >> up. Keep getting: >> >> doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line >> 31: ssl_key: Can't open file /etc/pki/dovecot/private/mailserver.crt: >> Pe

Re: Permission denied error on private key...

: Permission denied Different permissions on the mailserver.crt have no effect on the error. Maybe something I did in creating the file? I’m a little fuzzy when it comes to how you’re supposed to create the whole thing. Here are the steps I took: openssl genrsa -out mailserverkey.crt 2048 I then took

Permission denied error on private key...

to start up. Keep getting: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 31: ssl_key: Can't open file /etc/pki/dovecot/private/mailserver.crt: Permission denied Different permissions on the mailserver.crt have no effect on the error. Maybe something I did

Re: logins fail for virtual users (permission denied, we're not in group 5000)

> On Sep 16, 2017, at 5:05 PM, Paul Schreiber wrote: > > Followup: > > Received help on serverfault.com. Fix was to edit 10-master.conf. In the > service auth { … } section, setting either: > extra_groups = vmail > or > group = vmail > …allows things to

  1   2   3   4   >