- 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 … [View More]

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 … [View More]

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 … [View More]

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 … [View More]

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 … [View More]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. [View Less]

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. … [View More]

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 … [View More]

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 … [View More]

3 5

[Dovecot] logging IMAP size?
by Armijn Hemel 12 May '07

12 May '07

hi all, is there a way to somehow log the size of an IMAP session with Dovecot? With POP3 there is this pop3 format string I can set in dovecot.conf, but I don't see an equivalent for IMAP. If so, are there any plans to add this functionality? thanks, armijn -- --------------------------------------------------------------------------- armijn(a)uulug.nl | http://www.uulug.nl/ | UULug: Utrecht Linux Users Group ---------------------------------------------------------------------------

3 3

[Dovecot] dbox redesign
by Timo Sirainen 12 May '07

12 May '07

I don't think anyone uses dbox currently, so the whole format could still be redesigned. So I was thinking about doing two major changes: 1. Rely on index files a lot more. The flags are already stored in index files, so there's no need to waste I/O updating them to dbox files all the time. They could still be updated (if indexes get deleted, the flags aren't all gone), but less often. 2. Require fcntl() locking. Currently dbox uses dotlocks which is slow. Cydir could be a good alternative … [View More]also once index file code is made a bit more robust. Perhaps I could implement single instance attachments for cydir too.. Locking ======= The current dbox "index" file would be gone. It's pretty useless. Replace it with a whole new index file. Or perhaps it should be called "locks" file or something. The locks file would contain records: <file id> <lock timestamp> <status>. So something like: <header> 1 4645a60f 0 2 00000000 N 3 00000000 D That would mean that the first file is locked by some process, either for appending or expunging. The 2nd and 3rd files aren't locked. New messages can't be appended to 2nd file anymore. 3rd file is already deleted and this record needs to be removed when rewriting the file. Locking a dbox file for either appends or expunges is done like: 1. See if timestamp is zero - If not, see if it's older than .. let's say a day or so .. a) Yes: Continue to 2. b) No: Assume the file is locked 2. Do fcntl() byte range lock over the record line in the locks file. - If it failed, the record is locked 3. Write the timestamp. 4. Compare stat() and fstat() inodes to see if the file was rebuilt - If yes, reopen the file and goto 1 5. File is now locked. Do the append/expunge. 6. Write timestamp to zero. 7. Unlock the byte range. If a file is locked, append will try another file and expunge will mark the message as expunged instead of actually expunging it yet. Note that the locks file is read without locking. This is safe because data is never moved within the file, and it doesn't matter if the timestamp isn't read correctly always. The timestamp check is only an optimization. Actually I'm not sure if it would be better not to have the timestamp at all. Deleted records will stay in the file until the file is rebuilt. If a deleted record is noticed in the file, the process tries to lock the whole locks file. If it succeeds, it proceeds with writing the non-deleted records to a temporary file and rename()ing it over the locks file. Appending ========= 1. Find the first file in the locks file that has appendable=0 - If no such file was found, go to "create a new file" logic as described below 2. Lock the file record 3. Verify from the file's headers that this file can actually be appended to - If messages have been expunged from a dbox file, it can't be safely appended to anymore. - Other reasons include eg. configurable max. file size and daily rotations 4. Write the mail 5. Lock locks file's header 6. Get the UID from "next uid" field and update it 7. Unlock the header 8. Unlock the file record 9. Update index file Create a new file logic: 1. Create a temporary file 2. Write the messages there 3. Lock locks file's header (including fstat() / stat() rebuild check) 4. See what the latest file ID is in the file 5. rename() temp fail to msg.<latest file id+1> 6. Lock locks file for the range of the to-be-written record below 7. Write the new record to locks file 8. Go to step 6 in the original append logic Syncing / expunging =================== If locks file's header's "next uid" doesn't match the one currently in index file, the appending crashed between steps 6 and 9. Find the new message(s) and append them to index file. If the locks file is completely gone , rebuild it by going through all the msg.* files in the directory. If "expunge counter" (see below) doesn't match in locks file's header vs. index file header, go through all the msg.* files to see if a message exists in multiple files. If found, remove the duplicates. Typically neither of the above happens, so the only thing to do here is to write changes from index file to dbox files. This may mean flag changes once in a while, but most importantly expunges will always be synced. Initially figure out what files require expunging. Try to create a single lock range that includes all of them. If there are non-zero lock timestamps in that range, create multiple ranges. If a file couldn't be locked, the expunge is done by updating expunge-flag in the file. This can be done without locking (see below for flag updates). If a file was successfully locked, the expunging is done by: 1. Update "expunge offset" in file header to the offset of the first expunged message. If expunge offset is non-zero, the file is treated as non-appendable. Also when rebuilding and finding the same message from multiple files, this field is used to figure out which file should be truncated. 2. Copy the rest of the non-expunged messages to a new temporary file and add the file to locks file using the "Create a new file" logic described for appends. Instead of updating "next uid" field, update "expunge counter" field. 3. ftruncate() the old file. 4. Update "expunge counter" in index file. Sync locking ============ If there is one big "sync lock", then flags can be updated in any file with relying only on that lock. Some files may be locked, but they're locked for appends so flag updates (and other record updates as well) are safe. It would be interesting to make it work without that sync lock though, so that multiple processes could be syncing dbox at the same time. But there probably isn't much point. If the sync is locked, there's no real requirement to do the syncing at all then, it's just left to be done later. If multiple processes were syncing at the same time, the only problem would come from flag updates. Either the files would have to be locked for flag updates (with waiting locks, bad bad), or it would need to be able to handle the situation when a flag was written just when another process expunged messages from the file and truncated it. That could be done by checking (one way or another) after the flag write if a truncation had happened, and if so do the truncation again. Preventing out of sync disconnects ================================== Reading messages from dbox files requires no locking, so it's possible that while one session is reading a message another session goes and expunges the message by truncating the file. The only way to handle this situation is to disconnect the client. Also even if the message wasn't in the middle of being read, this kind of a out-of-sync could happen if a session hasn't synced itself yet (no NOOP/IDLE/etc. for a while) and tries to begin reading an expunged message. These could be avoided if the expunging process knew that there are other processes that still know about the message, so it could just mark the message as expunged instead of actually doing it. I think this could be done with yet another file that tracks what messages are expunged. The file would contain "dovecot.index.log file sequence + offset" records. Whenever message(s) are expunged, a new seq +offset is written containing the position in the log file for that transaction. All the processes accessing the mailbox would then read lock the file from eof to infinity. The lock is updated whenever mailbox is synced (and being careful not to have race conditions there). So syncing process would then try if it can write lock the file from "last real expunge" log position to end of file. If not, then using some binary search find the position how far it can be locked. If it managed to update the write lock position at least some, the messages up to that far in the transaction log can be expunged safely. One problem with this is that the file needs to be rotated once in a while so that it won't grow infinitely. This can be done only if the write lock can include the whole file (including infinity). And that can be done only if there's a single process having the mailbox open, which may never happen with shared mailboxes. I think I'll leave this feature to be implemented later. It's extra overhead that's probably rarely useful. Single instance attachments =========================== I'll change the dbox messages to have variable sized headers. The header could then contain information such as "at offset 5000 insert 11241242 bytes from file AB123427852". Fast copying ============ Would be nice if copying a message from one mailbox to another wouldn't require actually reading+writing the whole message contents. But I can't really figure out how to implement this without requiring that there is only a single dbox storage which contains the mails for all the mailboxes, and the mailboxes themselves are just Dovecot's index files containing pointers to the dbox storage. The problem with having everything in one storage is that if the index files are broken, the messages can't be placed into correct mailboxes anymore. Although one possibility would be treat mailboxes a bit similarly than keywords. So that when a message is copied to another mailbox, the message in dbox file is updated to contain information that it exists in such and such mailboxes. Hmm. Perhaps that would be good enough, yes. [View Less]

1 0

[Dovecot] Problems with BEFORE searches.
by Trever L. Adams 12 May '07

12 May '07

Ok, I am trying to modify some code given to me by the author of the dspam plugin for dovecot (sorry the name eludes me). I am modifying it to handle UNSEEN differently than SEEN. Below is the python code. I am not a python programmer, but I get the basic idea. ok, uids = conn.search(None, 'BEFORE', unreadsentbefore, 'SEEN') "11-May-2007 06:18:29 -0600" is the value of unreadsentbefore. However, this doesn't match any emails even though they are all dated as 5/10 and they have all been … [View More]

4 6

[Dovecot] read only maildir subscriptions
by Nagyon Almos 11 May '07

11 May '07

Hello, I have some (possibly very simple) questions about subscriptions: I store my old mails in /home/oldmails/ in one Maildir where I have only read-only permissions (I cannot delete, create or modify any files). Under thunderbird, I can successfully log in and read my new mails, but I cannot subscribe (?) within thunderbird to oldmails (it is grey not black as other folders). What did I do wrong? What other permissions does dovecot need? Here's the relevant part of dovecot.conf: … [View More]

2 2

[Dovecot] Dovecot not handling r/o mailboxes completely, and problem with ACL as a workaround
by Adam McDougall 11 May '07

11 May '07

First of all, I think dovecot is really fantastic and I have thanks for all the hard work. I think it will be the best fit for my ~5000 users when I have it setup completely. We normally have approx 500 concurrent IMAP connections during the day. I am trying to convert from courier-imap to dovecot, but I have an issue with public namespace folders that are not writable by certain users. Please let me know if I need to provide more information or how I can help solve this issue. In … [View More]courier-imap, we were able to take advantage of the maildir structure and standard unix users/groups to allow 'decsstaff' members to have full write access while 'decsall' members only have r/o unless also a member of 'decsstaff': -rw-rw-r-- 1 postlocal decsstaff 37597 May 5 23:37 /egr/mail/shared/decs/.support.In/cur/1178422658.M533373P54269.ice drwxrwxr-x 2 postlocal decsstaff 24576 May 5 23:37 /egr/mail/shared/decs/.support.In/cur drwxrws--- 6 postlocal decsall 4096 Apr 22 18:08 /egr/mail/shared/decs/.support.In drwxrwsr-x 34 postlocal wheel 4096 May 1 07:23 /egr/mail/shared/decs In short, upper directories are used to limit world access to just one group 'decsall', and once inside, r/o world access could be used as an anonymous substitution for 'decsall' and the group permissions would allow writing by 'decsstaff'. I don't know how courier stores and checks mail directory permissions, but it was aware when a user would not be able to delete or change messages and would return a READ-ONLY imap error when an attempt to change a message occurred (courier returns this in the IMAP response to update mail flags to reflect that the client wants to move to delete a mail). I understand that imap clients will usually only set status as read or deleted first and only try to delete an email for real on expunge, but it seems dovecot does not try to detect if a message is modifyable before it is too late for the user to find out. What happens is a user appears to be able to mark messages read, move them to another folder, or delete them (another way of moving to another folder eg. Trash). The user is clueless that the changes will not occur, and only finds out later when they reload the folder to find the messages back, or tries to expunge and get an unhelpful 'internal error' from dovecot (I can help trace this situation if it helps, but I think that stage should not be reached if things were working right). My configuration has the public folder control and indexes inside a user's home directory, so it will always be possible for dovecot to record message status changes, however I do not think dovecot should update the control and indexes to reflect an IMAP operation that is not allowed to complete due to restricted permissions on the actual email file. I suppose dovecot would have to check the permissions on mail message files. As a workaround, I wondered if I could apply dovecot ACLs to the public folders to reinforce my intentions of only allowing readonly access to certain users. If ACLs worked, I could even use it as a viable alternative to the unix permissions on the maildir contents and avoid using more unix groups than necessary. For most of our shared mailboxes, there will only be a few persons with write access, and up to a dozen people with read access, so even if I have to list every user seperately I could. However, I have not been able to get ACLs to do anything useful for me, and I hesitate to use the feature to work around might be a configuration error or bug. It is also more convenient for my migration procedure if I do not have to modify file permissions or structure during downtime to switch to dovecot. I am still not sure how dovecot ACLs affect the actual permissons of dovecot processes. I have mostly tried placing a dovecot-acl file in the maildir directory (alongside cur, tmp, new) and dovecot seems to be reading it according to the log, however I am not getting expected results from the ACLs. If the unix permissions allow a client to enter 'cur' and read mails, the mail client thinks it can delete or move them (until expunge) no matter even if I put acl entries with only 'r' permission. ACL questions (which might help others understand better as well): Is a 'user=foo rl' entry supposed to remove any possible write permissions in a maildir covered by such an ACL for user foo? If not, shouldn't it at least enforce restrictions on the available mail metadata which is more likely to be writable by the user? Is it even possible for an ACL to grant additional permissions above what is granted to a user by standard unix permissions? Does an empty ACL equate to the exact permissions granted by unix, and should an admin try to design an ACL to modify as little as possible, or should the admin try to use enough acl entries to form a complete description of the desired resulting permissions? I get the impression that broad ACLs should be listed first, and more specific ACLS listed below can add or remove ACL permissions applied earlier in the file as a 'last match' case. Should the acl plugin be able to print a summary of the resulting permissions in the log (with mail_debug=yes) when accessing a folder with an ACL? A snip from logs, I generated alot today and I'm not sure which portions would be most useful so I'll start with this: May 6 15:20:08 gribble dovecot: IMAP(mcdouga9): acl: initializing backend with data: vfile:/usr/local/etc/dovecot-acls May 6 15:20:08 gribble dovecot: IMAP(mcdouga9): acl: acl username = mcdouga9 May 6 15:20:08 gribble dovecot: IMAP(mcdouga9): acl: owner username = May 6 15:20:08 gribble dovecot: IMAP(mcdouga9): acl vfile: Global ACL directory: /usr/local/etc/dovecot-acls May 6 15:20:08 gribble dovecot: IMAP(mcdouga9): Namespace: type=public, prefix=#shared/decs/, sep=/, inbox=no, hidden=no, subscriptions=no May 6 15:20:08 gribble dovecot: IMAP(mcdouga9): maildir: data=/egr/mail/shared-dovecot2/decs:CONTROL=/home/mcdouga9/Maildir/dovecot/public/control/decs:INDEX=/home/mcdouga9/Maildir/dovecot/public/indexes/decs May 6 15:20:08 gribble dovecot: IMAP(mcdouga9): maildir: root=/egr/mail/shared-dovecot2/decs, index=/home/mcdouga9/Maildir/dovecot/public/indexes/decs, control=/home/mcdouga9/Maildir/dovecot/public/control/decs, inbox= May 6 15:20:08 gribble dovecot: IMAP(mcdouga9): opendir(/egr/mail/shared-dovecot2/decs/tmp) failed: Permission denied # dovecot --version 1.0.0 The reason I have so many public spaces below, is to match the existing directory structure we setup for courier, and also to help us keep the directory listing more tidy since otherwise we would end up with many folders all under one directory. Some of them have monthly rotation and it could get out of hand if we did not split them up. I understand it makes things more difficult for the global acl list at present, if I were to use it, but I may not have any conflicting folder names at this time. # dovecot -n # /usr/local/etc/dovecot.conf ssl_cert_file: /usr/local/etc/apache2/ssl/mail.egr.msu.edu.pem ssl_key_file: /usr/local/etc/apache2/ssl/mail.egr.msu.edu.pem login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login verbose_proctitle: yes first_valid_uid: 1000 first_valid_gid: 0 mail_location: maildir:~/Maildir:CONTROL=%h/Maildir/dovecot/private/control:INDEX=%h/Maildir/dovecot/private/indexes mail_debug: yes mmap_disable: yes maildir_copy_with_hardlinks: yes mail_plugins: acl mail_log_max_lines_per_sec: 0 imap_client_workarounds: delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep namespace: type: public separator: / prefix: #shared/be/ location: maildir:/egr/mail/shared-dovecot2/be:CONTROL=%h/Maildir/dovecot/public/control/be:INDEX=%h/Maildir/dovecot/public/indexes/be namespace: type: public separator: / prefix: #shared/cee/ location: maildir:/egr/mail/shared-dovecot2/cee:CONTROL=%h/Maildir/dovecot/public/control/cee:INDEX=%h/Maildir/dovecot/public/indexes/cee namespace: type: public separator: / prefix: #shared/chems/ location: maildir:/egr/mail/shared-dovecot2/chems:CONTROL=%h/Maildir/dovecot/public/control/chems:INDEX=%h/Maildir/dovecot/public/indexes/chems namespace: type: public separator: / prefix: #shared/decs/ location: maildir:/egr/mail/shared-dovecot2/decs:CONTROL=%h/Maildir/dovecot/public/control/decs:INDEX=%h/Maildir/dovecot/public/indexes/decs namespace: type: public separator: / prefix: #shared/egr/ location: maildir:/egr/mail/shared-dovecot2/egr:CONTROL=%h/Maildir/dovecot/public/control/egr:INDEX=%h/Maildir/dovecot/public/indexes/egr namespace: type: public separator: / prefix: #shared/me/ location: maildir:/egr/mail/shared-dovecot2/me:CONTROL=%h/Maildir/dovecot/public/control/me:INDEX=%h/Maildir/dovecot/public/indexes/me namespace: type: public separator: / prefix: #shared/org/ location: maildir:/egr/mail/shared-dovecot2/org:CONTROL=%h/Maildir/dovecot/public/control/org:INDEX=%h/Maildir/dovecot/public/indexes/org namespace: type: public separator: / prefix: #shared/toptest/ location: maildir:/egr/mail/shared-dovecot2/toptest:CONTROL=%h/Maildir/dovecot/public/control/toptest:INDEX=%h/Maildir/dovecot/public/indexes/toptest namespace: type: public separator: / prefix: #shared/ugs/ location: maildir:/egr/mail/shared-dovecot2/ugs:CONTROL=%h/Maildir/dovecot/public/control/ugs:INDEX=%h/Maildir/dovecot/public/indexes/ugs namespace: type: public separator: / prefix: #shared/vprgs/ location: maildir:/egr/mail/shared-dovecot2/vprgs:CONTROL=%h/Maildir/dovecot/public/control/vprgs:INDEX=%h/Maildir/dovecot/public/indexes/vprgs namespace: type: private separator: / prefix: mail/ hidden: yes namespace: type: private separator: / location: maildir:~/Maildir:CONTROL=%h/Maildir/dovecot/private/control:INDEX=%h/Maildir/dovecot/private/indexes inbox: yes auth default: mechanisms: plain login passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth user: postfix group: postfix master: plugin: acl: vfile:/usr/local/etc/dovecot-acls Thanks. [View Less]

6 13

[Dovecot] Log data on dovecot-auth socket
by Koen Vermeer 11 May '07

11 May '07

Hi, Is there any way I can monitor or log the data that is being received/sent on the dovecot-auth socket? I'm trying to debug some authentication stuff, and monitoring the conversation would be very useful. Thanks! Koen

2 2

[Dovecot] No authentication sockets found
by Stewart Dean 11 May '07

11 May '07

Thunderbird (2.0) is all of a sudden checking mail server capabilities and keep posting a popup saying: "Mail Server imap.bard.edu is not an IMAP4 mail server". To the best of my knowledge, neither Tbird nor DC have been updated, though the DC imap host was rebooted today 3 hours ago. Any info on what this is about? DC is currently serving out of a special port and in evaluation list....I can't imagine that this message would please the user community! Killing and restarting dovecot … [View More]

3 2

[Dovecot] locking questions
by Stewart Dean 11 May '07

11 May '07

I have Dovecot 1.0 in trial use by the IT staff, and have some locking questions Background, the mail server runs procmail, sendmail and NFS exports the user homedir and mailbox to a) a login shell host and b) a mailing list services host. It runs UWIMAP on the usual ports and dovecot on a arbitrary port number. Because of concern with NFS and file access contention. I have the following dovecot.conf file access parms set: a) mbox_dirty_syncs = no b) mbox_lazy_writes = no 1) I … [View More]am seeing these errmsgs. Are they anything I should be concerned about, or are they just the inevitable result of lock contention for mailboxes and folders by procmail, imap/dovecot and NFS? > In syslog, I am seeing this: > > Apr 23 18:46:34 mercury mail:err|error dovecot: IMAP(sdean): stat(/var/spool/mail/sdean.lock) failed: No such file or directory > Apr 23 18:46:34 mercury mail:err|error dovecot: IMAP(sdean): file_lock_dotlock() failed with mbox file /var/spool/mail/sdean: No such file or directory > > While in maillog: > > Apr 23 18:46:34 mercury mail:err|error dovecot: IMAP(sdean): stat(/var/spool/mail/sdean.lock) failed: No such file or directory > Apr 23 18:46:34 mercury mail:err|error dovecot: IMAP(sdean): file_lock_dotlock() failed with mbox file /var/spool/mail/sdean: No such file or directory 2) I earlier asked, but don't think I got an answer to this question: > Everybody wants to lock differently > 1) procmail (delivering for sendmail), which seems to want to use > dotlocking, fcntl and lockf locking; for whatever reasons, the compile > time tests seem to disallow flock. > 2) UWIMAP which according to wiki.dovecot.org/Migration/UW uses: > mbox_read_locks = flock > mbox_write_locks = dotlock flock > 3) I want to run dovecot in the same environment as I switch over, for > which the locking strategy is supposed to be (according to > http://wiki.dovecot.org/MboxLocking) > mbox_read_locks = fcntl > mbox_write_locks = dotlock fcntl > > Since that same page in the wiki says. "*It's important that all > software that's reading or writing to mboxes use the same locking > settings.",* I had recompiled procmail so it only usedotlocking and > fcntl (thus removing lockf in addition to the disallowed flock)...but > now I bumped into the Migration/UW page and there looks to be a conflict. > > I want to be able to run dovecot (for testing) and UWIMAP (for all > users/production) at the same time (but never at the same time with > the same mailbox), but UWIMAP is doc'ed to use flock and Dovecot doesn't > It's conceivable that the different locking strategies of UWIMAP and > Dovecot don't matter because they would never be going after the same > mail files (right?) but there is procmail, which has to interact with > both. It appears to not use flock OK, even though the docs say it > should since UWIMAP expects it, and I've disabled lockf as well. But > will there be a conflict with procmail and dovecot's use of fcntl, > which UWIMAP doesn't use? > > Help. 3) I occasionally see "Disconnected for inactivity" message. How long before that happens? Is the interval configurable? Thanks to all. A brother sysadmin was stunned by performance gained in Dovecot. He has to keep postmaster messages for a period and filters them into a separate folder...over a long weekend this folder could get to 1500 messages and 150MB...with UWIMAP he could only delete approx 800 at a time and then had to wait 5-10 minutes for it to process. With dc, he marked off the whole folder and it was gone in seconds. -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035 [View Less]

2 1

[Dovecot] Dovecot refuses connections
by John Rowe 11 May '07

11 May '07

I have recently upgraded to dovecot 1.0.0 on two machines running Scientific Linux 4.3/4.4 x86_64 kernel 2.6.9-22.0.1.EL. The systems come with openssl 0.9.7a and I have installed openssl-0.9.8e. Everything is 64-bit. /usr/local64/sbin/dovecot -n # /usr/local64/etc/dovecot.conf disable_plaintext_auth: no login_dir: /usr/local64/var/run/dovecot/login login_executable: /usr/local64/libexec/dovecot/imap-login first_valid_uid: 100 mail_extra_groups: mail default_mail_env: mbox:%h/mail:INBOX=/var/… [View More]

2 1

[Dovecot] dovecot 1.0.0 hang on one server
by Roberto Tagliaferri 11 May '07

11 May '07

Hi, i've upgraded 5 server from dovecot beta7 or old dovecot-stable to 1.0.0 but on one server dovecot crash after few hours without any log Apr 23 18:19:32 Info: POP3(username): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Apr 24 09:54:11 Info: Dovecot v1.0.0 starting up The startup is by hand (when i arrived at office!!) This server is a linux running on vmware, with 1.0rc7 is all ok , the other server is ok with 1.0.0 The config file are the same... -- Roberto … [View More]

2 1

[Dovecot] Changes in authentication's???
by Boris Ivanov 11 May '07

11 May '07

HI I use dovecot-1.0.r17 on FreeBSD scat.setcom 6.2-RELEASE. Recently authentification stop working. May 10 02:56:02 scat dovecot: auth(default): passwd(test,127.0.0.1): unknown user May 10 02:56:02 scat dovecot: auth(default): client out: OK 1 user=test User= &:/home/test:/tmp/email/bin/nonexistance= May 10 02:56:02 scat dovecot: auth(default): master in: REQUEST 23 43856 1 May 10 02:56:02 scat dovecot: auth(default): passwd(test,127.0.0.1): unknown user May 10 02:56:02 … [View More]scat dovecot: auth(default): master out: USER 23 test uid=1004 gid=31415 home=/home/test May 10 02:56:02 scat dovecot: imap-login: Login: user=<test>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured May 10 02:56:02 scat dovecot: IMAP(test): Effective uid=1004, gid=31415 May 10 02:56:02 scat dovecot: IMAP(test): mbox: data=/tmp/email/mbox/s/test May 10 02:56:02 scat dovecot: IMAP(test): mbox: INBOX defaulted to /tmp/email/mbox/s/test/inbox May 10 02:56:02 scat dovecot: IMAP(test): mbox: root=/tmp/email/mbox/s/test, index=/tmp/email/mbox/s/test, inbox=/tmp/email/mbox/s/test/inbox I generate passwd using next script: etc_path = /usr/local/www/data/Email/RefCont/etc pwd_mkdb -d ${etc_path} ${etc_path}master.passwd pw useradd -V ${etc_path} -n $1 -g mailusers -s /tmp/email/bin/nonexistance echo "$2" | pw usermod -V ${etc_path} -n $1 -h 0 My config: # /usr/local/etc/dovecot.conf protocols: imap pop3 listen(default): *:10143 listen(imap): *:10143 listen(pop3): *:10110 ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no login_process_size: 64 verbose_proctitle: yes first_valid_uid: 0 first_valid_gid: 0 mail_extra_groups: mail default_mail_env: mbox:/tmp/email/mbox/s/%u mail_location: mbox:/tmp/email/mbox/s/%u mail_debug: yes mbox_min_index_size: 100000 mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login verbose: yes debug: yes debug_passwords: yes passdb: driver: pam passdb: driver: passwd passdb: driver: passwd-file args: /usr/local/www/data/Email/RefCont/etc/master.passwd userdb: driver: passwd userdb: driver: passwd-file args: /usr/local/www/data/Email/RefCont/etc/passwd Whats wrong? Can it be fixed? Thanks -- Yours Boris [View Less]

3 2

[Dovecot] Tracing an IP of a user who deleted the message
by Eugene Gladchenko 11 May '07

11 May '07

Hello, Dovecot writes to the log file lines like these: May 10 13:19:04 mailserver dovecot: IMAP(office): copy -> Trash: uid=1131, msgid=<45E669BE.8090705(a)example.com>, box=Sent May 10 13:19:05 mailserver dovecot: IMAP(office): deleted: uid=1131, msgid=<45E669BE.8090705(a)example.com>, box=Sent May 10 13:53:08 mailserver dovecot: IMAP(office): copy -> Trash: uid=1719, msgid=<002701b483f5$7aa257e0$23833bda(a)example.com> May 10 13:53:08 mailserver dovecot: IMAP(office)… [View More]

4 3

[Dovecot] Dovecot and Outlook - IMAP Timeout error
by Phillip T. George 11 May '07

11 May '07

Hey guys, I'm having a problem with Dovecot and Outlook. I'm testing with Outlook XP (2002), but the problem occurs with Outlook 2003 as well. I'm using Dovecot 1.0.rc28. The specific error generated (for IMAP) is: "A connection to the server could not be established. <servername> is now in offline mode." In the details: "There may be a server or network problems or your timeout interval may be too short. Protocol: IMAP Server: <servername> … [View More] Port: 143" It is set up with a POP3 account and an IMAP account within Outlook -- using the same physical email account. The IMAP portion is only used for spam / ham submission, while the POP3 is used for downloading the actual email. The account on the server being used is named "me2.pg.east.eacsd.com" I have a single IMAP account set up in Thunderbird, which is using the account name "me.pg.east.eacsd.com". All mail that is received at "me.pg.east.eacsd.com" is forwarded to "me2.pg.east.eacsd.com" to generate some traffic. Here is the snippet of the mail log which involves me2.pg.east.eacsd.com ( | grep me2.pg.east.eacsd.com | grep -i imap): Apr 25 02:40:11 east dovecot: imap-login: Login: user=<me2.pg.east.eacsd.com>, method=PLAIN, rip=68.14.165.23, lip=64.22.71.38 Apr 25 02:40:13 east dovecot: IMAP(me2.pg.east.eacsd.com): Disconnected in IDLE Apr 25 02:41:10 east dovecot: IMAP(me2.pg.east.eacsd.com): Disconnected: Logged out Apr 25 02:45:41 east dovecot: imap-login: Login: user=<me2.pg.east.eacsd.com>, method=PLAIN, rip=68.14.165.23, lip=64.22.71.38 Apr 25 02:45:41 east dovecot: imap-login: Login: user=<me2.pg.east.eacsd.com>, method=PLAIN, rip=68.14.165.23, lip=64.22.71.38 Apr 25 02:46:18 east dovecot: IMAP(me2.pg.east.eacsd.com): Disconnected Apr 25 02:46:18 east dovecot: IMAP(me2.pg.east.eacsd.com): Disconnected Apr 25 02:50:49 east dovecot: imap-login: Login: user=<me2.pg.east.eacsd.com>, method=PLAIN, rip=68.14.165.23, lip=64.22.71.38 Apr 25 02:50:50 east dovecot: imap-login: Login: user=<me2.pg.east.eacsd.com>, method=PLAIN, rip=68.14.165.23, lip=64.22.71.38 Apr 25 02:51:27 east dovecot: IMAP(me2.pg.east.eacsd.com): Disconnected Apr 25 02:51:27 east dovecot: IMAP(me2.pg.east.eacsd.com): Disconnected Apr 25 02:55:58 east dovecot: imap-login: Login: user=<me2.pg.east.eacsd.com>, method=PLAIN, rip=68.14.165.23, lip=64.22.71.38 Apr 25 02:55:58 east dovecot: imap-login: Login: user=<me2.pg.east.eacsd.com>, method=PLAIN, rip=68.14.165.23, lip=64.22.71.38 Apr 25 02:56:56 east dovecot: IMAP(me2.pg.east.eacsd.com): Disconnected Apr 25 02:56:56 east dovecot: IMAP(me2.pg.east.eacsd.com): Disconnected Apr 25 03:01:27 east dovecot: imap-login: Login: user=<me2.pg.east.eacsd.com>, method=PLAIN, rip=68.14.165.23, lip=64.22.71.38 Apr 25 03:01:27 east dovecot: imap-login: Login: user=<me2.pg.east.eacsd.com>, method=PLAIN, rip=68.14.165.23, lip=64.22.71.38 Apr 25 03:01:58 east dovecot: IMAP(me2.pg.east.eacsd.com): Disconnected Apr 25 03:01:58 east dovecot: IMAP(me2.pg.east.eacsd.com): Disconnected There's more before that, but I'd figured that would be enough: Apr 24 17:18:05 east dovecot: IMAP(me.pg.east.eacsd.com): Disconnected in IDLE Apr 24 17:19:34 east dovecot: IMAP(me.pg.east.eacsd.com): Disconnected in IDLE Apr 24 17:19:42 east dovecot: IMAP(me.pg.east.eacsd.com): Disconnected in IDLE Apr 24 17:20:27 east dovecot: IMAP(me.pg.east.eacsd.com): Disconnected in IDLE Apr 24 17:20:42 east dovecot: imap-login: Login: user=<me.pg.east.eacsd.com>, method=PLAIN, rip=68.14.165.23, lip=64.22.71.38, TLS Apr 24 17:43:18 east dovecot: imap-login: Login: user=<me.pg.east.eacsd.com>, method=PLAIN, rip=68.14.165.23, lip=64.22.71.38, TLS As you can see from the logs, Thunderbird didn't have a problem, which eliminates the possibility of a bad net connection (I'd assume...but I could be wrong). The problem occurred at 3AM. Some people during the day can get it every hour or so. I was able to get it to occur twice (the first time is not shown in these logs). My questions. . . 1. Is there any way to fix this Outlook problem? I have all of the outlook workarounds enabled (along with some for Netscape): imap_client_workarounds = delay-newmail outlook-idle netscape-eoh pop3_client_workarounds = outlook-no-nuls oe-ns-eoh 2. Should Outlook really be connecting and disconnecting that often? 3. Could the problem be occurring because of POP3 and IMAP being used by the same account, and the quick downloading of email via POP3 is eliminating the email for IMAP, thereby causing inactivity in IMAP? Is there a workaround or a known Outlook settings to fix this? Thanks, Phillip [View Less]

2 1

[Dovecot] Troubleshooting - another suggestion...
by Charles Marcus 11 May '07

11 May '07

Hi Timo, I'm the one who suggested the '-n' option to capture the actual config settings that the running dovecot process was using (ala postfix), and you implemented it very quickly - so thanks for that! Now, I'd like to suggest an enhancement... Many people still do not provide basic things like dovecot version, and there are secondary config files like dovecot-ldap, whose settings are not included in the dovecot -n output. How difficult would it be to add these to the output so that … [View More]

2 2

[Dovecot] lucene plug-in
by ??? 11 May '07

11 May '07

Hello, Has anyone tried the lucene plug-in? I am interested to know more about this feature , how to setup / configure it? regards, - Joe

2 1

[Dovecot] corruption?
by Neal Becker 11 May '07

11 May '07

I'm using maildir (and have been for a long time). Today I have a problem: ls -al (maildir): [...] drwx------ 5 nbecker nbecker 4096 Jan 1 2006 .;SECTION= What's this? It seems to be causing my mail client (kmail, using dimap), to hang.

2 1

[Dovecot] maildir file name flags out of order?
by Aaron Solochek 11 May '07

11 May '07

I was trying to figure out why my false-positive spam messages were being tagged as "personal" by thunderbird, and I noticed a possible problem. According to DJB: http://cr.yp.to/proto/maildir.html > New flags may be defined later. Flags must be stored in ASCII order: e.g., "2,FRS". Looking at my maildir, I am seeing flags out of order, such as "2,Sdae" Shouldn't that be "2,Sade"? -Aaron

2 1

[Dovecot] Disconnected for inactivity in reading our output top=0/0
by Chris Gosley 11 May '07

11 May '07

Would someone please help with this error. Using: dovecot-1.0-2.rc28.fc6 On: Fedora Core 6 130 users all connect remotely via ADSL to server to pop their email. None of them have any problems at all with pop3. 3 users in one office, connect to the server via a NAT'd ADSL. Intermittently those three users will get a timeout error, Logfile shows: Apr 19 12:50:53 mail dovecot: auth(default): pam(vu0095,165.228.62.107): lookup service=dovecot Apr 19 12:50:53 mail dovecot: auth(default): … [View More]

3 2

[Dovecot] read only bug?
by Nagyon Almos 11 May '07

11 May '07

Hello All, I have been still struggling with the read only maildir and I think I found something: dovecot wants to rename a file but I/it have/has no rights to do that: dovecot: 2007-05-04 21:30:14 Error: IMAP(bela): rename(/home/store/oldmails/.personal/cur/1154939281.00005.pc1.S=1879:2,S, /home/store/oldmails/.personal/new/1178307014.P8610Q0M347618.pc1) failed: Permission denied Why dovecot wants to rename it? It is really a read only directory. Regards, A. … [View More]

3 5

[Dovecot] read only maildir
by Nagyon Almos 11 May '07

11 May '07

Hello All, I try to set up a read only maildir just as in the wiki, to no avail. The extra (public) namespace shows up but I can not susbscribe to it (in thunderbird) or if I change to that "directory" (in mutt), it is empty. Is it the problem mentioned in the wiki (SharedMailboxes#Subscriptions)? If yes, how can I see/use a folder which is not subscribeable? Any help would be greatly appreciated. Regards, A. _____________________________________________________________ "Egy anya oda … [View More]

5 9

[Dovecot] Error: Master request X not found
by Jordi Moles 11 May '07

11 May '07

*Hi, I've been getting the following error from time to time since i started to use dovecot more than one year ago: dovecot: May 07 19:57:24 Error: auth(default): Master request 88729.43523 not found I haven't stopped upgrading dovecot with the hope that this would be a bug and would be fixed some day, but with v1.0.0, i keep getting the same error. It just happens from time to time. Some of the users of my system complain about not being able to get to see their mails, and it is … [View More]

3 2

[Dovecot] namespace
by Stefan Klatt 11 May '07

11 May '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, i use dovecot 1.0 and try to implement an public mbox namespace parallel to a private and a public maildir namespace. namespace: type: public separator: / prefix: Archiv/ location: mbox:/srv/imapd/shared/archiv/maildir:CONTROL=/srv/imapd/user/%u/shared-settings/archiv/ control:INDEX=/srv/imapd/user/%u/shared-settings/archiv/index Dovecot use the index statement with the correct subdirectories and indexfiles at /srv/imapd/user/%u/… [View More]shared-settings/archiv but don't use the control statement and use a .subscriptions files at /srv/imapd/shared/archiv/maildir instead. :-( Has anybody a idea for this? Where is my fault? Here is the output of dovecot -n: # /etc/dovecot.conf ssl_cert_file: /etc/pki/tls/certs/cac.is-a-geek.com.cert ssl_key_file: /etc/pki/tls/private/cac.is-a-geek.com.key login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login mail_extra_groups: email dotlock_use_excl: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugins: zlib mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 imap_client_workarounds(default): outlook-idle tb-extra-mailbox-sep imap_client_workarounds(imap): outlook-idle tb-extra-mailbox-sep imap_client_workarounds(pop3): outlook-idle namespace: type: private separator: / location: maildir:/srv/imapd/user/%u/maildir inbox: yes namespace: type: public separator: / prefix: Public/ location: maildir:/srv/imapd/shared/public/maildir:CONTROL=/srv/imapd/user/%u/shared-settings/publ ic/control:INDEX=/srv/imapd/user/%u/shared-settings/public/index namespace: type: public separator: / prefix: Archiv/ location: mbox:/srv/imapd/shared/archiv/maildir:CONTROL=/srv/imapd/user/%u/shared-settings/archiv/ control:INDEX=/srv/imapd/user/%u/shared-settings/archiv/index auth default: passdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: static args: uid=600 gid=600 Mfg. Stefan Klatt - -- CaC, Computer and Communication Inhaber Stefan Klatt Triftstrasse 9 60528 Frankfurt Germany Tel.: +49-(0)172-6807809 Tel.: +49-(0)69-67808-900 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGPhoB+AkeCg4UPr4RAiz0AKCV1POqMdlUwSeWzWziSDF6N+4wrQCeMY9E 4AvWqiTwaS1OnCLFYPdZwjk= =Nw4r -----END PGP SIGNATURE----- [View Less]

2 1

[Dovecot] Sieve plugin
by Luigi Rosa 11 May '07

11 May '07

The Sieve plugin page of Wiki documentation (http://wiki.dovecot.org/LDA/Sieve?highlight=%28filter%29) says: "It's also not a good idea to build the plugin against self-compiled Dovecot sources, but then actually use a prebuilt binary package of Dovecot." Why isn't a good idea? Ciao, luigi -- / +--[Luigi Rosa]-- \ Every time you've heard someone say they saw a ghost, or an angel. Every story you've ever heard about vampires, werewolves, or aliens, is the system assimilating some … [View More]

2 1

[Dovecot] ownership/perms on DC file objects
by Stewart Dean 10 May '07

10 May '07

Back in late March I asked what ownership and permissions Dovecot's own directories and files should have; I have an obsessive nature, and wanted to get things right :(.. On April Fool's Day :), Timo responded: > Dovecot opens pretty much all the configuration etc. files as root > before dropping the privileges. So in general they could all be 0600 > owned by root In my typical turtle-crawl fashion, I got around to today, but the onership/perms came out somewhat differently, … [View More]which I put down here for anyone that wants to know......... I set everything under /var/run/dovecot to 600, owned by root:dovecot > 4242 root@mercury:/var/run/dovecot ## ls -alR > total 24 > drw------- 3 root dovecot 512 Mar 06 15:27 ./ > drwxr-xr-x 3 root system 512 Apr 18 2006 ../ > drw------- 2 root dovecot 512 May 09 10:37 login/ > ./login: > total 24 > drw------- 2 root dovecot 512 May 09 10:37 ./ > drw------- 3 root dovecot 512 Mar 06 15:27 ../ > srw------- 1 root dovecot 0 May 09 10:37 default= > -rw------- 1 root dovecot 230 May 09 10:36 ssl-parameters.dat > And restarted dovecot > 4243 root@mercury:/var/run/dovecot ## dovecot > but apparently /var/run/dovecot/login should be 750, but DC dealt with that automagically > Warning: Corrected permissions for login directory /var/run/dovecot/login > 4244 root@mercury:/var/run/dovecot ## ls -alR > total 24 > drw------- 3 root dovecot 512 Mar 06 15:27 ./ > drwxr-xr-x 3 root system 512 Apr 18 2006 ../ > drwxr-x--- 2 root dovecot 512 May 10 12:47 login/ > ./login: > total 24 > drwxr-x--- 2 root dovecot 512 May 10 12:47 ./ > drw------- 3 root dovecot 512 Mar 06 15:27 ../ > srwxrwxrwx 1 root dovecot 0 May 10 12:47 default= > -rw------- 1 root dovecot 230 May 09 10:36 ssl-parameters.dat > ...but then got in the syslog > May 10 12:49:51 mercury mail:err|error dovecot: imap-login: Can't open SSL param > eter file ssl-parameters.dat: Permission denied > May 10 12:49:51 mercury mail:err|error dovecot: child 1380384 (login) returned error 89 > > So I made it 640 which seems to do. > 4246 root@mercury:/var/run/dovecot ## chmod 640 login/ssl-parameters.dat > 4247 root@mercury:/var/run/dovecot ## ls -alR login > total 24 > drwxr-x--- 2 root dovecot 512 May 10 12:47 ./ > drw------- 3 root dovecot 512 Mar 06 15:27 ../ > srwxrwxrwx 1 root dovecot 0 May 10 12:47 default= > -rw-r----- 1 root dovecot 230 May 09 10:36 ssl-parameters.dat So it seems this will do (for others who obsess over things small):: a) /var/run/dovecot can be 600, root:dovecot b) /var/run/dovecot/login should be 750, root:dovecot c) /var/run/dovecot/login/ssl-parameters.dat might be 640, root: dovecot -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035 [View Less]

1 0

Re: [Dovecot] dovecot-dspam-integration
by Johannes Berg 10 May '07

10 May '07

Hi Trever, Please copy the mailing list too. On Mon, 2007-05-07 at 09:45 -0600, Trever L. Adams wrote: > 1) Why on line 350 of your code do you say "do (almost) everything"? > What is left out? Is it done still by dovcecot? I don't remember. You can probably find out by comparing the code. > 2) "I decided that hardlinking into special folders was too much work > (especially with removing the mails again!), so for now my plugin is > calling the dspam client directly." What … [View More]exactly was the problem? Can't > the problem be as simple as: > > a) unlink the message from inappropriate folder (if moving into spam, > unlink from unlearn, if moving out unlink from learn) using the file > name below > b) link the message to the appropriate folder with the name of <MESSAGE > ID>- > > Why do a without seeing if the file exists, well, if you use the full > message ID, because if people are following the rules with their MTA's > and/or mail clients, then message ID should be unique as it must be > unique on their system and it seems that all of them append the hose > name at the end, making it globally unique (or most likely so...). If > this is the case, then the client name. If this is in question then make > it <MESSAGE ID><DATE><FROM>. That should make it globally unique. > > This keeps one from having to mess with keeping lists. If people keep > dragging the same message to their outbox from sent, then the MESSAGE ID > may not be unique, but it will fit all of the same messages, hence I > think it isn't a problem. Also, unlink will cause the os to traverse the > directory, why should we do it as well as it will be a non-fatal error > if it doesn't exist. > > If you take my suggestions, and I am not just being stupid, please > provide some example processes/cron jobs to go with your code in the top > comments. Actually, the thing we care about is the dspam signature which is unique. So that's not a problem. The point is that you have to (a) when no files exist: move into spam: create a file <sig> with contents "spam" move out of spam: create a file <sig> with contents "notspam" (b) when <sig> file exists with contents "spam": move into spam: shouldn't happen move out of spam: unlink file (c) when <sig> file exists with contents "notspam": move into spam: unlink file move out of spam: shouldn't happen the cron job would have to iterate through all these files and call dspam depending on the contents of the file. And then it all has to be atomic. It's not really all that complex, but I was too lazy to implement it. johannes [View Less]

2 13

[Dovecot] Duplicate emails with several clients
by Erick Perez 10 May '07

10 May '07

Hi, I'm using Centos 4.4 (which is redhat linux but free) that comes with dovecot-0.99.11-4.EL4. I have done a clean reinstall of the server and I have users reporting that everytime they hit "send/receive" in their outlook or outlook express software, they get the same messages, as well as the new ones, over and over again. I use postfix + dovecot and only the pop3 protocol. My dovecot.conf has the following relevant entries default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u … [View More]

2 3

[Dovecot] Managesieve: first steps
by Joseba Torre 10 May '07

10 May '07

Hi, I'm trying to get managesieve to work but, as usual, I have some issues... - First of all, the compilation process after applying the patch is a bit strange. I've used this way (i'm using centOS 4 for this pre-tests): $ tar zxvf dovecot-1.0.0.tar.gz $ cd dovecot-1.0.0 $ gzip -cd ../dovecot-1.0.rc28-MANAGESIEVE-v4.diff.gz | patch -p1 $ autoreconf (This ends with an error about missing ./ylwrap) $ automake --add-missing (This copies ylwrap to ., but fails if executed before autoreconf) $ … [View More]autoreconf $ ./configure && make && sudo make install but I'm quite sure that should exist a better way... - After this, adding protocols = imap imaps pop3 pop3s managesieve and protocol managesieve { listen = *:2000 login_executable = /usr/local/libexec/dovecot/managesieve-login mail_executable = /usr/local/libexec/dovecot/managesieve } to dovecot.conf, everything seems to work fine (pop3 and imap work as usual, and I can connect to the managesieve port), but dovecot -n gives no output. (If I put out managesieve from the protocols, dovecot -n gives the normal output again). (This output is appended at the end) - Finally, I'm using Plain as the authentication mechanism, and I've been unable to connect using kmail or the sieve extension for thunderbird. As I'm not sure if any of these really work, I'll setup horde for further testing. Is there anything that I should be aware of? dovecot -n output: # /usr/local/etc/dovecot.conf syslog_facility: local1 protocols: imap imaps pop3 pop3s listen(default): *:143 listen(imap): *:143 listen(pop3): *:110 ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(pop3): *:995 ssl_cert_file: /usr/share/ssl/certs/dovecot-beta.pem ssl_key_file: /usr/share/ssl/certs/dovecot-beta.pem login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login mail_location: maildir:~/Maildir:INDEX=/var/dovecot/%u:CONTROL=/var/dovecot/%u mmap_disable: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %v.%u auth default: master_user_separator: * passdb: driver: passwd-file args: /usr/local/etc/dovecot-master.conf master: yes passdb: driver: pam args: blocking=yes userdb: driver: passwd args: blocking=yes socket: type: listen client: master: path: /var/run/dovecot/auth-master plugin: quota: fs Thanks. -- Joseba Torre. CIDIR Bizkaia. [View Less]

1 0

[Dovecot] removing old emails
by Ray 10 May '07

10 May '07

Hello, I need to remove mail older than for example 30 days. Email is stored in maildir format. can I just use a cron job and shell script or will that mess up indexs? Thanks Ray

3 3

[Dovecot] Dovecot and horde issues
by John H. Bennett III 10 May '07

10 May '07

Hello, First time poster to this list, please be kind. I am having difficulties trying to get the current stable version of horde's imp webmail to work correctly using dovecot 1.0rc15. I am using a pre-release version of SME Server 8 which runs on top of CentOS 5. I have also tried using the 1.0 release of dovecot as well. What is happenning is that when I login to imp, I don't see any folders. I can create folders in imp which do get created in my Maildir directory, but I can't … [View More]

3 4

[Dovecot] Email client dowloads previously read messages as new during migration.
by Eric and Barbara Sammons 09 May '07

09 May '07

I am migrating from UW to dovecot and using mbox. I have been able to find mbox to maildir migration information and tools; however, I have had little luck finding any tool or information for performing such a migration where I wish to keep mbox. ( I know I should migrate to MailDir, but in the case I wish to take baby steps.) I have setup dovecot pop3 communication and I go to my email client and everything works fine with the exception that all mail I have previously read (when using UW as … [View More]

4 3

[Dovecot] Troubleshooting enhancement request...
by Charles Marcus 09 May '07

09 May '07

Hi Timo, You were good enough to add the -n flag to the dovecot command to output the current *changed* config parameters (changed as compared to the defaults) of the running dovecot process. This makes it much easier to troubleshoot issues - thanks! Another flag that postfix has is the -d flag (postconf -d). This one outputs all of the DEFAULTS of the current running postfix process/version. I just used this today to compare what I had in my main.cf to what the defaults were - and for … [View More]

2 2

[Dovecot] Trying to modify the source - fopen problems
by Phillip T. George 09 May '07

09 May '07

Hello all, I don't know if this needs to be sent to a different list or not, if so, please let me know. Anyways, I'm trying to modify the dovecot source a bit, but the problem I'm having is that whenever I use "fopen", it always returns NULL. I've tried a variety of things, even fopen("/dev/null", "w") -- because that should almost always work. I'm trying to get it to work in src/pop3-login/client-authenticate.c Any idea why this might be happening? Any suggestions as to where to … [View More]

2 1

[Dovecot] Inconsistent Mailbox with Eudora as POP3 client
by Amon Ott 09 May '07

09 May '07

Hello everyone, one of our customers using QUALCOMM Windows Eudora Version 7.1.0.9 as POP3 client with Dovecot 1.0.0 under Linux using Maildirs reports that on various accounts they get occasional "inconsistent mailbox" errors at quit. The same Docevot binary in the same environment on other servers works fine for several other customers and ourselves. We use Postfix 2.2 with Dovecot deliver and Sieve plugin, nothing else touches the Maildirs. I have no idea what goes wrong there, I … [View More]already suspected memory corruptions. The system is low on memory and uses some swap (more memory soon), does that trigger such problems? The Eudora log shows: <Dominant>, Shutting down POP connection, QUIT [08:54:07 AM] There has been an error transferring your mail. I said: QUIT and then the POP3 server (xyz(a)my.domain.de) said: ERR Mailbox is in inconsistent state, please relogin. The mail syslog shows e.g.: Apr 27 08:50:26 gateway dovecot: POP3(mk): Disconnected: Mailbox is in inconsistent state. top=0/0, retr=0/0, del=0/715, size=20210522 # /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login first_valid_uid: 440 mail_extra_groups: mail maildir_copy_with_hardlinks: yes mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv auth default: user: dovecot-login verbose: yes passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 384 plugin: quota: fs Amon Ott -- Amon Ott - m-privacy GmbH Am Köllnischen Park 1, 10179 Berlin Tel: +49 30 24342334 Fax: +49 30 24342336 Web: http://www.m-privacy.de Handelsregister: Amtsgericht Charlottenburg HRB 84946 Geschäftsführer: Dipl.-Kfm. Holger Maczkowsky, Roman Maczkowsky GnuPG-Key-ID: EA898571 [View Less]

2 1

[Dovecot] Hot to get rid of \"DON\'T DELETE THIS MESSAGE\" messages?
by foxx＠freemail.gr 09 May '07

09 May '07

I'm using Dovecot 1.0.0 (mbox) with Postfix 2.4 on my FreeBSD box, as a pop3-only server (imap is disabled). All account mailboxes are accessed using Outlook clients. I've noticed that, whenever I'm retrieving mail with pop3, a "DON'T DELETE THIS MESSAGE" is created in mbox. Although these messages are never sent to client MUAs, I found them very annoying. BTW I don't use (or used before) UW or Pine or any other c-client, therefore I assume it's a Dovecot issue. Previously I was using Cyrus … [View More]

2 1

[Dovecot] sporadic slow/non response, problems copying to sent folder
by Danno Coppock 09 May '07

09 May '07

After experiencing these symptoms through many of the release candidates, we've been at v1.0.0 now for a few weeks, and they're still there. Perhaps a config issue with my setup (mbox locks?). It's really too disrupting to continue using this way. I've included symptoms, client info, mta info, log entries and config file. What other information can I provide? Please advise. Thanks, Danno symptoms: 1. Coming back to the idle client, and clicking on a newly arrived message, often … [View More]a long delay (seems like minutes, sometimes) will occur before the message loads from the server. 2. Sending messages, as often as not, the client will stall, sometimes indefinitely, on "copying message to sent folder". client: * usually not more than 2-3 clients running at any time. * Thunderbird 1.5.0.10 (on XP) * Thunderbird 1.5.0.5 (on FreeBSD 5.5) mta: * Sendmail 8.13.6/8.13.6 * $sudo sendmail -bt -d0.10 < /dev/null | grep HASFLOCK OS Defines: BSD4_4_SOCKADDR HASFCHOWN HASFCHMOD HASFLOCK === log entries May 3 21:27:09 tejas dovecot: imap-login: Login: user=<annie>, method=PLAIN, rip=71.216.71.193, lip =68.224.168.249, TLS May 3 21:28:00 tejas dovecot: IMAP(annie): Disconnected May 3 21:28:01 tejas dovecot: imap-login: Login: user=<annie>, method=PLAIN, rip=71.216.71.193, lip =68.224.168.249, TLS May 3 21:32:08 tejas dovecot: IMAP(annie): Disconnected for inactivity May 3 21:37:01 tejas dovecot: IMAP(annie): Disconnected May 3 21:37:02 tejas dovecot: imap-login: Login: user=<annie>, method=PLAIN, rip=71.216.71.193, lip =68.224.168.249, TLS May 3 21:37:55 tejas dovecot: IMAP(annie): Disconnected in IDLE May 3 21:38:18 tejas dovecot: IMAP(annie): Disconnected in IDLE May 3 21:56:02 tejas dovecot: imap-login: Login: user=<danno>, method=PLAIN, rip=71.216.71.193, lip =68.224.168.249, TLS May 3 21:56:17 tejas dovecot: IMAP(annie): Disconnected for inactivity May 3 21:58:32 tejas dovecot: IMAP(danno): Disconnected May 3 22:02:31 tejas dovecot: imap-login: Login: user=<danno>, method=PLAIN, rip=71.216.71.193, lip =68.224.168.249, TLS May 3 22:03:14 tejas dovecot: imap-login: Login: user=<danno>, method=PLAIN, rip=71.216.71.193, lip =68.224.168.249, TLS May 3 22:14:10 tejas dovecot: IMAP(annie): Disconnected May 3 22:14:38 tejas dovecot: IMAP(danno): Disconnected in IDLE May 3 22:16:24 tejas dovecot: imap-login: Login: user=<danno>, method=PLAIN, rip=71.216.71.193, lip =68.224.168.249, TLS May 3 22:16:33 tejas dovecot: imap-login: Login: user=<annie>, method=PLAIN, rip=71.216.71.193, lip =68.224.168.249, TLS May 3 22:16:44 tejas dovecot: imap-login: Login: user=<annie>, method=PLAIN, rip=71.216.71.193, lip =68.224.168.249, TLS May 3 22:18:36 tejas dovecot: imap-login: Login: user=<annie>, method=PLAIN, rip=71.216.71.193, lip =68.224.168.249, TLS May 3 22:19:16 tejas dovecot: IMAP(danno): Disconnected May 3 22:19:17 tejas dovecot: imap-login: Login: user=<danno>, method=PLAIN, rip=71.216.71.193, lip =68.224.168.249, TLS ===== config $grep -E -v '^ *(#|$)' dovecot.conf protocols = imaps login_process_size = 64 default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u mail_extra_groups = mail verbose_proctitle = yes first_valid_uid = 100 first_valid_gid = 0 mbox_read_locks = flock mbox_write_locks = flock protocol imap { imap_client_workarounds = delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep } protocol pop3 { pop3_uidl_format = %08Xu%08Xv pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } protocol lda { postmaster_address = postmaster(a)example.com sendmail_path = /usr/sbin/sendmail } auth default { mechanisms = plain passdb pam { } userdb passwd { } user = root } dict { } plugin { } [View Less]

3 2

[Dovecot] .imap files
by L. Scott Loftin 09 May '07

09 May '07

Dovecot version: 1.0.rc7 OS: Red Hat Fedora Core 6 CPU: x86 Filesystem: Linux I have recently upgraded from Fedora Core 4 to Fedora Core 6 (the FC6 was a clean install, not an upgrade). Prior to the upgrade, I used Dovecot to handle IMAP email that talked to Outlook clients. After the FC6 install and copying the .imap* files to the newly recreated user accounts, Outlook is not seeing the old email. Dovecot is creating new dovecot.* files to hold new email, not looking in the existing .… [View More]

4 6

[Dovecot] PATCH: Deliver looses mail and DSN if Return-Path is missing
by Steffen Kaiser 09 May '07

09 May '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, Dovecot v1.0.0 if there is no Return-Path in the message and Deliver cannot deliver the message, no DSN is sent _and_ the MTA is returned 0 (aka success) return code, which leads to mail loss. This is not the case, when the message actually finds a Return-Path, but fails to invoke the MTA. - --- src/deliver/mail-send.c (revision 47) +++ src/deliver/mail-send.c (working copy) @@ -42,7 +42,7 @@ i_info("msgid=%s: Return-Path … [View More]

3 5

[Dovecot] Dovecot Startup error
by kamran arshad 09 May '07

09 May '07

Hi, I have installed Dovecot 1.0.0 on a FreeBSD6.0 machine with Exim 4.66 and Vexim 1.5. When I restart the machine, dovecot does not load properly. The logs of /var/log/maillog are as: May 8 00:10:32 lhr dovecot: pop3-login: No authentication sockets found May 8 00:10:32 lhr dovecot: child 11478 (login) returned error 89 May 8 00:10:34 lhr dovecot: imap-login: No authentication sockets found May 8 00:10:34 lhr dovecot: child 11479 (login) returned error 89 When I kill it and then … [View More]

3 2

[Dovecot] lda reports a lot of errors
by Thomas Balsfulland 09 May '07

09 May '07

hello, i am using dovecot 1.0.rc15-1~bpo1 (from backports.org) on an debian sarge machine as lda imapd and pop3d with postfix 2.1.5-9. sometimes docvecot lda cannot write an mail to an existing mbox-file and the logfiles fills up with: deliver(user1(a)domain.tld): "2007-04-22 23:17:32 "Error: Cached message offset 6937844 is invalid for mbox file /home/vmail/domain.tld/user1 deliver(user1(a)domain.tld): "2007-04-22 23:17:32 "Error: Cached message offset 6937844 is invalid for mbox file /home/… [View More]

3 2

[Dovecot] [courier-dovecot-migrate.pl] - No such file or directory at courier-dovecot-migrate.pl line 230
by Wilkinson, Alex 09 May '07

09 May '07

Hi all, I am in the process of migrating my Maildir IMAP server from courier-imap to dovecot. I am now at the point of converting my Maildirs into a format that dovecot understands (as per http://wiki.dovecot.org/Migration/Courier) Problem: ------- #/usr/bin/perl courier-dovecot-migrate.pl --recursive Finding maildirs under . ./courierimapuiddb: OK No such file or directory at courier-dovecot-migrate.pl line 230. # Can anyone tell me what the problem is here ? And how to deal with it ? … [View More]

9 16