Op 01-12-15 om 08:41 schreef Steffen Kaiser:
On Mon, 30 Nov 2015, Frido Otten wrote:
In our dovecot setup we use 3 different config files. One for maildropping(sieve), one for dovecot/imap on standard ports with ssl config and one for dovecot/imap on standard ports+1 with a different ssl certificate. Currently the client using the standard port+1 config wants to make use of shared folders, but the thing is that the current namespace separator in all configs is '.'. This is conflicting with shared folders.
How does '.' conflict with shared folders?
Sorry for the confusion, I forgot to mention that we have usernames with a '.' in it. The separator and those usernames together with shared folders, won't work.
Can we simply run one of the dovecot/imap daemonsconfigured with a different separator and shared folders without having impact on sieve and the current connected users to the standard ports?
I hate all questions and answers with "simple" or "simply" in it. Sorry, I'll use easily then... ;) But yes, the IMAP separator does not have no impact on the filesystem _usually_. But mayhap you have a strange config anyway (with 3 configs) and the separator does influence the storage.
Double denial there.. ;) Why 3 different configs? It's for historic reasons, and probably they can be combined into one.
So if I understand this right, the separator as a '.' and sieve rules like this with a dot in the foldername:..
if allof (header :contains ["Return-path"] ["@dovecot.org"]) { fileinto "Maillist.Dovecot"; }
won't be affected with only one of both imap configs having '/' as a separator.
Regards, Frido