Okay, I'm cruising the wiki, and it is at best confusing to me. Maybe
someone on the list can help me out quickly?
Here is what I have:
dovecot 1.1.18, mbox format, currently no acl/namespace/etc. All works great.
What I want to be able to do:
Have an email account (or folder or mailbox) which can be accessed by
several people (say 3) with per-user seen flags. That is, say 3 people
all access the mail but each user has their own seen flag for the messages.
This would hopefully be done with mbox still, if possible, but I'm willing
to try a mixed mbox/maildir setup if required to accomplish the goal.
Questions:
1) Can I do this with 1.1.18, or do I need to upgrade?
2) Do I need to set :CONTROL in mail_location, and if so, what should
I set it to, and what does this control exactly (more precisely, does
this info need to be HA or not, etc) Is this where the seen flag info
will be stored (or is that in INDEXES)?
3) Can I do this with mbox only, or do I need maildir, or does it depend
on dovecot version?
4) Any additional help you can give me...
I basically understand the ideas behind it all, but from the wiki I'm
confused exactly what I need to do, and what version I might need. (If
the wiki example is for dovecot 1.2+, does that mean it won't work in
1.1, or just that it has to be done differently, etc).
Any help (clearing up my obvious confusion) would be appreciated...
Step by step directions would be even better! :)
--
Eric Rostetter
The Department of Physics
The University of Texas at Austin
This message is provided "AS IS" without warranty of any kind,
either expressed or implied. Use this message at your own risk.
Quoting Timo Sirainen <tss at iki.fi>:> You can't have per-user seen flags with mbox currently. So create a > public namespace with a maildir location and set up dovecot-acl file in > a way that allows only some specific users access to it. So for example:To refresh, I want a shared account, but my system was Dovecot 1.1 with all mbox mailboxes. Well, this is what I've done so far: 1) Upgraded to dovecot 1.2 (just because I could, I guess) 2) Tried to setup private/public namespaces... Edited "dovecot -n" output: # 1.2.4: /etc/dovecot.conf # OS: Linux 2.6.18-128.4.1.el5.centos.plus x86_64 CentOS release 5.3 (Final) [...] mail_location: mbox:~/mail/:INBOX=/var/spool/mail/%u:INDEX=/var/dovecot/indexes/ %u [...] mail_plugins(default): zlib acl mail_plugins(imap): zlib acl mail_plugins(pop3): zlib [...] namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: public separator: / prefix: shared/ location: maildir:/var/spool/mail/public:INDEX=/var/dovecot/indexes/public/%u list: no lda: postmaster_address: postmaster at physics.utexas.edu hostname: mail.ph.utexas.edu log_path: info_log_path: syslog_facility: mail auth default: passdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot-ldap.conf plugin: acl: vfile 3) Created /var/spool/mail/public/.myfolder for the account to deliver to. Created empty dovecot-shared file for it. 4) Created a .forward file in the account to run "deliver" which does in fact deliver the account's email to the right maildir location. 5) Created /var/spool/mail/public/.myfolder/dovecot-acl which has something like: owner lrwstiekxa user=me lrwstiekxa user=you lrst So, mail is delivered to this account correctly as a maildir mailbox. But, I don't know how to read it, and/or configured something incorrectly. It appears to be there, more or less: a0 namespace * NAMESPACE (("" "/")) NIL (("shared/" "/")) a0 OK Namespace completed. a0 list "" "shared/" * LIST (\Noselect \HasNoChildren) "/" "shared/" a0 OK List completed. But I can't figure out how to access it (either manuall via telnet as above, or from a client, etc). So, how do I access it, and/or what did I do wrong? While I've been doing email servers since the 1980's, this is my first try at using IMAP namespaces and shared folders, and I'm just not getting it... :( -- Eric Rostetter The Department of Physics The University of Texas at Austin This message is provided "AS IS" without warranty of any kind, either expressed or implied. Use this message at your own risk.