dovecot - May 2013 - imapc - different settings for different namespaces

Originally I was planning on allowing all kinds of mail settings inside
namespace {}, including imapc_* settings. But that's a bit difficult to
implement (although I think it will happen some day). So for now I was thinking:

imapc foo {
  host = imap.foo.com
  master_user = foomaster
  password = foopass
}

imapc bar {
  host = imap.bar.com
  ...
}

namespace {
  prefix = foo/
  location = imapc:foo
}
namespace {
  prefix = bar/
  location = imapc:bar
}

So basically if the path after imapc isn't absolute (/path or ~/path), then
treat the path as the imapc section name and use its settings.

Anyone have any improvement suggestions? I was planning on adding this to
v2.2.3. I'm not sure if the section names should be "imapc" or
something else (e.g. imap_remote {}).

On 05/31/2013 04:21 PM, Timo Sirainen wrote:
> Originally I was planning on allowing all kinds of mail settings inside
namespace {}, including imapc_* settings. But that's a bit difficult to
implement (although I think it will happen some day). So for now I was thinking:
>
> imapc foo {
>    host = imap.foo.com
>    master_user = foomaster
>    password = foopass
> }
>
> imapc bar {
>    host = imap.bar.com
>    ...
> }
>
> namespace {
>    prefix = foo/
>    location = imapc:foo
> }
> namespace {
>    prefix = bar/
>    location = imapc:bar
> }
>
> So basically if the path after imapc isn't absolute (/path or ~/path),
then treat the path as the imapc section name and use its settings.
>
> Anyone have any improvement suggestions? I was planning on adding this to
v2.2.3. I'm not sure if the section names should be "imapc" or
something else (e.g. imap_remote {}).
>
What ever happened with this? Doesn't look like it was committed. This 
looks like a cool idea. I was just thinking about pulling multiple 
external IMAP accounts under a single dovecot account and I ran into this.

On 20 Mar 2015, at 12:40, Gedalya <gedalya at gedalya.net>
wrote:
> 
> On 05/31/2013 04:21 PM, Timo Sirainen wrote:
>> Originally I was planning on allowing all kinds of mail settings inside
namespace {}, including imapc_* settings. But that's a bit difficult to
implement (although I think it will happen some day). So for now I was thinking:
>> 
>> imapc foo {
>>   host = imap.foo.com
>>   master_user = foomaster
>>   password = foopass
>> }
>> 
>> imapc bar {
>>   host = imap.bar.com
>>   ...
>> }
>> 
>> namespace {
>>   prefix = foo/
>>   location = imapc:foo
>> }
>> namespace {
>>   prefix = bar/
>>   location = imapc:bar
>> }
>> 
>> So basically if the path after imapc isn't absolute (/path or
~/path), then treat the path as the imapc section name and use its settings.
>> 
>> Anyone have any improvement suggestions? I was planning on adding this
to v2.2.3. I'm not sure if the section names should be "imapc" or
something else (e.g. imap_remote {}).
>> 
> 
> What ever happened with this? Doesn't look like it was committed. This
looks like a cool idea. I was just thinking about pulling multiple external IMAP
accounts under a single dovecot account and I ran into this.
I didn't need it after all for the project where it first seemed to be
necessary. Attached the code that I wrote so far, which I think allows you to
configure such imapc {} blocks, but there's no code to actually use them.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: diff
Type: application/octet-stream
Size: 12948 bytes
Desc: not available
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20150320/c392c073/attachment-0001.obj>
-------------- next part --------------