dovecot - Feb 2008 - Set up shared mailboxes for secretary-boss-relationship

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

some users are to read other users mailboxes (secretary-boss 
relationship), in order to filter out minor issues, SPAM, appointment 
requests etc. pp.

The "boss" wants to see/access his/her mailbox the usual way, no fancy
stuff.

Furthermore, this is a N:N relationship, meaning one user needs to read 
one set of user's mailboxes, another user needs to read another set of 
mailboxes; both may or may not overlap.

My idle solution would be to create some name space or a special
"shared"
directory in the secretary's Maildir/home dir and symlink the Maildir of 
all the "boss"'s Maildir roots.

Because only the "secretary" shall use/see the definition, I'm not
to make
one namespace per relationship, but predefine one namespace and issue the 
path via userdb, right?

Does somebody has some setup of this sort running?

Are there some differences in v1.1 in this aspect?

Currently I've setup that the secretaries connect with the real account of 
the boss(es), what is not good in my eyes, the secretaries should use 
their own accounts accessing the mails.

Bye,

- -- 
Steffen Kaiser
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHuT1QVJMDrex4hCIRAm5RAJ9ff3jWWhq3u2Lhk20pFKNbDe2sIACePToS
cagaxkCLzzd494PzN6Jm9xo=8eoM
-----END PGP SIGNATURE-----

On Feb 18, 2008, at 10:09 AM, Steffen Kaiser wrote:
> My idle solution would be to create some name space or a special  
> "shared" directory in the secretary's Maildir/home dir and
symlink
> the Maildir of all the "boss"'s Maildir roots.
That should work. Or you could symlink them directly into your boss's  
maildir.
> Because only the "secretary" shall use/see the definition,
I'm not
> to make one namespace per relationship, but predefine one namespace  
> and issue the path via userdb, right?
Right. Or use a post-login scripting to test if ~/Maildir/shared  
exists and then define the namespace. Or define the namespace in  
dovecot.conf and use post-login script to drop it if it's not found.  
I've in my TODO that Dovecot could do this dropping automatically if  
some setting is enabled (optional=yes or something).
> Are there some differences in v1.1 in this aspect?
I don't think so.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20080219/6c8970af/attachment-0002.bin>