Hy! I am currently configuring a new mailserver using postfix and dovecot 1.2.1. The filesystem strucutre in my spool directory is user1/ user2/ domain/info/ domain/office/ user1 and unser2 are ordinary users mailboxes, the latter two contain the virtual mailboxes for info at domain and office at domain as created by postfix. I want these virtual mailboxes (all of them are in maildir format) to be shared to certain real users. I configured a shared namespace: namespace shared { separator = / prefix = shared/%%d/%%n/ location = maildir:/var/spool/vmaildir/%%d/%%n/ #I tried ths as well # prefix = shared/%%u/ # location = maildir:/var/spool/vmaildir/%%u/ hidden = no subscriptions = no list = yes inbox = no } Then I configured a dictionary to list the folders, as described in the wiki: plugin { acl_shared_dict = proxy::acl } dict { acl = mysql:/etc/dovecot/dovecot-dict-sql.conf } where /etc/dovecot/dovecot-dict-sql.conf holds map { pattern = shared/shared-boxes/user/$to/$from table = virtual_user_shares value_field = dummy fields { from_user = $from to_user = $to } } The database table consists of +-------------+------------+-------+ | from_user | to_user | dummy | +-------------+------------+-------+ | info at domain | user1 | 1 | +-------------+------------+-------+ But when I login as user1 I can neither see nor subscribe to the info at domain mailbox. In the "flat" case (sharing the user2 mailbox to user1), this setup works. I am pretty clueless how to go on. cheers Mathias
On Fri, 2009-08-07 at 13:29 +0200, Mathias Tausig wrote:> I am currently configuring a new mailserver using postfix and dovecot > 1.2.1. The filesystem strucutre in my spool directory is > user1/ > user2/ > domain/info/ > domain/office/ > > I configured a shared namespace: > > namespace shared { > separator = / > prefix = shared/%%d/%%n/ > location = maildir:/var/spool/vmaildir/%%d/%%n/I don't think you should use a shared namespace for this. You just want everything in domain/ to be shared to users in that domain? Do you have multiple domains? Do user1 and user2 contain @domain? If you have multiple domains and user1 is really user1 at domain, I'd use something like: namespace public { separator = / prefix = shared/ location = maildir:/var/spool/vmail/%d subscriptions = no } If that doesn't do what you want, explain more clearly what you need.> plugin { > acl_shared_dict = proxy::acl > } > dict { > acl = mysql:/etc/dovecot/dovecot-dict-sql.conf > }These aren't needed with public namespaces. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20090807/c524c34a/attachment-0002.bin>
Hy! Am Freitag, den 07.08.2009, 14:13 -0400 schrieb Timo Sirainen:> On Fri, 2009-08-07 at 13:29 +0200, Mathias Tausig wrote: > > I am currently configuring a new mailserver using postfix and dovecot > > 1.2.1. The filesystem strucutre in my spool directory is > > user1/ > > user2/ > > domain/info/ > > domain/office/ > > > > I configured a shared namespace: > > > > namespace shared { > > separator = / > > prefix = shared/%%d/%%n/ > > location = maildir:/var/spool/vmaildir/%%d/%%n/ > > I don't think you should use a shared namespace for this. You just want > everything in domain/ to be shared to users in that domain?Not neccesarily everything. I want to be able to share info at domain to user1 and office at domain to user2.> Do you have multiple domains?Yes.> Do user1 and user2 contain @domain?No. They can receive mails under various domains which are aggregated into one domainless account.> [...] > > If that doesn't do what you want, explain more clearly what you need.I hope I was able to clarify my (desired) setup now. Thanks for trying to help me. cheers Mathias
Maybe Matching Threads
- How do you create a tree strucutre with ActiveRecord
- parkcall: How to remove announcement.
- Mixed-model with paired design & covariates
- LDAP + mail_location: Get "%d" from customfield
- Adding Spatial Correlation Strucutre to Logistic Regression / Contingency Analysis