search for: userdb_namespace

...special_use = \Drafts? }? mailbox Junk {? ? special_use = \Junk? }? mailbox Sent {? ? special_use = \Sent? }? mailbox "Sent Messages" {? ? special_use = \Sent? }? mailbox Trash {? ? special_use = \Trash? }? prefix =}passdb {? args = host=imap.gmail.com port=993 ssl=imaps? default_fields = userdb_namespace=gmail userdb_namespace/gmail/list=yes userdb_namespace/gmail/subscriptions=no userdb_namespace/gmail/separator=. userdb_namespace/gmail/prefix=INBOX.gmail. userdb_namespace/gmail/location=imapc: userdb_imapc_host=imap.gmail.com userdb_imapc_user=xxxx at gmail.com userdb_imapc_password=#hidden_use-P...

...port at SerNet.DE> Subject: 2.1: imapc LIST problem / usage question To: dovecot at dovecot.org Date: Fri, 9 Sep 2011 12:00:46 +0200 Organization: SerNet Service Network GmbH Hello, 2.1.alpha1 (latest Debian auto build on amd64) As a test, namespace for gmail integration set up by userdb with userdb_namespace=gmail userdb_namespace/gmail/list=yes userdb_namespace/gmail/subscriptions=no userdb_namespace/gmail/separator=. userdb_namespace/gmail/prefix=INBOX.gmail. userdb_namespace/gmail/location=imapc: userdb_imapc_host=imap.gmail.com userdb_imapc_user=ixxxxx at gmail.com userdb_imapc_password=xxxxx userd...

...\Junk > } > mailbox Sent { > special_use = \Sent > } > mailbox "Sent Messages" { > special_use = \Sent > } > mailbox Trash { > special_use = \Trash > } > prefix = > } > passdb { > args = host=imap.gmail.com port=993 ssl=imaps > default_fields = userdb_namespace=gmail userdb_namespace/gmail/list=yes userdb_namespace/gmail/subscriptions=no userdb_namespace/gmail/separator=. userdb_namespace/gmail/prefix=INBOX.gmail. userdb_namespace/gmail/location=imapc: userdb_imapc_host=imap.gmail.com userdb_imapc_user=xxxx at gmail.com userdb_imapc_password=#hidden_use-P...

...t; > } > > mailbox "Sent Messages" { > > special_use = \Sent > > } > > mailbox Trash { > > special_use = \Trash > > } > > prefix = > > } > > passdb { > > args = host=imap.gmail.com port=993 ssl=imaps > > default_fields = userdb_namespace=gmail userdb_namespace/gmail/list=yes userdb_namespace/gmail/subscriptions=no userdb_namespace/gmail/separator=. userdb_namespace/gmail/prefix=INBOX.gmail. userdb_namespace/gmail/location=imapc: userdb_imapc_host=imap.gmail.com userdb_imapc_user=xxxx at gmail.com userdb_imapc_password=#hidden_use-P...

...t;>>>>>> there >>>>>> >>>>>>>> can't be a space in it? Can I replace the space with an >>>>>>>> underscore, >>>>>>>> e.g. >>>>>>>> >>>>>>>> userdb_namespace_inbox = '{ mailbox Drafts { auto=subscribe >>>>>>>> special_use = \Drafts } mailbox Trash { auto=subscribe >>>>>>>> special_use = >>>>>> >>>>>>>> \Trash } }' >>>>>>> >>>&g...

Unfortunately, this yields the same problem Debug: Unknown userdb setting: plugin/userdb_namespace/inbox/mailbox/Bla/autoexpunge=6h Thorsten On Tue, Jan 17, 2017 at 10:16 AM, Thomas Leuxner <tlx at leuxner.net> wrote: > * Thorsten Hater <thorsten.hater at gmail.com> 2017.01.17 09:40: > > > namespace/inbox/mailbox/Bla/autoexpunge=6h > > > > from a userdb, wh...

...special_use = \Drafts? }? mailbox Junk {? ? special_use = \Junk? }? mailbox Sent {? ? special_use = \Sent? }? mailbox "Sent Messages" {? ? special_use = \Sent? }? mailbox Trash {? ? special_use = \Trash? }? prefix =}passdb {? args = host=imap.gmail.com port=993 ssl=imaps? default_fields = userdb_namespace=gmail userdb_namespace/gmail/list=yes userdb_namespace/gmail/subscriptions=no userdb_namespace/gmail/separator=. userdb_namespace/gmail/prefix=INBOX.gmail. userdb_namespace/gmail/location=imapc: userdb_imapc_host=imap.gmail.com userdb_imapc_user=xxxx at gmail.com userdb_imapc_password=#hidden_use-P...

Hi, Dovecot v2.3.7.2 on Ubuntu 18.04LTS I have configured for imap proxy to imap.gmail.com However whilst the imapc_host setting is working, imapc_port is not - it ignores the value I set and dovecot always tries to connect to gmail on port 143 (as per error log output). I have the imapc settings in the 10-mail.conf which gets loaded by dovecoat.conf Looks like a bug. Any assistance would

...\Junk > } > mailbox Sent { > special_use = \Sent > } > mailbox "Sent Messages" { > special_use = \Sent > } > mailbox Trash { > special_use = \Trash > } > prefix = > } > passdb { > args = host=imap.gmail.com port=993 ssl=imaps > default_fields = userdb_namespace=gmail userdb_namespace/gmail/list=yes userdb_namespace/gmail/subscriptions=no userdb_namespace/gmail/separator=. userdb_namespace/gmail/prefix=INBOX.gmail. userdb_namespace/gmail/location=imapc: userdb_imapc_host=imap.gmail.com userdb_imapc_user=xxxx at gmail.com userdb_imapc_password=#hidden_use-P...

...gt;>> >>>>>> just one long string, but how would the setting be named given there >>>> >>>>>> can't be a space in it? Can I replace the space with an underscore, >>>>>> e.g. >>>>>> >>>>>> userdb_namespace_inbox = '{ mailbox Drafts { auto=subscribe >>>>>> special_use = \Drafts } mailbox Trash { auto=subscribe special_use = >>>> >>>>>> \Trash } }' >>>>> >>>>> sort of: >>>>> >>>>> userdb_...

...ile without the virtual > namespace. Hmm. But the goal is for both POP3 and IMAP to see both namespaces. POP3 would see both via the virtual namespace. So, following the idea of passwd-file per %s, it seems like I should do something like: .../passwd.pop3: Set the "extra fields" = userdb_namespace/virtual/inbox=yes .../passwd.imap: Set the "extra fields" = userdb_namespace/inbox/inbox=yes Does that make sense? Michael

...t; > } > > mailbox "Sent Messages" { > > special_use = \Sent > > } > > mailbox Trash { > > special_use = \Trash > > } > > prefix = > > } > > passdb { > > args = host=imap.gmail.com port=993 ssl=imaps > > default_fields = userdb_namespace=gmail userdb_namespace/gmail/list=yes userdb_namespace/gmail/subscriptions=no userdb_namespace/gmail/separator=. userdb_namespace/gmail/prefix=INBOX.gmail. userdb_namespace/gmail/location=imapc: userdb_imapc_host=imap.gmail.com userdb_imapc_user=xxxx at gmail.com userdb_imapc_password=#hidden_use-P...

...ach setting ist one "Extra Field" >>> >>>> just one long string, but how would the setting be named given there >> >>>> can't be a space in it? Can I replace the space with an underscore, >>>> e.g. >>>> >>>> userdb_namespace_inbox = '{ mailbox Drafts { auto=subscribe >>>> special_use = \Drafts } mailbox Trash { auto=subscribe special_use = >> >>>> \Trash } }' >>> >>> sort of: >>> >>> userdb_namespace/inbox/mailbox/Drafts/auto=subscribe >&gt...

.../wiki2.dovecot.org/UserDatabase/ExtraFields > > Each setting ist one "Extra Field" > >> just one long string, but how would the setting be named given there >> can't be a space in it? Can I replace the space with an underscore, >> e.g. >> >> userdb_namespace_inbox = '{ mailbox Drafts { auto=subscribe >> special_use = \Drafts } mailbox Trash { auto=subscribe special_use = >> \Trash } }' > > sort of: > > userdb_namespace/inbox/mailbox/Drafts/auto=subscribe > > see also: > > http://www.dovecot.org/list/dov...

Dear all, is there a way to allow users to set up something like autoexpunge on an individual IMAP folder basis? The idea I implemented does not seem to work, namely returning namespace/inbox/mailbox/Bla/autoexpunge=6h from a userdb, which results in Debug: Unknown userdb setting: plugin/namespace/inbox/mailbox/Bla/autoexpunge=6h >From older questions on the mailing list I gather that the

...containing the needed mailbox definitions in the userdb lookup for such users? If so, how would the userdb lookup result be formatted? Presumably as just one long string, but how would the setting be named given there can't be a space in it? Can I replace the space with an underscore, e.g. userdb_namespace_inbox = '{ mailbox Drafts { auto=subscribe special_use = \Drafts } mailbox Trash { auto=subscribe special_use = \Trash } }' Or is there some other way to do this?

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 2 Aug 2016, Michael Fox wrote: > Update: > > I was able to eliminate the /var/log/mail.err error messages (shown below) > by creating a userdb.quota-status and userdb.lmtp passwd-file. However, > since userdb.pop3 and userdb.imap will have different extra-fields values > for namespace (different namespace/xxx/inbox=yes

* Thorsten Hater <thorsten.hater at gmail.com> 2017.01.17 10:57: > Unfortunately, this yields the same problem > > Debug: Unknown userdb > setting: plugin/userdb_namespace/inbox/mailbox/Bla/autoexpunge=6h > > userdb_namespace/inbox/mailbox/Bla/autoexpunge=6h 'plugin' is not part of the userdb override. It is literally as above. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signa...

...xpunge=6h } On Tue, Jan 17, 2017 at 11:03 AM, Thomas Leuxner <tlx at leuxner.net> wrote: > * Thorsten Hater <thorsten.hater at gmail.com> 2017.01.17 10:57: > > > Unfortunately, this yields the same problem > > > > Debug: Unknown userdb > > setting: plugin/userdb_namespace/inbox/mailbox/Bla/autoexpunge=6h > > > > userdb_namespace/inbox/mailbox/Bla/autoexpunge=6h > > 'plugin' is not part of the userdb override. It is literally as above. >

...aFields >> >> Each setting ist one "Extra Field" >> >>> just one long string, but how would the setting be named given there > >>> can't be a space in it? Can I replace the space with an underscore, >>> e.g. >>> >>> userdb_namespace_inbox = '{ mailbox Drafts { auto=subscribe >>> special_use = \Drafts } mailbox Trash { auto=subscribe special_use = > >>> \Trash } }' >> >> sort of: >> >> userdb_namespace/inbox/mailbox/Drafts/auto=subscribe >> >> see also: >&g...