- dovecot - dovecot.org

Re: [Dovecot] dbox redesign
by Bill Boebel 19 May '07

19 May '07

On Sat, May 12, 2007 9:10 am, Timo Sirainen <tss(a)iki.fi> said: > 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. > Yes, I think treating mailboxes similary to keywords is ideal. There really is no reason to physically separate mailboxes on disk. All that is needed is this logical separation if it can be done in a reliable way. Or maybe track this in mailbox-specific index files, and also have a corespodning text file that stores a list of messages that are contained in that mailbox... similar to maildir's dovecot-uidlist file. Then if you lose the index you can rebuild the index from the text file. Bill

4 7

[Dovecot] dovecot-shared being ignored?
by bhayden＠umn.edu 19 May '07

19 May '07

So, I'm working on a shared folder. Everything is nice except for one bit. My dovecot-shared file in the Maildir is either being ignored, or doesn't work the way I think it does. Any messages copied into the Maildir using a mail client are mode 660 and owned by the user who did the copy. Perms on the dovecot-shared file are 700 (I'm using Solaris ACLs in addition to the Dovecot ACLs in order to prevent unauthorized access via means that don't pass through Dovecot's IMAP server... ie SFTP/SCP, and so I'm using 700 with a rwx mask and access to the file set per user in the Solaris ACL). The message files being created 660 means they are accessible via SFTP/SCP to anyone in the group, and we have a single one for (nearly) all users. This is not really acceptable, so if anyone can offer guidance on the dovecot-shared that'd be great. I checked the wiki, and it has very minimal information. -Brian

2 1

[Dovecot] Virtual mailbox plans
by Timo Sirainen 18 May '07

18 May '07

Configuration ------------- There could be global and user-specific configuration files, similar to how ACLs work. I think the global virtual mailboxes should be only defaults though, so that users could delete them and create a new mailbox (virtual or non-virtual) with the same name. The global virtual mailboxes could be described in a single file, such as: Trash deleted Work/My Unseen (mailboxes "box1" "box2" "box2/*") or to "tss(a)iki.fi" to "timo.sirainen(a)iki.fi" unseen So the format would be <virtual mailbox name> LF <search condition, allowed to wrap to new line> LF LF <next virtual mailbox, etc.> Per-user virtual mailboxes could also be listed in a similar file. If the search condition is empty, a globally defined virtual mailbox has been deleted. Another way would be to have per-mailbox dovecot-virtual files, but I'm not sure how global virtual mailboxes could then be easily deleted. Also having all of them in a single file makes listing the mailboxes pretty fast. The search condition would be a standard IMAP SEARCH reply, with the exception of the mailboxes parameter to specify what mailboxes are used. Virtual mailboxes would be implemented as a new mail storage backend, so their namespace configuration would be like: namespace private { prefix = "virtual/" location = virtual:~/virtual:GLOBAL=/etc/dovecot/virtual-globals.conf } Syncing ------- ~/virtual directory would contain index files for the virtual mailboxes. If the index files don't exist, a full resync for the virtual mailbox is done. This means opening all the real mailboxes configured for the vbox, running the SEARCH command and adding the returned UIDs to the vbox's indexes. The index would contain at least mailbox ID and message UID numbers. Probably would be a good idea to also save UIDVALIDITY numbers just to be safe, although that's a bit of a waste of space and it could be handled in other ways too, such as changing the mailbox ID whenever its UIDVALIDITY changes.. Mailbox IDs would be mapped to names in mailbox list index. This index already exists, although there still seems to be some bugs in it. At least creating a new list index has a race condition. I should look into making the list index a bit more realiable. Also the list indexes work only with Maildir++ layout currently. After the vbox has initially been synced, it needs to also handle updates. I think optionally the updates could be done the same way as full sync (opening all mailboxes to see if there are changes), but a faster way would be to update the virtual mailboxes immediately when the real mailboxes are being modified. So IMAP, POP3 and deliver all need to be aware of the virtual mailboxes and what real mailboxes are mapped to what virtual ones. Whenever doing a change that causes the message to either be added to or removed from a virtual mailbox according to their rules, the virtual mailbox's index is updated immediately. Being able to determine this change quickly might be the biggest change required to Dovecot's base code. Changes ------- Virtual mailboxes would share their state with the real mailbox, so any flag changes done in the vbox would be immediately changed in the real mailbox as well. The same goes for expunges. Virtual mailboxes' transaction logs would use different records for expunges and removals. Expunges would be handled normally, but removals wouldn't be removed from the in-memory view of the mailbox until EXPUNGE command was given (although they would be removed from dovecot.index immediately, so new sessions wouldn't see them). This makes it possible to have a vbox with only unseen messages, but without the message getting expunged immediately after a client opens the mail. So the EXPUNGE command could act as a "session synchronization" command. And of course it would also expunge the messages that had been marked as \Deleted.

1 0

[Dovecot] deliver exit codes?
by Ralf Hildebrandt 18 May '07

18 May '07

Before switching to dovecot deliver for all local deliveries, I'm calling deliver from maildrop (yes, don't laugh). Snippet from my global /etc/maildroprc: # Store maillist & junk messages directly /^Precedence: ?list/ if ( $MATCH ) { exception { log "Bulk message: $MATCH" #to "$DEFAULT" to "|$DELIVER" } } I replaced to "$DEFAULT" (meaning: delivery to $HOME/Maildir) with to "|$DELIVER" (meaning: pipe the mail into dovecot deliver, and deliver to INBOX = $HOME/Maildir) This works really well, UNLESS a user exceeds his/her quota: In that particular case, deliver fails to deliver the mail and generates a bounce, all on it's own. It's exit status is 0 in that case, so my MTA (postfix) thinks that the mail has been delivered successfully. I'd prefer deliver to return EX_TEMPFAIL, which I can pass through maildrop back to postfix, which will then log a temporary error and will bounce the mail all by itself after 5 days time. But how? -- Ralf Hildebrandt (Ralf.Hildebrandt(a)charite.de) plonk(a)charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de The Imperial Vendor or Contractor probably told them that droid armies don't need redundant command centers, nor any kind of high availability ... you're supposed to buy several, and cluster them. Redundant Array of Inexpensive Droids?

2 1

[Dovecot] Disable plaintext authentications
by Alexander Moisseev 18 May '07

18 May '07

Dear Sirs, I have Postfix 2.5 with Dovecot 1.0.0 as authentication server. Can I disable SMTP plaintext authentications for WAN clients, but allow it for LAN ones?

2 1

[Dovecot] UID larger than next_uid in file /hosts/domain/user/dovecot-uidlist
by Chris Jeans 18 May '07

18 May '07

I'm having the following problem and would appreciate any help or tips on how to fix it. None of my users can send email via pop3 or imap clients the only consistent thing that i keep seeing in the logs are the following 2 messages: UID larger than next_uid in file /hosts/domain/user/dovecot-uidlist sync: UID inserted in the middle of mailbox After searching the web all I can find is this link http://dovecot.org/list/dovecot-cvs/2007-May/008819.html which deals with Index: maildir-uidlist.c I'm running dovecot 1.0.0 on FreeBSD 6.2. -- Chris Jeans cmjeans(a)gmail.com

2 1

Re: [Dovecot] Replication plans
by Bill Boebel 18 May '07

18 May '07

On Fri, May 18, 2007 1:10 pm, Timo Sirainen <tss(a)iki.fi> said: > On Fri, 2007-05-18 at 12:20 -0400, Bill Boebel wrote: >> So what about tackling this replication problem from a different >> angle... Make it Dovecot's job to replicate the index and control >> files between servers, and make it the file system's job to replicate >> just the mail data. This would require further disconnecting the >> index and control files from the mail data, so that there is less >> syncing required. i.e. remove the need to check directory mtimes and >> to compare directory listings against the index; and instead assume >> that the indexes are always correct. Periodically you could still >> check to see if a sync is needed, but you'd do this must less >> frequently. > > This would practically mean that you want either cydir or dbox storage. > > This kind of a hybrid replication / clustered filesystem implementation > would simplify the replication a bit, but all the difficult things > related to UID conflicts etc. will still be there. So I wouldn't mind > implementing this, but I think implementing the message content sending > via TCP socket wouldn't add much more code anymore. > > The clustered filesystem could probably be used to simplify some things > though, such as UID allocation could be done by renaming a "uid-<next > uid>" file. If the rename() succeeded, you allocated the UID, otherwise > someone else did and you'll have to find the new filename and try again. > But I'm not sure if this kind of a special-case handling would be good. > Unless of course I decide to use the same thing for non-replicated > cydir/dbox. Dbox definitely sounds promising. I'd avoid putting this uid-<nextuid> file in the same location as the mail storage though, because if you can truly keep mail storage isolated and infrequently accessed, then you can do cool things like store your mail data remotely on Amazon S3 or equivalent.

1 0

Re: [Dovecot] LDAP for Virtual Domains
by Bryan Vyhmeister 18 May '07

18 May '07

On May 16, 2007, at 10:29 PM, razor wrote: > 17.05.07 в 05:06 Bryan Vyhmeister в своём письме > писал(а): > >> Is anyone using LDAP along with Dovecot where mail is being >> accessed in the form of /var/vmail/${domain}/${user}? I have not >> figured out how to extract the domain from LDAP in order to make >> this work. I know this is sparse information but maybe there is an >> easy fix. If not, I can post more information. >> >> Bryan > > i am using exim+dovecot+lda+openldap Thank you for the info. Bryan

1 0

[Dovecot] Wiki relating to subscriptions
by Bruce Bodger 17 May '07

17 May '07

On this wiki page http://wiki.dovecot.org/Migration/UW appears this information: "It's possible to keep using the .mailboxlist}} filename (as long as it's in the same directory) by modifying {{{SUBSCRIPTION_FILE_NAME define in src/lib-storage/index/mbox/mbox-storage.h" However, if a user wanted to continue using .mailboxlist wouldn't they also have to change the same define in src/lib-storage/index/ maildir/maildir-storage.h? Also, (regarding v1.0.0 code) the default define in mbox-storage.h is ".subscriptions" whereas the default define in maildir-storage.h is "subscriptions" (no dot) B. Bodger New York, NY

2 1

[Dovecot] Maildir format migration
by Tony Tsang 17 May '07

17 May '07

Hi all, I am planning to use dovecot IMAP on my server. Currently it is running UW-IMAP server with Maildir format storing users' mail. I've found that dovecot uses different Maildir format from UW-IMAP. Is there any configuration option for adapting dovecot to use format used by UW-IMAP? Thanks a lot. Tony.

4 7

[Dovecot] Processing too fast?
by Daniel L. Miller 17 May '07

17 May '07

I'm trying to use Dovecot to make administering ASSP a bit easier. I've created a mailbox with a number of subfolders (Spam, Ham, etc.) and have ASSP setup to save mail in the appropriate folder e.g. /var/mail/ASSP/.INBOX.Ham/new. But I'm having problems with ASSP complaining about the newly created files - I believe the file gets opened, then it disappears before ASSP finishes writing to it. Is Dovecot grabbing the file from "new" and moving it to "cur" faster than ASSP can write? How can I get around this? ASSP only allows for a folder to save each category to - I can't specify an LDA. -- Daniel

4 3

[Dovecot] CONVERT Plugin
by Bruce Bodger 17 May '07

17 May '07

Timo, Running v1.0.0 The convert plugin works pretty damn good! No need to mess with external utilities. One comment, though: Running here on OS X, I configured it with this convert_mail line: convert_mail = mbox:~/Library/Mail/IMAP/:INBOX=/var/mail/%u and mail_location = maildir:~/Maildir The IMAP directory was renamed to IMAP-converted after the process but the inbox (in /var/mail) does not get renamed. The WIKI sounds like it should be renamed to something, too. B. Bodger New York, NY

2 2

[Dovecot] Digest settings
by Kenny Dail 17 May '07

17 May '07

Timo, Wonder if you can tweak the digests to hold more messages? In 5 hours this morning, I've received 6 digests, seems a little excessive to me. -- Kenny Dail <kend(a)amigo.net>

2 1

[Dovecot] dbmail benchmarking
by Timo Sirainen 16 May '07

16 May '07

I thought I'd try benchmarking with dbmail (v2.2.4) to see how much slower a SQL backend could actually be. Skip to bottom for the conclusions. Originally I ran the tests with the databases being in XFS filesystem. MySQL's performance was horrible. It went 3-7x faster with ext3. MySQL 5.0.30 backend (innodb): ./imaptest clients=1 - append=100 seed=1 secs=30 msgs=1000000 logout=0 Logi Sele Appe 100% 100% 100% 5% 1 291 303 So that's 10 messages/sec saved. Now how about with 5 concurrent clients? Logi Sele Appe 100% 100% 100% 5% 5 1259 1332 Pretty well. Then something more generic: ./imaptest clients=1 seed=1 secs=30 msgs=1000000 logout=0 Logi List Stat Sele Fetc Fet2 Stor Dele Expu Appe 100% 50% 50% 100% 100% 100% 50% 100% 100% 100% 30% 5% 1 37 36 75 73 110 34 24 73 78 Without Fetc (header/metadata fetching): Logi List Stat Sele Fet2 Stor Dele Expu Appe 100% 50% 50% 100% 100% 50% 100% 100% 100% 30% 5% 1 94 94 199 283 102 85 198 210 PostgreSQL 8.1.5 backend: ./imaptest clients=1 - append=100 seed=1 secs=30 msgs=1000000 logout=0 Logi Sele Appe 100% 100% 100% 5% 1 267 277 ./imaptest clients=5 - append=100 seed=1 secs=30 msgs=1000000 logout=0 Logi Sele Appe 100% 100% 100% 5% 5 1094 1144 ./imaptest clients=1 seed=1 secs=30 msgs=1000000 logout=0 Logi List Stat Sele Fetc Fet2 Stor Dele Expu Appe 100% 50% 50% 100% 100% 100% 50% 100% 100% 100% 30% 5% 9 29 40 74 72 99 22 12 64 71 ./imaptest clients=1 seed=1 secs=30 msgs=1000000 logout=0 fetch=0 Logi List Stat Sele Fet2 Stor Dele Expu Appe 100% 50% 50% 100% 100% 50% 100% 100% 100% 30% 5% 35 105 95 200 277 54 70 165 175 The last two tests gave "Unexpected tagged reply:" errors that I didn't get with MySQL. So apparently there's some PostgreSQL-specific bug in dbmail. The same values with Dovecot 1.0 + maildir: ./imaptest clients=1 - append=100 seed=1 secs=30 msgs=1000000 logout=0 Logi Sele Appe 100% 100% 100% 5% 1 346 364 ./imaptest clients=5 - append=100 seed=1 secs=30 msgs=1000000 logout=0 Logi Sele Appe 100% 100% 100% 5% 5 1408 1470 ./imaptest clients=1 seed=1 secs=30 msgs=1000000 logout=0 Logi List Stat Sele Fetc Fet2 Stor Dele Expu Appe 100% 50% 50% 100% 100% 100% 50% 100% 100% 100% 30% 5% 1 130 133 259 258 382 123 127 257 271 ./imaptest clients=1 seed=1 secs=30 msgs=1000000 logout=0 fetch=0 Logi List Stat Sele Fet2 Stor Dele Expu Appe 100% 50% 50% 100% 100% 50% 100% 100% 100% 30% 5% 1 155 163 339 478 169 175 338 354 So, what are the conclusions? - In raw append speed dbmail is almost as fast as maildir. - In raw read/write speed maildir is about 1,6 times faster - When adding metadata fetches Dovecot is 4 times faster than dbmail. This is most likely because dbmail doesn't have a cache equivalent to dovecot.index.cache so it has to do the fetches the slow way. I would have liked to also run the generic tests with more than 1 client, but then I start hitting dbmail bugs and the test stops (reported already to their bugtracker).

3 5

[Dovecot] OS X Mail Administration
by Bruce Bodger 16 May '07

16 May '07

I'd like to request some feed back from any OS X Mail Admins on the list, please. Currently running 10.4.9 here using postfix / dovecot and I'm about to take the plunge from mbox to maildir. I just migrated from uw-imap to dovecot. As you're aware, users inbox's are customarily stored in /var/mail/% username and personal folders under /Users/%username/Library/Mail/IMAP. I'd appreciate if you'd share with me the directory structure that you use, or would use in my situation. All mail storage will be on the server so disk space is not an issue. I'm a bit confused whether or not to keep the inbox separate from the other imap structure as is the OS X default: should all mailboxes be under inbox, etc. Your input would be appreciated. Thank you, B. Bodger New York, NY

3 3

[Dovecot] Maildir POP3 "UID larger than next_uid" bug
by Alexander Moisseev 16 May '07

16 May '07

dovecot 1.0.0; Free BSD 6.2; x86; UFS; no NFS IMAP not uses at all, POP3 only Problem description: POP3 client can't fetch second e-mail message from Maildir if first POP3 connect occurs before any message placed in Maildir. Details: 1. POP3-client first time tries to receive mail: May 14 16:17:36 host dovecot: pop3-login: Login: user=<user(a)mydomain.ru>, method=PLAIN, rip=192.168.0.100, lip=192.168.0.3 May 14 16:17:36 host dovecot: POP3(user(a)mydomain.ru): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 dovecot creates Maildir for that user: /var/mail/virtual/mydomain.ru/user/Maildir/ /cur /new /tmp dovecot.index dovecot.index.cache dovecot.index.log 2. Postfix MTA receives message for that user and places it at /var/mail/virtual/mydomain.ru/user/Maildir/new/1179145269.V43I3f5a4M116738.host.mydomain.local 3. POP3-client tries to receive mail: May 14 16:23:09 host dovecot: pop3-login: Login: user=<user(a)mydomain.ru>, method=PLAIN, rip=192.168.0.100, lip=192.168.0.3 May 14 16:23:09 host dovecot: POP3(user(a)mydomain.ru): Disconnected: Logged out top=0/0, retr=1/786, del=1/1, size=770 >>>>> dovecot creates file dovecot-uidlist with next_uid=1 (!!!): 1 1179145056 1 1 1179145269.V43I3f5a4M116738.host.mydomain.local:2, Message fetched successfully. 4. POP3-client tries to receive mail: May 14 16:23:29 host dovecot: pop3-login: Login: user=<user(a)mydomain.ru>, method=PLAIN, rip=192.168.0.100, lip=192.168.0.3 May 14 16:23:29 host dovecot: POP3(user(a)mydomain.ru): UID larger than next_uid in file /var/mail/virtual/mydomain.ru/user/Maildir/dovecot-uidlist (1 >= 1) May 14 16:23:29 host dovecot: POP3(user(a)mydomain.ru): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 File dovecot-uidlist disappears. 5. Postfix MTA receives message for that user and places it at /var/mail/virtual/mydomain.ru/user/Maildir/new/1179145534.V43I3f5a4M116827.host.mydomain.local 6. POP3-client tries to receive mail: May 14 16:47:20 host dovecot: pop3-login: Login: user=<user(a)mydomain.ru>, method=PLAIN, rip=192.168.0.100, lip=192.168.0.3 May 14 16:47:20 host dovecot: POP3(user(a)mydomain.ru): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Dovecot creates file dovecot-uidlist: 1 1179145056 2 1 1179145534.V43I3f5a4M116827.host.mydomain.local Dovecot moves message from new to cur directory and adds flag ":2,": /var/mail/virtual/mydomain.ru/user/Maildir/cur/1179145534.V43I3f5a4M116827.host.mydomain.local:2, Message not fetched. And POP3 client can't fetch it at all. All next messages fetches normally as they arrives. # /usr/local/etc/dovecot.conf protocols: pop3 pop3s ssl_cert_file: /etc/ssl/certs/host.mydomain.ru.crt ssl_key_file: /etc/ssl/private/host.mydomain.ru.key disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/pop3-login login_greeting: POP3 server ready verbose_proctitle: yes first_valid_gid: 0 mail_extra_groups: mail mail_location: maildir:~/Maildir mail_executable: /usr/local/libexec/dovecot/pop3 mail_plugin_dir: /usr/local/lib/dovecot/pop3 pop3_uidl_format: %08Xu%08Xv pop3_client_workarounds: outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login digest-md5 cram-md5 apop ntlm default_realm: mydomain.ru passdb: driver: pam passdb: driver: passwd-file args: /etc/auth/%d/passwd userdb: driver: passwd userdb: driver: static args: uid=5000 gid=5000 home=/var/mail/virtual/%d/%n socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master:

2 1

[Dovecot] imap-login: Disconnected: Connection queue full
by Ralf Hildebrandt 16 May '07

16 May '07

I'm getting "imap-login: Disconnected: Connection queue full:" messages like these: May 16 12:17:26 postamt dovecot: imap-login: Disconnected: Connection queue full: rip=160.45.172.202, lip=141.42.4.250 May 16 12:17:26 postamt dovecot: imap-login: Disconnected: Connection queue full: rip=141.42.165.160, lip=141.42.4.250, TLS May 16 12:18:23 postamt dovecot: imap-login: Disconnected: Connection queue full: rip=193.175.70.61, lip=141.42.4.250 Should I worry about these messages or are they of informational character only? Does it mean that the imap-login encountered more than "login_max_connections" and thus a new process had to be spawned? Is there a parameter I should be changing (config below) # /usr/local/sbin/dovecot --version 1.0.0 ---- snip --- # /usr/local/etc/dovecot.conf protocols: imap imaps pop3s ssl_cert_file: /etc/ssl/certs/postamt.pem ssl_key_file: /etc/ssl/private/postamt.key disable_plaintext_auth: no 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 login_process_per_connection: no login_process_size: 64 login_max_connections: 32 verbose_proctitle: yes mail_location: maildir:~/Maildir mail_read_mmaped: yes fsync_disable: yes maildir_copy_with_hardlinks: yes maildir_copy_preserve_filename: 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 imap_client_workarounds(default): outlook-idle netscape-eoh imap_client_workarounds(imap): outlook-idle netscape-eoh imap_client_workarounds(pop3): outlook-idle pop3_lock_session(default): no pop3_lock_session(imap): no pop3_lock_session(pop3): yes pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %v-%u pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh namespace: type: private separator: . prefix: INBOX. inbox: yes auth default: passdb: driver: pam userdb: driver: passwd plugin: quota: maildir quota: maildir:ignore=Trash ---- snip --- -- Ralf Hildebrandt (i.A. des IT-Zentrums) Ralf.Hildebrandt(a)charite.de Charite - Universitätsmedizin Berlin Tel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-Berlin Fax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to plonk(a)charite.de

2 4

[Dovecot] Login with firstname.lastname instead of loginname
by Ralf Hildebrandt 16 May '07

16 May '07

Some of our users use to login as firstname.lastname or firstname.lastname(a)charite.de instead of using the "correct" "flastname" login name. In order to get this behaviour a long-gone co-worker wrote an authdaemon.pl, which speaks the courier-authdaemon protocol. How can I emulate this behaviour with dovecot? Basically, all I need is a usernamen mapping ala: Ralf.Hildebrandt(a)charite.de rhilde Ralf.Hildebrandt rhilde for all my users -- I can generate this programatically using awk, but how can I make dovecot use that? -- Ralf Hildebrandt (i.A. des IT-Zentrums) Ralf.Hildebrandt(a)charite.de Charite - Universitätsmedizin Berlin Tel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-Berlin Fax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to plonk(a)charite.de

2 6

[Dovecot] Sorting by Received vs Sent
by Bill Boebel 16 May '07

16 May '07

Looks like in Cyrus, sorting by Received date is faster than sorting by the Sent header date because of the way they use the index and cache files... http://www.emaildiscussions.com/showpost.php?p=419246 Is this the case in Dovecot as well? Bill

2 1

[Dovecot] deleted Messages don't go into Trash Folder always
by Rainer Sigl 16 May '07

16 May '07

Hi all, most of the time deleted messages aren't moved into trash folder but go into nirwana. Sometimes it works correctly. But a restart does not guarantee this function. This effect exists with different imap clients. Can anybody help please. Rainer Sigl -- ----------------- Rainer Sigl, | email: sigl(a)mpe.mpg.de MPI f. extraterrestrische Physik, | phone: +49 (89) 30000-3557 Postfach 1312, | fax: +49 (89) 30000-3569 D-85741 Garching, Germany | web: http://www.mpe.mpg.de/~sigl/

3 3

[Dovecot] List problems?
by Charles Marcus 16 May '07

16 May '07

Hi Timo, Sorry to bother you, but I'm used to having at least 10-20 in the morning. This morning there are none... and the last one is from 3:00pm yesterday? So, this is a test, I guess... -- Best regards, Charles

2 1

[Dovecot] Deliver sending bounces from 'MAILER-DAEMON@'
by Erland Nylend 16 May '07

16 May '07

Hello, I'm having a problem with postfix and/or dovecots "deliver". I'm getting these lines in the mail log: | Apr 24 11:42:08 smtp2 postfix/qmgr[6176]: 05BAE3B67E: from=<>, size=3055, nrcpt=1 (queue active) | Apr 24 11:42:08 smtp2 postfix/qmgr[6176]: 05BAE3B67E: to=<MAILER-DAEMON@>, relay=none, delay=0.01, delays=0.01/0.01/0/0, dsn=5.1.3, status=bounced (bad address syntax) After some debugging, it seems that those lines in the log appear if I send mail to an account which is over quota. (I'm using the Maildir++ quota) This is from my dovecot.conf: | protocol lda { | postmaster_address = MAILER-DAEMON(a)my.domain.tld | mail_plugins = quota | auth_socket_path = /var/run/dovecot/auth-master | hostname = my.mail.server | sendmail_path = /usr/sbin/sendmail | } It seems to me that dovecot is sending bounce messages from 'MAILER-DAEMON@' .. Does anyone know why this is happening, or how I can specify the address to be used? I'm using dovecot 1.0.0. -- Erland Nylend

2 5

[Dovecot] assertion failed
by Adrian Stoica 15 May '07

15 May '07

What is this ? dovecot: Apr 24 13:03:29 Error: IMAP(tina.burdujan): file maildir-sync.c: line 1075 (maildir_sync_index): assertion failed: (uid >prev_uid) dovecot: Apr 24 13:03:29 Error: IMAP(tina.burdujan): Raw backtrace: /usr/libexec/dovecot/imap [0x80b8741] -> /usr/libexec/dovecot/imap [0x80b819c] -> /usr/libexec/dovecot/imap(maildir_sync_index+0x898) [0x80695f8] -> /usr/libexec/dovecot/imap [0x80698b3] -> /usr/libexec/dovecot/imap(maildir_ storage_sync_init+0x49) [0x8069aa9] -> /usr/libexec/dovecot/imap(imap_sync_init+0x40) [0x8062620] -> /usr/libexec/dovecot/imap(cmd_sync+0x71) [0x8 062b81] -> /usr/libexec/dovecot/imap(cmd_noop+0x26) [0x8059c76] -> /usr/libexec/dovecot/imap [0x805be7f] -> /usr/libexec/dovecot/imap [0x805bf20] -> /usr/libexec/dovecot/imap(_client_input+0x6c) [0x805c0fc] -> /usr/libexec/dovecot/imap(io_loop_handler_run+0xff) [0x80bef6f] -> /usr/libexec/do vecot/imap(io_loop_run+0x36) [0x80be366] -> /usr/libexec/dovecot/imap(main+0x46c) [0x806448c] -> /lib/libc.so.6(__libc_start_main+0xb9) [0xb7eb4e1 9] -> /usr/libexec/dovecot/imap [0x80568b1] dovecot: Apr 24 13:03:29 Error: child 25748 (imap) killed with signal 6 My conf is: exim + dovecot + mysql exim deliver mail to maildir , because i don't know how to use LDA from dovecot. the maildirs are very large, for one account could be 30000 mails. dovecot is version 1.0.0 dovecot -n shows: # /etc/dovecot.conf base_dir: /var/run/dovecot/login log_path: /var/log/mail.log login_dir: /var/run/dovecot login_executable: /usr/libexec/dovecot/imap-login login_process_per_connection: no login_process_size: 80 login_processes_count: 10 login_max_processes_count: 50 login_max_connections: 80 first_valid_uid: 1001 last_valid_uid: 1001 mail_extra_groups: exim,vmail mail_location: maildir:%Lh/Maildir mail_cache_min_mail_count: 1 dotlock_use_excl: yes fsync_disable: yes maildir_copy_with_hardlinks: yes maildir_copy_preserve_filename: yes mail_drop_priv_before_exec: yes mail_executable: /bin/imap.sh mail_plugins: quota imap_quota auth default: mechanisms: PLAIN CRAM-MD5 default_realm: testing.net cache_size: 256 worker_max_count: 100 passdb: driver: sql args: /etc/dovecot-crammd5.conf userdb: driver: prefetch plugin: quota: maildir

3 12

[Dovecot] Problems with Shared Mailbox
by Gerhard Schmidt 15 May '07

15 May '07

Hi, i've installed dovecot on a new mailserverand try to set up some shared mailboxes. I have everiting up an runnig so far. I have 3 mboxes to be shared. I have use the following setup namespace private { separator = prefix = location = inbox = yes hidden = yes } namespace public { separator = / prefix = zentrale/ location = mbox:/var/mail/shared:CONTROL=/var/mail/shared/.control:INDEX=/var/mail/shared/.index } the problem is with the dovecot.index files [root@mailserv /var/mail/shared/.index]# ls -alR total 6 drwxrwx--- 3 dovecot vhsal 512 May 7 13:49 . drwxrwx--- 4 mailnull vhsal 512 May 7 13:52 .. drwxrwx--- 5 dovecot vhsal 512 May 7 13:49 .imap -rw-rw---- 1 dovecot vhsal 0 May 7 13:49 dovecot-shared ./.imap: total 10 drwxrwx--- 5 dovecot vhsal 512 May 7 13:49 . drwxrwx--- 3 dovecot vhsal 512 May 7 13:49 .. drwxrwx--- 2 dovecot vhsal 512 May 7 13:50 Eingang drwxrwx--- 2 dovecot vhsal 512 May 7 13:49 Erledigt drwxrwx--- 2 dovecot vhsal 512 May 7 13:50 Spam -rw-rw---- 1 dovecot vhsal 0 May 7 13:49 dovecot-shared ./.imap/Eingang: total 38 drwxrwx--- 2 dovecot vhsal 512 May 7 13:50 . drwxrwx--- 5 dovecot vhsal 512 May 7 13:49 .. -rw-rw---- 1 dovecot vhsal 0 May 7 13:50 dovecot-shared -rw-rw---- 1 dovecot vhsal 896 May 7 13:51 dovecot.index -rw-rw---- 1 dovecot vhsal 23552 May 7 13:51 dovecot.index.cache -rw-rw---- 1 dovecot vhsal 6824 May 7 13:51 dovecot.index.log ./.imap/Erledigt: total 30 drwxrwx--- 2 dovecot vhsal 512 May 7 13:49 . drwxrwx--- 5 dovecot vhsal 512 May 7 13:49 .. -rw-rw---- 1 dovecot vhsal 0 May 7 13:49 dovecot-shared -rw-rw---- 1 dovecot vhsal 456 May 7 13:52 dovecot.index -rw-rw---- 1 dovecot vhsal 20480 May 7 13:45 dovecot.index.cache -rw-rw---- 1 dovecot vhsal 3364 May 7 13:52 dovecot.index.log ./.imap/Spam: total 26 drwxrwx--- 2 dovecot vhsal 512 May 7 13:50 . drwxrwx--- 5 dovecot vhsal 512 May 7 13:49 .. -rw-rw---- 1 dovecot vhsal 0 May 7 13:50 dovecot-shared -rw-rw---- 1 dovecot vhsal 240 May 7 13:51 dovecot.index -rw-rw---- 1 dovecot vhsal 17408 May 7 13:45 dovecot.index.cache -rw-rw---- 1 dovecot vhsal 648 May 7 13:51 dovecot.index.log When the directory is setup like this everthing works as planed. But sometimes (havn't quite figured when exactly the dovecot.index file of one of the Mailboxes is regenated with the false permissions set ./.imap/Eingang: total 38 drwxrwx--- 2 dovecot vhsal 512 May 7 13:53 . drwxrwx--- 5 dovecot vhsal 512 May 7 13:49 .. -rw-rw---- 1 dovecot vhsal 0 May 7 13:50 dovecot-shared -rw------- 1 estartu vhsal 376 May 7 13:53 dovecot.index -rw-rw---- 1 dovecot vhsal 23552 May 7 13:53 dovecot.index.cache -rw-rw---- 1 dovecot vhsal 7116 May 7 13:53 dovecot.index.log How can I gate dovecot to set the permissions of this files to rw-rw---- I am using Dovecot v1.0.rc29 Regards Gerhard Schmidt -- ---------------------------------------------------------------------------- Gerhard Schmidt | Nick : estartu IRC : Estartu | Fischbachweg 3 | | PGP Public Key 86856 Hiltenfingen | EMail: estartu(a)augusta.de | on request Germany | |

2 3

[Dovecot] Thunderbird or Dovecot bug? (multiple keywords)
by Troy Engel 15 May '07

15 May '07

Here's a strange one. I have a user who's using Thunderbird 2.0.0 and assigning multiple tags (keywords) to emails, which are getting "lost" (I'll explain) when he leaves the folder and comes back. I can reproduce this on *his* account myself, but cannot reproduce it on *my* account (separate new TBird 2.0.0 profiles on Windows XP). Use the two TBird default tags 'Important' and 'Work' for all these tests, which it refers to as $Label1 and $Label2 in IMAP-keywords land. If I go into my account, label an email with both tags, it sticks -- I can click on Drafts then back to Inbox, and both tags/keywords still show in the client. If I go into his account, add the two tags, then click on Drafts and back on Inbox, only the *second* tag (Work, $Label2) shows. If I remove that tag, then the first tag (Important, $Label1) immediately pops up! On the backend the actual Maildir files match the dovecot-keywords and have the correct letter appended in both cases - so, in his account when the email only shows one tag, the physical mail file has the letters for two tags. So Thunderbird should be showing both tags, like it does in my account where everything is working correctly. This leads me to believe that the problem has something to do with the difference of dovecot-keywords content, and the interaction TBird has with Dovecot. My account, working correctly, looks like: dovecot-keywords: 0 $Forwarded 1 $MDNSent 2 $Label2 3 $Label1 file: Maildir/cur/1178712608.H529732P11686.yak.fluid.com:2,RSdc ...which matches, d=$Label1 (Important), c=$Label2 (Work) and TBird is displaying the email as having both tags - all is well and good. Now, his account looks like: dovecot-keywords: 0 Junk 1 NonJunk 2 $Label4 3 $Label1 4 $Label2 5 $Label3 6 $Label5 file: Maildir/cur/1178728930.P28392Q0M960111.yak.fluid.com:2,RSbde ...again, everything matches on the server; yet, it Thunderbird is only displaying $Label2 (d,3). I also noticed something interesting, even if I have the TB 'Junk Controls' completely disabled on his account, and remove all tags using the menu option, that file still retains the 'b' (NonJunk) tag in the filename: Maildir/cur/1178728930.P28392Q0M960111.yak.fluid.com:2,RSb All this long-winded explanation leads me to believe that somehow the difference in dovecot-keywords is causing this problem, but what I can't tell is who's problem it is -- Dovecot, or Thunderbird? Thoughts welcome, -te PS: all the normal things tried like deleting the dovecot index files, Thunderbird cache files and profiles, etc. -- Troy Engel | Systems Engineer Fluid, Inc | http://www.fluid.com

2 3

[Dovecot] Why is direct invocation of dovecot preferred over inet inclusion?
by Stewart Dean 15 May '07

15 May '07

I'm used to putting things in inetd and, 1) should dovecot crash, I'd think it would get restarted if it was invoked from inet's imap-login 2) it would get started well after the boot ...wouldn't that be preferable. Enlighten me, please -- ==== 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

2 1

[Dovecot] Refreshing Dovecot
by Stewart Dean 15 May '07

15 May '07

If I've made configuration changes, is there a way to refresh...without killing and restarting....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

5 5

[Dovecot] maildir_file_do(/var/admhome/user/Maildir) racing
by Ralf Hildebrandt 15 May '07

15 May '07

dovecot version 1.0.0, compile from the sources. --------- snip -------- # /usr/local/etc/dovecot.conf listen: *:10143 ssl_listen: *:10943 ssl_cert_file: /etc/ssl/certs/postamt.pem ssl_key_file: /etc/ssl/private/postamt.key disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login mail_location: maildir:~/Maildir mail_plugins: quota imap_quota namespace: type: private separator: . prefix: INBOX. inbox: yes auth default: passdb: driver: pam userdb: driver: passwd plugin: quota: maildir quota: maildir:ignore=Trash --------- snip -------- We're using these odd ports, because there's still courier-imap on the original ports. One, just one (!) of our users gets: May 14 16:47:17 postamt dovecot: imap-login: Login: user=<username>, method=PLAIN, rip=141.42.x.y, lip=ip.of.the.server May 14 16:47:17 postamt dovecot: imap-login: Login: user=<username>, method=PLAIN, rip=141.42.x.y, lip=ip.of.the.server May 14 16:47:17 postamt dovecot: IMAP(username): maildir_file_do(/var/admhome/username/Maildir) racing May 14 16:47:17 postamt dovecot: IMAP(username): Disconnected: Internal error occurred. Refer to server log for more information. [2007-05-14 16:47:17] Now it's a bit hard for me to see what's going on. /var/admhome/username/Maildir is on /, thus: $ mount /dev/cciss/c0d0p6 on / type ext3 (rw,errors=panic) $ dmesg does not complain about any corruption $ uname -a Linux postamt.charite.de 2.6.21.1 #1 SMP Tue May 1 15:50:11 CEST 2007 i686 GNU/Linux OS: Debian testing -- Ralf Hildebrandt (i.A. des IT-Zentrums) Ralf.Hildebrandt(a)charite.de Charite - Universitätsmedizin Berlin Tel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-Berlin Fax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to plonk(a)charite.de

3 6

[Dovecot] Question: contention with blackberry
by Stewart Dean 15 May '07

15 May '07

My production imap is currently UWIMAP with mbox.. One of the problems commonly observed is mailbox lock loss, which happens when: a) a VIP has multiple secretaries accessing a single mailbox (actually, they are professional enough to have figured the realities of conflicting access and rarely have a problem), b) somebody leaving their machine on at home and coming in and firing up their work computer c) important people with Blackberries....and the BB service polls the mailbox every so often and breaks the lock. In any case, the maillog ends up with a message like this: > May 5 19:45:04 mercury mail:info imapd[2035774]: Logout user=xxxxx host=bda056.bis.na.blackberry.com [216.9.249.56] > May 5 19:46:52 mercury mail:info imapd[2502902]: Killed (lost mailbox lock) user=xxxxx host=cpe-24-161-103-11.hvc.res.rr.com [24.161.103.11] How will this work with Dovecot? I regard what is happening now as OK, working as designed. Although we may eventually move to a different mailbox format, I am only switching from UW to DC in the first step. -- ==== 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

3 2

[Dovecot] global vs user script
by M1 15 May '07

15 May '07

What is the order of execution if both user and global sieve script exists? Thanks.

4 10

[Dovecot] Mails, work and so on
by Timo Sirainen 14 May '07

14 May '07

You can probably guess from my flood of mails that I'm no longer busy. I still have a couple of exams but since I haven't spent any time at all studying for them or attending the lectures, I can just as easily leave them for next year. I've read and answered most of the "easy" mails in this list and in my INBOX. I'll try to answer the rest of them this weekend, so no need to forward them to me again, at least not yet. :) Now that I'm finally non-busy, it also appears that I haven't worked for a long time and I'm almost broke. :) So now would be a great time for your corporation to buy/sponsor some Dovecot development. Otherwise I'm probably soon busy with non-Dovecot related work. My own high priority TODO contains: - Get the rewritten Squat full text search index working. It probably needs a name change, since it's not all that close to Cyrus Squat anymore. Suggestions? Could of course be just "fts_dovecot". - Shared mailboxes / ACLs - dbox cleanups and possibly partial redesign. I'll write a separate mail about this later. - Index file code cleanups, simplifications and optimizations. Make it work with NFS with attribute cache enabled.

5 7

[Dovecot] How to get rid of locks
by Timo Sirainen 14 May '07

14 May '07

Although Dovecot is already read-lockless and it uses only short- lived write locks, it's be really nice to just get rid of the locking completely. :) I just figured out that O_APPEND is pretty great. If the operating system updates seek position after writing to a file opened with O_APPEND, writes to Dovecot's transaction log file can be made lockless. I see that this works with Linux and Solaris, but not with OS X. Could you BSD people try if it works there? http://dovecot.org/ tmp/append.c and see if it says "offset = 0" (bad) or non-zero (yay). The O_APPEND at least doesn't work with NFS, so it'll have to be optional anyway. Currently Dovecot always updates dovecot.index file after it has done any changes. This isn't really necessary, because the changes are already in transaction log, so the dovecot.index file can be read to memory and the new changes applied on top of it from transaction log (this is pretty much how mmap_disable=yes works). So I'm going to change this to work so that the dovecot.index is updated only if a) there are enough changes in transaction log (eg. 8kB or so) and b) it can be write-locked without waiting. Maildir then. It has this annoying problem that readdir() can skip files if another process is rename()ing them, causing Dovecot to think that the message was expunged. The only way I could avoid this by locking the maildir while synchronizing it. Today I noticed that this doesn't happen with OS X. I'm not sure if I was just lucky or if there really is something special implemented in it, because it doesn't work anywhere else. I'm not sure if this is tied to HFS+, or if it will work with zfs also (Solaris+zfs didn't work). So perhaps the locking could be disabled while running with OS X. More importantly I figured out that it can also be avoided with Linux +inotify. As long as the inotify event buffer doesn't overflow, the full list of files can be read by combining the readdir() output and files listed by inotify events. If the inotify buffer overflows (highly unlikely), the operation can just be retried and it most likely works the next time. So with these changes in place, changing a message flag or expunging a message would usually result in: - lockless write() call to dovecot.index.log - lockless read()ing (or looking into mmaped) dovecot.index.log to see if there's some new data besides what we just wrote that needs to be synchronized to maildir - rename() or unlink() calls to maildir. If a call return ENOENT, the maildir needs to be readdir()ed with inotify enabled to find the new filename. Not a single lock in the operation, assuming that dovecot.index file wasn't updated. Assigning UIDs to newly delivered mails would require locking though. dovecot-uidlist needs to be locked, and the UIDs need to be written to dovecot.index.log file in the correct order, which can also be done with dovecot-uidlist locking. Actually a single write() to dovecot.index.log isn't enough. I think there needs to be some kind of a flag written to the beginning of the transaction which marks the transaction as truly finished. If the flag isn't there, any reader knows to stop and wait until the flag is set. So this means that the writer needs to: 1. Do a single O_APPENDed write() call writing the whole transaction 2. Get the current offset with lseek(fd, 0, SEEK_CUR) (this is what the append.c tester checks) 3. pwrite() the finished-flag to beginning of the transaction Except at least with Linux pwrite() doesn't work if O_APPEND is enabled. There are two ways to work around this: a) fcntl(disable O_APPEND) + pwrite() + fcntl(enable O_APPEND) b) Keep two file descriptors open for the transaction log. First with O_APPEND flag and second without. pwrite() to the second one. a) is probably better because it doesn't waste file descriptors.

8 10

[Dovecot] PATCH: sendmail-like DSNs in Dovecot deliver (EX_TEMPFAIL always)
by Steffen Kaiser 14 May '07

14 May '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I've put together an always tempfail & sendmail-like DSN report back patch. Because I don't know how to transform the rejection reason into sysexit.h codes, it always tempfails. The hooks are so that: a) config file setting: lda_mode = mode b) command line: deliver --mode mode where mode is default or sendmail. When no mode is specified, it defaults to "default", which is the current behaviour. In sendmail mode, mail_send_rejection() simply prints the rejection reason to stdout, logs it and returns EX_TEMPFAIL. Ideally, the return value would be specific to the reason. I haven't poked into this deeply, but it doesn't look straight forward. Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBRkHNQS9SORjhbDpvAQIhdggAq79RHKa1gIUTFwAu7Gd2maIUkDTgbNu6 8+MEQHujOPkV6wcF+5ih/hkht5BnuBUiIbnp2dvKGaUcHY8avzYD6BEc6gIAyJjM YIKDANI5+BVnQWUdiQMlQrSrRIZBqFziL8v/LvICJUsiOqCKT7se37KuUOK14gXO FSghuPta0rorogJ8kh+VGdmnqNVzKb6eKrnFQUggiezTmTcHY6/DRsLbsKV//fyW cybualj+THF9cj+EajwCMsYypc9KOdVg6lhcCD87oskDmMqcG5lwF2HU9nclnMxE 6pOnaLGNfKmWyeAKOLgvMimjhkU74+NBwQ+b4h61JzZ6lbiZKWX7wA== =gE8Z -----END PGP SIGNATURE-----

3 5

[Dovecot] PATCH Deliver forgets sendmail_path if DEBUG is set
by Steffen Kaiser 14 May '07

14 May '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, Dovecot v1.0.0 deliver erases the environment if DEBUG is set, hence, also (probably) erases SENDMAIL_PATH if it has been read from configuration file. This happens with: Debian Etch, libc-2.3.6.so, gcc (GCC) 4.1.2 20061115 (prerelease) (Debian 4.1.1-21). Problem in log: May 10 12:33:07 ux-2s11-9 deliver(dvtest): execv() failed: No such file or directory May 10 12:33:07 ux-2s11-9 deliver(dvtest): Sendmail process terminated abnormally, exit status 75 Note the empty string in the function call execv(). Attached patch just deletes the DEBUG variable. Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBRkL45y9SORjhbDpvAQKeTAgAr6i6XrICqZsTaezUFqXO69cuwOt4iL5u K3PAF0ywAtrRkpWG+G8TUtypUkLp+CGEK3Ery1mWVp2/TeNPv6LxeUWWGxmdlSV3 XFQSV/VRuPtJ/Uc8wFWOBcpAn0H9rnLNkF5vv512t4zs99eF10++US5fZwFOXK8M azgaCEYwOrmZ4U2sCQwVQChXcZQq6MI5IcE3ChpzlUP45bq2dVZrXqAZ/xNo1iuG lQd/43XJu1++LxB8N1Fkbaeme+Ojt/c5fOKApjhnCJuQwi46jnSEeHbO2VUCz+ST mU34QR3zx+h4YW91oKQhFYkbSWEYmuXk2OoZaFUd1Q+E+oXHHuDBng== =CiqO -----END PGP SIGNATURE-----

2 2

[Dovecot] header-lines of subfolders have to be rescanned after each client startup
by Rainer Sigl 14 May '07

14 May '07

Hi all, after each startup of my different mail clients (thunderbird, outlook, ...) the contents of subfolders if I click in has to be renewed. This takes some time for large folders. I just migrated from courier. And there all subfolders were available immediately. Is there something to configure? Another effect regarding subfolders is that the client forgets, which subfolders were opened after shutdown and shows the folders closed. This means, that necessary subfolders have to be reopened after each startup. This was managed as well by my previous courier server. Many thanks for answers Rainer Sigl -- ----------------- Rainer Sigl, | email: sigl(a)mpe.mpg.de MPI f. extraterrestrische Physik, | phone: +49 (89) 30000-3557 Postfach 1312, | fax: +49 (89) 30000-3569 D-85741 Garching, Germany | web: http://www.mpe.mpg.de/~sigl/

2 4

[Dovecot] v1.1 plans
by Timo Sirainen 14 May '07

14 May '07

I think I won't do any actual releases until it's mostly feature complete. Then maybe v1.1.alpha1 or v1.1.beta1. So if you want to test it before then, use CVS or the nightly snapshots. I'm planning on keeping v1.1 almost completely compatible with v1.0. There could be some minor configuration file changes, but for most people v1.0's dovecot.conf should work with v1.1. I want to update index file handling to use less locks and update dovecot.index file less often. The file formats would still stay backwards compatible with v1.0. After this I'm hoping to get index files working well with NFS even with attribute cache enabled. Dovecot v2.0 then brings incompatible index files and more or less rewritten configuration file handling. It could still support old config file format and settings, but the default will be somewhat different. I'm hoping to release the first alphas/betas in 2-3 months, with v1.1.0 maybe even as early as next summer. The good thing here is that index file code hasn't changed much since v1.0, so it should be stable. The bad thing is that I've added a couple of completely new indexes. I'm also quite busy for the next month, but I'm not sure how much it affects my coding. :) The largest already implemented new features are: + Added support for IMAP UIDPLUS extension + IMAP SORT: Sort keys are indexed, which makes SORT commands faster. + IMAP THREAD: Threads are indexed into a dovecot.index.thread file. It can usually be updated incrementally, so this makes THREAD fast. + Added Dovecot-specific X-REFERENCES2 threading algorithm. It's similar to REFERENCES, but it doesn't do base subject merging and it sorts the threads by their newest message. + When saving messages, update cache file immediately with the data that we expect client to fetch later. Maildir-only currently. + Mailbox list indexes. Mailbox metadata is stored there, so STATUS commands can return synchronized mailboxes' metadata simply by reading a single mailbox list index file. - FIXME: Currently works only with Maildir++ layout. + Expire plugin can be used to keep track of oldest messages in specific mailboxes. A nightly run can then quickly expunge old messages from the mailboxes that have them. The tracking is done using lib-dict, so you can use either Berkeley DB or SQL database. + Namespaces are supported everywhere now. - FIXME: except by convert plugin + Full text search indexing support with Lucene and Squat backends. + OTP and S/KEY authentication mechanisms (by Andrey Panin). + mbox and Maildir works with both Maildir++ and FS layouts. You can change these by appending :LAYOUT=maildir++ or :LAYOUT=fs to mail_location. Features that I'm planning on implementing: - Fully supported shared mailboxes and IMAP ACL extension - Replace Squat FTS indexes with my new design - Case-insensitive searches with non-ASCII text as well - Maybe add support for all kinds of IMAP extensions that can be easily supported. LEMONADE extensions especially: CONDSTORE, CATENATE and maybe even URLAUTH if I can figure out how it should work. If a feature can be implemented completely as a plugin, it could still come in v1.1.beta stage, because it won't destabilize the rest of the Dovecot anyway.

17 36

[Dovecot] Feature Request: content-filter / MOVE scripts
by Daniel L. Miller 14 May '07

14 May '07

Since your "1.1 plans" announcement somehow turned into everybody handing in a wish list . . . thought I'd start one by itself - since I expect a few people to have opinions on this matter. I'm aware of a plug-in functionality in Dovecot, and that a plug-in exists for dspam processing - but my review of the plug-ins indicate they require compiling your own Dovecot - the plug-in setup isn't really suitable for packaged distros. As a packaged software user - I really really really don't like compiling my own software, either for features or bugfixes - I want leave that to the experts. On learning of 1.0's official release, I nudged the Debian package maintainers to check - and they were already on it and it updated. Thanx Timo, Jaldhar, and Fabio. I have some thoughts on an interface that would eliminate the need for compile-time plug-ins, but provide some major power to sysadmins. Basically, I want a way of telling an external program the following: 1. A message was moved. 2. The folder is moved from was XXX. 3. The folder it moved to was YYY. 4. The message moved was ZZZ. Armed with this information, just about anybody's spam fighting learn scripts can be called to do their thing. A few different ways have occurred to me: 1. Have a dedicated "content-filter" functionality built-in to Dovecot. Under this model, Dovecot.conf would include at least three new parameters: FILTER-FOLDER-SUFFIX, FILTER-FOLDER-IN-SCRIPT, and FILTER-FOLDER-OUT-SCRIPT. Whenever a message is moved into or out of a folder ending in SUFFIX the appropriate SCRIPT is called, with the arguments above being passed. 2. A bit more generic, less processing for Dovecot. Dovecot.conf parameter ACTION-SCRIPT (hey, feel free to use other names - I'm just brainstorming here). Any time any message is moved anywhere, call SCRIPT with the arguments. Having never looked at Dovecot's code, I'm just guessing, but this probably wouldn't take much to implement - but might be the most performance affecting. 3. Have a definable named-pipe to send the same information to. 4. Have a definable TCP socket to send the same information to. In any case, I figure it's best to prevent any message processing by Dovecot itself - so while it might be nice to define a list of headers to send to the scripts, instead of the whole message, that's probably not appropriate for Dovecot to focus on. On the other hand, any of the above options would probably benefit from a MAXIMUM_FILTER_SIZE parameter to limit the maximum message size. So what's the world got to say about this? (More importantly, how does TIMO feel about this?) ;). -- Daniel

3 2

[Dovecot] Dovecot, Postfix and SMTP AUTH....
by Bartosz Toczek 13 May '07

13 May '07

Hello. I've notice a problem with SMTP AUTH in postfix with dovecot. My configuration is based on Postgresql. I've created a function in postgresql which returns password and username and attached it to password_query. Query looks like this password_query = SELECT username_out as username, password_out as password FROM get_password(lower('%n'),lower('%d')); Problem is when get_password returns something like this... vmail=# SELECT username_out as username, password_out FROM get_password(lower(''),lower('')); LOG: statement: SELECT username_out as username, password_out FROM get_password(lower(''),lower('')); LOG: duration: 2.342 ms statement: SELECT username_out as username, password_out FROM get_password(lower(''),lower('')); username | password_out ----------+-------------- | (1 row) It returns 1 empty row.... When this is attached to postfix with smtp auth with such configuration # SMTP AUTH broken_sasl_auth_clients = yes smtpd_sasl_auth_enable = yes smtpd_sasl_security_options = noanonymous smtpd_sasl_authenticated_header = yes smtpd_sasl_local_domain = smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth my serwer starts to be open relay... I now that it returns empty string for username and password... so where is the password checked... if I dont send password as a parameter to my function. Definition of the function looks like this: CREATE FUNCTION get_password("login" character varying, "domain" character varying, OUT username_out character varying, OUT password_out character varying) RETURNS record Can you help with that... BT ---------------------------------------------------------------------- Zrob numer kumplom >> http://link.interia.pl/f1a5d

4 4

[Dovecot] Public folders using NAMESPACE
by Joakim Ryden 13 May '07

13 May '07

Howdy folks! I've been trying to research how to (or if possible at all) implement public folders using the namespace feature on a server with multiple virtual domains. After about an hour of looking around I'm a little confused. :) I guess there are two questions: 1) Is it possible / does it work? 2) If yes, does anyone have a sample configuration or write-up of How You Did It[TM] to share? I've been mainly focusing on the thread from here: http://www.dovecot.org/list/dovecot/2006-June/013683.html and the wiki ACL documentation: http://wiki.dovecot.org/ACL but I'm having a hard time piecing it all together... Thanks for any and all tips! --Jo

2 5

[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.

2 1

[Dovecot] Deferring, instead of rejecting, messages when at quota
by Mike Brudenell 13 May '07

13 May '07

Greetings - I'm having trouble working out where to alter this behaviour (so please forgive me if it turns out to be an Exim thing rather than Dovecot!)... My test service is using Exim as the MTA and Dovecot's "deliver" for the LDA. We are using Maildir mailboxes with filestore quotas. When I send a large test message to myself that cannot be delivered because I don't have sufficient available quota remaining an error message is immediately returned to the sender and the incoming message discarded. The error message says this: Your message was automatically rejected by Dovecot Mail Delivery Agent. The following reason was given: Not enough disk space Instead of Exim rejecting the incoming message and generating the error response because of deliver's failure to, umm, deliver I'd like the message to be retained in Exim's queue so that it can be retried periodically. With our old/live system (Sendmail + UW IMAP's "tmail" LDA) I edited the tmail source code to return a different exit code: one that caused Sendmail to defer (re-queue) the message rather than reject it. How do I achieve this effect with Exim + deliver please? Is it a case of: * Setting something in Dovecot's configuration file (I can't spot what!); * Changing a return code in deliver's source (if so, whereabouts and to what?); * Or is there an Exim directive I need to add to the transport definition in its configuration file? With thanks, Mike B-) -- The Computing Service, University of York, Heslington, York Yo10 5DD, UK Tel:+44-1904-433811 FAX:+44-1904-433740 * Unsolicited commercial e-mail is NOT welcome at this e-mail address. *

3 3

[Dovecot] wierd ssl-parameters.dat regeneration error
by Kyle Wheeler 13 May '07

13 May '07

I just had a strange problem with my Dovecot 1.0 installation. After about two weeks, it logged these messages: dovecot: Error: ssl-build-param: rename(/usr/local/var/lib/dovecot/ssl-parameters.dat.tmp, /usr/local/var/lib/dovecot/ssl-parameters.dat) failed: No such file or directory dovecot: Error: child 30689 (ssl-build-param) returned error 89 And thereafter, all login attempts resulted in this: dovecot: Error: imap-login: read(ssl-parameters.dat) failed: Unexpected EOF dovecot: Error: child 19036 (login) returned error 89 Thankfully, deleting the ssl-parameters.dat file (/var/run/dovecot/memoryhole.net/login/ssl-parameters.dat) and restarting dovecot fixed the problem, but it seems odd to me that dovecot expects /usr/local/var/lib/dovecot to exist (because, of course, it doesn't). I'm not defining that directory in the config file anywhere. Does anyone have any idea what's going on? ~Kyle -- I'm sick of following my dreams. I'm just going to ask them where they're going and hook up with them later. -- Mitch Hedberg

2 10

[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

[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 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.

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 read for several hours (the time was the current to figure out why it isn't working). Is there a problem with BEFORE and SEEN together? Is there a BEFORE bug in the system? Some of the messages are -500 and others, I am not sure. Thanks, Trever Adams

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: namespace private { separator = / prefix = oldmails/ location = maildir:/home/oldmails/:CONTROL=~/Maildir/control-oldmails:INDEX=~/Maildir/index-oldmails } and when I try to subscribe to it, dovecot says: dovecot: 2007-04-30 17:58:53 Info: IMAP(xxx): Effective uid=7001, gid=1000 dovecot: 2007-04-30 17:58:53 Info: IMAP(xxx): Namespace: type=private, prefix=regi/, sep=/, inbox=no, hidden=no, subscriptions=no dovecot: 2007-04-30 17:58:53 Info: IMAP(xxx): maildir: data=/home/oldmails/:CONTROL=~/Maildir/control-oldmails:INDEX=~/Maildir/index-oldmails dovecot: 2007-04-30 17:58:53 Info: IMAP(xxx): maildir: root=/home/oldmails, index=~/Maildir/index-oldmails, control=~/Maildir/control-oldmails, inbox= Thanks for any help in advance. Regards, A. <br><br>_______________________________________________________________<br> <a href="http://cthandler.adverticum.net/?cturl=http%3A%2F%2Fwww.klikkbank.hu%2Flako… " target="new">INTEZZE PÉNZÜGYEIT AZ INTERNETEN!</a> Lakossági számlacsomag havi 199 Ft-ért! Bankkártya éves kártyadíj nélkül! <a href="http://cthandler.adverticum.net/?cturl=http%3A%2F%2Fwww.klikkbank.hu%2Flako… " target="new">www.klikkbank.hu</a>

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 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.

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 appears to have at least temporarily stopped this behavior. Also and perhaps related, I am seeing a syslog message: imap-login: No authentication sockets found child xxxxxx (login) returned error 89 using SSL encrypted IMAP service Background: DC 1.0, invoked from /etc/rc.local during boot. After stopping and restarting DC, things seem to work again. As per an old problem, I checked /var/run/dovecot, but it was empty with plenty of space. FWIW, the owner/group for login dir (/var/run/dovecot) is dovecot:dovecot, perm 755, while /var/run/dovecot/login is root:dovecot, 750. Host is running AIXV5.3 TL5 SP6 (latest level), DC is compiled with IBM's AIX for C, V6.0 dovecot -n output > # /usr/local/etc/dovecot.conf > listen: *:10143 > ssl_listen: *:10943 > disable_plaintext_auth: no > verbose_ssl: yes > login_dir: /var/run/dovecot/login > login_executable: /usr/local/libexec/dovecot/imap-login > verbose_proctitle: yes > first_valid_uid: 200 > mail_location: mbox:~/mail:INBOX=/var/spool/mail/%u:INDEX=/var/dcndx/%u > mail_debug: yes > mbox_dirty_syncs: no > mbox_lazy_writes: no > auth default: > verbose: yes > debug: yes > passdb: > driver: pam > userdb: > driver: passwd Do I need to set an O/S or SSL max for authentication sockets? If so, any info would be appreciated Thanks! -- ==== 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

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 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

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/spool/mail/%u mail_location: mbox:%h/mail:INBOX=/var/spool/mail/%u mail_debug: yes mmap_disable: yes lock_method: dotlock mbox_read_locks: lockf mbox_write_locks: lockf auth default: passdb: driver: pam userdb: driver: passwd I have two issues: 1. It won't start from xinetd. I get very little in the logs, just: Apr 7 07:07:41 xyz xinetd[2545]: START: imaps pid=17445 from=144.173.228.126 Apr 7 07:07:41 xyz xinetd[2545]: EXIT: imaps pid=17445 duration=0(sec) where 'xyz' is the host name 2. If I instead I run dovecot as a daemon then both my machines have suffered the problem where dovecot runs for several days and then disallows connections with: Apr 29 04:06:07 xyz dovecot: imap-login: opendir(.) failed when trying to get list of authentication servers: Permission denied Apr 29 04:06:07 xyz last message repeated 2 times Apr 29 04:06:07 xyz dovecot: child 5645 (login) returned error 89 Apr 29 04:06:07 xyz dovecot: child 5646 (login) returned error 89 Apr 29 04:06:07 xyz dovecot: child 5647 (login) returned error 89 Killing and restarting dovecot seems to fix it. Thanks for your help. John

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 Tagliaferri Responsabile Progettazione & Produzione TosNet s.r.l. - Internet Service Provider r.tagliaferri(a)tosnet.it www.tosnet.it

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 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

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): deleted: uid=1719, msgid=<002701b483f5$7aa257e0$23833bda(a)example.com> I've got a bunch of users that work with the login 'office'. Is it possible to determine the IP of the user that deleted messages? If not, what can be done about it in the future? Thank you. -- Eugene Gladchenko EVG15-RIPE

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> 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

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 the output would include the running dovecot version, as well as any extra config settings from any other files that are loaded when dovecot starts? It would sure make it easier, both for us troubleshooting on our own, and when asking for help on the list. Many thanks, and terrific job on 1.0! Now all dovecot lacks is full support for IMAP ACLs/shared folders, and support for single-instance storage, and it will have no real competition... -- Best regards, Charles

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): client out: OK 1 user=vu0095 Apr 19 12:50:53 mail dovecot: auth(default): master in: REQUEST 376 12300 1 Apr 19 12:50:53 mail dovecot: auth(default): passwd(vu0095,165.228.62.107): lookup Apr 19 12:50:53 mail dovecot: auth(default): master out: USER 376 vu0095 system_user=vu0095 uid=580 gid=580 home=/home/vu0095 Apr 19 12:50:53 mail dovecot: pop3-login: Login: user=<vu0095>, method=PLAIN, rip=165.228.62.107, lip=203.36.211.209 Apr 19 12:51:49 mail dovecot: POP3(vu0095): Disconnected for inactivity in reading our output top=0/0, retr=1/0, del=0/2, size=25266 Apr 19 12:51:49 mail dovecot: POP3(vu0095): Disconnected: Logged out top=0/0, retr=2/25393, del=2/2, size=25266 99% of the time everything is perfect, it is only the three users in the one office that get this error, it is of course the head office for the customer and so they are very upset, because they get timeout errors on their email clients. They are using different versions of outlook, and outlook express, I have deactivated all nortons email scanning etc Have set the three email clients to pop mail at different times, eg. 7, 13, 17 minutes to try an avoid the possibility of simultaneous pop requests from the one IP address. Dovecot -n # /etc/dovecot.conf protocols: pop3 pop3s listen: * ssl_disable: yes login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/pop3-login login_greeting: POP Server ready. login_processes_count: 20 mail_executable: /usr/libexec/dovecot/pop3 mail_plugin_dir: /usr/lib/dovecot/pop3 pop3_client_workarounds: outlook-no-nuls oe-ns-eoh auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: pam userdb: driver: passwd

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. ______________________________________________ 2600 állásból Te is találsz megfelelőt! Mérnöki, értékesítői, asszisztensi, pénzügyi és IT állások a Jobline.hu-n! http://www.jobline.hu

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 se bagózik a megjelenésedre. Szerinte gyönyörű vagy és punktum." Meglepetéskönyvek anyák napjára. http://ad.adverticum.net/b/cl,1,6022,162660,225668/click.prm

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 always at the time when this error is logged. Surfing through many forums, i came across with a cause that many people point to: "client closed connection at the exact same time master was logging it in" i don't know if this is what happens to my system, to be honest, i don't have a clue how to check that, i just would like to know if somebody has come up with a solution for this problem, as it seems many people are still trying to face it. thank you. ***

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/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-----

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 program that's doing something they're not supposed to be doing. --The Oracle, "Matrix Reloaded"

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, 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

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 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

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 client_workarounds = oe6-fetch-no-newmail outlook-idle outlook-pop3-no-nuls mbox_locks = fcntl everything else is at default value. Also, we do not upgrade dovecot because it is not part of the upstream provider, and we do not want to break binary compatibility updates. Thanks for your guidance. -- ------------------------------------------------------------ Erick Perez Panama Sistemas Integradores de Telefonia IP y Soluciones Para Centros de Datos Panama, Republica de Panama Cel Panama. +(507) 6694-4780 ------------------------------------------------------------

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) $ 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.

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 see them. If I revert back to dovecot-0.99.14-1.2, then I am able to see my folders. I have been looking in the wiki at the steps needed to upgrade from 0.99 to 1.0 and I thought everything had been taken care of, but since things aren't working, I have overlooked something. I also browsed the archives and see that others are using horde with various dovecot 1.x releases, so I know it should be possible to get it to work. My dovecot.conf currently only as the below, which works fine for 0.99: maildir_copy_with_hardlinks = no my /etc/pam.d/dovecot has: more /etc/pam.d/dovecot #%PAM-1.0 auth required pam_nologin.so auth include system-auth account include system-auth session include system-auth imp servers.php: $servers['_prompt'] = array( 'name' => 'Choose a mail server:' ); $servers['thebennetthome2.com'] = array( 'name' => 'IMAP Server', 'server' => 'localhost', 'protocol' => 'imap/notls', 'port' => '143', 'maildomain' => 'test.com', 'smtphost' => 'localhost', 'realm' => 'test.com', 'preferred' => '' ); php -v PHP 5.1.6 (cli) (built: Apr 9 2007 03:37:21) Copyright (c) 1997-2006 The PHP Group Zend Engine v2.1.0, Copyright (c) 1998-2006 Zend Technologies I do get some php errors when logging into horde, and a lot of php errors when creating folders that I can post if needed. I did post my issue to the horde list as well, but there has been no answer to date. Please let me know what other information is needed to assist me with fixing this issue. Thank you very much, John Bennett Thanks, John H. Bennett III bennettj(a)johnbennettservices.com

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 my POP server) is downloaded again as NEW. Is there a way to prevent this from happening without setting my client to delete mail from server? thank you!

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 some reason I had uncommented a bunch of things that didn't need to be uncommented (because they were the default setting), resulting in a much larger output from the postconf -n command. I know its not a big deal, but any chance of implementing this for dovecot? This would make it easy to keep the conf file (and the -n output) clean and neat. Many, many thanks for 1.0.0! -- Best regards, Charles

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 put the code instead? (I'm trying to check the username against some information in a file OR pass the username to a process and have it do the work) Thanks, Phillip

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 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

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 and never had such a problem. Any idea how this can be fixed? FreeBSD 6.2 Release, Postfix 2.4, Dovecot 1.0.0 dovecot -n report: base_dir: /var/run/dovecot/ protocols: pop3 listen: * ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/pop3-login login_process_per_connection: no login_processes_count: 1 login_max_processes_count: 10 verbose_proctitle: yes first_valid_uid: 2000 last_valid_uid: 2999 first_valid_gid: 2000 last_valid_gid: 2000 mail_extra_groups: mail mail_location: mbox:/var/empty/:INBOX=/var/mail/%u:INDEX=MEMORY dotlock_use_excl: yes mbox_read_locks: flock mbox_write_locks: flock mail_executable: /usr/local/libexec/dovecot/pop3 mail_plugin_dir: /usr/local/lib/dovecot/pop3 pop3_no_flag_updates: yes pop3_uidl_format: %08Xu%08Xv pop3_client_workarounds: outlook-no-nuls oe-ns-eoh auth default: default_realm: domain.com username_format: %n passdb: driver: passwd userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: regards, Athan

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 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 { }

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 .imap.* files. Is there a way to either convert the .imap* files into the new dovecot.* files or any way to recover the email that anyone knows about? Thanks! Scott

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 missing, rejection reason: %s", orig_msgid == NULL ? "" : str_sanitize(orig_msgid, 80), str_sanitize(reason, 512)); - - return 0; + return EX_TEMPFAIL; } smtp_client = smtp_client_open(return_addr, NULL, &f); Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBRkGA0S9SORjhbDpvAQIh0Qf/RUkmWnK+LhB3/ZwY+AnyTAYGBPB7qTCp bVchn4F7zL+W2fIYZGz6YG1bKUtHE3qMQAY3gYijspNZBejS0Z8cTI983ZMwJFP+ ygMAicyEDFSWrFWYnzBnpvHYZEK9VjQ4HnDIkojDQx+pQH0LS/Ve0/JbiaNuwMRQ g0ay3puas8xiyktRHVHslDfbanrfzwpbO7qtNpFrF9aCKo3RLIhFCKSjaXD75BfQ K7XrmOjFECkB1bLeaFJrVzm/DoayRn1HusKQjtwKCRx4YBgOP0d5OQGQTvqRLx33 agHXdNxFN6vYB/QbIMcoI6xyWw6POHpiRjLJ5maWsdhlMFIrRVNOJg== =xshk -----END PGP SIGNATURE-----

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 start it, then it starts working properly. /var/log/maillog:May 8 09:33:02 lhr dovecot: auth(default): Killed with signal 15 /var/log/maillog:May 8 09:33:02 lhr dovecot: Killed with signal 15 /var/log/maillog:May 8 09:33:13 lhr dovecot: Dovecot v1.0.0 starting up /var/log/maillog:May 8 09:33:13 lhr dovecot: auth-worker(default): mysql: Connected to 127.0.0.1 (exim) My configuration file is : lhr# dovecot -n # /usr/local/etc/dovecot.conf protocols: imap pop3 listen(default): *:143 listen(imap): *:143 listen(pop3): * ssl_disable: yes disable_plaintext_auth: no 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 first_valid_uid: 90 last_valid_uid: 93 first_valid_gid: 90 last_valid_gid: 93 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): %08Xu%08Xv auth default: verbose: yes debug: yes passdb: driver: sql args: /usr/local/etc/dovecot-sql.conf userdb: driver: sql args: /usr/local/etc/dovecot-sql.conf Please help me in this regard. Thanks in advance. Kamran Arshad --------------------------------- Don't pick lemons. See all the new 2007 cars at Yahoo! Autos.

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/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/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/vmail/domain.tld/user1 40 lines from this per second and will never stop! i need to stop postfix and dovecot, kill -9 the deliver-process, fix the mbox (unlock it with mutt) and start dovecot and postfix again. then the mail will be deliverd without errors. some minutes to hours later i got the same problem with a random user and domain. my configs: /etc/postfix/main.cf: : virtual_mailbox_domains = /etc/postfix/virtual_domains virtual_mailbox_base = /home/vmail virtual_mailbox_maps = hash:/etc/postfix/virtual_boxes virtual_alias_maps = hash:/etc/postfix/virtual_user virtual_minimum_uid = 100 virtual_uid_maps = static:1005 virtual_gid_maps = static:1005 virtual_transport = dovecot dovecot_destination_recipient_limit = 1 : /etc/postfix/master.cf: : # dovecot lda # ============================================================================== # service type private unpriv chroot wakeup maxproc # command + args # (yes) (yes) (yes) (never) (100) # ============================================================================== dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/lib/dovecot/deliver -d ${recipient} the dovecot.conf is attached, the mailuser-file looks like: user1@domain.tld:password:1005:1005::/home/vmail/domain.tld can someone help? thanks a lot. regards thomas -- thomas balsfulland tbals(a)ctrl-c.de zwischen mut und dummheit liegt nur ein grat der sich durch das vorbereitetsein unterscheidet

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 ? Platform: FreeBSD 7.0-CURRENT #0: Tue Apr 10 13:47:53 WST 2007. Cheers! -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.

9 16

[Dovecot] Tru64 patch for mountpoint.c
by Simon L Jackson 09 May '07

09 May '07

I believe that there is one more patch required for a successful build on Tru64: # diff ./src/lib/mountpoint.c.orig ./src/lib/mountpoint.c 60a61,63 > #ifdef __osf__ > point_r->type = p_strdup(pool, getvfsbynumber(buf.f_type)); > #else 62c65,66 < point_r->block_size = buf.f_bsize; --- > #endif > point_r->block_size = buf.f_bsize; Cheers -- Simon L Jackson Carringbush.Net +- Carringbush.Net Hosting * Development * Advice Web: www.carringbush.net <http://www.carringbush.net/> Email: simon.jackson(a)carringbush.net <mailto:simon.jackson@carringbush.net> Office: +61 3 9411 4400 Support: +61 3 9411 4444 Fax: +61 3 9411 4499 Level 1 15 Bedford Street Collingwood VIC 3066 Australia P.O. Box 1464 Collingwood VIC 3066 Australia +-

2 2

[Dovecot] ldap and digest-md5 problem
by Łukasz Mierzwa 09 May '07

09 May '07

Hi, I'm using dovecot-1.0.0 on gentoo box and I have problem with authentication using digest-md5 and passwords stored as plain text in ldap database, when I use cram-md5 it works, while digest-md5 give this error (squirrelmail login): May 5 16:03:32 srv dovecot: auth(default): client in: AUTH 1 DIGEST-MD5 service=IMAP secured lip=127.0.0.1 rip=127.0.0.1 May 5 16:03:32 srv dovecot: auth(default): client out: CONT 1 [password hash] May 5 16:03:32 srv dovecot: auth(default): client in: CONT<hidden> May 5 16:03:32 srv dovecot: auth(default): ldap(user(a)domain.com,127.0.0.1): pass search: base=ou=domain.com,cn=Users,dc=domain,dc=com scope=subtree filter=(&(objectClass=posixAccount)(uid=user)) fields=userPassword May 5 16:03:32 srv dovecot: auth(default): ldap(user(a)domain.com,127.0.0.1): result: userPassword(password)=<hidden> May 5 16:03:32 srv dovecot: auth(default): digest-md5 (user(a)domain.com,127.0.0.1) password mismatch May 5 16:03:32 srv dovecot: auth(default): client out: FAIL 1 user=user(a)domain.com May 5 16:03:32 srv dovecot: imap-login: Aborted login: user=<user(a)domain.com>, method=DIGEST-MD5, rip=127.0.0.1, lip=127.0.0.1, secured It seems that client and dovecot hashes calculated for DIGEST-MD5 are different, I tested squirrelmail 1.4.9a, kmail 3.5.6 both can't login using digest-md5 so maybe dovecot does not working correctly? Passwords where created using phpldapadmin and "clear" password type, cram-md5 logins are ok. I can't find any info on ldap and digest-md5 incompatibility in dovecot wiki, can anyone give my a hint? my dovecot-ldap.conf: uris = ldaps://127.0.0.1 dn = uid=dovecot,cn=Daemons,dc=domain,dc=com dnpass = secret sasl_bind = no tls = no auth_bind = no ldap_version = 3 base = ou=%d,cn=Users,dc=domain,dc=com deref = never scope = subtree pass_attrs = userPassword=password pass_filter = (&(objectClass=posixAccount)(uid=%n)) default_pass_scheme = PLAIN my dovecot.conf: protocols = imap imaps managesieve shutdown_clients = yes syslog_facility = mail ssl_cert_file = /etc/ssl/cert ssl_key_file = /etc/ssl/key verbose_ssl = no login_process_per_connection = yes login_processes_count = 2 login_max_processes_count = 10 login_user = dovecot login_dir = /var/run/dovecot/login login_chroot = yes mail_location = maildir:/var/mail/%d/%n mail_extra_groups = postfix mail_full_filesystem_access = no mail_debug = no verbose_proctitle = yes first_valid_uid = 2000 last_valid_uid = 2000 first_valid_gid = 2000 last_valid_uid = 2000 maildir_copy_with_hardlinks = yes disable_plaintext_auth = yes protocol imap { imap_client_workarounds = outlook-idle } protocol lda { postmaster_address = postmaster(a)domain.com hostname = domain.com mail_plugins = cmusieve } auth_default_realm = pcserwis.net auth_username_format = %Lu auth_verbose = yes auth_debug = yes auth_debug_passwords = no auth default { mechanisms = plain login cram-md5 digest-md5 passdb ldap { args = /etc/dovecot/dovecot-ldap.conf } userdb static { args = uid=2000 gid=2000 home=/var/mail/%d/%n } socket listen { client { path = /var/spool/postfix/private/auth mode = 0660 user = vmail group = postfix } master { path = /var/run/dovecot/auth-master mode = 0600 user = vmail } } } protocol managesieve { listen = *:2000 login_executable = /usr/libexec/dovecot/managesieve-login mail_executable = /usr/libexec/dovecot/managesieve } -- Łukasz Mierzwa

2 2

[Dovecot] Switching from mailbox to maildir.. duplicates!
by Lars Johansen 09 May '07

09 May '07

Hi We have been running a dovecot server for some time.. users connect with pop. Now this server is going to be substituted with a new one.. before we used mbox, but now we will move to maildir! I have done some testing transfering the mail with the mb2md script, the conversion works correctly, but users gets duplicates since they selected "keep mail on server" I have googled for the problem, and set pop3_reuse_xuidl=yes and pop3_uidl_format = %08Xu%08Xv is the same on both servers.. but no luck. My first tought was to script in an X-UIDL header for each mail that was converted.. but that wont work since the mail already downloaded by the client didnt contain that header.. is there anyone that has some experience with this, or knows if its possible? Many Greetings, Lars Johansen

3 2

[Dovecot] Strange Mail Problem
by Jason Baker 09 May '07

09 May '07

I submitted this question to the Postfix maillist and they suggested that I post to this one. Here's my issue: I have a Postifx email system running on a CentOS 4 box, with Dovecot pop3 and imap. Last week, one of my users reported to me that about a dozen emails suddenly showed up in his in box (as unread messages), but none of them were addressed to him. Under further investigation, they turned out to be from another user's inbox. The messages were all over a month old. How could mail simply show up in one inbox from another user's? We're using Mozilla Thunderbird 1.5. Anyone else run into issues like this? -- *Jason Baker */IT Coordinator/ *Glastender Inc.* 5400 North Michigan Road Saginaw, Michigan 48604 USA 800.748.0423 Phone: 989.752.4275 ext. 228 Fax: 989.752.4444 www.glastender.com <http://www.glastender.com> -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GIT$ d- s: a C++$ LU+++$ P+ L++>L++++ !E--- W+++ N o? K? w !O M !V PS PE++ Y? PGP- t 5? X+ R+ tv+ b- DI-- D++ G e+ h--- r+++ y+++ ------END GEEK CODE BLOCK------

4 4

[Dovecot] busy still for a week
by Timo Sirainen 09 May '07

09 May '07

This school year is pretty much finished next thursday (for the classes I intended to pass). After that I should again have enough energy to read and answer the 150 mails in this list .. :) And maybe release v1.0.1 fixing the newly found bugs.

3 3

[Dovecot] File Changes and IDLE
by Andy Shellam 09 May '07

09 May '07

Hi Timo and all, I used to use Dovecot back in the 0.99 days a couple of years ago, had since moved to Courier IMAP, but with the release of Dovecot 1.0.0, I'm looking at moving back! One thing I currently have set up and working with Courier is the use of the enhanced IDLE mode, whereby Courier uses FAM (File Alteration Monitor) to monitor changes in the INBOX, and sends the details to the client as soon as a new mail arrives. Is this something that Dovecot supports? If possible, I'd prefer not to use FAM, as it crashes at random intervals and I have to keep restarting it. When I configured Dovecot, it said "File change notification method ..... : none". Does this mean FreeBSD doesn't support any method of notifying of file changes? Is there any way I can install, or re-configure the kernel, to include this support? Thanks, Andy

3 2

[Dovecot] input / output error in dovecot.log
by Joe Wong 09 May '07

09 May '07

Hello, >From time to time, I saw input / output error on rename() or pwrite_full(), for example: dovecot: May 02 05:46:18 Error: IMAP(joe): rename(/fs/joe/Maildir/.Sent Items/tmp/1178084777.P21895Q0M200058.tkodog.no-ip.com.com, /fs/joe/Maildir/.Sent Items/cur/1178084777.P21895Q0M200058.tkodog.no-ip.com:2,S) failed: Input/output error dovecot: May 02 06:29:49 Error: IMAP(victor): pwrite_full() failed with file /fs/victor/Maildir/dovecot.index.log: Input/output error dovecot: May 02 08:21:29 Error: IMAP(victor): pwrite_full() failed with file /fs/victor/Maildir/dovecot.index.log: Input/output error dovecot: May 03 06:02:06 Error: IMAP(joe): rename(/fs/joe/Maildir/.Sent Items/tmp/1178172125.P16867Q0M173436.tkodog.no-ip.com, /fs/joe/Maildir/.Sent Items/cur/1178172125.P16867Q0M173436.tkodog.no-ip.com.com:2,S) failed: Input/output error What could be the cause of this problem and the consequences? Regards, - Joe

2 1

[Dovecot] auth(default): Error sending status request (Operation not permitted)
by Keith Bjorndahl 09 May '07

09 May '07

After upgrading to dovecot-1.0.0 from dovecot-0.99.14, I've started getting the following errors: auth(default): Error sending status request (Operation not permitted) but yet everything _seems_ to be functioning okay ... so far. This is a FC4 system, SELinux is re-configured and still generates errors with SELinux disabled. Ideas?

2 1