- dovecot - dovecot.org

[Dovecot] Mailbox creation with Spam
by Master Abi 13 May '07

13 May '07

Hi all, I got dovecot working, but I would like to know when and what creates the mailbox (cur, new, trash, etc ). I noticed that when a client connects for the first time that mailbox is created or when a mail arrives for the first time (i think). I would like to give each mailbox a Spam folder, and possibly doing this automatically. Is this possible with some dovecot setting and not via scripting. Thanks master

2 1

[Dovecot] fs quota plugin and NFS
by Nicolas STRANSKY 13 May '07

13 May '07

Hi, I'm trying to use the Dovecot v1 fs quota plugin. The server uses NFS mounted volumes for INBOX and other maildir folders. The /usr/bin/quota command is working seamlessly but I get errors with the quota plugin, which gives the following logs: Apr 19 17:46:15 rouge dovecot: IMAP(xyxyxyx): quotactl(Q_GETQUOTA, nfs.xxx.yyy.org:/home) failed: No such file or directory Apr 19 17:46:18 rouge dovecot: IMAP(yxyxyxy): quotactl(Q_GETQUOTA, nfs.xxx.yyy.org:/home) failed: No such file or directory Is there a way to get it work ? Thanks, -- Nico Il faut s'entraider, c'est la loi de nature. -+- Jean de La Fontaine (1621-1695), L'Âne et le Chien (Fables VIII.17) -+-

2 3

[Dovecot] mailquota in ldap attribute 'mailQuota'
by Shahmat Dahlan 13 May '07

13 May '07

I've tried having the ldap quota in an ldap attribute, which still doesn't work. /etc/dovecot.conf protocols = imap pop3 mail_location = maildir:/data/mail/%u/Maildir protocol imap { mail_plugins = quota imapquota } plugin { quota = maildir:ignore=Trash } the rest are defaults added an attribute 'mailQuota' with value '10240' kbytes or 10Mbytes as for /etc/dovecot-ldap.conf user_attrs = mail,homeDirectory=home,uidNumber=uid,gidNumber=gid,quotaStorage=mailQuota Would appreciate if anyone could assist on this. I'd prefer to use the above than setting the mail quota manually: quota = maildir:storage=10240:ignore=Trash We are actually in the planning stage of migrating all of current our mailboxes from Netscape to Dovecot, instead of upgrading it to those new Sun.

1 0

[Dovecot] Migrating to Maildir -> path
by Wouter de Jong 13 May '07

13 May '07

Hello, I'm in the process of migrating to Maildir, and I wondered what would be an acceptable path. I want to do virtual-accounts only, so $HOME/Maildir/ is not an option. I was thinking of /some/path/username(a)domain.tld/Maildir/ and later perhaps /some/path/(firstletter)/username(a)domain.tld/Maildir/ but perhaps Maildir/ is a bit too redundant here.... Anyone who could advice ? Many thanks, Wouter

3 2

[Dovecot] Mixing MBOX and Maildir?
by Marc Perkel 13 May '07

13 May '07

Is it possible to have some folders be mbox and some be maildir format? Why you might ask? Sometime for diagnostics I have the Exim MTA archive certain messages in MBOX format and then I want to copy them into an imao folder to look at them with Thunderbird. When I used MBOX all I had to do was copy the file into a folder and it worked. So what I'd like to do is have a folder with a special name that is MBOX and the rest be maildir. Ideally have Dovecot be smart so that if the file exists then it is assumed to be MBOX and if the directory exists then it is assumed to be maildir. Has anyone done anything like this?

6 10

[Dovecot] Time adjusting
by Robert McKenzie 13 May '07

13 May '07

Would it be possible to have an option/variable in the config file to allow for easier setting of the maximum time to sleep for rather than having it hard coded or allow for adjustment up to an amount greater than 5 as it is at present but still have an upper limit hard coded. My system is regularly out on boot up by up to 7 seconds and consequently dovecot kills itself, if I restart it is fine and keeps going without a problem until the next reboot. Regards, Robert McKenzie. -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.467 / Virus Database: 269.7.0/801 - Release Date: 12/05/2007 18:40

4 3

[Dovecot] Writing a new mailbox access module
by Tom Alsberg 13 May '07

13 May '07

Having finished a few other projects, I'm contemplating trying to write a new mailbox module which could be useful for us here. I would appreciate any guidance. Basically, I need (or rather, could use) a module that provides a merge of two mailboxes (which are themselves accessed by other modules), cascading them, so that: * The user sees one mailbox M, which contains all the messages in the mailboxes A and B. * A and B are both already accessible by existing Dovecot mailbox access modules, but possibly by different modules (e.g. A is an mbox, B is a Maildir). * Any write operation (creation of a new message, etc.) is eventually performed on B. * As soon as a message that was in A is accessed (either for read or for write), it is transferred to B. I would use such a module to combine the spool file in /var/mail with some INBOX in the user's home directory. The incentive is the following: * Traditionally, users receive their mail in the spool, commonly in /var/spool. Mailers, like mail, elm, pine, mutt, etc. move each read message to some record mailbox (commonly ~/mbox, but with the more advanced mailers it can be configured to be some other mailbox, even a Maildir). * Users keep working this way. IMAP will not substitute the regular mail access when inside the network here. But it should be as convenient as possible to use it from the outside (e.g. at home, or from an Internet Café, or using some Webmail interface). * Mainly for administrative reasons, it is desirable that mail keeps being delivered to the spool, and not directly to the user's home directory. One of the reasons is that mail never fails to be delivered as long as there is space in the spool. When the user is out of quota on his home directory, the mail does not get rejected, and a failure only occurs when the user initiates some operation (like reading the message). Another reason is simply to be compatible with the way traditional mailers and users work. * IMAP, and IMAP clients (e.g. Thunderbird, the most common one here), on the other hand, usually do not recognize the concept of a spool. There is an INBOX, where all mail arrives, and this is where all new messages should arrive, and remain, unless they are deleted moved elsewhere. * It would of course not be desirable to just move messages automatically after the user reads them, because it would confuse users when a message suddenly disappears from a mailbox all by itself. * The best way I can think of to be consistent with both the traditional way mailers work (moving messages from spool to ~/mbox after they are read) and the way IMAP is commonly used (INBOX contains all received messages not deleted or moved, including messages that just arrived), would be using such a module as I suggested, with (using the previous terminology) e.g. M=INBOX, A=spool, and B=~/mbox. I have just skimmed again through the mailbox code (which I last looked at over a year ago, back when it was in alpha releases), not going too much into details. From past experience and current skimming, working with that code doesn't seem too straightforward, though. I can think of how to implement the logic I described on its own (i.e. as a library with a few functions), but not sure how difficult it will be to interface it with Dovecot. Is there any developer/module writer's guide somewhere that explains the mailbox access module interface? I'd appreciate some basic guidance to start with. If I get to working on it seriously, expect lots of questions from me about the code :-) Regards, -- Tom -- Tom Alsberg - hacker (being the best description fitting this space) Web page: http://www.cs.huji.ac.il/~alsbergt/ DISCLAIMER: The above message does not even necessarily represent what my fingers have typed on the keyboard, save anything further.

2 1

[Dovecot] dovecot deliver tries to setuid but why?
by Daniel 13 May '07

13 May '07

Hi! I've set up postfix(2.4.1) + dovecot(1.0-cvs) + dovecot-lda(1.0-cvs). Dovecot's deliver is running as vmail:vmail (according to postfix's master.cf). Now the problem (when receiving mail): deliver(leva): auth input: leva deliver(leva): auth input: uid=8006 deliver(leva): auth input: gid=8000 deliver(leva): auth input: home=/var/mail/virtual/leva deliver(leva): setuid(8006) failed: Operation not permitted Every virtual user has different uids, but the gid is the *same* for everyone. The gid is 8000(vmail) for everybody, and deliver runs as 8000:8000 (vmail:vmail). vmail group has write access to the users' maildirs. So why does deliver try to setuid when it has group write permission to the destination directory? Thanks! Daniel

2 1

[Dovecot] Virtual User Home Directory, and APOP Clear Text Passwords
by imacat 13 May '07

13 May '07

Dear all, Hi. This is imacat from Taiwan. I'm new to this list. I was migrating from Qpopper to Dovecot. (Qpopper copies the mailbox when POP3 logged in, which causes quota problem.) Generally Dovecot is nice. However, I have a few questions: 1. I have a few virtual users, and I'm not using IMAP. Do I still have to give them a writable home directory? I mean, they exists only for me to receive mails from fetchmail. They really have nothing but their inbox. But if I do not give them a writable home directory, I got this error in my syslog all the time: mbox: Can't create root mail directory /home/homeless/mail: Permission denied 2. I would like to use APOP in addition to SSL/TLS. Currently Dovecot saves APOP passwords as clear text. I understand this. But is it possible to have some sort of encoding, for example, Base64? Just to prevent casual reads. I have several users. I do not want to know their passwords just to add them to the APOP database. I do not want other roots to read my passwords, intended or not. Encoded passwords also have the advantage that I can use passwords that contain the colon sign ":". It would be nice if something a little harder than Base64 can be used. Thank you very much in advance. -- imacat ^_*' imacat(a)mail.imacat.idv.tw PGP Key: http://www.imacat.idv.tw/me/pgpkey.txt Tavern IMACAT's http://www.imacat.idv.tw/ Woman's Voice http://www.wov.idv.tw/ TLUG List Manager http://www.linux.org.tw/mailman/listinfo/tlug

2 6

[Dovecot] SASL using different auth database?
by Dave McGuire 13 May '07

13 May '07

Hi folks. Is it possible to configure Dovecot to authenticate against one mechanism (i.e., /etc/passwd) for POP/IMAP connections, while providing a SASL authentication socket that satisfies authentication requests against a different mechanism, say MySQL? The goal here is to allow users to have different passwords for SMTP authentication and POP/IMAP connections. I am converting an existing installation to Dovecot...this installation currently has quite a few users who are configured with SMTP authentication (Cyrus SASL/saslauthdb) using different passwords than are configured for their POP connections (via cucipop, /etc/passwd). If someone can think of any better way to accomplish this goal, I'm all ears. Thanks, -Dave -- Dave McGuire Port Charlotte, FL

3 5