-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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?
Can we simply run one of the dovecot/imap daemons
configured 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.
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.
- --
Steffen Kaiser
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEVAwUBVl1PKnz1H7kL/d9rAQKg1Qf+N0M28bjIXatRlYIlk7AG99DN5pvN/ZhF
X70oflJFc947fybOIiiTvvnz7yQJNtsp8BQ1k0GJ5GWB7vgyEhOzgrVykkB9QErQ
Teme5zSQiG8KS8E8rDDatRn2RdQ/7jhAeALKEzWvjRXkz3zDqqiblkPnH/7vjxho
zwaBfcH8AGhkhTE0st8Z3jxlaIB0wdjWtZYKZCD3jnQziurqae0o4HD4IcGSROpo
EY5PzLN8FROzS9t2dowm/meCTP1+jy+is06weALlw1fzUTglD2firn5OPESsXcFG
Hl2mL2Jt3wsp/m+nVv8XyK5ZTA5zE5IP5djjBxcT3SbBtPmaXOB7ig==
=qeFK
-----END PGP SIGNATURE-----