- dovecot - dovecot.org

[Dovecot] Shared maildir through namespace help...
by Brice Figureau 14 Mar '06

14 Mar '06

Hi, I'm a happy user of dovecot since the 0.99.x days, and recently switched my user base to 1.0b2. Now, to the point, I got a request (from marketing) to share a lot of maildirs between two (and possibly more) accounts. Those two accounts have differents uid/gid. The maildirs are actually in one of the account. I thought I could possibly craft a public namespace for those maildirs as explained in the wiki, but alas, it doesn't quite work as I expected: excerpt of dovecot.conf: namespace public { separator = / prefix = marketing/ location = maildir:/home/marketing/Maildir:INDEX=%h/ } users belong to the marketing group. $ find /home/marketing/Maildir -ls 4767751 4 drwxrwxr-x 3 marketing marketing 4096 Mar 14 11:57 . 4767752 4 drwxrwsr-x 6 marketing marketing 4096 Mar 14 11:59 ./Maildir 4767753 4 drwxrwsr-x 2 marketing marketing 4096 Mar 14 11:57 ./Maildir/cur 4767754 4 drwxrwsr-x 2 marketing marketing 4096 Mar 14 11:57 ./Maildir/tmp 4767755 4 drwxrwsr-x 2 marketing marketing 4096 Mar 14 11:57 ./Maildir/new 4767756 0 -rw-r--r-- 1 marketing marketing 0 Mar 14 11:57 ./Maildir/dovecot-shared >From there, the namespace is visible from all the IMAP accounts. Now, if a user creates a new folder in this public namespace, here is what I get: 4767757 4 drwx--S--- 5 brice marketing 4096 Mar 14 12:05 ./Maildir/.test 4767758 4 drwx--S--- 2 brice marketing 4096 Mar 14 11:59 ./Maildir/.test/cur 4767759 4 drwx--S--- 2 brice marketing 4096 Mar 14 11:59 ./Maildir/.test/new 4767760 4 drwx--S--- 2 brice marketing 4096 Mar 14 11:59 ./Maildir/.test/tmp 4767761 0 -rw-r--r-- 1 brice marketing 0 Mar 14 11:59 ./Maildir/.test/dovecot-shared 4767762 4 -rw------- 1 brice marketing 6 Mar 14 11:59 ./Maildir/subscriptions As you can see: the cur,new,tmp dir don't have the right permissions (they're not rw for the group), and moreover, the 'subscriptions' file has the same problem. The result is that any other user don't have access to this directory even if it is in a public namespace. Now, the question, is: is that setup could work only with virtual users setup with a static uid/gid ? Is there a mean to implement what I want ? Does using symlinks instead of the namespace could work ? Regards, -- Brice Figureau <brice+dovecot(a)daysofwonder.com>

2 2

[Dovecot] operation not supported ?
by Frank Bonnet 14 Mar '06

14 Mar '06

Hello I have this error message in the errorlog but I configured dovecot to use /var/mail/%u anyone could explain ? dovecot: Mar 14 10:49:36 Error: imap(xxxxxx): flock() failed with file /user/xxxxxx/Mail/.imap/INBOX/dovecot.index.log: Operation not supported Thank you

2 1

[Dovecot] mbox to maildir conversion - good idea regarding Outlook?
by Gerhard Hofmann 14 Mar '06

14 Mar '06

Hi list, first of all, many thanks to the Dovecot authors for supplying an IMAP server that works well with M$-Outlook! I have used UW-imapd for quite a while and was annoyed by frequent "imap...timeout..." error messages. Now I'd like to give maildir format a try because I want to use email sub-folders. What are other Outlook users' experiences with maildir? Is it as stable as mbox? Regards Gerhard

6 7

RE: [Dovecot][solved] imap permission denied
by Roland Schmid 13 Mar '06

13 Mar '06

> You better take a look at doc/mail-storages.txt as stated in the comments > of the configuration file. > thanks, now it works. The dovecot.conf was wrong configured and the permissions in the /home folders where given not correctly Now we are able to read our mail with outlook and via SquirellMails Kind regards, Roland

2 1

Re: [Dovecot] Migrating UW-IMAP to Dovecot on Solaris 9
by Bertrand Leboeuf 13 Mar '06

13 Mar '06

Works well if I use default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u but everything stays in mbox format How can I set new users to Maildir format, old ones with mbox, If I use default_mail_env = maildir:%h/Maildir mailboxes get created in Maildir but I don't get any new email the new emails are sent to /var/mail/%u right now. > >if you're using wu-imap, you'll need this for pop to work. > >pop3_uidl_format = %08Xv%08Xu > >and if your site is relatively big, dovecot may run out of file >descriptors, you may need to use this. > >/usr/bin/plimit -n 8192,8192 `cat /usr/local/var/run/dovecot/master.pid` > > >and watch the logs :) > > >> In the process of migrating to Dovecot 1.0beta3, any tips or >> step-by-step instructions that might relate to Solaris 9. >> >> Thanks >> >> Bertrand Leboeuf >> leboeuf(a)emt.inrs.ca >> >> >

1 0

[Dovecot] tls
by lenny＠edpausa.com 13 Mar '06

13 Mar '06

is it possible to turn off TLS and only SSL ? The reason are many reasons for this, one major being the fact that TLS is automatically discovered by many clients on the standard ports, thus requiring a valid cert for production use, while SSL could be set up on some unknown to anybody port with self signed cert for testing, etc... thank you

1 0

RE: [Dovecot] imap permission denied
by Roland Schmid 13 Mar '06

13 Mar '06

> Are you sure that the home directory is correctly specified? > no I am not sure. In my dovecot.conf I have added this line: default_mail_env = mbox:/var/mail/:INBOX=/var/mail/%u Does each user have its own INBOX files in their home folder? Kind regards, Roland

1 0

[Dovecot] imap permission denied
by Roland Schmid 13 Mar '06

13 Mar '06

Hello, we have problems to access our users mailboxes with SquirrelMail. The log file /var/log/mail.log says permission denied, only one user is allowed to read his mail with SquirrelMail. We are running Debian Sarge, Mailserver is Postfix, imap server is dovecot. Our Mailboxes are stored in the mbox format. Folder of the mbox files is /var/mail/ the users are unix system accounts. Normally we read are mail with the POP-Client Outlook, this works well. But we also want to be able to read our mail (each user his own mails) via SquirrelMail /var/log/mail.log says: Mar 13 10:54:40 webserver dovecot: imap(unix-system-account): mkdir_parents(/var/mail/.imap/INBOX) failed: Permission denied In the folder where the mbox files are stored exists 3 folders called INBOX.drafts INBOX.sent INBOX.trash These folders are owned by the user who is able to read his mail via SquirrelMail and owned by the group mail. Only the user has read and write permissions. Does each user need to have his own INBOX Files? Could you please help me Kind regards, Roland

1 0

[Dovecot] Help please: Error: net_connect
by Brad 13 Mar '06

13 Mar '06

Having some issues with having the deliver lda deliver properly. Here are the vitals of the config : ============================= socket listen { master { path = /var/run/dovecot-auth-master mode = 0660 user = maildir group = maildir } } protocol lda { module_dir = /usr/local/lib/dovecot/lda postmaster_address = postmaster(a)bradphinney.com auth_socket_path = /var/run/dovecot-auth-master } passdb passwd-file { # Path for passwd-file args = /etc/dovecot-passdb } userdb static { # Template for settings. Can return anything a userdb could normally # return, eg.: uid, gid, home, mail, nice # # A few examples: # args = uid=600 gid=600 home=/export/mail/maildir/%u mail=maildir:/export/mail/maildir/%u ==================================== The deliver program is setuid and setgid maildir. The passdb seems to be working fine since I can log in fine using a client. When I try to deliver mail however .. I get this dovecot: Mar 12 20:42:02 Info: auth(default): master out: USER 1 superduper uid=600 gid=600 home=/export/mail/maildir/superduper mail=maildir:/export/mail/maildir/superduper dovecot: Mar 12 20:42:02 Error: auth(default): and then after a while .. this appears deliver: Error: net_connect(/var/run/dovecot-auth-master) failed: Permission denied And the really odd thing is that the mail seems to be delivered and placed in the maildir. Any help would be appreciated ..

1 0

[Dovecot] Limiting Dovecot access by user-spesific ip addresses?
by Timo Neuvonen 13 Mar '06

13 Mar '06

Hi, Is there any possibility to limit access to mailboxes by user-spesific ip addresses? So, I'd like to have a configuration which by default restricts reading emails to company's own ip-address range. So far, this could be achieved by a basic firewall rule, but not any more the following: However, there is need for a few users to access their emails from world-wide internet, so there should be a possibility to define for certain users an option to skip the allowed address range check. Regards, Timo

3 5