Displaying 20 results from an estimated 14164 matches for "acled".
Did you mean:
acked
2017 Jun 13
2
GPO Problem
Thanks Elias.
But I run samba-tool ntacl sysvolreset and:
root at DC02:~# samba-tool ntacl sysvolreset
lp_load_ex: refreshing parameters
Initialising global parameters
Processing section "[global]"
Processing section "[netlogon]"
Processing section "[sysvol]"
Processing section "[sistemas]"
ldb_wrap open of idmap.ldb
lp_load_ex: refreshing parameters
2019 Mar 07
2
Regression ACL & namespace prefix
Sorry, we have not yet been able to look into this..
It's now in our internal system as DOP-966
Aki
> On 7 March 2019 17:31 Michal Hlavinka via dovecot <dovecot at dovecot.org> wrote:
>
>
> Hi,
> any progress with this issue? Do you need more information to debug and
> fix this?
>
> Cheers
> Michal Hlavinka
>
> On 9/18/18 4:10 PM, Michal Hlavinka
2018 Sep 18
4
Regression ACL & namespace prefix
Hi
tl;dr:
Seems that for Global ACL directory, namespace prefix is not part of the
path, when looking for acl file.
Long version:
We're planning to update dovecot in next os update to 2.2.36 and while
going through regression testing, we found a problem with ACL
configuration combined with namespace.
Test uses "Global ACL directory" configuration.
Relevant configuration part:
2017 Jun 06
2
GPO Problem
2017-06-06 15:54 GMT-03:00 Rowland Penny via samba <samba at lists.samba.org>:
> On Tue, 6 Jun 2017 15:35:42 -0300
> Epsilon Minus via samba <samba at lists.samba.org> wrote:
>
>> Hi. I have a problem applying GPO. I do not know where to look
>> Reviewing I found this:
>>
>> # samba-tool ntacl sysvolcheck
>> lp_load_ex: refreshing parameters
2017 Jun 06
2
GPO Problem
Hi. I have a problem applying GPO. I do not know where to look
Reviewing I found this:
# samba-tool ntacl sysvolcheck
lp_load_ex: refreshing parameters
Initialising global parameters
Processing section "[global]"
Processing section "[netlogon]"
Processing section "[sysvol]"
Processing section "[sistemas]"
ldb_wrap open of idmap.ldb
Module
2019 Mar 12
1
Regression ACL & namespace prefix
Hi,
thanks for the answer. I think your environment was not set up correctly
to reproduce this bug. I've retested with 2.3.5 and I can still
reproduce it. I've attached a script that will configure everything for
testing and if you have a virtual machine available, you can use it
directly (it expects linux with systemd for dovecot restart).
relevant section from config:
namespace {
2017 Jun 15
2
samba-tool ntacl sysvolreset ERROR
This is my smb.conf
root at DC02:~# cat /etc/samba/smb.conf
# Global parameters
[global]
workgroup = CLINICAGUEMES
realm = CLINICAGUEMES.COM.AR
netbios name = DC02
server role = active directory domain controller
server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl,
winbindd, ntp_signd, kcc, dnsupdate
idmap_ldb:use rfc2307 = yes
ldap server require strong
2017 Jun 13
0
GPO Problem
>
> onnect_acl_xattr: setting 'inherit acls = true' 'dos filemode = true' and
> 'force unknown acl user = true' for service Unknown Service (snum == -1)
> connect_acl_xattr: setting 'inherit acls = true' 'dos filemode = true' and
> 'force unknown acl user = true' for service Unknown Service (snum == -1)
> lp_load_ex: refreshing
2009 Apr 05
2
Prohibit removing INBOX
Hello list,
I'm using dovecot 1.1.11 and I'm going to prohibit users to remove
their INBOX and some other directories in the mailbox root.
I used Access Control Lists (http://wiki.dovecot.org/ACL) to do this:
protocol imap {
mail_plugins = acl
}
plugin {
# With global ACLs in /etc/dovecot/acls/ directory:
acl = vfile:/etc/dovecot/acls
}
/etc/dovecot/acls/.DEFAULT:
owner
2015 Sep 02
0
sysvolreset erros (sernet-samba 4.2.3)
Helllo,
I have clean sernet-samba-ad install, and then join to existing domain.
When I tried samba-tool ntacl sysvolreset I have ERROR:
[root at dc04 ~]# samba-tool ntacl sysvolreset
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[netlogon]"
Processing section "[sysvol]"
Processing section "[netlogon]"
Processing
2006 Dec 04
1
make errors, rsync 2.6.9 with acls patch
Hi. I'm attempting to compile rsync 2.6.9 with both the acls & xattr
patches on an MacBook pro (ie: Intel processor), with the latest
Apple Developer Tools. While this is OS X client, I've enabled acls
via "sudo /usr/bin/fsaclctl -p / -e" and rebooted, prior to
attempting to compile rsync. Is there something else inherent in OS X
Server perhaps, that I'm still
2015 Sep 23
2
[dovecot-2.2.18] dsync error: Error: Can't delete mailbox INBOX: INBOX can't be deleted. Problem with name of folders?
Hi All!
I'm also hitted by this problem. I'm trying to migrate emails from very
old dbmail to dovecot (maildir). I read old threads with similar problem
but I found only such solutions:
- upgrade to 2.2.13
- workarround : use imapsync
- no solution
I'd like to not use imapsync, have you got an idea what should I do to
do migration successfully?
dsync throws:
doveadm(root): Debug:
2018 Feb 15
2
ACLs, shared, public, virtual mailboxes not working
Hello,
Thank you for your reply. Here's my acl files:
public/TestFolder dovecot-acl
anyone lr
user=user1 akxeilprwts
-user=user1
user=user2 lr
public/TestFolder1 dovecot-acl
user=user1 lr
user=user2 lr
public/dovecot-acl
user=user1 lr
user=user2 lr
and I have another dovecot-acl file in shared/office folder:
user=user1 at domain.com lrwstipekxa
user=user2 at domain.com lrwstipekxa
2019 Mar 07
0
Regression ACL & namespace prefix
I tested with release 2.3.5, and
doveadm -Dv acl debug -u testuser pub
doveadm(testuser): Debug: acl vfile: file /etc/dovecot/global-acls/pub/INBOX not found
doveadm(testuser): Debug: acl vfile: file /home/vmail/pub/Mail/mailboxes/INBOX/dbox-Mails/dovecot-acl not found
doveadm(testuser): Debug: acl vfile: file /etc/dovecot/global-acls/ not found
doveadm(testuser): Debug: acl vfile: file
2018 Feb 15
2
ACLs, shared, public, virtual mailboxes not working
Hello,
I'm running Dovecot 2.2.3, and am having issues with my public
folders, shared folders, and virtual/ALl folders apparently ACLs are
on that list as well.
I was debugging an unrelated problem with my smtp server and got the
following dovecot debug log output. Below is also a doveconf -n output
as well as my shared-folder definition file and my global-acls file.
What I'm trying to
2012 Apr 24
6
acls not copied when creating subfolder of private INBOX
Using brand new dovecot 2.1.5 I still have a problem with the inheritance of acls.
Setting:
- maildir with private INBOX and public folders.
- users maildir directory (/home/mail/user/ahelmcke) contains dovecot-acl file
- public folders root directory (/home/mail/Fax) contains dovecot-acl file
When creating a subfolder of the public folder the dovecot-acl files gets copied to the subfolders
2019 Dec 08
5
Shared namespace is empty after migration to new Dovecot installation
Hi all,
I've used most of this weekend finalizing my migration from an old
server running Dovecot 2.2.22 to a brand new installation running 2.3.8.
In general, the migration was painless, everything just clicked, but
checking up on the finer details post migration i've found out that user
shared folders does not seem to work anymore, and I simply can't get it
to work.
The setups
2015 Feb 10
2
Dovecot 2.2.15 issues with global ACL
Hello,
We have upgraded from Dovecot 2.2.13 to 2.2.15 and we are using global ACL file.
The content of the ACL file is as following:
* owner r
INBOX owner lrwstipekxa
INBOX/* owner lrwstipekxa
user owner rwstipekxa
user/* owner rwstipekxa
This worked fine but after update any user cannot see any folders from under the INBOX, also they cannot create any new folders.
Error into the logs are
2017 Jun 06
0
GPO Problem
On Tue, 6 Jun 2017 15:35:42 -0300
Epsilon Minus via samba <samba at lists.samba.org> wrote:
> Hi. I have a problem applying GPO. I do not know where to look
> Reviewing I found this:
>
> # samba-tool ntacl sysvolcheck
> lp_load_ex: refreshing parameters
> Initialising global parameters
> Processing section "[global]"
> Processing section
2010 Nov 26
3
Plan: ACL changes
Global ACLs are intended to apply to a few mailboxes for all users. For example you could have a master user called "spam" that would have access to each user's "spam" mailbox, but nothing else.
Global ACLs are kind of ugly. A mailbox's ACL is found from exactly the same name as what the mailbox's virtual name is. So for example if you have
namespace {
separator