similar to: ACL problems on shared folder

Displaying 20 results from an estimated 6000 matches similar to: "ACL problems on shared folder"

2017 May 31
0
shared folder and private index file problems
Hello, I'm using Dovecot 2.2.30 with Pideonhole 0.4.18 and I'm having some problems, perhaps someone can give an hint on how to solve them. When I try to create a folder in the toplevel directory of a shared mailbox, i get a "permission denied" although I have the rights, example: 1.doveadm -f table acl rights -u bob at example.com shared/bill at example.com Rights lookup
2018 Jun 06
1
Shared mailboxes, index files and 'per-user-seen' flags
Hello, i have a dovecot server version 2.3.1 under CentOS 6.9 and we're using shared mailboxes with index files shared. With this configuration I can see a lot of error messages like: Jun 6 13:20:31 mail dovecot: Error: imap(userA at tutech.de)<4513> <onjjWPdtDuLAqG3R>: /export/home/imap/userA at tutech.de/shared /userB at tutech.de/folder/dovecot.index.pvt view is
2017 Nov 10
0
rawlog segfaults (error 4 in libdovecot.so.0.0.0)
rawlog files are plain text, readable files. you do not need to dump them with doveadm. can you get gdb "bt full" for the core file? Aki On 10.11.2017 11:35, T. Robers wrote: > Hello everybody, > > i tried to debug imap sessions with the rawlog feature and rawlog > creates files but when i try to dump them doveadm tells me > [...] Error: zlib.read((file)): unexpected EOF
2018 Jan 23
0
Panic: data stack: Out of memory when allocating bytes
On Tue, Jan 23, 2018 at 18:21:38 +0100, Thomas Robers wrote: > Hello, > > I'm using Dovecot 2.3 and sometimes i get this: > > --- snip --- > Jan 23 14:23:13 mail dovecot: imap(bob at tutech.de)<4880><PDqibHFjMvrAqG1n>: > Panic: data stack: Out of memory when allocating 134217768 bytes Interesting... imap is trying to allocate 128MB and failing. A couple of
2017 Nov 10
3
rawlog segfaults (error 4 in libdovecot.so.0.0.0)
Hello everybody, i tried to debug imap sessions with the rawlog feature and rawlog creates files but when i try to dump them doveadm tells me [...] Error: zlib.read((file)): unexpected EOF at [...]. I looked at syslog files and i see, that rawlog gets terminated with a segfault, e.g.: segfault at 10 ip 00007ff6da362596 sp 00007fffe725a080 error 4 in libdovecot.so.0.0.0[7ff6da2a4000+122000] Is
2018 Jan 18
1
Panic: file ostream-zlib.c: line 36 (o_stream_zlib_close): assertion failed:
Hi, after updating Dovecot to version 2.3 I get a lot of core-dumps like: > Jan 18 10:08:20 mail dovecot: imap(bob at tutech.de)<18200><CIPhNwljJcdYS/hg>: Panic: file ostream-zlib.c: line 36 (o_stream_zlib_close): assertion failed: (zstream->ostream.finished || > zstream->ostream.ostream.stream_errno != 0) > Jan 18 10:08:20 mail dovecot: imap(bob at
2018 Jan 23
2
Panic: data stack: Out of memory when allocating bytes
Hello, I'm using Dovecot 2.3 and sometimes i get this: --- snip --- Jan 23 14:23:13 mail dovecot: imap(bob at tutech.de)<4880><PDqibHFjMvrAqG1n>: Panic: data stack: Out of memory when allocating 134217768 bytes Jan 23 14:23:13 mail dovecot: imap(bob at tutech.de)<4880><PDqibHFjMvrAqG1n>: Fatal: master: service(imap): child 4880 killed with signal 6 (core dumped)
2018 Jan 23
2
Panic: data stack: Out of memory when allocating bytes
On Tue, Jan 23, 2018 at 14:03:27 -0500, Josef 'Jeff' Sipek wrote: > On Tue, Jan 23, 2018 at 18:21:38 +0100, Thomas Robers wrote: > > Hello, > > > > I'm using Dovecot 2.3 and sometimes i get this: > > > > --- snip --- > > Jan 23 14:23:13 mail dovecot: imap(bob at tutech.de)<4880><PDqibHFjMvrAqG1n>: > > Panic: data stack: Out of
2017 Jun 16
0
Error: fts_solr: received invalid uid '0'?
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
2014 Oct 27
1
Dovecot 2.2.14 and per user \Seen flags
Hello, I have a Dovecot Installation Version 2.2.14 on CentOS 6.5 with shared folder. UserA shares his INBOX to user UserB. I activated "per user \Seen flags" with location = maildir:%%h/Maildir:INDEX=%h/shared/%%u:CONTROL=%h/shared/%%u:INDEXPVT=%h/shared I think the INDEXPVT setting activates this setting, right? I activated this setting when there were already several accounts in
2017 Nov 13
0
ACL on shared folder
Hello everybody, we're using shared mailboxes as an archive to which everyone has full rights, set with doveadm. The rights look like this: doveadm acl get -u bob at example.com shared/archive at example.com ID Global Rights user=bob at example.com admin create delete expunge insert lookup \ post read write write-deleted write-seen Looking at
2018 Feb 09
1
Shared folders and quota
Hi all, we are able to observe a very strange behaviour: User A wants to copy a mail to a shared mailbox of user B. This works like a charme if the quota of user A is lower than the used space of user B. But is the used space of user B higher than the quota size of User A, "User A" is not longer able to copy the message to the shared folder of user B. His IMAP Client says something
2017 Nov 19
2
Sieve coding question
On 11/16/17 11:03 AM, Stephan Bosch wrote: > Op 11/16/2017 om 7:42 PM schreef lists.dovecot at rogerklorese.com: >> Is there a more appropriate list on which to ask for assistance in >> coding Sieve rules, or may I ask here? > I know of no other suitable venue, so go ahead. > > Regards, > > Stephan. Here is the config. I don't think IMAPsieve is configured... #
2017 Jun 19
1
core dump on ocfs2
Hi everybody I'm finding on my server a lot of a lot of errors like this: Jun 19 14:22:45 posta2 kernel: [885017.412902] BUG: soft lockup - CPU#2 stuck for 22s! [dovecot-lda:11955] Jun 19 14:22:45 posta2 kernel: [885017.412906] Modules linked in: ocfs2(E) jbd2 quota_tree dm_service_time dm_multipath ocfs2_dlmfs(E) ocfs2_stack_o2cb(E) ocfs2_dlm( E) ocfs2_nodemanager(E)
2017 Jun 22
1
Trouble after Upgrade to v2.2.30.2 missing value for DOVECOT_
Hi, I keep getting these errors after upgraded to 2.2.30.2. I can't seems to find what is going on. This is running a Freebsd 10.3-RELEASE-p11 :( Can someone please assist ? Jun 22 14:45:23 starlite2 dovecot: auth: Debug: Loading modules from directory: /usr/local/lib/dovecot/auth Jun 22 14:45:23 starlite2 dovecot: auth: Debug: Module loaded:
2017 Jun 04
0
SIG11/Auth/FreeBSD
On Fri, Jun 02, 2017 at 11:15:41AM -0500, Larry Rosenman wrote: > I'm seeing lots of: [snipped] > Jun 2 00:00:05 thebighonker exim[57437]: dovecot_login authenticator failed for ec2-52-40-16-7.us-west-2.compute.amazonaws.com (ADM > IN) [52.40.16.7]:51339 I=[192.147.25.65]:465: 535 Incorrect authentication data (set_id=web) > Jun 2 00:00:06 thebighonker exim[57439]: dovecot_login
2018 Jan 25
1
dovecot Digest, Vol 177, Issue 55
No reason to tell me about security, I just need chmod for my tests. Where to change it ? On Thu, Jan 25, 2018 at 12:00 PM, <dovecot-request at dovecot.org> wrote: > Send dovecot mailing list submissions to > dovecot at dovecot.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://dovecot.org/mailman/listinfo/dovecot > or, via email,
2017 Jun 06
3
v2.2.30.1 released
On 06/05/2017 11:05 AM, Angel L. Mateo wrote: > I have updated my dovecot proxy servers from 2.2.28 to 2.2.30. Since the upgrade I'm having the error: > > Jun 5 10:54:51 musio12 dovecot: auth: Fatal: master: service(auth): child 63632 killed with signal 11 (core not dumped) > > Me too, with # 2.2.30.1 (eebd877): /opt/dovecot/etc/dovecot/dovecot.conf # Pigeonhole
2017 Jun 05
0
fts_solr: uid0?
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
2018 Jan 29
1
Panic: data stack: Out of memory when allocating bytes
Any idea what the problem could be? Is there anything more i could do to encircle the problem? Or perhaps is the information i provided uncomplete? Am 25.01.2018 um 16:24 schrieb Thomas Robers: > Hi, > > Am 24.01.2018 um 23:39 schrieb Josef 'Jeff' Sipek: >> It looks like the binaries are stripped.? There should be a "debug" >> package >> you can