similar to: Extensions.conf error - 'Maximum Include level(10) exceeded'

Displaying 20 results from an estimated 100 matches similar to: "Extensions.conf error - 'Maximum Include level(10) exceeded'"

2006 Jan 13
0
Extensions.conf error - 'Maximum Include level (10) exceeded'
Can someone tell me why the following from extensions.conf generates this error on asterisk load? Jan 13 09:27:24 WARNING[31701]: config.c:938 ast_config_internal_load: Maximum Include level (10) exceeded As far as I can tell I don't have a DEPTH of 10 includes. I certainly have more than 10 include statements, but I don't have them drilled down to a depth of 10. I'm thinking the
2006 Jan 13
0
Extensions.conf error - 'MaximumInclude level(10) exceeded'
I don't follow. Are you saying there's a limit of 10 contexts within extensions.conf? If, on the other hand, your saying that each context can only have 10 #include statements, I tried that too. See below. I put 12 #include's across two contexts, and still got the same error, I not sure that goto's are much of a solution, but I'll have to proof it. And that's my
2018 Aug 07
2
limit sharing ability to certain users
Now the attributes are correctly read for the user test at onnet.ch <mailto:test at onnet.ch>, but other users are not able to authenticate anymore. root at buserver:/var/spool/postfix/virtual/onnet.ch/test/Maildir/.super# doveadm user test at onnet.ch field value uid 5000 gid 5000 home /var/spool/postfix/virtual/onnet.ch/test/ mail maildir:~/Maildir quota_rule *:bytes=1073741824 acl
2018 Aug 07
0
limit sharing ability to certain users
Hmm. if you put it *after* the ldap userdb, it should not have prevented users from logging in. What happens if you do userdb { ? driver = passwd-file ? args = .... ? skip = notfound ? result_failure = continue-ok } Aki On 07.08.2018 12:58, Simeon Ott wrote: > Now the attributes are correctly read for the user test at onnet.ch > <mailto:test at onnet.ch>, but other users are not
2018 Aug 07
2
limit sharing ability to certain users
? attached the dovecot -n, linked files, debug log lines during a standard client login root at buserver:/etc/dovecot/conf.d# doveconf -n # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-6-amd64 x86_64 Debian 8.11 auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = plain debug_log_path = syslog disable_plaintext_auth = no
2018 Aug 07
0
limit sharing ability to certain users
Ah. You probably need to change ldap userdb so that you add userdb { driver = ldap ? args = /etc/dovecot/dovecot-ldap.conf result_success = continue-ok } so that the next one is processed. you can use 'doveadm user test at onnet.ch' to verify that the attributes are read for this user, and with another username that they are not. Aki On 07.08.2018 12:23, Simeon Ott wrote: > ?
2018 Aug 07
2
limit sharing ability to certain users
still the same? root at buserver:/etc/dovecot# doveadm user test2 at onnet.ch field valueuserdb lookup: user test2 at onnet.ch doesn't exist relevant config output from doveconf -n userdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap result_success = continue-ok } userdb { args = username_format=%Lu /etc/dovecot/share.passwd driver = passwd-file result_failure =
2018 Aug 07
2
limit sharing ability to certain users
May you please clarify that? Where should I omit the userdb_ prefix? Which of my attempts are you pointing at? As stated, I omitted the userdb_ prefix when working with an LDAP attribute. > On 7 Aug 2018, at 10:03, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > with ldap userdb, you need to omit the userdb_ prefix. > > Aki > > > On 07.08.2018 10:54, Simeon Ott
2018 Aug 08
2
limit sharing ability to certain users
http://repo.dovecot.org/ <http://repo.dovecot.org/> Sami > On 8 Aug 2018, at 10.27, Simeon Ott <simeon.ott at onnet.ch> wrote: > > Okay, this seems to be due to the fact that the option ?use_globals_only" is supported only in v2.2.31+ > We are on Debian jessie with dovecot v2.2.13 ? even an upgrade to current stable stretch won?t help (dovecot v2.2.27). So we will
2018 Aug 05
4
limit sharing ability to certain users
Hello Is it possible to limit the ability of sharing it?s own mailboxes to only a few users? We have a few sensitive mailboxes of users where the ability to share via IMAP SETACL should be prevented. I tried the following so far? doveadm acl remove -u test at onnet.ch INBOX user=test at onnet.ch admin but when doing this the admin rights are still there doveadm acl rights -u test at
2018 Aug 08
0
limit sharing ability to certain users
Okay, this seems to be due to the fact that the option ?use_globals_only" is supported only in v2.2.31+ We are on Debian jessie with dovecot v2.2.13 ? even an upgrade to current stable stretch won?t help (dovecot v2.2.27). So we will wait until the packages find their way into the repository. thanks anyway > On 7 Aug 2018, at 13:00, Simeon Ott <simeon.ott at onnet.ch> wrote: >
2018 Aug 06
0
limit sharing ability to certain users
You could do userdb { ?? driver = username_format=%Lu passwd-file ?? args = /etc/dovecot/share.passwd } #? /etc/dovecot/share.passwd test at onnet.ch::::::: userdb_acl=vfile:/etc/dovecot/dovecot-acl userdb_acl_globals_only = yes should prevent the user from modifying any ACL files. Aki On 05.08.2018 17:04, Simeon Ott wrote: > Hello > > Is it possible to limit the ability of sharing
2018 Aug 05
0
limit sharing ability to certain users
Hello Is it possible to limit the ability of sharing it?s own mailboxes to only a few users? We have a few sensitive mailboxes of users where the ability to share via IMAP SETACL should be prevented. I tried the following so far? doveadm acl remove -u test at onnet.ch <mailto:test at onnet.ch> INBOX user=test at onnet.ch <mailto:user=test at onnet.ch> admin but when doing this the
2016 Oct 10
1
Hierarchy separator and LAYOUT=FS change
Hello, I stumbled across a 5-year-old post on the dovecot list about changing the dovecot hierarchy separator to enable shared mailboxes (http://www.dovecot.org/list/dovecot/2011-January/056201.html <http://www.dovecot.org/list/dovecot/2011-January/056201.html>). At the moment I?m stuck in a pretty similar situation. Migrated from courier to dovecot 2 years ago and preserved the
1997 Jul 30
0
samba, OnNet and Win95
I'm running into a problem with Win95 clients and I hope someone has a fix for this. Our servers are Solaris boxes providing file services via both NFS and samba (1.9.16p11). The Win95 clients were recently upgraded to the latest version of FTP Software OnNet which makes the NFS stuff almost transparent to the users. I'm not sure how OnNet hooks in to Win95 but you could map a drive to
2018 Aug 09
0
limit sharing ability to certain users
Thanks Sami, thanks Aki I just updated the packages on our testing server and now it works like expected. There are some LDAP tests to come. Are there many productive server out there using this repository? Simeon > On 8 Aug 2018, at 09:41, Sami Ketola <sami.ketola at dovecot.fi> wrote: > > > http://repo.dovecot.org/ <http://repo.dovecot.org/> > > Sami >
2004 May 08
5
1800 Provider
Hi list, I'm interested in receiving incoming call to my Asterisk PBX thru an 1800 number. Anybody knows a provider with best minute rate? I heard that that Nufone can provide this service for around 3cents/min for calls made within 48 continental states. Any provider that can give better rate, even with additional limitation such as much few states that a call can originate? How do
2006 Dec 11
0
Asterisk Sends 180-RINGINGto UAeven withprogressinband=yes
Hmmm. Ok, that's true. At the very least it will create confusing CDR's I think... maybe. We're not billing our OnNet traffic at all. Only the traffic that goes OffNet, to our switch is billed (if it leaves our switch that is...). I was thinking earlier too that we only need progressinband on traffic that goes to the PSTN, via our switch. OnNet traffic will never generate reorder
2018 Aug 07
0
limit sharing ability to certain users
As Sami pointed out, I had wrong syntax: > close, but few typos. userdb should be: > > userdb { > ? driver = passwd-file > ? args = username_format=%Lu /etc/dovecot/share.passwd > } > > Sami On 06.08.2018 22:52, Simeon Ott wrote: > Thanks for the advice Aki > >> On 6 Aug 2018, at 07:26, Aki Tuomi <aki.tuomi at dovecot.fi >> <mailto:aki.tuomi at
2018 Aug 06
2
limit sharing ability to certain users
Thanks for the advice Aki > On 6 Aug 2018, at 07:26, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > userdb { > driver = username_format=%Lu passwd-file > args = /etc/dovecot/share.passwd > } Something is wrong with the suggested driver configuration ? Leads to a fatal ? I think there is missing a driver name. Any chance of doing this via LDAP attribute? Here is