- dovecot - dovecot.org

[Dovecot] Replication plans
by Timo Sirainen 06 Jun '07

06 Jun '07

Several companies have been interested in getting replication support for Dovecot. It looks like I could begin implementing it in a few months after some other changes. So here's how I'm planning on doing it: What needs to be replicated: - Saving new mails (IMAP, deliver) - Copying existing mails - Expunges - Flag and keyword changes - Mailbox creations, deletions and renames - Subscription list - IMAP extension changes, such as ACLs I'll first talk about only master/slave … [View More]configuration. Later then master/multi-slave and multi-master. Comments? Basic design ------------ Since the whole point of master-slave replication would be to get a reliable service, I'll want to make the replication as reliable as possible. It would be easier to implement much simpler master-slave replication, but in error conditions that would almost guarantee that some messages get lost. I want to avoid that. Both slave and master would be running a dovecot-replication process. They would talk to each others via TCP connection. Master would be feeding changes (transactions) to slave, and slave would keep replying how far it's committed the changes. So there would be an increasing sequence number sent with each transaction. Master keeps all the changes in memory until slave has replied that it has committed the changes. If the memory buffer gets too large (1MB?) because the slave is handling the input too slowly or because it's completely dead, the master starts writing the buffer to a file. Once the slave is again responding the changes are read from the file and finally the file gets deleted. If the file gets too large (10MB?) it's deleted and slave will require a resync. Master always keeps track of "user/mailbox -> last transaction sequence" in memory. When the slave comes back up and tells the master its last committed sequence, this allows the master to resync only those mailboxes that had changed. If this mapping doesn't exist (master was restarted), all the users' mailboxes need to be resynced. The resyncing will also have to deal with new mailboxes, ACL changes and such. I'm not completely sure yet how the resyncing will work. Probably the only important thing here is that it would be good if it would resolve any message UID conflicts (even though they shouldn't happen, see below) by comparing either the messages' MD5 contents, or with maildir it would be enough to just compare the maildir filename. It's possible that the slave doesn't die completely but only some transactions fail. This shouldn't normally happen, so the easiest way to handle it would be to try a full resync, and if that still fails stop the whole slave. Another way would be to just mark that one user or mailbox as dirty and try to resync it once in a while. imap, pop3 and deliver would connect to dovecot-replication either using UNIX sockets or POSIX message queue. Queue could be faster, but sockets would allow better security checks. Or I suppose it would be possible to send some kind of a small authentication token in each message with queues. The communication protocol would be binary and the existing dovecot.index.log format would be used as much as possible (making it simple for slave to append changes to mailboxes' dovecot.index.log). dovecot-replication process would need read/write access to all users' mailboxes. So either it would run as root or it would need to have at least group-permission rights to all mailboxes. A bit more complex solution would be to use multiple processes each running with their own UIDs, but I think I won't implement this yet. The replication would require support for shared mailboxes. That way the mailboxes could be accessed using the configured shared namespaces, for example "shared/<username>/INBOX". (LMTP server could be implemented in a similar way BTW) Configuration ------------- I'm not yet sure how this should work. The simplest possibility would be just to configure a single slave and everything would be replicated there. But it should be possible to split users into multiple slaves (still one slave/user). The most configurable way to do this would be to have userdb return the slave host. Hmm. Actually that could work pretty well if the userdb returned slave's name and each slave would have a separate socket/queue where dovecot-replication listens in. I'm not sure if they could all still be handled by a single dovecot-replication process or if there should be a separate one for each of them. The configuration would then be something like: # slave for usernames beginning with letters A..K replication users_a_k { host = slave1.example.com # other options? } # L..Z and others replication users_l_z_rest { host = slave2.example.com } Saving ------ This is the most important thing to get right, and also the most complex one. Besides replicating mails that are being saved via Dovecot, I think also externally saved mails should be replicated when they're first seen. This is somewhat related to doing an initial sync to a slave. The biggest problem with saving is how to robustly handle master crashes. If you're just pushing changes from master to slave and the master dies, it's entirely possible that some of the new messages that were already saved in master didn't get through to slave. So when you switch to using slave, those messages are gone. The biggest problem with this is that when saving new mails, they'll be assigned UIDs that were already used by the original master. If a locally caching client had already seen the UID from the original master, it'll think the message is the original one instead of the new one. So the newly added message pretty much gets lost, and if the user could expunge the message (thinking it's the original one) without ever even seeing it. This UID conflict could be avoided by making the master tell slave whenever it's saving new mails. The latency between master-slave communication could be avoided with a bit of a trick: - When beginning to save/copy a mail, tell slave to increase UID counter by one. Slave replies with the new highest-seen-UID counter. - UID allocation is done after all the mails are saved/copied within a transaction. At this stage wait until slave has replied that it has reserved UIDs at least as high as we're currently allocating (other processes could have caused it to get even higher). - If save/copy is aborted, tell the slave to decrease the UID counter by the number of aborted messages. - UID counter desync shouldn't happen, but if it does handle that also somehow. Then the UID allocation latency depends on how long it takes to write the message, and where the message comes from. With IMAP APPEND there's probably no wait required, unless the APPEND command and the whole message arrives in one IP packet. With deliver and copying it might have to wait a while. So the UID allocation should work with minimal possible latency. It could use a separate TCP connection to slave and maybe a separate high priority process in the slave that would handle only UID allocations. The above will make sure that conflicting UIDs aren't used, but it doesn't make sure that messages themselves aren't lost. If the master's hard disk failed completely and it can't be resynced anymore, the messages saved there are lost. This could be avoided by making the saving wait until the message is saved to slave: - save mail to disk, and at the same time also send it to slave - allocate UID(s) and tell to slave what they were, wait for "mail saved" reply from slave before committing the messages to mailbox permanently This would however add more latency than the simpler UID allocation counter. I don't know if it should be optional which way is used. Perhaps I'll implement the full save-sync first and if it seems too slow then I'll implement optionally the UID allocation counter. Save messages from imap/deliver would contain at least: 1. user name (unless using UNIX sockets, then it's already known) 2. mailbox name 3. UIDVALIDITY 4a) UID 4b) global UID, filename, offset and size of the message 4a) would be used with the UID allocation counter behavior. The message would be sent after the message was saved and UIDs were allocated. 4b) would be used with the wait-slave-to-save behavior. The message would be sent immediately whenever new data was received for the message, so possibly multiple times for each message. The last block would then contain size=0. After saving all the mails in a transaction, there would be a separate "allocate UIDs x..y for global UIDs a, b, c, d, etc." message which the slave then replies and master forwards the reply to imap/deliver. If the slave is down, or if a timeout (a few seconds?) occurs while waiting for the reply from slave, imap/deliver could just go on saving the message. If this is done it's possible that if the master also dies soon, there will be UID conflicts. But since this should be a rare error condition, it's unlikely that the master will die soon after a misbehaving slave. Copying ------- Copying has similar UID conflict problems than saving. The main difference is that there's no need to transfer message contents, which makes it faster to handle copies reliably. Copying could be handled with the UID allocation counter way described above. Since the message already exists in the server, there's no way that the message gets lost. So it would be possible to allow master and slave to go into desync, because the user would still find the message from the original mailbox. Move operation is done with "copy + mark \deleted + expunge" combination. This could be problematic if the master had managed to do all that before slave saw the COPY at all. Since the message isn't yet copied to the new mailbox in slave, clients wouldn't see it there, but locally caching clients might not see the message in the original mailbox either because they had already received EXPUNGE notification for it. So this should be avoided in some way. Perhaps it would be better to just treat copies the same way as saves: Require a notification from slave before replying to client with OK message. Alternatively the wait could be done at EXPUNGE command, as described below. Expunges -------- Losing expunge transactions wouldn't be too bad, because the worst that can happen is that the user needs to expunge the message again. Except that having an expunged message suddenly appear again in the middle of the mailbox violates IMAP protocol. I don't know if/how that will break clients. Solution here would again be that before EXPUNGE notifications are sent to client we'll wait for reply from slave that it had also processed the expunge. Flag and keyword changes ------------------------ Most likely doesn't matter if some of them are lost. If someone really cares about them, it would be possible to again do the slave-waiting for either all the changes or just when some specific flags/keywords change. Other changes ------------- Mailbox creations, deletions, renames and subscription changes could all be handled in a similiar way to flag/keyword changes. Handling changes implemented by IMAP extensions such as ACL is another thing. It's probably not worth the trouble to implement a special replication handler for each plugin. These changes most likely will happen somewhat rarely though, so they could be implemented by sending the whole IMAP command to slave and have it execute the command using a regular imap process. The commands could be marked with some "replication" flag so Dovecot knows that they need to be sent to slave. Although instead of executing a new imap process for each user (probably each command), it could be possible to use one imap process and just change the mailbox name in the command. So instead of eg. "setacl mailbox (whatever)" the IMAP process would execute "setacl shared/username/mailbox (whatever)". That would require telling Dovecot what parameter contains the mailbox name. Should be pretty easy to implement, unless some IMAP extensions want multiple mailbox names or the position isn't static. I can't think of any such extensions right now though. Master/multi-slave ------------------ Once the master/slave is working, support for multiple slaves could be added. The main thing to be done here is to have the slaves select which one of them is the new master, and then they'll have to sync the mailboxes with each others, because each of them might have seen some messages that others hadn't. This is assuming that save/etc. operations that are waiting for a reply from slave would wait for only one reply from the first slave that happens to respond. The number of slave replies to wait for could be also configurable, in case you're worried of a simultaneous master+slave crash. Multi-master ------------ After master/multi-slave is working, we're nearly ready for a full multi-master operation. The master farm will need global locking. Perhaps there is a usable existing implementation which could be used. In any case there needs to be a way to keeps track of what master owns what locks. The easiest way to implement multi-master is to assume that a single user isn't normally accessed from different servers at the same time. This wouldn't be a requirement, but it would make the performance better. For most users you could handle this by making sure that load balancer transfers all connections from the same IP to the same server. Or you could use a Dovecot proxy that transfers the connections. So, once the user is accessed only from one server, the operation becomes pretty much like master/multi-slave. You'll just need to be able to dynamically change the current master server for the user. This can be done by grabbing a global per-user lock before modifying the mailbox. The lock wouldn't have to be released immediately though. If no other server needs the lock, there's no point in locking/unlocking constantly. Instead the lock server could request the current lock owner to release the lock whenever another server wants it. [View Less]

8 20

[Dovecot] multiple dovecot invocations
by Stewart Dean 05 Jun '07

05 Jun '07

I need to have multiple invocations of dovecot running, one for productions and then one or more for test/dev, doing things like trying different authentication methods, getting quota working, etc. I knew how to do this with inetd, but I have been convinced that direct invocation is preferable, so I need to know how to do multiple invocations of dovecot. I had thought that perhaps I could do this: dovecot -c /usr/local/etc/dovecot2.conf where dovecot2.conf has different different … [View More]

2 1

Re: [Dovecot] AIX mail quota plugin problems + dotlock problem resolved
by Timo Sirainen 05 Jun '07

05 Jun '07

On Tue, 2007-06-05 at 12:30 -0400, Stewart Dean wrote: > quotactl(Q_GETQUOTA, /) failed: Invalid argument So apparently this quotactl() call is wrong with AIX: if (quotactl(root->mount->mount_path, QCMD(Q_GETQUOTA, USRQUOTA), root->uid, (void *)&dqblk) < 0) { I don't know why though. You could try changing root->mount->mount_path to some actual mbox file path to see if it returns errors then. Except weren't your mailboxes NFS mounted? quotactl() doesn't work … [View More]

2 2

[Dovecot] IMAP traffic logging
by Chris Laif 05 Jun '07

05 Jun '07

Hi. I wonder if it is possible to log the number of bytes send in response to IMAP commands. Unfortunately there seems to be no config option similar to "pop3_logout_format". Courier writes a log file like this (header/body bytes): imaplogin: DISCONNECTED, ip=[::ffff:10.123.0.234], headers=0, body=0 Chris

3 4

[Dovecot] Dovecot Authentication Problem - Help pls!
by Odhiambo WASHINGTON 05 Jun '07

05 Jun '07

Hello List, This is dovecot 1.0.0 on FreeBSD 4.11-STABLE. I did not provide this information before:-) I am back again and I think I am edging closer to getting a solution. I have done some modifications and now dovecot gives me a different error message than before.... Here is what I have for the password_query and user_query password_query = SELECT popbox.cleartext AS password FROM popbox, domain \ WHERE popbox.local_part = 'eddie' AND popbox.domain_name = 'demo.wananchi.com' \ AND … [View More]popbox.domain_name = domain.domain_name; +----------+ | password | +----------+ | boeing8 | +----------+ user_query = SELECT CONCAT(domain.path, '/', popbox.mbox_name) as home, \ 69 as uid, 6 as gid FROM popbox, domain WHERE popbox.local_part = 'eddie' \ AND popbox.domain_name = 'demo.wananchi.com' AND \ popbox.domain_name = domain.domain_name; +--------------------------------------------+-----+-----+ | home | uid | gid | +--------------------------------------------+-----+-----+ | /var/spool/virtual/demo.wananchi.com/eddie | 69 | 6 | +--------------------------------------------+-----+-----+ When I test to connect to the pop3 daemon, this is what happens now: root@ns2]#telnet 0 7173 Trying 0.0.0.0... Connected to 0. Escape character is '^]'. +OK Welcome. Dovecot is Ready to serve your emails. user eddie(a)demo.wananchi.com +OK pass boeing8 -ERR [IN-USE] Internal login failure. Refer to server log for more information. Connection closed by foreign host. ...and this is what dovecot writes to the log: [root@ns2]#less /var/log/dovecot.log dovecot: May 30 12:00:04 Info: auth(default): client in: AUTH 1 PLAIN service=POP3 secured lip=62.8.64.4 rip=62.8.64.4 resp=AGVkZGllQGRlbW8ud2FuYW5jaGkuY29tAGJvZWluZzg= dovecot: May 30 12:00:04 Info: auth-worker(default): mysql: Connected to localhost (virtualemail) dovecot: May 30 12:00:04 Info: auth-worker(default): sql(eddie(a)demo.wananchi.com,62.8.64.4): query: SELECT popbox.cleartext AS password FROM popbox, domain WHERE popbox.local_part = 'eddie' AND popbox.domain_name = 'demo.wananchi.com' AND popbox.domain_name = domain.domain_name dovecot: May 30 12:00:04 Info: auth(default): client out: OK 1 user=eddie(a)demo.wananchi.com dovecot: May 30 12:00:04 Info: auth(default): master in: REQUEST 2 36772 1 dovecot: May 30 12:00:04 Info: auth-worker(default): sql(eddie(a)demo.wananchi.com,62.8.64.4): SELECT CONCAT(domain.path, '/', popbox.mbox_name) as home, 69 as uid, 6 as gid FROM popbox, domain WHERE popbox.local_part = 'eddie' AND popbox.domain_name = 'demo.wananchi.com' AND popbox.domain_name = domain.domain_name dovecot: May 30 12:00:05 Error: child 39853 (auth-worker) killed with signal 11 dovecot: May 30 12:00:05 Info: auth(default): master out: FAIL 2 dovecot: May 30 12:00:05 Info: pop3-login: Internal login failure: user=<eddie(a)demo.wananchi.com>, method=PLAIN, rip=62.8.64.4, lip=62.8.64.4, secured User's mail is stored in /var/spool/virtual/$domain/$user/{new,cur,tmp} The path /var/spool/virtual/ is owned by uid:gid 69:6, and is writeable by that uid. dovecot -n: # /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot.log protocols: imap pop3 listen(default): *:7143 listen(imap): *:7143 listen(pop3): *:7110 ssl_disable: yes disable_plaintext_auth: no shutdown_clients: 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_user: exim login_greeting: Welcome. Dovecot is Ready to serve your emails. login_process_size: 64 login_max_processes_count: 200 verbose_proctitle: yes first_valid_uid: 69 first_valid_gid: 0 mail_extra_groups: dovecot:mail mail_location: maildir:/var/spool/virtual/%d/%n 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 digest-md5 cram-md5 verbose: yes debug_passwords: yes passdb: driver: sql args: /usr/local/etc/dovecot-sql.conf userdb: driver: sql args: /usr/local/etc/dovecot-sql.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 384 user: root group: wheel Here is a backtrace of the dovecot-auth crash: [root@ns2]#gdb /usr/local/libexec/dovecot/dovecot-auth dovecot-auth.core GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"...(no debugging symbols found)... Core was generated by `dovecot-auth'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/libcrypt.so.2...(no debugging symbols found)...done. Reading symbols from /usr/lib/libpam.so.1...(no debugging symbols found)...done. Reading symbols from /usr/local/lib/compat/pkg/libmysqlclient.so.10...(no debugging symbols found)...done. Reading symbols from /usr/lib/libm.so.2...(no debugging symbols found)...done. Reading symbols from /usr/local/lib/libsqlite3.so.8...(no debugging symbols found)...done. Reading symbols from /usr/lib/libc.so.4...(no debugging symbols found)...done. Reading symbols from /usr/lib/libz.so.2...(no debugging symbols found)...done. Reading symbols from /usr/libexec/ld-elf.so.1...(no debugging symbols found)...done. #0 0x805dc00 in userdb_blocking_lookup () (gdb) bt #0 0x805dc00 in userdb_blocking_lookup () #1 0x805dd50 in userdb_blocking_lookup () #2 0x806175a in sql_drivers_register_all () #3 0x8060d1c in sql_query () #4 0x805de62 in userdb_blocking_lookup () #5 0x8055724 in auth_stream_is_empty () #6 0x80557f4 in auth_stream_is_empty () #7 0x8055894 in auth_stream_is_empty () #8 0x80668ac in io_loop_handler_run () #9 0x80662a1 in io_loop_run () #10 0x805770f in main () #11 0x804fd52 in _start () (gdb) Please help! -Wash http://www.netmeister.org/news/learn2quote.html DISCLAIMER: See http://www.wananchi.com/bms/terms.php -- +======================================================================+ |\ _,,,---,,_ | Odhiambo Washington <wash(a)wananchi.com> Zzz /,`.-'`' -. ;-;;,_ | Wananchi Online Ltd. www.wananchi.com |,4- ) )-,_. ,\ ( `'-'| Tel: +254 20 313985-9 +254 20 313922 '---''(_/--' `-'\_) | GSM: +254 722 743223 +254 733 744121 +======================================================================+ Hindsight is an exact science. [View Less]

4 10

[Dovecot] AIX mail quota plugin problems
by Stewart Dean 05 Jun '07

05 Jun '07

From reading the wiki for a filesystem quota, I took my shot at 1) building my binaries using the mods in AIXPluginsSupport 2) changing dovecot.conf and 3) putting the plugins in the library But I'm getting this error message when I invoke dovecot: Plugin imap_quota not found from directory /usr/local/lib/dovecot Error: imap dump-capability process returned 89 It would seem that a) I have the syntax or the parameters wrong b) I didn't get the changes to the AIX build environment right I've … [View More]attached the dovecot -n output. Here are the details of what I did. 1) dovecot.conf =========== within the imap config section =========== # Support for dynamically loadable plugins. mail_plugins is a space separated # list of plugins to load. #mail_plugins = #mail_plugin_dir = /usr/lib/dovecot/imap # SD 5/24/07 tryout FS quota plugin mail_plugins = quota imap_quota mail_plugin_dir = /usr/local/lib/dovecot/imap plugin { # Here you can give some extra environment variables to mail processes. # This is mostly meant for passing parameters to plugins. %variable # expansion is done for all values. # Quota plugin. Multiple backends are supported: # dirsize: Find and sum all the files found from mail directory. # Extremely SLOW with Maildir. It'll eat your CPU and disk I/O. # dict: Keep quota stored in dictionary (eg. SQL) # maildir: Maildir++ quota # fs: Read-only support for filesystem quota #quota = maildir # SD 5/24/07 Try FS quota support quota = fs I've tried it as both mail_plugin_dir = /usr/local/lib/dovecot/imap and mail_plugin_dir = /usr/local/lib/dovecot 2) Both ways I see this error message: > 4229 root@mercury:/usr/local/etc ## dovecot > ILoading modules from directory: /usr/local/lib/dovecot > IModule loaded: /usr/local/lib/dovecot/lib10_quota_plugin.so > FPlugin imap_quota not found from directory /usr/local/lib/dovecot > Error: imap dump-capability process returned 89 > > 4272 root@mercury:/usr/local/lib/dovecot/imap ## dovecot > ILoading modules from directory: /usr/local/lib/dovecot/imap > IModule loaded: /usr/local/lib/dovecot/imap/lib10_quota_plugin.so > FPlugin imap_quota not found from directory /usr/local/lib/dovecot/imap > Error: imap dump-capability process returned 89 > 3) These directories have the following contents: 4292 root@mercury:/usr/local/lib/dovecot ## ls -al total 1168 drwxr-xr-x 3 root system 512 May 24 12:36 ./ drwxr-xr-x 7 root system 512 May 21 14:31 ../ -rw-r--r-- 1 root sys 292522 May 22 15:12 052207-1455-64bit-ssl.lib10_quota_plugin.a -rwxr-xr-x 1 root sys 904 May 22 15:12 052207-1455-64bit-ssl.lib10_quota_plugin.la* -rwxr-xr-x 1 root sys 270499 May 22 15:12 052207-1455-64bit-ssl.lib10_quota_plugin.so* drwxr-xr-x 2 root system 512 May 24 12:41 imap/ lrwxrwxrwx 1 root system 65 May 24 12:36 lib10_quota_plugin.a@ -> /usr/local/lib/dovecot/052207-1 455-64bit-ssl.lib10_quota_plugin.a lrwxrwxrwx 1 root system 66 May 24 12:36 lib10_quota_plugin.la@ -> /usr/local/lib/dovecot/052207- 1455-64bit-ssl.lib10_quota_plugin.la* lrwxrwxrwx 1 root system 66 May 24 12:36 lib10_quota_plugin.so@ -> /usr/local/lib/dovecot/052207- 1455-64bit-ssl.lib10_quota_plugin.so* root@mercury:/usr/local/lib/dovecot/imap ## ls -al total 152 drwxr-xr-x 2 root system 512 May 24 12:41 ./ drwxr-xr-x 3 root system 512 May 24 12:36 ../ -rw-r--r-- 1 root system 19250 May 22 15:12 052207-1455-64bit-ssl.lib11_imap_quota_plugin.a -rwxr-xr-x 1 root system 944 May 22 15:12 052207-1455-64bit-ssl.lib11_imap_quota_plugin.la* -rwxr-xr-x 1 root system 28645 May 22 15:12 052207-1455-64bit-ssl.lib11_imap_quota_plugin.so* lrwxrwxrwx 1 root system 66 May 24 12:36 lib10_quota_plugin.so@ -> /usr/local/lib/dovecot/052207- 1455-64bit-ssl.lib10_quota_plugin.so* lrwxrwxrwx 1 root system 75 May 24 12:36 lib11_imap_quota_plugin.a@ -> /usr/local/lib/dovecot/ima p/052207-1455-64bit-ssl.lib11_imap_quota_plugin.a lrwxrwxrwx 1 root system 76 May 24 12:36 lib11_imap_quota_plugin.la@ -> /usr/local/lib/dovecot/im ap/052207-1455-64bit-ssl.lib11_imap_quota_plugin.la* lrwxrwxrwx 1 root system 76 May 24 12:36 lib11_imap_quota_plugins.so@ -> /usr/local/lib/dovecot/i Any suggestions? -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035 [View Less]

2 2

[Dovecot] testink
by Timo Sirainen 05 Jun '07

05 Jun '07

# Protocols we want to be serving: # imap imaps pop3 pop3s #protocols = imap imaps # IP or host address where to listen in for connections. It's not currently # possible to specify multiple addresses. "*" listens in all IPv4 interfaces. # "[::]" listens in all IPv6 interfaces, but may also listen in all IPv4 # interfaces depending on the operating system. You can specify ports with # "host:port". #imap_listen = * #pop3_listen = *

3 6

[Dovecot] Is there a "connect acl" ?
by Oliver Schulze L. 05 Jun '07

05 Jun '07

Hi, I have been reading the acl documentation and it seems that a "connect acl" is not available. I need to limit the users that can login in an IP number, is that posible with dovecot 1.0? (i.e. only these users can login from the Internet) Or a new plugin should be written? It is complicated to do that? Thanks Oliver -- Oliver Schulze L. | http://tinymailto.com/oliver Asuncion - Paraguay | http://www.solojuegos.mobi

4 5

[Dovecot] Backing up mail?
by Knute Johnson 04 Jun '07

04 Jun '07

My mail server is running on a Fedora FC5 box. I need to move the mail server to another computer and so I need to back up my user's mail and move it. I have found mail in /var/spoo/mail/[users] and in their home directories there is a 'mail' directory. All users have an 'Inbox' file that is empty and I think the one IMAP user has a 'Trash' file that is huge! Are those the only files I need to copy or are there others lurking out there that I don't know about? Thanks, -- Knute Johnson Molon Labe...

1 0

[Dovecot] tweaking performance
by Paul A 04 Jun '07

04 Jun '07

Hi, I was wondering if anyone had some ideas on what I can tweak to gain more performance. We have tome timeouts reports on pop3 during heavy load periods. Using imap/pop3 with maildir with 7,000 users using mostly pop3. # /usr/local/etc/dovecot.conf protocols: imap 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 … [View More]

2 1

[Dovecot] dovecot-shared tries to fchown index+control files but fails
by Adam McDougall 04 Jun '07

04 Jun '07

I have some public mailboxes setup in 1.0.0, location = maildir:/egr/mail/shared/org:CONTROL=%h/Maildir/dovecot/public/control/org:INDEX=%h/Maildir/dovecot/public/indexes/org I also have a dovecot-shared file in the maildir folders so messages that are added to the inbox get a decent set of default permissions. However, I think dovecot is also trying to fchown the index files (stored in a user home directory, far away from the shared mail) to match the owner of the dovecot-shared file. … [View More]

2 4

[Dovecot] Client certificate verification/authentication
by eizert 04 Jun '07

04 Jun '07

I would like to use Client certificate verification/authentication. My MTA used this function. I've a problem to make a valid certificate. For my MTA i used : openssl req -new -nodes -x509 -keyout user_key.pem -out user_req.pem -days 365 openssl ca -out user_signed.pem -infiles user_req.pem openssl pkcs12 -in user_signed.pem -inkey user_key.pem -out user.p12 -export -name "user@hotsname" user.p12 match in my MTA Not in Dovecot... In my log, i've simply : dovecot: auth(default): Client … [View More]

2 4

[Dovecot] dovecot-sieve-1.0 (hg) does not build
by Bernhard Schmidt 04 Jun '07

04 Jun '07

Hi, the dovecot-sieve plugin from the hg repository (http://hg.dovecot.org/dovecot-sieve-1.0/) does not build against current dovecot-1.0 repository. /bin/bash ../../libtool --tag=CC --mode=link gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -DENABLE_REGEX -o sievec sievec.o map.o imparse.o libsieve.la /usr/src/dovecot-1.0/src/lib/liblib.a gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -… [View More]

2 3

[Dovecot] Sharing nested folders / maildir variations?
by SeattleServer.com 04 Jun '07

04 Jun '07

Hey all, So I've got a shared namespace in dovecot where users can, via a custom control panel, share their folders into (which creates a symlink) in order to allow anyone on their domain to access it. I store mail in maildir. The issue is that when people share folders, they expect that when they make subfolders, those are automatically shared as they are contained within it. According to the Maildir++ specification, "Can folders have subfolders, defined in a recursive fashion? … [View More]

2 3

[Dovecot] Dovecot waking every 50ms when doing nothing
by Ross Burton 04 Jun '07

04 Jun '07

Hi, My laptop runs a local IMAP server so that I'm immune from breaking my mail client, and when playing around with powertop I discovered that Dovecot (in particular imap-login) wakes up every 1000ms and then every 50ms even when no clients are connected. A bit of stracing shows this: gettimeofday({1180875699, 667917}, NULL) = 0 <0.000010> poll([{fd=7, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=10, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=3, events=POLLIN|POLLPRI|… [View More]

7 16

[Dovecot] frequent index rebuilds versus disabled indexes
by Justin McAleer 04 Jun '07

04 Jun '07

Ok, here's the short and sweet version of my dilemma. I have a group of servers mounting a shared NFS device to hold mail data for many different domains. Is it worth the load balancing management nightmare of setting up dedicating smtp, pop, and imap to one server (failing over to another in the group if the server goes down) to keep indexes on local disk? It's very tempting to just disable indexes and not worry about which server a user hits, and considering the vast majority of our … [View More]

2 1

[Dovecot] Quota handling - v2 - updated FR
by Charles Marcus 04 Jun '07

04 Jun '07

This revised proposal for a Feature Request is the result of my desire to implement quotas, but not have the attendant headaches that inevitably accompany its implementation. Ralf Hildebrandt wrote: > I have to face it, my users are retards: Is there any other kind of user? ;) <snip> > Thus I need a feature in dovecot that will tell them via email: > > Level1: "You ALMOST exceeded your quota, you're at 90% now" > Level2: "You're very close to exceededin your quota, you'… [View More]re at 95% > now" > Level3: "Would you please clean up now? You're at 99% now" What I'd *really* like to see implemented is something along the lines outlined below - but of course, this will depend entirely on whether or not Timo thinks it is doable - or desirable... I'm thinking this would be best handled by the Quota plug-in - either as part of the current one, or as a separate/different one... *** 1. Have a 'special' user-specific folder (by special, I mean like the Drafts, Sent, Templates folders) that dovecot controls. For purposes of this FR, call it the 'over-quota' folder. Question: could the .tmp folder be used for this? No sense in reinventing the wheel if necessary... and then if someone migrated from dovecot to something else, and messages were left in there from an over-quota condition, that other solution would most likely just move these to .new the first time it ran, right? Or, possibly, could dovecot create a new one maybe, .oqt (for over-quota), and store the queued messages there until the over-quota condition was rectified? Anyway, the main thing is, this folder should be essentially hidden from the user so they do *not* have access to it, and should temporarily hold messages that come in that are unable to be delivered due to an over-quota condition. *** 2. Make dovecot aware of and use a special 'Quota Status' message that it uses to inform a user that they are over quota. This message should be able to be customized, with variables (like, for example, it should list the messages that are currently being prevented from being moved to the Inbox - including, optionally, the Subject, the sender, date/time, attachments, size, etc - as well as provide general quota information (ie, how close to or over quota they are, and how much they'd need to delete or move to Local Folders to allow delivery of all of the messages being held), and lastly, any custom information the System Admin wanted to provide - like, maybe, specific instructions for how to move messages to Local Folders, how to request additional storage allowance, etc. *** 3. When user is over quota, have LDA deliver to the folder referenced above (# 1) - (yes, accept the message for final delivery from the sending mta), and then update the Quota Status message and move it to the Inbox. Optionally, a bounce/notification could be generated to the sender, informing them that their message is being 'held in queue' or something to that effect, due to the recipient being over-quota. *** 4. Once the user deletes enough mail to come back under quota, dovecot would then move messages from the 'over-quota' folder to his Inbox. Ok, again, am willing to hear *valid* reasons how/why this is a terrible idea... :) -- Best regards, Charles [View Less]

6 10

[Dovecot] delivery and quota question
by Arkadiusz Miskiewicz 04 Jun '07

04 Jun '07

Hi, I'm considering using delivery for delivering emails. The question is about quota. Does delivery check quota for single maildir or for entire collection of user folders? Example: /var/mail/user/{new,cur,tmp} /var/mail/user/.Some_Folder/{new,cur,tmp} /var/mail/user/.Some_Other_Folder/{new,cur,tmp} Can I somehow get deliver checking size for all these folders? I need quota per user not per folder. -- Arkadiusz Miśkiewicz PLD/Linux Team arekm / maven.pl http://ftp.pld-linux.org/

2 1

[Dovecot] Simple questions about Quota
by Venilton Junior 04 Jun '07

04 Jun '07

Hi folks, hope that get some help for some doubts :P I've configured dovecot in a clustered environment 3 X HP Proliant DL380+RHEL ES 4.0+EVA4000+GFS. Everything is working great. But, when I putted this cluster on production, I had some problems with quota+ldap in my dovecot. Here follows my configuration: /etc/dovecot.conf last_valid_gid = 101 maildir_copy_with_hardlinks = no login_greeting = Internet ready. disable_plaintext_auth = no auth_default_realm =domain.… [View More]

2 1

[Dovecot] Dovecot and Seamonkey/Mozilla "delete attachment"
by Bryce Nesbitt 04 Jun '07

04 Jun '07

I'm having persistent trouble deleting larger attachments from messages in Mozilla/Seamonkey mail, and I'm thinking it may be related to Dovecot. A bug report is over at https://bugzilla.mozilla.org/show_bug.cgi?id=381759 I do not have the version number of Dovecot available, unless you know how to get it from the IMAP prompt: > telnet idiom.com 143 Trying 216.240.32.1... Connected to idiom.com. Escape character is '^]'. * OK Dovecot ready. How can I track this down more? Is anyone … [View More]

2 1

[Dovecot] Error: no authentication failed
by gaoqiang.qian＠nokia.com 04 Jun '07

04 Jun '07

Hi, I have installed the dovecot on my redhat linux host. But when I log in with dovecot/test I got Error: no authentication failed after I got ok dovecot ready when I connect to local host. dovecot/test was set in the password.dovecot file. But I do not know how can I use this username and password in the configuration file. Could anyone give me a hand to let me know how to configurate the username and password for login. Thanks

2 1

[Dovecot] Overriding IMAP commands
by Tony Tsang 04 Jun '07

04 Jun '07

Hi all, I am writing a plugin to override some built-in imap commands. But when client logs out, imap segfaults during unregistering commands. What is the correct procedure for overriding imap commands in dovecot? Thanks. Tony Tsang.

2 1

Re: [Dovecot] Namespace Problems
by Kenny Dail 04 Jun '07

04 Jun '07

> Hi all, > > after an update from dovecot beta version to 1.0.0.-1 today morning I > had different effects: > thunderbird-, kmail-, Apple-clients, pine and squirrelmail could > receive email correct with imaps. But not MSOutlook!!! > Varying the namespace configurations in dovecot.conf I got different > results with MSOutlook working but with thunderbird, squirrelmail etc. > all folders are displayed but not the root Inbox etc. > Its important to know that I … [View More]

3 2

[Dovecot] Stop Maildir appending to path
by Henry 04 Jun '07

04 Jun '07

dovecot -n: # /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S protocols: imaps ssl_listen: 208.xxx.xxx.xxx login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_extra_groups: mail mail_debug: yes auth default: passdb: driver: pam passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: passwd userdb: driver: static args: uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes socket: … [View More]

3 2

[Dovecot] What are they trying to do here?
by Jon Slater 04 Jun '07

04 Jun '07

Hi! I’m new to the list, and I’m not really having a ‘problem’, but I’m seeing something in my log files that I wonder if I should be concerned. I’ve been using Dovecot (dovecot-0.99.14-8.fc4) on my Fedora Core 4 (kernel 2.6.17-1.2142_FC4) machine from quite some time. For the last few days, I’ve been seeing this in my daily ‘Logwatch’ e-mail: dovecot: Authentication Failures: rhost= : 139 Time(s) root: 13 Time(s) Unknown Entries: check pass; user … [View More]

2 1

[Dovecot] dovecot scaling issue?
by it-dovecot＠ml.epigenomics.com 04 Jun '07

04 Jun '07

Hi! We are running dovecot-imapd on Debian sarge out of the backports.org packages (version 1.0.rc15-1~bpo1). We have ~ 80 clients using secure IMAP. I understand that imap-login has to run for every SSL connection. Thus I already increased the max value for the number of imap-login processes. But unfortunately dovecot is unresponsive from time to time. Where can I tune the installation? Do I need to upgrade to 1.0.0, for which no backported packages exist for Debian sarge? This is the … [View More]

2 1

[Dovecot] Dovecot support for smd5 and ldap-md5
by Eric and Barbara Sammons 04 Jun '07

04 Jun '07

Working with a dovecot migration, I am curious what version (if any) of Dovecot (dovecot-auth) supports SMD5 and ldap-MD5 when using Dovecot -> OpenLDAP direct binding? Thank you! Eric

2 1

[Dovecot] TLS errors when vodafone connecting to dovecot server.
by Andrew Pounce 04 Jun '07

04 Jun '07

Hi, I've been trying to setup the vodafone email sync ( provided by visto apparently ) and have not been able to do so - I'm getting an error message in my mail logs which looks as if there is a problem with certificates somewhere. May 31 16:49:39 imap dovecot: imap-login: SSL_accept() failed: error:14094416:SSL routines:SSL3_READ_BYTES:sslv3 alert certificate unknown [206.124.112.22] Thunderbird has no problems with using TLS against this server and I'm not entirely sure if dovecot (or … [View More]

2 1

[Dovecot] CMU Sieve pluigin missing proper charset support
by Jan Srzednicki 04 Jun '07

04 Jun '07

Hello, After testing the Sieve plugin for the LDA, I have noticed that it does not handle charset issues properly. IETF draft says: 4.3. Subject and From Parameters The ":subject" parameter specifies a subject line to attach to any vacation response that is generated. UTF-8 characters can be used in the string argument; implementations MUST convert the string to [RFC2047] encoded words if and only if non-ASCII characters are present. Implementations MUST generate an … [View More]

2 1

[Dovecot] Error starting dovecot 1.0.0 /var/run/dovecot/auth-master failed: No such file or directory
by Yashesh Bhatia 01 Jun '07

01 Jun '07

Hello: i'm trying a tutorial (http://workaround.org/articles/ispmail-etch/en.html) for setting up postfix / dovecot but am getting some errors when i try to start dovecot here's some details of the enviromnent. (Fedora Core 6) $ uname -a Linux foo.com 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:37:32 EDT 2006 i686 i686 i386 GNU/Linux $ ./dovecot --version 1.0.0 $ ./dovecot -n # /opt/dovecot-1.0.0/etc/dovecot.conf protocols: imap imaps pop3 pop3s ssl_disable: yes login_dir: /opt/dovecot-1.0.0/… [View More]var/run/dovecot/login login_executable(default): /opt/dovecot-1.0.0/libexec/dovecot/imap-login login_executable(imap): /opt/dovecot-1.0.0/libexec/dovecot/imap-login login_executable(pop3): /opt/dovecot-1.0.0/libexec/dovecot/pop3-login mail_location: maildir:/var/spool/foomail/%d/%n mail_executable(default): /opt/dovecot-1.0.0/libexec/dovecot/imap mail_executable(imap): /opt/dovecot-1.0.0/libexec/dovecot/imap mail_executable(pop3): /opt/dovecot-1.0.0/libexec/dovecot/pop3 mail_plugin_dir(default): /opt/dovecot-1.0.0/lib/dovecot/imap mail_plugin_dir(imap): /opt/dovecot-1.0.0/lib/dovecot/imap mail_plugin_dir(pop3): /opt/dovecot-1.0.0/lib/dovecot/pop3 auth default: passdb: driver: pam passdb: driver: sql args: /opt/dovecot-1.0.0/etc/dovecot_sql.conf userdb: driver: passwd userdb: driver: static args: uid=721 gid=721 home=/var/spool/foomail/%d/%n allow_all_users=yes socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: foomail $ now when i try to start dovecot it dies giving the following error message in /var/log/maillog Jun 1 20:30:16 foo dovecot: Dovecot v1.0.0 starting up Jun 1 20:30:16 foo dovecot: auth(default): bind(/var/run/dovecot/auth-master) failed: No such file or directory Jun 1 20:30:16 foo dovecot: auth(default): net_listen_unix(/var/run/dovecot/auth-master) failed: No such file or directory Jun 1 20:30:16 foo dovecot: Auth process died too early - shutting down Jun 1 20:30:16 foo dovecot: child 9760 (auth) returned error 89 I've read the http://wiki.dovecot.org/CompilingSource but am stuck now with this issue. i also googled around a bit but could get any more information about this problem. any help is appreciated. thanks in advance. yashesh bhatia. ---------------------------------------------------------------- Go Pre http://www2.localaccess.com/rlalonde/pre.htm ---------------------------------------------------------------- [View Less]

1 1

[Dovecot] SSHA salt?
by Andreas Baitis 01 Jun '07

01 Jun '07

Hi there, I was wondering if someone could explain how dovecot/dovecotpw produces salt for use in ssha passwords, I'd like to replicate this in PHP so I can write my passwords from php in ssha instead of just sha1. Thanks in advance, Andrea Baitis

1 1

[Dovecot] Dovecot authentication for PostFix, anyone?
by Marco Fioretti 31 May '07

31 May '07

Greetings, the postfix sasl readme, http://www.postfix.org/SASL_README.htm says: >Dovecot provides an [authentication alternative to Cyrus] that may be worth considering. In principle, I like the idea of doing without Cyrus, since I have to run an IMAP server anyway and had already chosen Dovecot. The question is if that page is up to date and if you could share comments or, if they exist, safer/more efficient ways to use Dovecot as authentication server for PostFix, as well as any … [View More]

4 3

[Dovecot] Dovecot Authentication Problem (REVISED)
by Odhiambo WASHINGTON 31 May '07

31 May '07

Hello List, I am back again and I think I am edging closer to getting a solution. I have done some modifications and now dovecot gives me a different error message than before.... Here is what I have for the password_query and user_query password_query = SELECT popbox.cleartext AS password FROM popbox, domain \ WHERE popbox.local_part = 'eddie' AND popbox.domain_name = 'demo.wananchi.com' \ AND popbox.domain_name = domain.domain_name; +----------+ | password | +----------+ | boeing8 | +---… [View More]-------+ user_query = SELECT CONCAT(domain.path, '/', popbox.mbox_name) as home, \ 69 as uid, 6 as gid FROM popbox, domain WHERE popbox.local_part = 'eddie' \ AND popbox.domain_name = 'demo.wananchi.com' AND \ popbox.domain_name = domain.domain_name; +--------------------------------------------+-----+-----+ | home | uid | gid | +--------------------------------------------+-----+-----+ | /var/spool/virtual/demo.wananchi.com/eddie | 69 | 6 | +--------------------------------------------+-----+-----+ When I test to connect to the pop3 daemon, this is what happens now: root@ns2]#telnet 0 7173 Trying 0.0.0.0... Connected to 0. Escape character is '^]'. +OK Welcome. Dovecot is Ready to serve your emails. user eddie(a)demo.wananchi.com +OK pass boeing8 -ERR [IN-USE] Internal login failure. Refer to server log for more information. Connection closed by foreign host. ...and this is what dovecot writes to the log: [root@ns2]#less /var/log/dovecot.log dovecot: May 30 12:00:04 Info: auth(default): client in: AUTH 1 PLAIN service=POP3 secured lip=62.8.64.4 rip=62.8.64.4 resp=AGVkZGllQGRlbW8ud2FuYW5jaGkuY29tAGJvZWluZzg= dovecot: May 30 12:00:04 Info: auth-worker(default): mysql: Connected to localhost (virtualemail) dovecot: May 30 12:00:04 Info: auth-worker(default): sql(eddie(a)demo.wananchi.com,62.8.64.4): query: SELECT popbox.cleartext AS password FROM popbox, domain WHERE popbox.local_part = 'eddie' AND popbox.domain_name = 'demo.wananchi.com' AND popbox.domain_name = domain.domain_name dovecot: May 30 12:00:04 Info: auth(default): client out: OK 1 user=eddie(a)demo.wananchi.com dovecot: May 30 12:00:04 Info: auth(default): master in: REQUEST 2 36772 1 dovecot: May 30 12:00:04 Info: auth-worker(default): sql(eddie(a)demo.wananchi.com,62.8.64.4): SELECT CONCAT(domain.path, '/', popbox.mbox_name) as home, 69 as uid, 6 as gid FROM popbox, domain WHERE popbox.local_part = 'eddie' AND popbox.domain_name = 'demo.wananchi.com' AND popbox.domain_name = domain.domain_name dovecot: May 30 12:00:05 Error: child 39853 (auth-worker) killed with signal 11 dovecot: May 30 12:00:05 Info: auth(default): master out: FAIL 2 dovecot: May 30 12:00:05 Info: pop3-login: Internal login failure: user=<eddie(a)demo.wananchi.com>, method=PLAIN, rip=62.8.64.4, lip=62.8.64.4, secured The output of dovecot -n: # /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot.log protocols: pop3 listen: *:7173 ssl_disable: yes disable_plaintext_auth: no shutdown_clients: no login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/pop3-login login_greeting: Welcome. Dovecot is Ready to serve your emails. login_process_size: 64 login_max_processes_count: 200 verbose_proctitle: yes first_valid_uid: 69 first_valid_gid: 6 mail_extra_groups: exim mail_location: maildir:/var/spool/virtual/%d/%n mail_debug: yes mail_executable: /usr/local/libexec/dovecot/pop3 mail_plugin_dir: /usr/local/lib/dovecot/pop3 pop3_uidl_format: %Mf pop3_client_workarounds: outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login digest-md5 cram-md5 verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /usr/local/etc/dovecot-sql.conf userdb: driver: sql args: /usr/local/etc/dovecot-sql.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 384 user: root group: wheel User's mail is stored in /var/spool/virtual/$domain/$user/{new,cur,tmp} The path /var/spool/virtual/ is owned by uid:gid 69:6, and is writeable by that uid. I'd be happy to use a second brain and a third eye to help me figure out the problem. -Wash http://www.netmeister.org/news/learn2quote.html DISCLAIMER: See http://www.wananchi.com/bms/terms.php -- +======================================================================+ |\ _,,,---,,_ | Odhiambo Washington <wash(a)wananchi.com> Zzz /,`.-'`' -. ;-;;,_ | Wananchi Online Ltd. www.wananchi.com |,4- ) )-,_. ,\ ( `'-'| Tel: +254 20 313985-9 +254 20 313922 '---''(_/--' `-'\_) | GSM: +254 722 743223 +254 733 744121 +======================================================================+ Democracy is a device that insures we shall be governed no better than we deserve. -- George Bernard Shaw [View Less]

1 1

[Dovecot] dovecot performance question
by Paul A 30 May '07

30 May '07

Hi, using the latest dovecot with pop3/imap. Using mostly outlook 2003 for pop3 and squirrel mail imap. I have a lot of users reporting back that imap is very slow. We average about 300 imap and another 700 pop session at any given time. Here's my config: 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/… [View More]

3 3

[Dovecot] Index file rewrite status
by Timo Sirainen 30 May '07

30 May '07

The biggest problem with getting v1.0 out was getting its index file code stable. v1.1 plans included doing large changes to the index file code, so it's important to get the new code stable as soon as possible. Since I've managed to stay pretty productive for the last few weeks, I've been mostly just coding the index changes. Once I'm sure that the code is again fully working I'll commit it to hg, relax a bit and then I'll again start answering mails in this list. It looks like the code is … [View More]almost working, but it's still giving failures once in a while. Below are anyway a few benchmarks for you to see how it's progressing. I haven't yet done all the optimizations I've planned, but looks like it already gives 25-30% better performance in cydir tests. The cydir benchmarks are the most important ones because cydir relies completely on index files, so the benchmarks are practically index benchmarks. And the 25-30% is mostly about CPU usage I think, reduced dovecot.index file rewrites will help with disk I/O as well. The new index code should be pretty NFS friendly. I think there is going to be only one place where I'll need to force attribute cache flush and then probably a couple of places where data cache needs to be flushed (I'm not exactly sure about that yet, I'll have to know more about NFS data caching). One other thing I'm hoping to implement is that the index functions would almost never fail. If anything breaks, the indexes should be moved to memory. Any corrupted data should be ignored and anything that looks good would still be used (important with cydir/dbox). I've even managed to remove about 500 lines of code: 26 files changed, 3258 insertions(+), 3753 deletions(-) (about 2000 insert+deletions are just cut&pasting code to different files) Append-only tests: mmap_disable=no, fsync_disable=yes Current hg (before index rewrite), cydir: ./imaptest - append=100,0 logout=0 select=0 clients=1 secs=5 Logi Appe 100% 100% 1 2602 1/ 1 0 2671 1/ 1 0 2750 1/ 1 0 2363 1/ 1 Totals: 1 13206 Index rewrite, cydir: Totals: Logi Appe 100% 100% 1 4251 1/ 1 0 3914 1/ 1 0 3514 1/ 1 0 2985 1/ 1 0 2538 1/ 1 Totals: 1 17202 Maildir (not much difference between rewrite/no rewrite): Logi Appe 100% 100% 1 917 1/ 1 0 498 1/ 1 0 284 1/ 1 0 273 1/ 1 0 296 1/ 1 Totals: 1 2268 mbox (+300 with index rewrite): Logi Appe 100% 100% 1 1827 1/ 1 0 1688 1/ 1 0 1811 1/ 1 0 2040 1/ 1 Totals: 1 9114 Then a bit more generic test: Old index code, cydir: ./imaptest secs=10 clients=10 Logi List Stat Sele Fetc Fet2 Stor Dele Expu Appe Logo 100% 50% 50% 100% 100% 100% 50% 100% 100% 100% 100% 30% 5% 3417 1713 1713 3416 3403 4840 1719 1260 3403 1999 6816 New index code, cydir: Logi List Stat Sele Fetc Fet2 Stor Dele Expu Appe Logo 100% 50% 50% 100% 100% 100% 50% 100% 100% 100% 100% 30% 5% 4686 2349 2317 4678 4675 6636 2323 1628 4675 2585 9353 [View Less]

1 0

[Dovecot] Converting mbox to Maildir, all prior read messages are downloaded as new
by Eric and Barbara Sammons 30 May '07

30 May '07

I am running dovecot 0.99. Everything works great; however, now I am looking at several different tools to convert mbox to Maildir. It seems the tools, mb2md.pl, perfect_maildir.pl, and others all do what they claim; however, when the messages are converted and they are stored in Maildir/cur, the email clients download these messages as new. This typically wouldn't be a problem; however, I am dealing with 100s of users with 1000s of emails and this really isn't acceptable behavior to … [View More]

5 6

[Dovecot] deliver rejection message
by Timo Sirainen 30 May '07

30 May '07

Currently the typical rejection message is: --------- Your message was automatically rejected by Dovecot Mail Delivery Agent. The following reason was given: Quota exceeded. --------- Then there is MDN + message headers in other MIME parts. But of course there sucky clients that can't display MDNs and users get confused. Any suggestions how to improve this message? I'm not sure if the "Dovecot Mail Delivery Agent" even needs to be in there. How about something like: --------- Your message … [View More]

5 6

Re: [Dovecot] [dovecot] IMAP basics
by Paul Scott 30 May '07

30 May '07

Picking up a broken thread after gettin exim4 to send my mail out. version 1.0.0 on Debian sid: I now have fetchmail delivering three POP mailboxes to my Maildir. How do I tell Dovecot about this mail? TIA, Paul Scott

1 0

Re: [Dovecot] Dovecot] dovecot performance question
by Kenny Dail 30 May '07

30 May '07

> Hi, using the latest dovecot with pop3/imap. Using mostly outlook 2003 for > pop3 and squirrel mail imap. > > I have a lot of users reporting back that imap is very slow. We average > about 300 imap and another 700 pop session at any given time. reporting that imap is slow or that squirrelmail is slow? ;) How is the load average on the server? We found at our site to keep Apache/squirrelmail happy, we dedicated a server for our webmail users. Mostly being a RAM issue in that … [View More]

2 1

[Dovecot] namespace problem
by Rainer Sigl 29 May '07

29 May '07

Hi all, after an update from dovecot beta version to 1.0.0.-1 today morning I had different effects: thunderbird-, kmail-, Apple-clients, pine and squirrelmail could receive email correct with imaps. But not MSOutlook!!! Varying the namespace configurations in dovecot.conf I got different results with MSOutlook working but with thunderbird, squirrelmail etc. all folders are displayed but not the root Inbox etc. Its important to know that I migrated from courier-imap to dovecot. My well … [View More]working namespace config BEFORE upgrade to 1.0.0-1: namespace private { #separator = / prefix = INBOX. # prefix = inbox = yes #hidden = yes } #the second namespace I need to work with Apple because they use / namespace private { separator = / prefix = INBOX/ inbox = no hidden = yes } Here my actual namespace configs: namespace private { separator = prefix = INBOX. inbox = no hidden = no } namespace private { separator = / prefix = INBOX/ inbox = no hidden = yes } namespace private { separator = . prefix = INBOX. inbox = yes hidden = yes } In varying inbox and hidden keywords I found this configuration. Most things are working with this but in squirrelmal I can't access inbox, the main folder. How do I have to configure that everythings works satisfying?? Many thanks Rainer Sigl [0]root@mpemail:/etc/dovecot# dovecot -n # /etc/dovecot/dovecot.conf log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot-info.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: imaps pop3s ssl_cert_file: /etc/ssl/certs/mpemail.pem ssl_key_file: /etc/ssl/private/mpemail-key.pem 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 login_chroot: no verbose_proctitle: yes mail_extra_groups: mail default_mail_env: maildir:/home/virtual_mail/%u mail_location: maildir:/home/virtual_mail/%u mail_debug: yes mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 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): UID%u-%v namespace: type: private prefix: INBOX. namespace: type: private separator: / prefix: INBOX/ hidden: yes namespace: type: private separator: . prefix: INBOX. inbox: yes hidden: yes auth default: passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: static args: uid=1002 gid=1002 home=/home/virtual_mail/%u userdb: driver: passwd userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf -- ----------------- 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/ [View Less]

1 0

[Dovecot] Namespace Problems repost without attachment
by Rainer Sigl 29 May '07

29 May '07

Hi all, after an update from dovecot beta version to 1.0.0.-1 today morning I had different effects: thunderbird-, kmail-, Apple-clients, pine and squirrelmail could receive email correct with imaps. But not MSOutlook!!! Varying the namespace configurations in dovecot.conf I got different results with MSOutlook working but with thunderbird, squirrelmail etc. all folders are displayed but not the root Inbox etc. Its important to know that I migrated from courier-imap to dovecot. My well … [View More]

1 0

[Dovecot] Namespace Problems
by Rainer Sigl 29 May '07

29 May '07

Hi all, after an update from dovecot beta version to 1.0.0.-1 today morning I had different effects: thunderbird-, kmail-, Apple-clients, pine and squirrelmail could receive email correct with imaps. But not MSOutlook!!! Varying the namespace configurations in dovecot.conf I got different results with MSOutlook working but with thunderbird, squirrelmail etc. all folders are displayed but not the root Inbox etc. Its important to know that I migrated from courier-imap to dovecot. My well … [View More]working namespace config BEFORE upgrade to 1.0.0-1: namespace private { #separator = / prefix = INBOX. # prefix = inbox = yes #hidden = yes } #the second namespace I need to work with Apple because they use / namespace private { separator = / prefix = INBOX/ inbox = no hidden = yes } Here my actual namespace configs: namespace private { separator = prefix = INBOX. inbox = no hidden = no } namespace private { separator = / prefix = INBOX/ inbox = no hidden = yes } namespace private { separator = . prefix = INBOX. inbox = yes hidden = yes } In varying inbox and hidden keywords I found this configuration. Most things are working with this but in squirrelmal I can't access inbox, the main folder. How do I have to configure that everythings works satisfying?? dovecot.conf and dovecot-sql.conf I send in the attachment. Many thanks 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/ -- ----------------- 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/ ## Dovecot configuration file # '#' character and everything after it is treated as comments. Extra spaces # and tabs are ignored. If you want to use either of these explicitly, put the # value inside quotes, eg.: key = "# char and trailing whitespace " # Default values are shown after each value, it's not required to uncomment # any of the lines. Exception to this are paths, they're just examples # with real defaults being based on configure options. The paths listed here # are for configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var # --with-ssldir=/etc/ssl # Base directory where to store runtime data. #base_dir = /var/run/dovecot/ # Protocols we want to be serving: # imap imaps pop3 pop3s #protocols = imap imaps protocols = imaps pop3s # IP or host address where to listen in for connections. It's not currently # possible to specify multiple addresses. "*" listens in all IPv4 interfaces. # "[::]" listens in all IPv6 interfaces, but may also listen in all IPv4 # interfaces depending on the operating system. If you want to specify ports # for each service, you will need to configure these settings inside the # protocol imap/pop3 { ... } section, so you can specify different ports # for IMAP/POP3. #listen = * # IP or host address where to listen in for SSL connections. Defaults # to above if not specified. #ssl_listen = # Disable SSL/TLS support. #ssl_disable = no # PEM encoded X.509 SSL/TLS certificate and private key. They're opened before # dropping root privileges, so keep the key file unreadable by anyone but # root. #ssl_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem #ssl_key_file = /etc/ssl/private/ssl-cert-snakeoil.key ssl_cert_file = /etc/ssl/certs/mpemail.pem ssl_key_file = /etc/ssl/private/mpemail-key.pem # If key file is password protected, give the password here. Alternatively # give it when starting dovecot with -p parameter. #ssl_key_password = # File containing trusted SSL certificate authorities. Usually not needed. #ssl_ca_file = # Request client to send a certificate. #ssl_verify_client_cert = no # How often to regenerate the SSL parameters file. Generation is quite CPU # intensive operation. The value is in hours, 0 disables regeneration # entirely. #ssl_parameters_regenerate = 168 # SSL ciphers to use #ssl_cipher_list = ALL:!LOW # Disable LOGIN command and all other plaintext authentications unless # SSL/TLS is used (LOGINDISABLED capability). Note that 127.*.*.* and # IPv6 ::1 addresses are considered secure, this setting has no effect if # you connect from those addresses. #disable_plaintext_auth = yes # Use this logfile instead of syslog(). /dev/stderr can be used if you want to # use stderr for logging (ONLY /dev/stderr - otherwise it is closed). log_path = /var/log/dovecot.log # For informational messages, use this logfile instead of the default info_log_path = /var/log/dovecot-info.log # Prefix for each line written to log file. % codes are in strftime(3) # format. log_timestamp = "%Y-%m-%d %H:%M:%S " # Syslog facility to use if you're logging to syslog. Usually if you don't # want to use "mail", you'll use local0..local7. Also other standard # facilities are supported. #syslog_facility = mail ## ## Login processes ## # Directory where authentication process places authentication UNIX sockets # which login needs to be able to connect to. The sockets are created when # running as root, so you don't have to worry about permissions. Note that # everything in this directory is deleted when Dovecot is started. #login_dir = /var/run/dovecot/login # chroot login process to the login_dir. Only reason not to do this is if you # wish to run the whole Dovecot without roots. # http://wiki.dovecot.org/Rootless login_chroot = no # User to use for the login process. Create a completely new user for this, # and don't use it anywhere else. The user must also belong to a group where # only it has access, it's used to control access for authentication process. # Note that this user is NOT used to access mails. # http://wiki.dovecot.org/UserIds login_user = dovecot # Set max. process size in megabytes. If you don't use # login_process_per_connection you might need to grow this. #login_process_size = 32 # Should each login be processed in it's own process (yes), or should one # login process be allowed to process multiple connections (no)? Yes is more # secure, espcially with SSL/TLS enabled. No is faster since there's no need # to create processes all the time. #login_process_per_connection = yes # Number of login processes to create. If login_process_per_connection is # yes, this is the number of extra processes waiting for users to log in. #login_processes_count = 3 # Maximum number of extra login processes to create. The extra process count # usually stays at login_processes_count, but when multiple users start logging # in at the same time more extra processes are created. To prevent fork-bombing # we check only once in a second if new processes should be created - if all # of them are used at the time, we double their amount until limit set by this # setting is reached. This setting is used only if login_process_per_use is yes. #login_max_processes_count = 128 # Maximum number of connections allowed in login state. When this limit is # reached, the oldest connections are dropped. If login_process_per_connection # is no, this is a per-process value, so the absolute maximum number of users # logging in actually login_processes_count * max_logging_users. #login_max_logging_users = 256 # Greeting message for clients. #login_greeting = Dovecot ready. # Space-separated list of elements we want to log. The elements which have # a non-empty variable value are joined together to form a comma-separated # string. #login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c # Login log format. %$ contains login_log_format_elements string, %s contains # the data we want to log. #login_log_format = %$: %s ## ## Mail processes ## # Maximum number of running mail processes. When this limit is reached, # new users aren't allowed to log in. #max_mail_processes = 1024 # Show more verbose process titles (in ps). Currently shows user name and # IP address. Useful for seeing who are actually using the IMAP processes # (eg. shared mailboxes or if same uid is used for multiple accounts). verbose_proctitle = yes # Show protocol level SSL errors. #verbose_ssl = no # Valid UID range for users, defaults to 500 and above. This is mostly # to make sure that users can't log in as daemons or other system users. # Note that denying root logins is hardcoded to dovecot binary and can't # be done even if first_valid_uid is set to 0. #first_valid_uid = 500 #last_valid_uid = 0 # Valid GID range for users, defaults to non-root/wheel. Users having # non-valid GID as primary group ID aren't allowed to log in. If user # belongs to supplementary groups with non-valid GIDs, those groups are # not set. #first_valid_gid = 1 #last_valid_gid = 0 # Grant access to these extra groups for mail processes. Typical use would be # to give "mail" group write access to /var/mail to be able to create dotlocks. mail_extra_groups = mail # ':' separated list of directories under which chrooting is allowed for mail # processes (ie. /var/mail will allow chrooting to /var/mail/foo/bar too). # This setting doesn't affect login_chroot or auth_chroot variables. # WARNING: Never add directories here which local users can modify, that # may lead to root exploit. Usually this should be done only if you don't # allow shell access for users. See # /usr/share/doc/dovecot-common/configuration.txt for more information. #valid_chroot_dirs = # Default chroot directory for mail processes. This can be overridden for # specific users in user database by giving /./ in user's home directory # (eg. /home/./user chroots into /home). Note that usually there is no real # need to do chrooting, Dovecot doesn't allow users to access files outside # their mail directory anyway. #mail_chroot = # Enable mail process debugging. This can help you figure out why Dovecot # isn't finding your mails. mail_debug = yes # Default MAIL environment to use when it's not set. By leaving this empty # dovecot tries to do some automatic detection as described in # /usr/share/doc/dovecot-common/mail-storages.txt. There's a few special # variables you can use, eg.: # # %u - username # %n - user part in user@domain, same as %u if there's no domain # %d - domain part in user@domain, empty if there's no domain # %h - home directory # # See /usr/share/doc/dovecot-common/variables.txt for full list. Some examples: # # default_mail_env = maildir:/var/mail/%1u/%u/Maildir # default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u # default_mail_env = mbox:/var/mail/%d/%n/:INDEX=/var/indexes/%d/%n # default_mail_env = maildir:/home/virtual_mail/%u # If you need to set multiple mailbox locations or want to change default # namespace settings, you can do it by defining namespace sections: # # You can have private, shared and public namespaces. The only difference # between them is how Dovecot announces them to client via NAMESPACE # extension. Shared namespaces are meant for user-owned mailboxes which are # shared to other users, while public namespaces are for more globally # accessible mailboxes. # # REMEMBER: If you add any namespaces, the default namespace must be added # explicitly, ie. default_mail_env does nothing unless you have a namespace # without a location setting. Default namespace is simply done by having a # namespace with empty prefix. namespace private { separator = prefix = INBOX. inbox = no hidden = no } namespace private { separator = / prefix = INBOX/ inbox = no hidden = yes } namespace private { separator = . prefix = INBOX. inbox = yes hidden = yes } #namespace private { # Hierarchy separator to use. You should use the same separator for all # namespaces or some clients get confused. '/' is usually a good one. # separator = / # Prefix required to access this namespace. This needs to be different for # all namespaces. For example "Public/". # prefix = INBOX/ # prefix = # Physical location of the mailbox. This is in same format as # default_mail_env, which is also the default for it. #location = # There can be only one INBOX, and this setting defines which namespace # has it. # inbox = no # If namespace is hidden, it's not advertised to clients via NAMESPACE # extension or shown in LIST replies. This is mostly useful when converting # from another server with different namespaces which you want to depricate # but still keep working. For example you can create hidden namespaces with # prefixes "~/mail/", "~%u/mail/" and "mail/". # hidden = yes #} # Space-separated list of fields to initially save into cache file. Currently # these fields are allowed: # Space-separated list of fields to initially save into cache file. Currently # these fields are allowed: # # flags, date.sent, date.received, size.virtual, size.physical # mime.parts, imap.body, imap.bodystructure # # Different IMAP clients work in different ways, so they benefit from # different cached fields. Some do not benefit from them at all. Caching more # than necessary generates useless disk I/O, so you don't want to do that # either. # # Dovecot attempts to automatically figure out what client wants and it keeps # only that. However the first few times a mailbox is opened, Dovecot hasn't # yet figured out what client needs, so it may not perform optimally. If you # know what fields the majority of your clients need, it may be useful to set # these fields by hand. If client doesn't actually use them, Dovecot will # eventually drop them. # # Usually you should just leave this field alone. The potential benefits are # typically unnoticeable. #mail_cache_fields = # Space-separated list of fields that Dovecot should never save to cache file. # Useful if you want to save disk space at the cost of more I/O when the fields # needed. #mail_never_cache_fields = # The minimum number of mails in a mailbox before updates are done to cache # file. This allows optimizing Dovecot's behavior to do less disk writes at # the cost of more disk reads. #mail_cache_min_mail_count = 0 # When IDLE command is running, mailbox is checked once in a while to see if # there are any new mails or other changes. This setting defines the minimum # time to wait between those checks. Dovecot is however able to use dnotify # and inotify with Linux to reply immediately after the change occurs. #mailbox_idle_check_interval = 30 # Allow full filesystem access to clients. There's no access checks other than # what the operating system does for the active UID/GID. It works with both # maildir and mboxes, allowing you to prefix mailboxes names with eg. /path/ # or ~user/. #mail_full_filesystem_access = no # Maximum allowed length for mail keyword name. It's only forced when trying # to create new keywords. #mail_max_keyword_length = 50 # Save mails with CR+LF instead of plain LF. This makes sending those mails # take less CPU, especially with sendfile() syscall with Linux and FreeBSD. # But it also creates a bit more disk I/O which may just make it slower. # Also note that if other software reads the mboxes/maildirs, they may handle # the extra CRs wrong and cause problems. #mail_save_crlf = no # Use mmap() instead of read() to read mail files. read() seems to be a bit # faster with my Linux/x86 and it's better with NFS, so that's the default. # Note that OpenBSD 3.3 and older don't work right with mail_read_mmaped = yes. #mail_read_mmaped = no # Don't use mmap() at all. This is required if you store indexes in remote # filesystems (NFS or clustered filesystem). #mmap_disable = no # Don't write() to mmaped files. This is required for some operating systems # which use separate caches for them, such as OpenBSD. #mmap_no_write = no # Locking method for index files. Alternatives are fcntl, flock and dotlock. # Dotlocking uses some tricks which may create more disk I/O than other locking # methods. NOTE: If you use NFS, remember to change also mmap_disable setting! # Solaris doesn't support flock, so Solaris users need to change this to fcntl. #lock_method = flock # By default LIST command returns all entries in maildir beginning with dot. # Enabling this option makes Dovecot return only entries which are directories. # This is done by stat()ing each entry, so it causes more disk I/O. # (For systems setting struct dirent->d_type, this check is free and it's # done always regardless of this setting) #maildir_stat_dirs = no # Copy mail to another folders using hard links. This is much faster than # actually copying the file. This is problematic only if something modifies # the mail in one folder but doesn't want it modified in the others. I don't # know any MUA which would modify mail files directly. IMAP protocol also # requires that the mails don't change, so it would be problematic in any case. # If you care about performance, enable it. #maildir_copy_with_hardlinks = no # Which locking methods to use for locking mbox. There's four available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory. # fcntl : Use this if possible. Works with NFS too if lockd is used. # flock : May not exist in all systems. Doesn't work with NFS. # lockf : May not exist in all systems. Doesn't work with NFS. # # You can use multiple locking methods; if you do the order they're declared # in is important to avoid deadlocks if other MTAs/MUAs are using multiple # locking methods as well. Some operating systems don't allow using some of # them simultaneously. #mbox_read_locks = fcntl #mbox_write_locks = dotlock fcntl # Maximum time in seconds to wait for lock (all of them) before aborting. #mbox_lock_timeout = 300 # If dotlock exists but the mailbox isn't modified in any way, override the # lock file after this many seconds. #mbox_dotlock_change_timeout = 30 # When mbox changes unexpectedly we have to fully read it to find out what # changed. If the mbox is large this can take a long time. Since the change # is usually just a newly appended mail, it'd be faster to simply read the # new mails. If this setting is enabled, Dovecot does this but still safely # fallbacks to re-reading the whole mbox file whenever something in mbox isn't # how it's expected to be. The only real downside to this setting is that if # some other MUA changes message flags, Dovecot doesn't notice it immediately. # Note that a full sync is done with SELECT, EXAMINE, EXPUNGE and CHECK # commands. #mbox_dirty_syncs = yes # Like mbox_dirty_syncs, but don't do full syncs even with SELECT, EXAMINE, # EXPUNGE or CHECK commands. If this is set, mbox_dirty_syncs is ignored. #mbox_very_dirty_syncs = no # Delay writing mbox headers until doing a full write sync (EXPUNGE and CHECK # commands and when closing the mailbox). This is especially useful for POP3 # where clients often delete all mails. The downside is that our changes # aren't immediately visible to other MUAs. #mbox_lazy_writes = yes # If mbox size is smaller than this (in kilobytes), don't write index files. # If an index file already exists it's still read, just not updated. #mbox_min_index_size = 0 # Maximum dbox file size in kilobytes until it's rotated. #dbox_rotate_size = 2048 # Minimum dbox file size in kilobytes before it's rotated # (overrides dbox_rotate_days) #dbox_rotate_min_size = 16 # Maximum dbox file age in days until it's rotated. Day always begins from # midnight, so 1 = today, 2 = yesterday, etc. 0 = check disabled. #dbox_rotate_days = 0 # umask to use for mail files and directories #umask = 0077 # Drop all privileges before exec()ing the mail process. This is mostly # meant for debugging, otherwise you don't get core dumps. It could be a small # security risk if you use single UID for multiple users, as the users could # ptrace() each others processes then. #mail_drop_priv_before_exec = no # Set max. process size in megabytes. Most of the memory goes to mmap()ing # files, so it shouldn't harm much even if this limit is set pretty high. #mail_process_size = 256 # Log prefix for mail processes. See # /usr/share/doc/dovecot-common/variables.txt for list of possible variables #you can use. #mail_log_prefix = "%Us(%u): " ## ## IMAP specific settings ## protocol imap { # Login executable location. #login_executable = /usr/lib/dovecot/imap-login # IMAP executable location. Changing this allows you to execute other # binaries before the imap process is executed. # # This would write rawlogs into ~/dovecot.rawlog/ directory: # mail_executable = /usr/lib/dovecot/rawlog /usr/lib/dovecot/imap # # This would attach gdb into the imap process and write backtraces into # /tmp/gdbhelper.* files: # mail_executable = /usr/lib/dovecot/gdbhelper /usr/lib/dovecot/imap # #mail_executable = /usr/lib/dovecot/imap # Maximum IMAP command line length in bytes. Some clients generate very long # command lines with huge mailboxes, so you may need to raise this if you get # "Too long argument" or "IMAP command line too large" errors often. #imap_max_line_length = 65536 # Support for dynamically loadable modules. #mail_use_modules = no #mail_modules = /usr/lib/dovecot/modules/imap # Send IMAP capabilities in greeting message. This makes it unnecessary for # clients to request it with CAPABILITY command, so it saves one round-trip. # Many clients however don't understand it and ask the CAPABILITY anyway. #login_greeting_capability = no # Workarounds for various client bugs: # delay-newmail: # Send EXISTS/RECENT new mail notifications only when replying to NOOP # and CHECK commands. Some clients ignore them otherwise, for example # OSX Mail. Outlook Express breaks more badly though, without this it # may show user "Message no longer in server" errors. Note that OE6 still # breaks even with this workaround if synchronization is set to # "Headers Only". # outlook-idle: # Outlook and Outlook Express never abort IDLE command, so if no mail # arrives in half a hour, Dovecot closes the connection. This is still # fine, except Outlook doesn't connect back so you don't see if new mail # arrives. # netscape-eoh: # Netscape 4.x breaks if message headers don't end with the empty "end of # headers" line. Normally all messages have this, but setting this # workaround makes sure that Netscape never breaks by adding the line if # it doesn't exist. This is done only for FETCH BODY[HEADER.FIELDS..] # commands. Note that RFC says this shouldn't be done. # tb-extra-mailbox-sep: # With mbox storage a mailbox can contain either mails or submailboxes, # but not both. Thunderbird separates these two by forcing server to # accept '/' suffix in mailbox names in subscriptions list. # The list is space-separated. #imap_client_workarounds = outlook-idle } ## ## POP3 specific settings ## protocol pop3 { # Login executable location. #login_executable = /usr/lib/dovecot/pop3-login # POP3 executable location #mail_executable = /usr/lib/dovecot/pop3 # Don't try to set mails non-recent or seen with POP3 sessions. This is # mostly intended to reduce disk I/O. With maildir it doesn't move files # from new/ to cur/, with mbox it doesn't write Status-header. #pop3_no_flag_updates = no # Support LAST command which exists in old POP3 specs, but has been removed # from new ones. Some clients still wish to use this though. Enabling this # makes RSET command clear all \Seen flags from messages. #pop3_enable_last = no # POP3 UIDL format to use. You can use following variables: # # %v - Mailbox UIDVALIDITY # %u - Mail UID # %m - MD5 sum of the mailbox headers in hex (mbox only) # %f - filename (maildir only) # # If you want UIDL compatibility with other POP3 servers, use: # UW's ipop3d : %08Xv%08Xu # Courier version 0 : %f # Courier version 1 : %u # Courier version 2 : %v-%u # Cyrus (<= 2.1.3) : %u # Cyrus (>= 2.1.4) : %v.%u # Older Dovecots : %v.%u # # Note that Outlook 2003 seems to have problems with %v.%u format which was # Dovecot's default, so if you're building a new server it would be a good # idea to change this. %08Xu%08Xv should be pretty fail-safe. # # NOTE: Nowadays this is required to be set explicitly, since the old # default was bad but it couldn't be changed without breaking existing # installations. %08Xu%08Xv will be the new default, so use it for new # installations. # pop3_uidl_format = UID%u-%v # POP3 logout format string: # %t - number of TOP commands # %T - number of bytes sent to client as a result of TOP command # %r - number of RETR commands # %R - number of bytes sent to client as a result of RETR command # %d - number of deleted messages # %m - number of messages (before deletion) # %s - mailbox size in bytes (before deletion) #pop3_logout_format = top=%t/%T, retr=%r/%R, del=%d/%m, size=%s # Support for dynamically loadable modules. #mail_use_modules = no #mail_modules = /usr/lib/dovecot/modules/pop3 # Workarounds for various client bugs: # outlook-no-nuls: # Outlook and Outlook Express hang if mails contain NUL characters. # This setting replaces them with 0x80 character. # oe-ns-eoh: # Outlook Express and Netscape Mail breaks if end of headers-line is # missing. This option simply sends it if it's missing. # The list is space-separated. #pop3_client_workarounds = } ## ## dovecot-lda specific settings ## # protocol lda { # If you wish to use plugins you need to specify plugin directory # For example quota enforcing is implemented by plugin #module_dir = /usr/local/lib/dovecot/lda # Address from LDA should send MDNs like out of quota # postmaster_address = postmaster(a)your.dom # If there is no user-specific Sieve-script, global Sieve script is # executed if set. #global_script_path = # UNIX socket path to master authentication server to find users. #auth_socket_path = /var/run/dovecot-auth-master # } ## ## Authentication processes ## # Executable location #auth_executable = /usr/lib/dovecot/dovecot-auth # Set max. process size in megabytes. #auth_process_size = 256 # Authentication cache size in kilobytes. 0 means it's disabled. # Note that bsdauth, PAM and vpopmail require cache_key to be set for caching # to be used. Also note that currently auth cache doesn't work very well if # you're using multiple passdbs with same usernames in them. #auth_cache_size = 0 # Time to live in seconds for cached data. After this many seconds the cached # record is no longer used, *except* if the main database lookup returns # internal failure. #auth_cache_ttl = 3600 # Space separated list of realms for SASL authentication mechanisms that need # them. You can leave it empty if you don't want to support multiple realms. # Many clients simply use the first one listed here, so keep the default realm # first. #auth_realms = # Default realm/domain to use if none was specified. This is used for both # SASL realms and appending @domain to username in plaintext logins. #auth_default_realm = # List of allowed characters in username. If the user-given username contains # a character not listed in here, the login automatically fails. This is just # an extra check to make sure user can't exploit any potential quote escaping # vulnerabilities with SQL/LDAP databases. If you want to allow all characters, # set this value to empty. #auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ # Username character translations before it's looked up from databases. The # value contains series of from -> to characters. For example "#@/@" means # that '#' and '/' characters are translated to '@'. #auth_username_translation = # Username to use for users logging in with ANONYMOUS SASL mechanism #auth_anonymous_username = anonymous # More verbose logging. Useful for figuring out why authentication isn't # working. auth_verbose = no # Even more verbose logging for debugging purposes. Shows for example SQL # queries. auth_debug = no # In case of password mismatches, log the passwords and used scheme so the # problem can be debugged. Requires auth_debug=yes to be set. #auth_debug_passwords = no # Maximum number of dovecot-auth worker processes. They're used to execute # blocking passdb and userdb queries (eg. MySQL and PAM). They're # automatically created and destroyed as needed. #auth_worker_max_count = 30 # Kerberos keytab to use for the GSSAPI mechanism. Will use the system # default (usually /etc/krb5.keytab) if not specified. #auth_krb5_keytab = auth default { # Space separated list of wanted authentication mechanisms: # plain digest-md5 cram-md5 apop anonymous gssapi # mechanisms = plain userdb static { args = uid=1002 gid=1002 home=/home/virtual_mail/%u } # passdb passwd-file { # args = /etc/passwd # } ## ## dovecot-lda specific settings ## # socket listen { # master { # path = /var/run/dovecot-auth-master # mode = 0600 # user = vmail # User running Dovecot LDA # #group = mail # Or alternatively mode 0660 + LDA user in this group # } # } # # Password database is used to verify user's password (and nothing more). # You can have multiple passdbs and userdbs. This is useful if you want to # allow both system users (/etc/passwd) and virtual users to login without # duplicating the system users into virtual database. # # http://wiki.dovecot.org/Authentication # # Users can be temporarily disabled by adding a passdb with deny=yes. # If the user is found from that database, authentication will fail. # The deny passdb should always be specified before others, so it gets # checked first. Here's an example: #passdb passwd-file { # File contains a list of usernames, one per line #args = /etc/dovecot.deny #deny = yes #} # PAM authentication. Preferred nowadays by most systems. # Note that PAM can only be used to verify if user's password is correct, # so it can't be used as userdb. If you don't want to use a separate user # database (passwd usually), you can use static userdb. # passdb pam { # [session=yes] [cache_key=<key>] [<service name>] # # session=yes makes Dovecot open and immediately close PAM session. Some # PAM plugins need this to work, such as pam_mkhomedir. # # cache_key can be used to enable authentication caching for PAM # (auth_cache_size also needs to be set). It isn't enabled by default # because PAM modules can do all kinds of checks besides checking password, # such as checking IP address. Dovecot can't know about these checks # without some help. cache_key is simply a list of variables (see # /usr/share/doc/dovecot-common/variables.txt) which must match for the # cached data to be used. # Here are some examples: # %u - Username must match. Probably sufficient for most uses. # %u%r - Username and remote IP address must match. # %u%s - Username and service (ie. IMAP, POP3) must match. # # If service name is "*", it means the authenticating service name # is used, eg. pop3 or imap. # # Some examples: # args = session=yes * # args = cache_key=%u dovecot #args = dovecot # } # /etc/passwd or similar, using getpwnam() # In many systems nowadays this uses Name Service Switch, which is # configured in /etc/nsswitch.conf. # passdb passwd { # } # /etc/shadow or similiar, using getspnam(). Deprecated by PAM nowadays. #passdb shadow { #} # BSD authentication. Used by at least OpenBSD. #passdb bsdauth { # [cache_key=<key>] - See cache_key in PAM for explanation. #args = #} # passwd-like file with specified location #passdb passwd-file { # Path for passwd-file #args = #} # checkpassword executable authentication # NOTE: You will probably want to use "userdb prefetch" with this. #passdb checkpassword { # Path for checkpassword binary #args = #} # SQL database passdb sql { # Path for SQL configuration file, see /etc/dovecot/dovecot-sql.conf for # example args = /etc/dovecot/dovecot-sql.conf } # LDAP database #passdb ldap { # Path for LDAP configuration file, see /etc/dovecot/dovecot-ldap.conf for # example #args = #} # vpopmail authentication #passdb vpopmail { # [cache_key=<key>] - See cache_key in PAM for explanation. #args = #} # # User database specifies where mails are located and what user/group IDs # own them. For single-UID configuration use "static". # # http://wiki.dovecot.org/Authentication # http://wiki.dovecot.org/VirtualUsers # # /etc/passwd or similar, using getpwnam() # In many systems nowadays this uses Name Service Switch, which is # configured in /etc/nsswitch.conf. userdb passwd { } # passwd-like file with specified location #userdb passwd-file { # Path for passwd-file #args = #} # static settings generated from template #userdb static { # Template for settings. Can return anything a userdb could normally # return, eg.: uid, gid, home, mail, nice # # A few examples: # # args = uid=500 gid=500 home=/var/mail/%u # args = uid=500 gid=500 home=/home/%u mail=mbox:/home/%u/mail nice=10 # #args = #} # SQL database userdb sql { # Path for SQL configuration file, see /etc/dovecot/dovecot-sql.conf for # example args = /etc/dovecot/dovecot-sql.conf } # LDAP database #userdb ldap { # Path for LDAP configuration file, see /etc/dovecot/dovecot-ldap.conf for # example #args = #} # vpopmail #userdb vpopmail { #} # "prefetch" user database means that the passdb already provided the # needed information and there's no need to do a separate userdb lookup. # This can be made to work with SQL and LDAP databases, see their example # configuration files for more information how to do it. # http://wiki.dovecot.org/AuthSpecials #userdb prefetch { #} # User to use for the process. This user needs access to only user and # password databases, nothing else. Only shadow and pam authentication # requires roots, so use something else if possible. Note that passwd # authentication with BSDs internally accesses shadow files, which also # requires roots. Note that this user is NOT used to access mails. # That user is specified by userdb above. user = root # Directory where to chroot the process. Most authentication backends don't # work if this is set, and there's no point chrooting if auth_user is root. # Note that valid_chroot_dirs isn't needed to use this setting. #chroot = # Number of authentication processes to create #count = 1 # Require a valid SSL client certificate or the authentication fails. #ssl_require_client_cert = no # Take the username from client's SSL certificate, using X509_NAME_oneline() # which typically uses subject's Distinguished Name. #ssl_username_from_cert = no } # It's possible to export the authentication interface to other programs, # for example SMTP server which supports talking to Dovecot. Client socket # handles the actual authentication - you give it a username and password # and it returns OK or failure. So it's pretty safe to allow anyone access to # it. Master socket is used to a) query if given client was successfully # authenticated, b) userdb lookups. # listener sockets will be created by Dovecot's master process using the # settings given inside the auth section #auth default_with_listener { # mechanisms = plain # passdb pam { # } # userdb passwd { # } # socket listen { # master { # path = /var/run/dovecot-auth-master # # WARNING: Giving untrusted users access to master socket may be a # # security risk, don't give too wide permissions to it! # #mode = 0600 # # Default user/group is the one who started dovecot-auth (root) # #user = # #group = # } # client { # path = /var/run/dovecot-auth-client # mode = 0660 # } # } #} # connect sockets are assumed to be already running, Dovecot's master # process only tries to connect to them. They don't need any other settings # than path for the master socket, as the configuration is done elsewhere. # Note that the client sockets must exist in login_dir. #auth external { # socket connect { # master { # path = /var/run/dovecot-auth-master # } # } #} plugin { # Here you can give some extra environment variables to mail processes. # This is mostly meant for passing parameters to plugins. %variable # expansion is done for all values. # Quota plugin #quota = dirsize:%h/mail # Convert plugin. If set, specifies the source storage path which is # converted to destination storage (default_mail_env). #convert_mail = mbox:%h/mail } [View Less]

2 1

[Dovecot] Migration from tpop3d to dovecot - troubles galore!
by Odhiambo WASHINGTON 29 May '07

29 May '07

Hi people, I am trying to migrate some users from tpop3d (Maildir mailboxes) to dovecot. The most important aspect of this migration, and which I cannot seem to get right, is to first be able to make dovecot to authenticate against the current DB being used by tpop3d so that I can use imapsync to transfer the user mails. And I do believe that is what I am unable to get right!! So here goes what I have tried so far: Take a case of one username, eddie, who belongs to the domain, demo.… [View More]wananchi.com. 1. This query is what I am using for password_query. I do suspect it is wrong, but well, this is what it yields from the current DB: mysql> SELECT CONCAT(domain.path, '/', popbox.mbox_name), popbox.password_hash FROM popbox, domain WHERE popbox.local_part = 'eddie' AND popbox. domain_name = 'demo.wananchi.com' AND popbox.domain_name = domain.domain_name; +--------------------------------------------+---------------------------------------+ | CONCAT(domain.path, '/', popbox.mbox_name) | password_hash | +--------------------------------------------+---------------------------------------+ | /var/spool/virtual/demo.wananchi.com/eddie | {md5}897fad9cbef974ff95254417234ff1df | +--------------------------------------------+---------------------------------------+ 2. This is what I use for user_query and the result: mysql> SELECT CONCAT(domain.path, '/', popbox.mbox_name) as home, 6 as uid, 6 as gid FROM popbox, domain WHERE popbox.local_part = 'eddie' AND popbox.domain_name = 'demo.wananchi.com' AND popbox.domain_name = domain.domain_name; +-------------------------------------------------+-----+-----+ | home | uid | gid | +-------------------------------------------------+-----+-----+ | /var/spool/virtual/nyerimunicipal.co.ke/eddie | 6 | 6 | +-------------------------------------------------+-----+-----+ 3. Getting a typical user would need this query, for example: mysql> select CONCAT(local_part,'\@',domain_name) as user from popbox limit 10; +-------------------------+ | user | +-------------------------+ | eddie(a)demo.wananchi.com | +-------------------------+ 4. My tables, and the data they contain: (a) mysql> desc popbox; +----------------+--------------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +----------------+--------------+------+-----+---------+-------+ | domain_name | varchar(255) | | PRI | | | | local_part | varchar(255) | | PRI | | | | password_hash | varchar(255) | YES | | NULL | | | mbox_name | varchar(255) | YES | | NULL | | | password_hash2 | varchar(255) | YES | | NULL | | +----------------+--------------+------+-----+---------+-------+ (b) mysql> select * from popbox limit 1; +-------------------+------------+---------------------------------------+-----------+----------------+ | domain_name | local_part | password_hash | mbox_name | password_hash2 | +-------------------+------------+---------------------------------------+-----------+----------------+ | demo.wananchi.com | eddie | {md5}7bb1be8a78498a9de40098a593199819 | eddie | 9IYjWHc4Cs9/w | +-------------------+------------+---------------------------------------+-----------+----------------+ PS: Not all users have password_hash2, which I think is Unix crypt!!! (c) mysql> desc domain; +---------------+--------------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +---------------+--------------+------+-----+---------+-------+ | domain_name | varchar(255) | | PRI | | | | unix_user | varchar(255) | YES | | NULL | | | password_hash | varchar(255) | YES | | NULL | | | path | varchar(255) | YES | | NULL | | | max_popbox | int(11) | YES | | NULL | | +---------------+--------------+------+-----+---------+-------+ (d) mysql> select * from domain limit 1; +--------------+-----------+---------------------------------------+--------------------------------------+-----------------+ | domain_name | unix_user | password_hash | path | max_popbox | +--------------+-----------+---------------------------------------+--------------------------------------+-----------------+ | dlsnovit.org | exim | {md5}d108219901e577db69c249645ae3a49f | /var/spool/virtual/demo.wananchi.com | 5 | +--------------+-----------+---------------------------------------+--------------------------------------+-----------------+ [root@ns2]#less /var/log/dovecot.log dovecot: May 29 17:42:57 Warning: Killed with signal 15 dovecot: May 29 17:42:59 Info: Dovecot v1.0.0 starting up dovecot: May 29 17:42:59 Info: auth-worker(default): mysql: Connected to localhost (virtualemail) dovecot: May 29 17:44:02 Info: auth(default): client in: AUTH 1 PLAIN service=POP3 secured lip=62.8.64.4 rip=62.8.64.4 resp=AGVk ZGllQGRlbW8ud2FuYW5jaGkuY29tAGJvZWluZzg= dovecot: May 29 17:44:02 Info: auth-worker(default): sql(eddie(a)demo.wananchi.com,62.8.64.4): query: SELECT CONCAT(domain.path, '/', popbox.mbox_n ame), popbox.password_hash FROM popbox, domain WHERE popbox.local_part = 'eddie' AND popbox.domain_name = 'demo.wananchi.com' AND popbox.domain_n ame = domain.domain_name dovecot: May 29 17:44:02 Error: child 40402 (auth-worker) killed with signal 11 dovecot: May 29 17:44:03 Info: auth(default): client out: FAIL 1 user=eddie(a)demo.wananchi.com temp dovecot: May 29 17:44:05 Info: pop3-login: Aborted login: user=<eddie(a)demo.wananchi.com>, method=PLAIN, rip=62.8.64.4, lip=62.8.64.4, secured o That password_hash - is it usable at all with dovecot? o Could password_hash2 be used? I could popolate the table with a known value and use it, just for imapsync to complete!! o What default_pass_scheme should I use in my userdb configuration? I'll very much appreciate help on this. I am currently testing with pop3, but once I get successful authentication, I will switch to imap for imapsync. Thanks for your time, and help, and advise:-) -Wash http://www.netmeister.org/news/learn2quote.html DISCLAIMER: See http://www.wananchi.com/bms/terms.php -- +======================================================================+ |\ _,,,---,,_ | Odhiambo Washington <wash(a)wananchi.com> Zzz /,`.-'`' -. ;-;;,_ | Wananchi Online Ltd. www.wananchi.com |,4- ) )-,_. ,\ ( `'-'| Tel: +254 20 313985-9 +254 20 313922 '---''(_/--' `-'\_) | GSM: +254 722 743223 +254 733 744121 +======================================================================+ One, with God, is always a majority, but many a martyr has been burned at the stake while the votes were being counted. -- Thomas B. Reed [View Less]

1 0

[Dovecot] About create mailbox by dovecot
by gaoqiang.qian＠nokia.com 29 May '07

29 May '07

Hi, I am a beginner of Dovecot. Actually I have just used yum install dovecot in my red hat linux host server. Could anyone tell me how can I start to use the dovecot to create a mailbox in my domain name. It seems there are lots of documents in the homepage of dovecot, but I do not know which one is the one specifically start to create mailbox. Thanks Qiang

1 0

[Dovecot] Stop Maildir appending to path
by Henry 28 May '07

28 May '07

Dovecot is working perfectly except for one problem. I have local users and virtual users. Local users are ~/Maildir. And virtual users are /home/vmail/domain/user. The problem is, it keeps trying to fetch virtual mail at /home/vmail/domain/user/Maildir. It doesn't exist the user/ dir is the Maildir. To get around this, I have to make symlinks on each virtual email. What should I check? How do I make it stop appending Maildir to my virtual users path? If I set mail_location to the … [View More]

2 1

[Dovecot] IMAP Bandwidth Monitoring
by Phillip T. George 28 May '07

28 May '07

Hello all, I'm wanting to set up IMAP bandwidth monitoring, but I don't see any IMAP size transfer entries in the log file. How would I turn this on? Please refer me to the manual if I've somehow missed it :) Thanks, Phillip

2 1

[Dovecot] IMAP basics
by Paul Scott 28 May '07

28 May '07

I have several POP mail accounts. I have installed and partially configured Dovecot 1.0.0 on Debian sid. I am having trouble understanding some of the basics. For starters do I need to fetch my POP mail (fetchmail, etc.) myself? TIA, Paul Scott

2 1

[Dovecot] Variable expansion in LDA vs POP/IMAP
by Stephane Enten 27 May '07

27 May '07

Hello all, I'm trying to understand when exactly the variable substitution happens in Dovecot, as I get different results in the LDA and in the POP/IMAP server. Here's my general setup: - Postfix MTA, delivers mail via Dovecot LDA - users list sits in a database - mail directory is stored in the database, but with Dovecot variables inside Delivery works perfectly fine, Dovecot's deliver get a "mail" column from the database (that looks like this: /mail/01/%2LMd/%2.2LMd/%LMd/mail/%Ln/… [View More]

3 4

[Dovecot] UID confusion
by Kevin 27 May '07

27 May '07

I have just finished reading the info on the wiki on setting up virtual users with Dovecot and Postfix. http://wiki.dovecot.org/DovecotLDAPostfixAdminMySQL I'm confused about the UID and GID's. In the docs it shows a user, vmail being created with a UID of 101. Then it looks like GID 12 is used for Postfix or Mail. I'm not sure which it is and would like to know. Bulldozer

2 1

Re: [Dovecot] question mailbox format
by sc2＠gmx.at 27 May '07

27 May '07

ok after playing a while now it works , but i have one problem open.. a.) now he makes for pop3 index files in /var/indexes/%u/imap/index etc... you said that is correct too if i only use pop3 ? b.) i have as INBOX file /var/spool/mail/%u set, when somebody logs in, and the mailbox exist he gets the email (from mbox file), but when the mbox does not exist he makes a directory, instead of a file like /var/spool/mail/%u. The problem is when a new mail comes and the mbox file does not exist, … [View More]

4 7