- dovecot - dovecot.org

[Dovecot] Automatic Debian packages for Dovecot v2.2.
by Stephan Bosch 19 Feb '12

19 Feb '12

Hi, For our testing enthusiasts I've created new automatic Debian repositories for Dovecot v2.2. Repositories are available for Debian oldstable, stable and testing, on both i386 and am64. Read the following wiki item for more information: http://wiki2.dovecot.org/PrebuiltBinaries#Automatically_Built_Packages The repository for Dovecot v1.2 has been defunct for a few months now and is expected to be removed soon. For the coming month or so, the builders at Xi will not be active during Dutch daytime. There are some issues with the virtual host's I/O performance that need to be resolved first. Regards, Stephan.

2 1

[Dovecot] I'm confused about my namespace parms
by Steve Campbell 19 Feb '12

19 Feb '12

Hi, I'm new to the list and to dovecot. I'm having a strange situation that provides no errors, so I'm having a little problem diagnosing what's going on. I've been running a Centos 3 mail server with sendmail for our company for quite a few years. I finally got approval for new servers this year and put Centos 6.2 on it. I'm sticking with sendmail, but that's not important. Up to this point, I've got all working fairly well. I've found that if I configure dovecot to use the mixed format (pop and imap INBOX in /var/spool/mail, Imap folders in /home/user/mail, two namespaces) as in the examples for "namespace", most works fine. Anyone who has used imap previously on our old system and work as if nothing has changed. Anyone who has never used Imap before can't seem to access the server using our webmail app (Horde/Imp). Dovecot is providing both pop and imap. An account that is set up from a normal mail client as imap has no problems as well. Sendmail is set up to create a new user in the /var/spool/mail folder. When I moved from the old server to the new server, I copied /home and /var/spool/mail to the new server - in other words, I kept the same scheme. There are no errors in the maillog, and it indicates that the user is getting logged in and out, but the return to Horde is that the user entered the wrong name or password. I'm thinking that this is probably due to how dovecot is trying to look for the imap folders, but the lack or any errors makes it a little difficult to diagnose. I'm fairly certain that what was installed on the old server was UW-Imap and was provided by the imap-2002 rpm. I tried using the examples for UW-Imap compatability but that didn't work at all. I haven't been able to figure out what's different about the old imap folder contents and what's missing in the newly created imap folders to allow Horde to access this account. I'll look at the Horde config to see if anything is there, but I'm cautious about changing anything that might break the current users' ability. Most of the accounts are set up as POP with the ability to see what's left on the server using Horde, webmail, and IMAP. Any help in tracing this down would really help. I think my biggest problem is I don't understand the "namespace" parameter as well as I should. So there it is. It seems I've got at least 3 areas to concentrate on. Steve Campbell ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/

2 2

[Dovecot] Move templates args to override_fields setting?
by Ralf Hildebrandt 18 Feb '12

18 Feb '12

After upgrading from 2.0.x to 2.1.x I get a lot of: Feb 18 18:18:12 postamt dovecot: auth-worker(31443): Warning: userdb passwd: Move templates args to override_fields setting OK, it's just a warning, but how do I fix that in a 2.0.x compatible way? The only place userdb is used is in this contaxt: # for user*masteruser logins passdb { args = /usr/local/etc/dovecot/dovecot.masteruser driver = passwd-file master = yes } # User via passwd userdb { driver = passwd args = cache_key=%u } -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de

2 2

[Dovecot] expunging
by Micah Anderson 18 Feb '12

18 Feb '12

I am having trouble scaling some regular dovecot cleanup operations on our servers. On a daily basis, I'm wanting to do this on each server, which contains its own isolated set of user storage: /usr/bin/doveadm expunge -A mailbox Trash* savedbefore 21d /usr/bin/doveadm expunge -A mailbox Spam savedbefore 7d /usr/bin/doveadm expunge -A mailbox Sent savedbefore 120d but these are a very expensive operations. For example, just doing the Spam expunge takes 30 minutes (or more, depending on the load) of heavy disk operations, on each machine it is run on. There are approximately 20k users on each machine. It seems like it does not use the iterate query, but rather it looks into the database at the expires table and rather it iterates over every user mentioned there. This is a problem because I've got multiple dovecot machines with different sets of users on them, using the same table, so that means that its doing stat() calls on each system for every user mentioned there and failing to find the user on the filesystem (because the user is on another system). In these cases it spits out an error: doveadm(user): Info: User no longer exists, skipping For users that do exist on this system, it seems to do something on the order of 15 stat() calls, at minimum. What are some things I can do to make this less of an expensive process? If I had a shared storage system that each machine used, this would cut down on the resource waste because I'd only need to run the query once, but unfortuntely, that isn't how these systems were designed. thanks for any ideas, tips etc. micah

3 3

[Dovecot] Quota warnings and LMTP
by joshua＠hybrid.pl 18 Feb '12

18 Feb '12

Hello, I have dovecot 2.0 configured with virtual users in MySQL, SMTP is handled by exim which uses dovecot LMTP transport. I'd like to test quota warning messages, but in wiki2 there is only an example for delivering it with dovecot-lda. I tried several ways of using lmtp binary, but without success. How to replace this: cat << EOF | /usr/local/libexec/dovecot/dovecot-lda -d $USER -o "plugin/quota=maildir:User quota:noenforcing" From: postmaster(a)domain.com Subject: quota warning Your mailbox is now $PERCENT% full. EOF with lmtp? Greetings, -- Jacek Osiecki

3 2

[Dovecot] Order of operations in Dovecot
by Eric Gregory 18 Feb '12

18 Feb '12

Hi, I'm working on an IMAP client and had a question about the order in which commands are responded to in Dovecot. In other IMAP servers I've looked at, when you issue two commands simultaneously (i.e. pipelining) it looks something like this: a fetch something b fetch something else * 1 FETCH (result) a OK FETCH completed * 1 FETCH (result) b OK FETCH completed This works well because it's clear which results are associated with which tag; the 'a' fetch results immediately precede the a's OK response, and likewise the 'b' fetch results immediately precede the b's OK response. But in Dovecot (version 2.0.13) the results of the two simultaneous commands are ordered like this: a fetch something b fetch something else * 1 FETCH (result) * 1 FETCH (result) a OK FETCH completed b OK FETCH completed This makes associating the results of the fetch commands quite a bit more difficult, since it's not entirely clear which results are paired with which tag. My question is this: is this Dovecot's intended behavior, or did I find a bug? I realize the IMAP spec is really vague about this. If this is the intended behavior, is there any advice for clients on how to determine which results are associated with which command? Thanks! - Eric

2 1

[Dovecot] Upgraded to 2.1 - ulimit error
by Marc Perkel 17 Feb '12

17 Feb '12

Not sure what this means: Warning: fd limit (ulimit -n) is lower than required under max. load (4096 < 20000), because of service auth { client_limit } What do I need to do?

1 1

[Dovecot] Dovecot 2.1.0 packages for CentOS 6 / RHEL6
by Morten Stevens 17 Feb '12

17 Feb '12

Hi, First, Timo, Thank you for Dovecot 2.1.0. I've built Dovecot 2.1.0 RPMs including Dovecot-Pigeonhole 0.3.0 for RHEL6, CentOS 6 and Scientific Linux 6. If anyone is interested in testing these RPMs: http://oss.imt-systems.com/mstevens/el6/dovecot/2.1.0/ Feedback would be appreciated. After some testing, we will use these RPMs on our IMAP servers. Best regards, Morten

2 2

[Dovecot] Dovecot lda parameters
by Клименко Николай 17 Feb '12

17 Feb '12

hi all I have the following scheme. Postfix with virtual users with dovecot LDA. AD as database. Dovecot and Postfix get the following Idap attributes from AD: sAMAccountName, mail and mail_alias. The problem is that I can’t make dovecot lda move the user’s mail to the folder with the name from sAMAccountName attribute, as mail always moves to folder with e-mail address name. Is it posible to delivery e-mail to folder with name from ldap attributes sAMAccountName? --

1 0

[Dovecot] Favorable mention in Linux Productivity Magazine
by Steve Litt 17 Feb '12

17 Feb '12

Hi all, The latest Linux Productivity Magazine, http://www.troubleshooters.com/lpm/201202/201202.htm, discusses the positive role Dovecot played in my migration away from Kmail. This is currently topical as Kmail is in the midst to transforming to Kmail2, which requires an Akonadi database and is not popular. I hope you enjoy the magazine. SteveT Steve Litt Troubleshooters.Com

1 0

[Dovecot] How to delete old mails in dovecot 1.2.x
by Przemysław Orzechowski 16 Feb '12

16 Feb '12

Hi I have already read this page but there is no info on how to delete old mails in dovecot 1.2 http://wiki1.dovecot.org/QuestionsAndAnswers#How_can_I_create_a_cron_or_som… I need to delete old mails from over 100 mailboxes with average of 10k mails / mailbox Is there a way to delete old mails (by message date not file creation date) as with doveadm in dovecot 2 ? Thanks in advance bellow my dovecot -n (not sure if it is neccessary or not so just in case) # 1.2.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-33-server x86_64 Ubuntu 10.04.3 LTS log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s ssl_cert_file: /etc/ssl/makolab/star_makolab_pl.crt ssl_key_file: /etc/ssl/makolab/star_makolab_pl.key disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login mail_privileged_group: mail mail_location: maildir:~/Maildir mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 auth default: passdb: driver: pam userdb: driver: passwd plugin: quota: fs:Limit uzytkownika:user quota2: fs:Limit domeny:group

3 4

[Dovecot] log message about client_limit may in fact be due to ulimit
by Christoph Bußenius 16 Feb '12

16 Feb '12

Hi, our Dovecot proxy started logging about reaching the client_limit once there were about 1000 connections running over it: Feb 14 15:22:02 vmmailproxy1 dovecot: master: Warning: service(anvil): client_limit (100000) reached, client connections are being dropped Feb 14 15:22:18 vmmailproxy1 dovecot: master: Warning: service(ipc): client_limit (100000) reached, client connections are being dropped I was a bit perplexed because 100.000 is far above 1000. However we found out that in fact the problem was the number of open files, and we have fixed it by putting 'ulimit -n 6000' into the init script. Even though the log claims that connections would be dropped, the number of imap-login processes kept rising above 1000. The "doveadm proxy list" would fail with an error message: $ sudo doveadm proxy list doveadm(root): Error: LIST failed: Disconnected Segmentation fault The segfault did not happen every time I tried it. I'm sorry I don't have any core dumps or backtraces, because I was more concerned about putting the proxy into a sane state. Maybe I can reproduce this on a test server if you would like a back trace. Anyway, I suggest changing the log message if the failure is not actually due to the client_limit. # 2.0.18: /etc/ports/dovecot/dovecot.conf # OS: Linux 2.6.32-38-server x86_64 Ubuntu 10.04.2 LTS auth_username_format = %n default_client_limit = 60000 default_process_limit = 10000 disable_plaintext_auth = no mail_location = maildir:/nonexistent managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave passdb { args = /etc/ports/dovecot/passwd driver = passwd-file } protocols = imap pop3 lmtp sieve service anvil { client_limit = 100000 } service auth { client_limit = 60000 } service ipc { client_limit = 100000 } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } shutdown_clients = no ssl_cert = </etc/ssl/certs/mailproxy+chain.pem ssl_key = </etc/ssl/private/mailproxy.key syslog_facility = local6 verbose_proctitle = yes protocol imap { imap_capability = IMAP4rev1 IDLE THREAD=REFERENCES SORT QUOTA ACL UIDPLUS } The passwd file has all entries looking like this: login:::::::proxy=y host=backend1 nopassword=yes -- Christoph Bußenius Rechnerbetriebsgruppe der Fakultäten Informatik und Mathematik Technische Universität München +49 89-289-18519 <> Raum 00.05.055 <> Boltzmannstr. 3 <> Garching

2 6

[Dovecot] Released Pigeonhole v0.3.0 for Dovecot v2.1.0
by Stephan Bosch 16 Feb '12

16 Feb '12

Hello Dovecot users, Now that Dovecot v2.1.0 is out there, I release Pigeonhole v0.3.0. The most significant new features are support for the Sieve editheader extension and the sieve-filter tool. I haven't received much feedback on these new features, which can either mean that they are mostly bug-free or that not many people have tried these, so these are still considered experimental. Changelog v0.3.0: * Renamed sieve_global_path setting to sieve_default for clarity. Old name is still recognized for backwards compatibility. Support for the ancient (pre v1.1) name for this setting "global_script_path" is now dropped. * Added means to prohibit use of redirect action. Setting sieve_max_redirects to 0 now means that redirect is disallowed in stead of unlimited. Default value remains four. * Fixed interaction of Sieve include extension with ManageSieve. It is updated to match new requirements in the draft include specification. Missing included scripts are no longer an error at upload time. * Updated RFC2822 header field body verification to exclude non-printing characters (RFC5322). Only Sieve actions that can create unstructured header values (currently enotify/mailto and editheader) are affected by this change. + Completed sieve-filter tool to a useful state. The sieve-filter tool provides a means to (re)filter messages in a mailbox through a Sieve script. + Implemented the Sieve editheader extension. It is now possible to add and remove message headers from within Sieve. + ManageSieve: added support for reading quoted and literal strings as a stream. Fixes support for handing large SASL responses (analogous to similar changes in Dovecot). It is now also allowed to use a quoted string for the PUTSCRIPT script argument. + Added code to cleanup tmp directory in Sieve storage directory (sieve_dir) every once in a while. + Added support for substituting the entire message during Sieve processing. This is used for the filter action provided by the new sieve_extprograms plugin (provided separately for now). The filter action allows passing the message through an external program. + Added support for restricting certain Sieve language extensions to (admin-controled) global scripts. Restricted extensions can be configured using the new sieve_global_extensions setting. This is particularly useful for some of the Dovecot-specific (plugin-based) Sieve extensions, that can be somewhat hazardous when under direct control of users (e.g. sieve_extprograms). The release is available as follows: http://www.rename-it.nl/dovecot/2.0/dovecot-2.1-pigeonhole-0.3.0.tar.gz http://www.rename-it.nl/dovecot/2.0/dovecot-2.1-pigeonhole-0.3.0.tar.gz.sig Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this new release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

2 2

[Dovecot] Dovecot v2.2 plans
by Timo Sirainen 16 Feb '12

16 Feb '12

Here's a list of things I've been thinking about implementing for Dovecot v2.2. Probably not all of them will make it, but I'm at least interested in working on these if I have time. Previously I've mostly been working on things that different companies were paying me to work on. This is the first time I have my own company, but the prioritization still works pretty much the same way: - 1. priority: If your company is highly interested in getting something implemented, we can do it as a project via my company. This guarantees that you'll get the feature implemented in a way that integrates well into your system. - 2. priority: Companies who have bought Dovecot support contract can let me know what they're interested in getting implemented. It's not a guarantee that it gets implemented, but it does affect my priorities. :) - 3. priority: Things other people want to get implemented. There are also a lot of other things I have to spend my time on, which are before the 2. priority above. I guess we'll see how things work out. dsync-based replication ----------------------- I'll write a separate post about this later. Besides, it's coming for Dovecot v2.1 so it's a bit off topic, but I thought I'd mention it anyway. Shared mailbox improvements --------------------------- Support for private flags for all mailbox formats: namespace { type = public prefix = Public/ mail_location = mdbox:/var/vmail/public:PVTINDEX=~/mdbox/indexes-public } - dsync needs to be able to replicate the private flags as well as shared flags. - might as well add a common way for all mailbox formats to specify which flags are shared and which aren't. $controldir/dovecot-flags would say which is the default (private or shared) and what flags/keywords are the opposite. - easy way to configure shared mailboxes to be accessed via imapc backend, which would allow easy shared mailbox accesses across servers or simply between two system users in same server. (this may be tricky to dsync.) - global ACLs read from a single file supporting wildcards, instead of multiple different files - default ACLs for each namespace/storage root (maybe implemented using the above..) Metadata / annotations ---------------------- Add support for server, mailbox and mail annotations. These need to be dsyncable, so their changes need to be stored in various .log files: 1. Per-server metadata. This is similar to subscriptions: Add changes to dovecot.mailbox.log file, with each entry name a hash of the metadata key that was changed. 2. Per-mailbox metadata. Changes to this belong inside mailbox_transaction_context, which write the changes to mailbox's dovecot.index.log files. Each log record contains a list of changed annotation keys. This gives each change a modseq, and also allows easily finding out what changes other clients have done, so if a client has done ENABLE METADATA Dovecot can easily push metadata changes to client by only reading the dovecot.index.log file. 3. Per-mail metadata. This is pretty much equivalent to per-mailbox metadata, except changes are associated to specific message UIDs. The permanent storage is in dict. The dict keys have components: - priv/ vs. shared/ for specifying private vs. shared metadata - server/ vs mailbox/<mailbox guid>/ vs. mail/<mailbox guid>/<uid> - the metadata key name This would be a good time to improve the dict configuration to allow things like: - mixed backends for different hierarchies (e.g. priv/mailbox/* goes to a file, while the rest goes to sql) - allow sql dict to be used in more relational way, so that mail annotations could be stored with tables: mailbox (id, guid) and mail_annotation (mailbox_id, key, value), i.e. avoid duplicating the guid everywhere. Things to think through: - How to handle quota? Probably needs to be different from regular mail quota. Probably some per-user "metadata quota bytes" counter/limit. - Dict lookups should be done asynchronously and prefetched as much as possible. For per-mail annotation lookups mail_alloc() needs to include a list of annotations that are wanted. Configuration ------------- Copy all mail settings to namespaces, so it'll be possible to use per-namespace mailbox settings. Especially important for imapc_* settings, but can be useful for others as well. Those settings that aren't explicitly defined in the namespace will use the global defaults. (Should doveconf -a show all of these values, or simply the explicitly set values?) Get rid of *.conf.ext files. Make everything part of dovecot.conf, so doveconf -n outputs ALL of the configuration. There are mainly 3 config files I'm thinking about: dict-sql, passdb/userdb sql, passdb/userdb ldap. The dict-sql is something I think needs a bigger redesign (mentioned above in "Metadata" section), but the sql/ldap auth configs could be merged. One way could be: sql_db sqlmails { # most settings from dovecot-sql.conf.ext, except for queries driver = mysql connect = ... } ldap_db ldapmails { # most settings from dovecot-ldap.conf.ext, except attributes/filters } passdb { driver = sql db = sqlmails sql_query = select password from users where username = '%u' } passdb { driver = ldap db = ldapmails ldap_attributes { password = %{ldap:userPassword} } ldap_filter = ... } The sql_db {} and ldap_db {} would be generic enough to be used everywhere (e.g. dict-sql), not just for passdb/userdb. Some problems: - Similar to the per-namespace mail settings, doveconf -a would output all sql_query, ldap_attributes, ldap_filter, etc. settings for all passdbs/userdbs. Perhaps a similar solution? - The database configs contain passwords, so they should be readable only by root. This makes running dovecot-lda and maybe doveadm difficult, since they fail at "permission denied" when trying to open the config. There are probably only two solutions: a) The db configs need to be !include_try'd or b) the configs can be world-readable, but only passwords are placed to only-root-readable files by using "password = <db.password" IMAP state saving/restoring --------------------------- IMAP connections are often long running. Problems with this: 1. Currently each connection requires a separate process (at least to work reliably), which means each connection also uses quite a lot of memory even when they aren't doing anything for a long time. 2. Some clients don't handle lost connections very nicely. So Dovecot can't be upgraded without causing some user annoyance. Also in a cluster if you want to bring down one server, the connections have to be disconnected before they can be moved to another server. If IMAP session state could be reliably saved and later restored to another process, both of the above problems could be avoided entirely. Typically when a connection is IDLEing there are really just 4 things that need to be remembered: username, selected mailbox name, its UIDVALIDITY and HIGHESTMODSEQ. With this information the IMAP session can be fully restored in another process without losing any state. So, what we could do is: 1. When an IMAP connection has bee IDLEing for a while (configurable initial time, could be dynamically adjusted): - move the IMAP state and the connection fd to imap-idle process - the old imap process is destroyed - imap-idle process can handle lots of IMAP connections - imap-idle process also uses inotify/etc. to watch for changes in the specified mailbox - if any mailbox changes happen or IMAP client sends a command, start up a new imap process, restore the state and continue from where we left off - This could save quite a lot of memory at the expense of some CPU usage 2. Dovecot proxy <-> backend protocol could be improved to support moving connection to another backend. Possibly using a separate control connection to avoid making the proxying less efficient in normal operation. 3. When restarting Dovecot, move all the connections to a process that keeps the connections open for a while. When Dovecot starts up, create imap processes back to the connections. This allows changing configuration for existing client connections (which sometimes may be bad! need to add checks against client-visible config conflicts), upgrading Dovecot, etc. without being visible to clients. The only problem is SSL connections: OpenSSL doens't provide a way to save/restore state, so either you need to set shutdown_clients=no (and possibly keep some imap-login processes doing SSL proxying for a long time), or SSL connections need to be killed. Of course the SSL handling could be outsourced to some other software/hardware outside Dovecot. The IMAP state saving isn't always easy. Initially it could be implemented only for the simple cases (which are a majority) and later extended to cover more. IMAP extensions --------------- - CATENATE is already implemented by Stephan - URLAUTH is also planned to be implemented, somewhat differently than in Apple's patch. The idea is to create a separate imap-urlauth service that provides extra security. - NOTIFY extension could be implemented efficiently using mailbox list indexes, which already exists in v2.1. - FILTERS extension can be easily implemented once METADATA is implemented - There are also other missing extensions, but they're probably less important: BINARY & URLAUTH=BINARY, CONVERT, CONTEXT=SORT, CREATE-SPECIAL-USE, MULTISEARCH, UTF8=* and some i18n stuff. Backups ------- Filesystem based backups have worked well enough with Dovecot in the past. But with new features like single instance storage it's becoming more difficult. There's no 100% consistent way to even get filesystem level backups with SIS enabled, because deleting both the message file and its attachment files can't be done atomically (although usually this isn't a real problem). Restoring SIS mails is more difficult though, first you need to restore the dbox mail files and then you need to figure out what attachment files from SIS need to be restored, and finally you'll need to do doveadm import to put them into their final destination. I don't have much experience with backup software, but other people in my company do. The initial idea is to implement a Dovecot backup agent to one (commercial) backup software, which allows doing online backups and restoring mails one user/mailbox/mail at a time. I don't know the details yet how exactly this is going to be implemented, but the basic plan is probably to implement a "backup" mail storage backend, which is a PostgreSQL pg_dump-like flat file containing mails from all mailboxes. doveadm backup/import can then export/import this format via stdout/stdin. Incremental backups could possibly be done by giving a timestamp of previous backup run (I'm not sure about this yet). Once I've managed to implement the first fully functional backup agent, it should become clearer how to implement it to other backup solutions. Random things ------------- - dovecot.index.cache file writing is too complex, should be simplified - Enable auth_debug[_passwords]=yes on-the-fly for some specific users/IPs via doveadm - Optimize virtual mailboxes using mailbox list indexes. It wouldn't anymore need to keep all the backend mailboxes' index files open. - Would be nice to go forward with supporting key-value databases as mail storage backends.

5 11

[Dovecot] Sieve_extprograms plugin for Pigeonhole v0.3
by Stephan Bosch 16 Feb '12

16 Feb '12

As indicated in the release announcement of Pigeonhole v0.3.0, there is also a new experimental plugin available for Pigeonhole v0.3: the sieve_extprograms plugin. This can be used to pipe messages to and filter messages through external programs (shell scripts). Also, string data can be retrieved from such external programs. The plugin can currently only be obtained from its Mercurial repository: http://hg.rename-it.nl/pigeonhole-0.3-sieve-extprograms Refer to the INSTALL and README files for more information: http://hg.rename-it.nl/pigeonhole-0.3-sieve-extprograms/raw-file/tip/INSTALL http://hg.rename-it.nl/pigeonhole-0.3-sieve-extprograms/raw-file/tip/README The vendor-specific Sieve language extension provided by this plugin are documented here: http://hg.rename-it.nl/pigeonhole-0.3-sieve-extprograms/raw-file/tip/doc/rf… Please test this plugin. The plan is to include it into the main Pigeonhole release eventually. Regards, Stephan.

1 0

Re: [Dovecot] [Dovecot 2.1] imap service crash when using some clients
by interfaSys sàrl 16 Feb '12

16 Feb '12

Hello Pascal, I've just tested rc6 and get almost the same results. imap still crashes, but Horde still works. I forgot to mention that this is on FreeBSD 8 using gcc 4.6 and LTO. And contrary to what I said in my initial email, it doesn't seem to be ACL plugin related. imap crashes even if it's not in the plugins list. Here is the backtrace: # gdb /usr/libexec/dovecot/imap /path/to/core Core was generated by `imap'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/dovecot/libdovecot-storage.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/libdovecot-storage.so.0 Reading symbols from /usr/lib/dovecot/libdovecot.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/libdovecot.so.0 Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /usr/lib/librt.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/librt.so.1 Reading symbols from /usr/lib/dovecot/lib01_acl_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/lib01_acl_plugin.so Reading symbols from /usr/lib/dovecot/lib02_imap_acl_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/lib02_imap_acl_plugin.so Reading symbols from /usr/lib/dovecot/lib10_quota_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/lib10_quota_plugin.so Reading symbols from /usr/lib/dovecot/lib11_imap_quota_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/lib11_imap_quota_plugin.so Reading symbols from /usr/lib/dovecot/lib11_trash_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/lib11_trash_plugin.so Reading symbols from /usr/lib/dovecot/lib20_autocreate_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/lib20_autocreate_plugin.so Reading symbols from /usr/lib/dovecot/lib20_fts_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/lib20_fts_plugin.so Reading symbols from /usr/lib/dovecot/lib20_zlib_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/lib20_zlib_plugin.so Reading symbols from /lib/libz.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libz.so.5 Reading symbols from /usr/lib/libbz2.so.4...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libbz2.so.4 Reading symbols from /usr/lib/dovecot/lib21_fts_squat_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/lib21_fts_squat_plugin.so Reading symbols from /usr/lib/dovecot/lib30_imap_zlib_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/lib30_imap_zlib_plugin.so Reading symbols from /usr/lib/dovecot/lib90_antispam_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/lib90_antispam_plugin.so Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x00000000105c64e7 in imap_match () from /usr/lib/dovecot/libdovecot.so.0 (gdb) bt full #0 0x00000000105c64e7 in imap_match () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #1 0x00000000104b4bf6 in mailbox_list_iter_next () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #2 0x0000000000416b99 in cmd_list_continue.6853 () No symbol table info available. #3 0x000000000042166d in cmd_list_full () No symbol table info available. #4 0x0000000000000000 in ?? () No symbol table info available. #5 0x8080808080808080 in ?? () No symbol table info available. #6 0x0000000000000004 in ?? () No symbol table info available. #7 0x0000000010a3f1a8 in ?? () No symbol table info available. #8 0x0000000010aa4390 in ?? () No symbol table info available. #9 0x0000000010a3f174 in ?? () No symbol table info available. #10 0x00007fffffffe9a0 in ?? () No symbol table info available. #11 0x0000000010596e4f in p_strdup () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #12 0x0000000010a22200 in ?? () No symbol table info available. #13 0x0000000010aa4458 in ?? () No symbol table info available. #14 0x0000000010aa4340 in ?? () No symbol table info available. #15 0x0000000010aa4498 in ?? () No symbol table info available. #16 0x0000000110a3f040 in ?? () No symbol table info available. #17 0x0000000010a3f128 in ?? () No symbol table info available. #18 0x0000000010a3e840 in ?? () No symbol table info available. #19 0x0000000010a3f040 in ?? () No symbol table info available. #20 0x0000000010a22200 in ?? () No symbol table info available. #21 0x0000000000000001 in ?? () No symbol table info available. #22 0x0000000010a22200 in ?? () No symbol table info available. #23 0x0000000000000000 in ?? () No symbol table info available. #24 0x000000000041d320 in client_command_input.12433 () No symbol table info available. #25 0x00000000004203ca in client_handle_input () No symbol table info available. #26 0x0000000010a574e0 in ?? () No symbol table info available. #27 0x00000000105ae219 in i_stream_read () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #28 0x000000000041d13f in client_input () No symbol table info available. #29 0x00000000105ce276 in io_loop_call_io () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #30 0x00000000105c9ea3 in io_loop_handler_run () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #31 0x00000000105c9f78 in io_loop_run () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #32 0x00000000105c9fb3 in master_service_run () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #33 0x00000000004158bb in main () No symbol table info available. Regards, Olivier > On 01/18/2012 02:03 AM interfaSys sàrl wrote: > >/ Hello, > />/ > />/ I've just noticed that when Horde is connecting to Dovecot 2.1, it > />/ crashes the imap service if Dovecot is configured to use the ACL plugin. > />/ I'm not sure what's so special about the command Horde sends, but it > />/ shouldn't make Dovecot crash. Everything is fine when using Thunderbird. > />/ > />/ Here is the message in Dovecot's logs > />/ "Fatal: master: service(imap): child 89974 killed with signal 11 (core > />/ not dumped)" > />/ > />/ The message says that the core is not dumped, even though I did add > />/ drop_priv_before_exec=yes to my config file. > / > dovecot stop > ulimit -c unlimited > dovecot > > Now connect with Horde and let it crash. > > >/ I've tried connecting to the pid using gdb, but the process just hangs > />/ as soon as I'm connected. > />/ > / > continue > [wait for the crash] > bt full > detach > quit > > > Regards, > Pascal

2 7

[Dovecot] v2.1.0 released
by Timo Sirainen 16 Feb '12

16 Feb '12

http://dovecot.org/releases/2.1/dovecot-2.1.0.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.0.tar.gz.sig Here's finally the the stable v2.1 release. I expect this release to be quite stable, since it's already being used in several large installations. Changes since rc7: FS layout related crashfix, two man pages added. The biggest changes since v2.0: * Plugins now use UTF-8 mailbox names rather than mUTF-7: acl, autocreate, expire, trash, virtual * auth_username_format default changed to %Lu. If you really want case sensitive usernames, set it back to empty. * Solr full text search backend changed to use mailbox GUIDs instead of mailbox names, requiring reindexing everything. solr_old backend can be used with old indexes to avoid reindexing, but it doesn't support some newer features. * Expire plugin: Only go through users listed by userdb iteration. Delete dict rows for nonexistent users, unless expire_keep_nonexistent_users=yes. * Temporary authentication failures sent to IMAP/POP3 clients now includes the server's hostname and timestamp. This makes it easier to find the error message from logs. * dsync was merged into doveadm. There is still "dsync" symlink pointing to "doveadm", which you can use the old way for now. The preferred ways to run dsync are "doveadm sync" (for old "dsync mirror") and "doveadm backup". + imapc (= IMAP client) storage allows using a remote IMAP server to be used as storage. This allows using Dovecot as a smart (caching) proxy or using dsync to do migration from remote IMAP server. + Mailbox indexing via queuing indexer service (required for Lucene) + Lucene full text search (FTS) backend rewritten with support for different languages + FTS finally supports "OR" search operation + FTS supports indexing attachments via external programs + IMAP FUZZY extension, supported by Lucene and Solr FTS backends + IMAP SPECIAL-USE extension to describe mailboxes + Mailbox list indexes + Statistics tracking via stats service. Exported via doveadm stats. + Autocreate plugin creates/subscribes mailboxes physically only when the mailbox is opened for the first time. Mailbox listing shows the autocreated mailboxes even if they don't physically exist. + Password and user databases now support default_fields and override_fields settings to specify template defaults/overrides. + SCRAM-SHA-1 authentication mechanism by Florian Zeitz + LDAP: Allow building passdb/userdb extra fields from multiple LDAP attributes by using %{ldap:attributeName} variables in the template. + Improved multi-instance support: Track automatically which instances are started up and manage the list with doveadm instance commands. All Dovecot commands now support -i <instance_name> parameter to select the instance (instead of having to use -c <config path>). See instance_name setting. + auth: Implemented support for Postfix's "TCP map" sockets for user existence lookups. - listescape plugin works perfectly now

3 7

[Dovecot] There is a way to know if a email has been expunged ?
by Alex Baule 16 Feb '12

16 Feb '12

Hy Everyone...and Timo ! There is a way to know if a email was expunged (deleted from hard disk) inside a plugin ? I rewrite the expunge function, but the real expunge function is void, i can't know if was really expunged. There is a way to know this ?

2 8

[Dovecot] Any possibility of running query after sucessful login?
by Jacek Osiecki 16 Feb '12

16 Feb '12

Hi, I'm using finally dovecot 2.0 after quite a smooth upgrade from 1.0 :) with virtual mailboxes stored in sql database. Sometimes I need to check if a mailbox has been used recently or not. Checking for logins in dovecot logs sometimes means searching through gigabytes of info... I was just wondering if there is any possibility of running another query after successful login - just to fill some extra field like "last_login"? So far my only idea is to replace user/password query with procedure like login(user,password) that would also return a line as required by user/password query. However, some mysql implementations (for example, standard php-mysql) can't handle procedures which return values - so will it work in dovecot? Or maybe some other ideas how to do that? Greetings, -- Jacek Osiecki joshua(a)ceti.pl GG:3828944 I don't want something I need. I want something I want.

2 4

[Dovecot] index synchronization during local delivery
by Andy YB Hu 16 Feb '12

16 Feb '12

Hi there, Now our system will take dovecot as the whole imap back end, and keep the LDA of ours, But our system has our own UID generation mechanism (in dovecot it's incremental from 1), which will be done while local delivery, So when local deliveries, it will first generate the UID, move the mail into maildir, then synchronize the mailbox index, which is part of dovecot LDA does. The question is what API or something else about index synchronization I can integrate into our own LDA program easily? Seems mailbox_copy() would be the possibility? Thanks.

2 7

Re: [Dovecot] 2.1b6 imapc sync error
by Metro Domain Admin 15 Feb '12

15 Feb '12

On Wed, Feb 15, 2012, at 10:50 PM, Timo Sirainen wrote: > On 15.2.2012, at 22.48, Metro Domain Admin wrote: > > > On Wed, Feb 15, 2012, at 09:36 PM, Timo Sirainen wrote: > >> Yes, it's because of "sync". The "Not supported" comes from imapc > >> backend, because Dovecot tried to do some changes to it that weren't > >> possible with IMAP protocol (modseq changes probably). I think the > >> migration still was successful though. > > > > The migration went beautifully otherwise. But are the errors minor > > enough that I can continue with sync? > > Probably better to continue with "backup" just in case. :) > > > I had the idea that I could sync back to the imapc account, as a > > fallback option (and, presumably I'd want to preserve the /tmp/imapc > > directory for this?). > > That's not something that I've tested, and I don't know how well it works > (if at all). > OK, "backup" it is then. Thanks.

1 0

[Dovecot] MySQL server has gone away
by Mark Moseley 15 Feb '12

15 Feb '12

I'm running 2.0.17 and I'm still seeing a decent amount of "MySQL server has gone away" errors, despite having multiple hosts defined in my auth userdb 'connect'. This is Debian Lenny 32-bit and I'm seeing the same thing with 2.0.16 on Debian Squeeze 64-bit. E.g.: Jan 12 20:30:33 auth-worker: Error: mysql: Query failed, retrying: MySQL server has gone away Our mail mysql servers are busy enough that wait_timeout is set to a whopping 30 seconds. On my regular boxes, I see a good deal of these in the logs. I've been doing a lot of mucking with doveadm/dsync (working on maildir->mdbox migration finally, yay!) on test boxes (same dovecot package & version) and when I get this error, despite the log saying it's retrying, it doesn't seem to be. Instead I get: dsync(root): Error: user ...: Auth USER lookup failed dsync(root): Fatal: User lookup failed: Internal error occurred. Refer to server log for more information. Watching tcpdump at the same time, it looks like it's going through some of the mysql servers, but all of them have by now disconnected and are in CLOSE_WAIT. Here's an (edited) example after doing a dsync that completes without errors, with tcpdump running in the background: # sleep 30; netstat -ant | grep 3306; dsync -C^ -u mailbox(a)test.com backup mdbox:~/mdbox tcp 1 0 10.1.15.129:57436 10.1.52.48:3306 CLOSE_WAIT tcp 1 0 10.1.15.129:49917 10.1.52.49:3306 CLOSE_WAIT tcp 1 0 10.1.15.129:35904 10.1.52.47:3306 CLOSE_WAIT 20:49:59.725005 IP 10.1.15.129.35904 > 10.1.52.47.3306: F 1126:1126(0) ack 807 win 1004 <nop,nop,timestamp 312603858 766667259> 20:49:59.725459 IP 10.1.52.47.3306 > 10.1.15.129.35904: . ack 1127 win 123 <nop,nop,timestamp 766667998 312603858> 20:49:59.725568 IP 10.1.15.129.57436 > 10.1.52.48.3306: F 1126:1126(0) ack 807 win 1004 <nop,nop,timestamp 312603858 1842560856> 20:49:59.725779 IP 10.1.52.48.3306 > 10.1.15.129.57436: . ack 1127 win 123 <nop,nop,timestamp 1842561225 312603858> dsync(root): Error: user mailbox(a)test.com: Auth USER lookup failed dsync(root): Fatal: User lookup failed: Internal error occurred. Refer to server log for more information. 10.1.15.129 in this case is the dovecot server, and the 10.1.52.0/24 boxes are mysql servers. That's the same pattern I've seen almost every time. Just a FIN packet to two of the servers (ack'd by the mysql server) and then it fails. Is the retry mechanism supposed to transparently start a new connection, or is this how it works? In connecting remotely to these same servers (which aren't getting production traffic, so I'm the only person connecting to them), I get seemingly random disconnects via IMAP, always coinciding with a "MySQL server has gone away" error in the logs. This is non-production, so I'm happy to turn on whatever debugging would be useful. Here's doveconf -n from the box the tcpdump was on. This box is just configured for lmtp (but have seen the same thing on one configured for IMAP/POP as well), so it's pretty small, config-wise: # 2.0.17: /etc/dovecot/dovecot/dovecot.conf # OS: Linux 3.0.9-nx i686 Debian 5.0.9 auth_cache_negative_ttl = 0 auth_cache_ttl = 0 auth_debug = yes auth_failure_delay = 0 base_dir = /var/run/dovecot/ debug_log_path = /var/log/dovecot/debug.log default_client_limit = 3005 default_internal_user = doveauth default_process_limit = 1500 deliver_log_format = M=%m, F=%f, S="%s" => %$ disable_plaintext_auth = no first_valid_uid = 199 last_valid_uid = 201 lda_mailbox_autocreate = yes listen = * log_path = /var/log/dovecot/mail.log mail_debug = yes mail_fsync = always mail_location = maildir:~/Maildir:INDEX=/var/cache/dovecot/%2Mu/%2.2Mu/%u mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = zlib quota mail_privileged_group = mail mail_uid = 200 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave mdbox_rotate_interval = 1 days mmap_disable = yes namespace { hidden = no inbox = yes list = yes location = prefix = INBOX. separator = . subscriptions = yes type = private } passdb { args = /opt/dovecot/etc/lmtp/sql.conf driver = sql } plugin { info_log_path = /var/log/dovecot/dovecot-deliver.log log_path = /var/log/dovecot/dovecot-deliver.log quota = maildir:User quota quota_rule = *:bytes=25M quota_rule2 = INBOX.Trash:bytes=+10%% quota_rule3 = *:messages=3000 sieve = ~/sieve/dovecot.sieve sieve_before = /etc/dovecot/scripts/spam.sieve sieve_dir = ~/sieve/ zlib_save = gz zlib_save_level = 3 } protocols = lmtp sieve service auth-worker { unix_listener auth-worker { mode = 0666 } user = doveauth } service auth { client_limit = 8000 unix_listener login/auth { mode = 0666 } user = doveauth } service lmtp { executable = lmtp -L process_min_avail = 10 unix_listener lmtp { mode = 0666 } } ssl = no userdb { driver = prefetch } userdb { args = /opt/dovecot/etc/lmtp/sql.conf driver = sql } verbose_proctitle = yes protocol lmtp { mail_plugins = zlib quota sieve } Thanks!

4 29

[Dovecot] 2.1b6 imapc sync error
by Metro Domain Admin 15 Feb '12

15 Feb '12

I received this error at the end of a migration from imapc to mdbox. Is it because I wanted doveadm 'sync' instead of 'backup'? I didn't get time to do any testing, but since you're pushing for the release, here it is: kerio2:~ adminuser$ /opt/dovecot/bin/doveadm -o imapc_user=jsample -o imapc_password=****** -o imapc_host=*.*.*.* sync -R -u jsample_dc(a)mydomain.com imapc:/tmp/imapc dsync(jsample_dc(a)mydomain.com): Error: Can't update mailbox Archives/2011: Not supported dsync(jsample_dc(a)mydomain.com): Error: Can't update mailbox Archives/2012: Not supported dsync(jsample_dc(a)mydomain.com): Error: Can't update mailbox INBOX: Not supported ...etc, for all mailboxes in the account. This is my userdb entry: jsample_dc@mydomain.com:{***}password:502:6:IMAPC RECIPIENT::/bin/false: kerio2:~ adminuser$ /opt/dovecot/bin/doveconf -n # 2.1.rc6: /opt/dovecot-2.1.rc6/etc/dovecot/dovecot.conf # OS: Darwin 9.8.0 Power Macintosh auth_cache_negative_ttl = 0 auth_cache_size = 1 M auth_debug = yes auth_mechanisms = plain login auth_username_format = %n(a)mydomain.com auth_verbose = yes disable_plaintext_auth = no instance_name = dovecot-2.1.rc6 listen = 192.168.20.40 mail_home = /var/mail/%d/%n mail_location = mdbox:~/mdbox mail_plugin_dir = /opt/dovecot/lib/dovecot mail_plugins = fts fts_squat # I know, this is deprecated in 2.1 mail_privileged_group = mail maildir_very_dirty_syncs = yes namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = scheme=CRYPT username_format=%u /opt/dovecot/etc/dovecot/users driver = passwd-file } plugin { fts = squat } postmaster_address = postmaster(a)mydomain.com protocols = imap lmtp service auth { unix_listener /var/spool/postfix/private/auth { group = _postfix mode = 0660 user = _postfix } unix_listener auth-userdb { group = mail mode = 0660 user = adminuser } } service imap { executable = imap postlogin } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = _postfix mode = 0666 user = _postfix } } service postlogin { executable = script-login rawlog -t } service stats { fifo_listener stats-mail { mode = 00 } } ssl_ca = </opt/local/apache2/conf/ssl/gd_bundle.crt ssl_cert = </opt/local/apache2/conf/ssl/server4.crt ssl_key = </opt/local/apache2/conf/ssl/server4.key userdb { args = username_format=%u /opt/dovecot/etc/dovecot/users driver = passwd-file } verbose_proctitle = yes protocol imap { mail_max_userip_connections = 16 } kerio2:~ adminuser$

2 1

[Dovecot] domain quota in sql
by Adam Szpakowski 15 Feb '12

15 Feb '12

Hi, I have a problem with setting up quota usage tracking for domains. Problem is, that domain quota is always based on only one user in domain, the last one on whom behalf any operation was performed. To recreate this situation, one has only to perform: doveadm quota recalc -u USER on a user, and the domain quota takes the value of this user quota. Have anyone a clue what could cause this problem? Quota tracking is set up both for users and domains. For users quota tracking is working fine, data is saved into dbase without problems. We are using dovecot 2.0.15. Quota enforcing (rules) is NOT a part of the problem. Important parts of config: dict { quota = mysql:/etc/dovecot/dovecot-dict-used-quota.conf.ext quota2 = mysql:/etc/dovecot/dovecot-dict-used-quota-domain.conf.ext } plugin { quota = dict:User quota::proxy::quota quota2 = dict:Domain quota:%d:proxy::quota2 } /etc/dovecot/dovecot-dict-used-quota.conf.ext map { pattern = priv/quota/storage table = used_quota username_field = username value_field = bytes } map { pattern = priv/quota/messages table = used_quota username_field = username value_field = messages } /etc/dovecot/dovecot-dict-used-quota-domain.conf.ext map { pattern = priv/quota/storage table = used_quota_domain username_field = domain value_field = bytes } map { pattern = priv/quota/messages table = used_quota_domain username_field = domain value_field = messages } -- Adam Szpakowski

4 10

[Dovecot] Dovecot-2.0.18 and Dovecot-Pigeonwhole-0.2.6
by Ralf Zimmermann 15 Feb '12

15 Feb '12

Hi all, today I have compiled Dovecot-2.0.18 with Dovecot-Pigeonwhole-0.2.6. Now I have following Problem with sieve: ------------------------%<--------------------------------------------- main_script: line 249: error: included personal script 'vacation.sieve' does not exist. main_script: error: validation failed. ------------------------%<--------------------------------------------- I have a definition for 'sieve_dir' and the sieve script 'vacation.sieve' exits in the folder. # Dovecot Sieve Parameters plugin { ... sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } If I use Dovecot-2.0.17 and Dovecot-Pigeonwhole-0.2.5 with the same configuration I can define include :personal "vacation.sieve"; in my main sieve script. All works fine. Greets Ralf

3 3

Re: [Dovecot] 2.1.rc5 Cannot delete folders from trash
by Daniel L. Miller 15 Feb '12

15 Feb '12

On 2/14/2012 4:42 PM, Willie Gillespie wrote: > On 02/14/2012 01:40 PM, Daniel L. Miller wrote: >> On 2/14/2012 12:06 PM, Willie Gillespie wrote: >>> On 2/13/2012 8:34 PM, Daniel L. Miller wrote: >>>> I'm fighting the same issue. With the current release (2.1rc6) no >>>> errors >>>> are logged - but I'm having problems deleted folders from trash. I've >>>> enabled tb-extra-mailbox-sep. Two folders that were previously in >>>> Trash >>>> were successfully removed. I deleted four more - after several >>>> Thunderbird restarts, compacts, refreshes, I have killed three of >>>> them - >>>> there is still one folder that won't "die". Thunderbird reports the >>>> mailbox doesn't exist, yet it continues to appear. >>> >>> Out of curiosity -- does the mailbox actually exist if you look on the >>> Dovecot server? >>> Secondly, is it listed in your subscription file? >> >> At one time - yes they were. After further playing, they do not exist in >> the on-disk folder structure, nor in the subscription file. But still >> show in the client - with errors. > > Sounds like a Thunderbird bug then. With Thunderbird shut down, you > could browse into the profile. > ~\.thunderbird or > C:\Users\name\AppData\Roaming\Thunderbird\whatever\ImapMail\server.name > > Find the mailbox that is not supposed to be there and move/delete it. > The filename will usually just be the mailbox name. A .msf file is > Thunderbird's index file. It will create .sbd folders for any > sub-mailboxes. I tried going in via squirrelmail - saw no subfolders under trash. Went back in with Thunderbird - all gone. -- Daniel

1 0

[Dovecot] pop3 not autocreating directory structure
by Jan-Frode Myklebust 15 Feb '12

15 Feb '12

We use: mail_home = /srv/mailstore/%256LRHu/%Ld/%Ln mail: mdbox:~/mdbox and I just noticed one of our newly provisioned users initially failed to pop her mails. I saw several of these: dovecot:: pop3(new.user(a)example.net): Error: Couldn't open INBOX: Mailbox doesn't exist: INBOX dovecot:: pop3(new.user(a)example.net): Couldn't open INBOX top=0/0, retr=0/0, del=0/0, size=0 before she switched to imap and then everything looked fine: dovecot:: imap(new.user(a)example.net): Disconnected: Logged out bytes=11/338 Looking at the timestamps in the filesystem I see that the users home directory wasn't created before switcing to imap. Is this a know problem? -jf

2 3

[Dovecot] v2.1.rc7 released
by Timo Sirainen 15 Feb '12

15 Feb '12

http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc7.tar.gz http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc7.tar.gz.sig Okay, one more RC, because I needed a new feature implemented and forgot I wasn't supposed to do any changes anymore before v2.1.0. After that I figured I'll just do a few more changes and release RC7. So, v2.1.0 will probably be released within 1-2 days. So, the one new feature is: + Added ignore_on_failure setting for namespaces. If namespace initialization fails with this enabled (e.g. permission denied), the namespace is silently skipped for the user. Also (not really worth mentioning in NEWS) if you now connect to imap/pop3 port when auth process is misconfigured and dies, instead of hanging the client for 5 mins it gets disconnected pretty much immediately.

1 0

[Dovecot] R: Re: LMTP : Can't handle mixed proxy/non-proxy destinations
by cinzia.delcoiro＠libero.it 15 Feb '12

15 Feb '12

Hi Timo, I'm writing to alert you that even in version 2.1. we have the error: "Can't handle mixed proxy/non-proxy destinations" when we write to two users: one existent and one not. The error occurs randomly. I configure LDAP query in the file : dovecot-ldap.conf in this way: pass_attrs = mail=user,userPassword=password,=proxy=y,mailHost=host, =proxy_timeout=600 specifying "=proxy=y" in order to proxy every mail. As workaround, can I configure a static "host" for non-existing users? This is my dovecot -n # 2.1.rc5: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.18-194.el5 x86_64 Red Hat Enterprise Linux Server release 5.5 (Tikanga) auth_mechanisms = plain login base_dir = /usr/local/var/run/dovecot/ disable_plaintext_auth = no listen = 127.0.0.1 lmtp_proxy = yes mail_gid = mailusers mail_location = maildir:/mnt/mbox1/mailusers/%n/Maildir mail_uid = mailusers passdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf driver = ldap } plugin { quota = maildir:User Quota } protocols = lmtp service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } service_count = 0 vsz_limit = 256 M } service lmtp { inet_listener lmtp { port = 24 } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } ssl = no syslog_facility = local5 userdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf driver = ldap } protocol imap { mail_plugins = quota imap_quota } protocol lmtp { postmaster_address = info(a)amm2.miur.it } Regards Cinzia >----Messaggio originale---- >Da: tss(a)iki.fi >Data: 28-gen-2012 18.32 >A: "Alexis Lelion"<alexis.lelion(a)gmail.com> >Cc: "Dovecot Mailing List"<dovecot(a)dovecot.org> >Ogg: Re: [Dovecot] LMTP : Can't handle mixed proxy/non-proxy destinations > >On 27.1.2012, at 12.59, Alexis Lelion wrote: > >> Jan 25 09:05:12 mail01 postfix/lmtp[23934]: A92709300DB: to=< >> user_on_mail02(a)domain.com>, relay=mail01.domain.com[private/dovecot-lmtp], >> delay=0.07, delays=0.01/0/0/0.06, dsn=4.3.0, status=deferred (host >> mail01.domain.com[private/dovecot-lmtp] said: 451 4.3.0 < >> user_on_mail02(a)domain.com> Can't handle mixed proxy/non-proxy destinations >> (in reply to RCPT TO command)) >> >> I was wondering if there was another way of handling this, for example >> by triggering an immediate queue lookup from postfix or forwarding a >> copy of the mail to the other server. Note that the postfix >> "queue_run_delay" was increased to 15min on purpose, so I cannot change >> that. > >It would be possible to change the code to support mixed destinations, but it's probably not a simple change and I have other things to do.. > >Maybe you could work around it so that LMTP always proxies the mails, to localhost as well, but to a different port which doesn't do proxying at all. > >

3 2

[Dovecot] v2.1.rc6 released
by Timo Sirainen 15 Feb '12

15 Feb '12

http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc6.tar.gz http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc6.tar.gz.sig I've finally finished all of my email backlog. If you haven't received an answer to some question/bugreport, resend the mail. This is hopefully the last v2.1 RC. If I don't receive any (serious) bug reports about this release in next few days, I'll just change the version number to v2.1.0 (and maybe update man pages, some are still missing..) I'll also create dovecot-2.2 hg repository today and add some pending patches from Stephan there and start doing some early spring cleaning in there. :) Since v2.1.rc5 there have been lots of small fixes and logging improvements, but I also did a few bigger things since they really had to be done soon and I didn't want v2.2.0 release to be only a few months after v2.1.0 with barely any new features. * Added automatic mountpoint tracking and doveadm mount commands to manage the list. If a mountpoint is unmounted, error handling is done by assuming that the files are only temporarily lost. This is especially helpful if dbox alt storage becomes unmounted. * Expire plugin: Only go through users listed by userdb iteration. Delete dict rows for nonexistent users, unless expire_keep_nonexistent_users=yes. * LDA's out-of-quota mails now include DSN report instead of MDN. + LDAP: Allow building passdb/userdb extra fields from multiple LDAP attributes by using %{ldap:attributeName} variables in the template. + doveadm log errors shows the last 1000 warnings and errors since Dovecot was started. + Improved multi-instance support: Track automatically which instances are started up and manage the list with doveadm instance commands. All Dovecot commands now support -i <instance_name> parameter to select the instance (instead of having to use -c <config path>). See instance_name setting. + doveadm mailbox delete: Added -r parameter to delete recursively + doveadm acl: Added "add" and "remove" commands. + Updated to Unicode v6.1 - mdbox: When saving to alt storage, Dovecot didn't append as much data to m.* files as it could have. - dbox: Fixed error handling when saving failed or was aborted - IMAP: Using COMPRESS extension may have caused assert-crashes - IMAP: THREAD REFS sometimes returned invalid (0) nodes. - dsync: Fixed handling non-ASCII characters in mailbox names.

3 6

[Dovecot] doveadm director proxy
by Jan-Frode Myklebust 15 Feb '12

15 Feb '12

I'm trying to configure a doveadm service that will proxy trough our directors, following the recipie at: http://wiki2.dovecot.org/Director#Doveadm_server So on the backends I have: service doveadm { inet_listener { port = 24245 address = * } } doveadm_proxy_port = 24245 local 192.168.42.0/24 { doveadm_password = suPerSeecret } I assume the "local" line is supposed to point at my local network..? On the directors I have the same, plus: protocol doveadm { auth_socket_path = director-userdb } When testing "doveadm quota" on the directors, it complained quota plugin not being loaded, so I added: mail_plugins=quota Then it complained about "doveadm_password not set, can't authenticate", so I added: doveadm_password = suPerSeecret in the main section. Now I get trough to my backend servers, but they complain about: dovecot:: doveadm: Error: doveadm client attempted non-PLAIN authentication Any ideas for what that might be? This is with dovecot v2.0.14. -jf

2 1

[Dovecot] 2.1.rc5 Cannot delete folders from trash
by Mike Constabel 14 Feb '12

14 Feb '12

Hi, If I delete a folder "foo" in Thunderbird, it is moved to trash. [root@dovecot1][tmp:exec](~) # ll /mailspool1/xxxx.de/test1/mdbox/mailboxes/Trash/ insgesamt 16K drwx------ 4 vmail vmail 4,0K 31. Jan 22:16 . drwx------ 8 vmail vmail 4,0K 31. Jan 22:16 .. drwx------ 2 vmail vmail 4,0K 12. Feb 11:51 dbox-Mails drwx------ 3 vmail vmail 4,0K 31. Jan 22:16 foo [root@dovecot1][tmp:exec](~) # [root@dovecot1][tmp:exec](~) # [root@dovecot1][tmp:exec](~) # ll /mailspool1/xxx.de/test1/mdbox/mailboxes/Trash/foo/ insgesamt 12K drwx------ 3 vmail vmail 4,0K 31. Jan 22:16 . drwx------ 4 vmail vmail 4,0K 31. Jan 22:16 .. drwx------ 2 vmail vmail 4,0K 12. Feb 11:52 dbox-Mails [root@dovecot1][tmp:exec](~) # ll /mailspool1/xxxx.de/test1/mdbox/mailboxes/Trash/foo/dbox-Mails/ insgesamt 12K drwx------ 2 vmail vmail 4,0K 12. Feb 11:52 . drwx------ 3 vmail vmail 4,0K 31. Jan 22:16 .. -rw------- 1 vmail vmail 224 12. Feb 11:52 dovecot.index.log [root@dovecot1][tmp:exec](~) # If I delete foo from trash, thunderbird removed it from view, but if I restart thunderbird, the folder is still in trash. No error in dovecot log, no error in thunderbird. tcpdump: 156 45.101512 192.168.10.1 192.168.10.117 TCP 54094 > imap [ACK] Seq=353 Ack=1617 Win=10144 Len=0 TSV=2414467591 TSER=251091441 157 45.349600 192.168.10.1 192.168.10.117 IMAP Request: 16 list "" "Trash/*" 158 45.349717 192.168.10.117 192.168.10.1 IMAP Response: * LIST (\HasNoChildren) "/" "Trash/foo" 159 45.349756 192.168.10.1 192.168.10.117 TCP 54094 > imap [ACK] Seq=375 Ack=1727 Win=10144 Len=0 TSV=2414467653 TSER=251091503 160 45.395546 192.168.10.1 192.168.10.117 IMAP Request: 17 list "" "Trash/foo/*" 161 45.395624 192.168.10.117 192.168.10.1 IMAP Response: * LIST (\Noselect \HasNoChildren) "/" "Trash/foo/" 162 45.395662 192.168.10.1 192.168.10.117 TCP 54094 > imap [ACK] Seq=401 Ack=1802 Win=10144 Len=0 TSV=2414467665 TSER=251091515 163 45.439998 192.168.10.1 192.168.10.117 IMAP Request: 18 delete "Trash/foo/" 164 45.440067 192.168.10.117 192.168.10.1 IMAP Response: 18 NO [CANNOT] Invalid mailbox name 165 45.440104 192.168.10.1 192.168.10.117 TCP 54094 > imap [ACK] Seq=425 Ack=1839 Win=10144 Len=0 TSV=2414467676 TSER=251091526 166 45.493978 192.168.10.1 192.168.10.117 IMAP Request: 19 IDLE with dovecot 1.2 and Maildir I can delete folders from trash. Something wrong in my config? Thunderbird-Bug? # 2.1.rc5 (b9e74767cd39): /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-xen-amd64 x86_64 Debian 6.0.4 auth_cache_size = 1 M auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login cram-md5 auth_verbose = yes auth_verbose_passwords = plain debug_log_path = /var/log/dovecot/dovecot-debug.log dict { expire = sqlite:/etc/dovecot/dovecot-dict-expire.conf.ext } disable_plaintext_auth = no hostname = mx4.xxxx.de info_log_path = /var/log/dovecot/dovecot-info.log log_path = /var/log/dovecot/dovecot.log mail_debug = yes mail_location = mdbox:~/mdbox mail_plugins = quota notify mail_log expire mail_privileged_group = mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace inbox { inbox = yes location = mailbox Archive/2011 { auto = subscribe } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / type = private } passdb { args = scheme=PLAIN username_format=%u /etc/imap.userdb driver = passwd-file } plugin { expire = Trash expire2 = Trash/* expire3 = Spam expire_dict = proxy::expire quota = dict:User quota::file:/mailspool1/%d/%n/dovecot-quota quota_rule = *:storage=9000M:messages=1000000 sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } postmaster_address = postmaster@localhost protocols = " imap lmtp sieve pop3" ssl_ca = </etc/postfix/psw-ssl/ssl.ca-bundle ssl_cert = </etc/postfix/psw-ssl/ssl.crt ssl_key = </etc/postfix/psw-ssl/ssl.key userdb { args = username_format=%Lu /etc/imap.userdb driver = passwd-file } protocol lmtp { mail_plugins = quota notify mail_log expire sieve } protocol lda { mail_plugins = quota notify mail_log expire } protocol imap { imap_logout_format = bytes=%i/%o mail_plugins = quota notify mail_log expire imap_quota } protocol pop3 { mail_plugins = quota notify mail_log expire }

6 7

[Dovecot] R: Re: R: Re: LMTP : Can't handle mixed proxy/non-proxy destinations
by cinzia.delcoiro＠libero.it 14 Feb '12

14 Feb '12

Charles I need to accept mail also for nonexistent users because I'm delivering a particular service (Certified Mail). Regards Cinzia >----Messaggio originale---- >Da: CMarcus(a)Media-Brokers.com >Data: 14-feb-2012 16.42 >A: "Dovecot Mailing List"<dovecot(a)dovecot.org> >Ogg: Re: [Dovecot] R: Re: LMTP : Can't handle mixed proxy/non-proxy destinations > >On 2012-02-14 10:02 AM, cinzia.delcoiro(a)libero.it ><cinzia.delcoiro(a)libero.it> wrote: >> I'm writing to alert you that even in version 2.1. we have the error: "Can't >> handle mixed proxy/non-proxy destinations" when we write to two users: one >> existent and one not. > >why are you accepting mail for non existing users? > >Catch-alls are a very very bad idea in 99.999% of cases, and usually >when someone thinks they need a catchall, they are mistaken. > >-- > >Best regards, > >Charles >

1 0

[Dovecot] Boehm
by Daniel L. Miller 14 Feb '12

14 Feb '12

As the Boehm GC is an available option, do I take that to mean it's beneficial for some users but not most? -- Daniel

2 1

[Dovecot] Synchronization error in NFS
by Andy YB Hu 14 Feb '12

14 Feb '12

Hi there, Not sure whether it's a bug or env setting issue. I am running some concurrent testings under NFS. The dovecot (version 2.0.13) are deployed in 2 servers (same setup), whose maildir are on the file server via NFS. Here are the output of dovecot -n: [root@MyMachine src]$dovecot -n # 2.0.13: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.18-274.3.1.el5 i686 Red Hat Enterprise Linux Server release 5.7 (Tikanga) nfs auth_anonymous_username = andy auth_debug = yes auth_debug_passwords = yes auth_mechanisms = anonymous plain auth_verbose = yes auth_verbose_passwords = plain disable_plaintext_auth = no lock_method = dotlock log_path = /tmp/log mail_debug = yes mail_fsync = always mail_gid = andy mail_location = maildir:/tmp/NFS mail_nfs_index = yes mail_nfs_storage = yes mail_uid = andy mmap_disable = yes passdb { driver = pam } ssl = no userdb { driver = passwd } Here are what I am doing: One session running loop of COPY commands (while(1) COPY...) connects to one dovecot server; The other session running loop of SELECT commands (while(1) SELECT...) connects to the other dovecot server. Both are accessing the same mail box (/tmp/NFS); After some while (not accurate duration, maybe 2 seconds, or 1 min), I found the number of EXISTS returned from SELECT command is not correct(less than the real number). Then I stop the both sessions. In the /tmp/log: Feb 07 03:44:59 imap(andy): Error: Corrupted transaction log file /tmp/NFS/dovecot.index.log seq 2: Unexpected garbage at EOF (sync_offset=2204) Feb 07 03:44:59 imap(andy): Error: Index /tmp/NFS/dovecot.index: Lost log for seq=2 offset=2204 Feb 07 03:44:59 imap(andy): Warning: fscking index file /tmp/NFS/dovecot.index Then I tried to dump the index, sometime it's failed because of the index corruption. If not, it says: [root@MyMachine src]$doveadm dump /tmp/NFS > /tmp/dump ; vi /tmp/dump doveadm(root): Error: Log synchronization error at seq=2,offset=744 for /tmp/NFS/dovecot.index: Broken extension introduction: Headersize too large (2273345664) doveadm(root): Warning: fscking index file /tmp/NFS/dovecot.index doveadm(root): Error: fcntl(write-lock) locking failed for file /tmp/NFS/dovecot.index.log: Bad file descriptor doveadm(root): Error: mail_index_wait_lock_fd() failed with file /tmp/NFS/dovecot.index.log: Bad file descriptor doveadm(root): Error: Log synchronization error at seq=2,offset=744 for /tmp/NFS/dovecot.index: Broken extension introduction: Headersize too large (2273345664) doveadm(root): Warning: fscking index file /tmp/NFS/dovecot.index doveadm(root): Error: fcntl(write-lock) locking failed for file /tmp/NFS/dovecot.index.log: Bad file descriptor doveadm(root): Error: mail_index_wait_lock_fd() failed with file /tmp/NFS/dovecot.index.log: Bad file descriptor And sometime from the dump output, in the RECORD part: -- RECORDS: 5 RECORD: seq=1, uid=1, flags=0x00 RECORD: seq=2, uid=2, flags=0x00 RECORD: seq=3, uid=3, flags=0x00 RECORD: seq=4, uid=4, flags=0x00 RECORD: seq=5, uid=6, flags=0x00 The uid 5 is missed. but in uidlist file, it's there.. Here are all what I found. If you need additional information, pls let me know. The clock on the 3 machines are synchronized. You can also reproduce it if the 2 sessions are APPEND and SELECT. If both sessions are running towards the same dovecot server, even the maildir are on the NFS, it works very well without any error.

2 8

[Dovecot] Released Pigeonhole v0.2.6 for Dovecot v2.0.18
by Stephan Bosch 13 Feb '12

13 Feb '12

Hello Dovecot users, Pigeonhole v0.2.5 does not compile against the new Dovecot v2.0.18 release. That is why a release a new version now. Other changes are included as well, of which the one regarding the include extension requires special attention; Changelog v0.2.6: * This release fixes unintentional behavior of the include extension. Included script names with a name like "name.sieve" would implicitly map to a script file called "name.sieve" and not "name.sieve.sieve". Keep in mind that the .sieve file extension has no meaning from within the Sieve language. A Sieve script is always stored with an appended .sieve file extension, also when the name already ends with a .sieve suffix. IMPORTANT: Some installations have relied on this unintentional feature, so check your script includes for issues before upgrading. * Matched changes regarding auth_verbose setting in Dovecot. This means that this release will only compile against Dovecot v2.0.18. - Fixed problem in ManageSieve that caused it to omit a WARNINGS response code when the uploaded script compiled with warnings. - Made sure that locations of Sieve error never report `line 0'. - Fixed potential segfault occurring when interpreter initialization fails. The release is available as follows: http://www.rename-it.nl/dovecot/2.0/dovecot-2.0-pigeonhole-0.2.6.tar.gz http://www.rename-it.nl/dovecot/2.0/dovecot-2.0-pigeonhole-0.2.6.tar.gz.sig Refer to http://pigeonhole.dovecot.org and the Dovecot v2.0 wiki for more information. Have fun testing this new release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

[Dovecot] Logging to messages instead of secure
by Cliff Hayes 13 Feb '12

13 Feb '12

I need to log to /var/log/messages instead of /var/log/secure on a fedora system. Is this the correct entry for dovecot.conf? syslog_facility = info

1 0

[Dovecot] Managesieve doesn't listen on 2000/4190
by Jacek Osiecki 13 Feb '12

13 Feb '12

Hi, Finally I decided to give a try to dovecot 2.0, after spending few years with 1.2. Unfortunately, it doesn't go smooth - finally I managed to cope with LMTP transport and exim, but failed to run managesieve. I have compiled pigeonhole, installed it, configured, everything seems to be done well - except the fact, that nothing is listening on port 2000 or 4190. Here is my doveconf -n. Any ideas? # 2.0.16: /etc/dovecot/dovecot.conf # OS: Linux 2.6.39.4-vs2.3.1-pre9.2-nfs41-nfsd x86_64 auth_debug = yes auth_debug_passwords = yes debug_log_path = /var/log/dovecot/debug.log dict { quota = mysql:/etc/dovecot/dovecot-dict-sql.conf } disable_plaintext_auth = no first_valid_uid = 79 info_log_path = /var/log/dovecot/info.log last_valid_uid = 79 log_path = /var/log/dovecot/main.log mail_debug = yes managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave passdb { driver = pam } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = /var/mail/sieve/%d/%u.sieve sieve_dir = /var/mail/sieve/%d/%u sieve_global_path = /var/mail/sieve/%d/global.sieve } postmaster_address = postmaster(a)hybrid.pl service imap-login { inet_listener imap { address = 127.0.0.1 port = 143 } inet_listener imaps { address = 0.0.0.0 port = 993 ssl = yes } } service lmtp { inet_listener lmtp { address = 127.0.0.1 port = 24 } unix_listener lmtp { mode = 0666 } } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service pop3-login { inet_listener pop3 { address = 127.0.0.1 port = 110 } inet_listener pop3s { address = 0.0.0.0 port = 995 ssl = yes } } ssl = no userdb { driver = passwd } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = " sieve quota" } protocol lda { mail_plugins = " sieve quota" } Best regards, -- Jacek Osiecki joshua(a)ceti.pl GG:3828944 I don't want something I need. I want something I want.

2 2

Re: [Dovecot] Problems sending email direct into publich folders
by Kuran, Fabian 13 Feb '12

13 Feb '12

Hi, > Depends on how you want to do this.. For example all mails intended to be put to public namespace could be sent > to a "publicuser" named user, which has write permissions to the public namespace. Then you'll simply create a > sieve script for the publicuser which redirects the mails to the wanted folder (e.g. fileinto "public/hrztest"). I'm also migrating from cyrus-imapd to dovecot. But this solution isn't very good to me. With cyrus I could easily send an email to (for example) bb+shared/archive(a)mydomain.com. Then the mail will be putted to the public folder. Is there a comparable way to do this with Dovecot? FYI: I'm using dovecot in a clustered and multidomain setup. The Mails will be deliviered over LMTP. -- Bye, Fabian Kuran

2 1

[Dovecot] v2.1.0 status
by Timo Sirainen 13 Feb '12

13 Feb '12

I'll release v2.1.rc6 in maybe 16 hours or so. If no problems are reported in it after a few days I'll just change version to 2.1.0. So now's a great time to try the latest v2.1 hg version to see if there are any problems. I've gone through all of my old mails. Let me know if you think something is still missing / unfixed in v2.1 hg. Preferably today. Next up: Creating dovecot-2.2 tree with great new features. :)

4 8

[Dovecot] Dovecot 2.0.18 build error with pigeonhole
by Morten Stevens 13 Feb '12

13 Feb '12

Hi, It is probably a problem with pigeonhole 0.2.5. ... make[3]: *** [managesieve-proxy.o] Error 1 make[3]: *** Waiting for unfinished jobs.... Here is my build log: http://oss.imt-systems.com/mstevens/temp/build.log Someone an idea? Best regards, Morten

4 4

[Dovecot] Some Doveadm Tools lack proper exit codes
by Thomas Leuxner 13 Feb '12

13 Feb '12

Happy New Year Everyone, and *yes* it's that time of the year to archive old stuff again. Please implement proper error codes to support this (scripting) endeavor. => Good $ doveadm user foo userdb lookup: user foo doesn't exist $ echo $? 2 => Bad $ doveadm acl get -u tlx(a)leuxner.net FOO doveadm(tlx(a)leuxner.net): Error: Can't open mailbox FOO: Mailbox doesn't exist: FOO ID Global Rights $ echo $? 0 $ doveconf -n | head # 2.1.rc1 (056934abd2ef): /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.3 Thanks Thomas

2 3

[Dovecot] v2.0.18 released
by Timo Sirainen 12 Feb '12

12 Feb '12

http://dovecot.org/releases/2.0/dovecot-2.0.18.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.18.tar.gz.sig + DIGEST-MD5 authentication supports authorization id now. Patch by Yubao Liu + Added instance_name setting which is used to prefix Dovecot processes in ps output. - LDA/LMTP: Sending a large mail via submission_host or via LMTP proxy may have caused a hang. - Fixed dbox + mail_attachment_dir + zlib problems. - Login processes weren't logging all intended messages with auth_verbose=yes - IMAP: THREAD REFS sometimes returned invalid (0) nodes. - IMAP: CONTEXT search return option wasn't handled at all. - dbox: Various error handling fixes. - snarf plugin: Keep the mailbox locked during snarfing to avoid duplicates.

1 0

[Dovecot] Inherited ACLs for mailboxes created by not-owner
by Michael Stilkerich 12 Feb '12

12 Feb '12

Hi, I have shared one of my mailboxes to another user providing him full rights to that mailbox. $ doveadm acl get -u user1 doc ID Global Rights user=user2 admin create delete expunge insert lookup post read write write-deleted write-seen When that user creates a new mailbox within the shared mailbox, the mailbox is successfully created but with an empty ACL. $ doveadm acl get -u user1 doc/hallo ID Global Rights According to the wiki, it should inherit the ACL from its parent, i.e. have full permissions for user2. Dovecot logs the following errors when I access the parent folder the first time after the other user created the child mailbox: dovecot: imap(user1): Error: Mailbox doc/hallo: Corrupted index, uidvalidity=0 dovecot: imap(user1): Error: Recent flags state corrupted for mailbox INBOX dovecot: imap(user1): Error: /home/dovecot/user1/mailboxes/INBOX/dbox-Mails/dovecot.index reset, view is now inconsistent dovecot: imap(user1): Error: Recent flags state corrupted for mailbox Sent dovecot: imap(user1): Error: /home/dovecot/user1/mailboxes/Sent/dbox-Mails/dovecot.index reset, view is now inconsistent dovecot: imap(user1): Error: /home/dovecot/user1/mailboxes/INBOX/dbox-Mails/dovecot.index reset, view is now inconsistent This is on dovecot 2.1rc5. -Michael

2 4

[Dovecot] Some Dovecot LDA version sends MDN rather than DSN for overquota.
by Mark Sapiro 12 Feb '12

12 Feb '12

It appears that there is some version of the Dovecot LDA that is sending an RFC 3798 MDN rather than an RFC 3464 DSN to report non-delivery to a user who is over quota. See <https://bugs.launchpad.net/mailman/+bug/693134> for a discussion of this and <https://bugs.launchpad.net/mailman/+bug/693134/+attachment/1773018/+files/A…> for the actual MDN message. The issue is that apparently a user was over quota and Dovecot returned an MDN with a disposition of deleted. This is intended to mean the the mail was delivered to the user but the user deleted it without reading it. If the message was actually not delivered, this should be reported to the MTA so it can return an appropriate SMTP status, or the LDA should send an RFC 3464 DSN with an action of failed. Note that I do not actually use the Dovecot LDA nor do I have any access to the system where the notice in the bug report was received, so I may have incomplete information and this may not be relevant to current versions of Dovecot, but I think it is wrong for Dovecot to report over quota non-delivery via an MDN. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 3

[Dovecot] Passdb disconnected unexpectedly when trying to do Director with LMTP
by Mark Zealey 12 Feb '12

12 Feb '12

Hi there, I'm running Dovecot 2.0.16 just set up the director with cut&paste from the wiki. It's working & running fine for pop/imap connections (as verified by doveadm director status user), however when I specify 'RCPT TO' for a (tcp) lmtp connection straight away I get: 451 4.3.0 <xxx(a)yyy.com> Temporary user lookup failure and in the logs: 2012-02-11T14:22:54+00:00 xxx dovecot: lmtp(27997): Error: passdb lookup(xxx(a)yyy.com): Disconnected unexpectedly I'm sure this is an obvious issue for someone who's come across it before. The /var/run/dovecot/director-userdb socket is on the system; exactly the same permissions as the standard auth-userdb Here are the relevant bits of my config (I'm setting lmtp to listen on a different port than normal). Backend password database is mysql if that makes any difference. lmtp_proxy = yes service lmtp { inet_listener lmtp_test { port = 2450 } } protocol lmtp { auth_socket_path = director-userdb } Thanks, Mark

3 3

[Dovecot] Lost in configuration
by forumer＠smartmobili.com 12 Feb '12

12 Feb '12

Hi, I am trying to configure dovecot/postfix with virtual users and sasl auth but there are so many tutorials with mistakes and subtle differences that at the end I am lost. So I am running Ubuntu server 11.04 (natty) and when I installed my server I had followed the following guide http://workaround.org/ispmail/etch Then I have migrated to dovecot 2.1 and now I am trying to allow authenticated user to use my smtp server because for the moment I get : Relay access denied Here is my configuration (first is file hierarchy followed by file contents) and I would like to know what I need to do to allow authenticated user send email. In this tutorial http://library.linode.com/email/postfix/dovecot-mysql-ubuntu-10.04-lucid#sp… it seems I have to add some configuration lines inside /etc/pam.d/smtp and add database configuration inside /etc/postfix/sasl/smtpd.conf. But what I find weird is the fact I have to configure some sql queries from smtpd.conf while normally dovecot has already all the information to do this kind of query. So before to keep on modifying my config I would like to be sure I am following the right way. Thanks ########################### /etc/postfix ########################### drwxr-xr-x 3 root root 4096 2012-02-12 13:33 ./ drwxr-xr-x 116 root root 4096 2012-02-12 13:21 ../ -rw-r--r-- 1 root root 373 2011-07-24 11:50 dynamicmaps.cf -rw-r--r-- 1 root root 1928 2012-02-12 12:45 main.cf -rw-r--r-- 1 root root 5762 2011-08-03 22:06 master.cf -rw-rw---- 1 root postfix 140 2011-07-24 11:43 mysql-virtual-alias-maps.cf -rw-rw---- 1 root postfix 132 2011-07-24 11:47 mysql-virtual-mailbox-domains.cf -rw-rw---- 1 root postfix 128 2011-07-24 11:47 mysql-virtual-mailbox-maps.cf -rw-r--r-- 1 root root 19509 2011-04-05 06:07 postfix-files -rwxr-xr-x 1 root root 8729 2011-04-05 06:07 postfix-script* -rwxr-xr-x 1 root root 25752 2011-04-05 06:07 post-install* drwxr-xr-x 2 root root 4096 2012-02-12 12:41 sasl/ root@xa-12345:/etc/postfix# ll sasl/ drwxr-xr-x 2 root root 4096 2012-02-12 12:41 ./ drwxr-xr-x 3 root root 4096 2012-02-12 13:33 ../ -rw-r--r-- 1 root root 26 2012-02-12 12:41 smtpd.conf ########################### /etc/dovecot ########################### drwxr-xr-x 3 root root 4096 2011-09-24 11:42 ./ drwxr-xr-x 116 root root 4096 2012-02-12 13:21 ../ drwxr-xr-x 2 root dovecot 4096 2012-02-12 12:03 conf.d/ -rw-r--r-- 1 root dovecot 3693 2011-09-23 15:11 dovecot.conf -rw-r--r-- 1 root dovecot 410 2011-09-23 15:11 dovecot-db.conf.ext -rw-r--r-- 1 root dovecot 782 2011-09-23 15:11 dovecot-dict-sql.conf.ext -rw-r--r-- 1 root dovecot 5508 2011-09-23 15:38 dovecot-sql.conf -rw-r--r-- 1 root dovecot 5348 2011-09-23 15:11 dovecot-sql.conf.ext -rw-r--r-- 1 root dovecot 116 2011-09-23 15:11 README ########################### /etc/default/saslauthd ########################### -rw-r--r-- 1 root root 2043 2012-02-12 11:57 /etc/default/saslauthd ########################### /var/spool/postfix/var/run/ ########################### drwxr-xr-x 3 root root 4096 2012-02-12 12:35 ./ drwxr-xr-x 3 root root 4096 2012-02-12 12:35 ../ drwxr-xr-x 2 root sasl 4096 2012-02-12 12:35 saslauthd/ I have added postfix to the sasl group (don't know if it was necessary but I found this instruction on a website) /etc/group: sasl:x:45:postfix /etc/default/saslauthd: ---------------------- START=yes PWDIR="/var/spool/postfix/var/run/saslauthd" PARAMS="-m ${PWDIR}" PIDFILE="${PWDIR}/saslauthd.pid" DESC="SASL Authentication Daemon" NAME="saslauthd" MECHANISMS="pam" MECH_OPTIONS="" THREADS=5 OPTIONS="-c -m /var/spool/postfix/var/run/saslauthd" mkdir -p /var/spool/postfix/var/run/saslauthd chown -R root.sasl /var/spool/postfix/var/run/saslauthd Then I have checked saslauth is running after restart: root@xa-12345:/home/vmail# ps -ef | grep saslauthd root 6123 1 0 13:21 ? 00:00:00 /usr/sbin/saslauthd -a pam -c -m /var/run/saslauthd -n 5 root 6124 6123 0 13:21 ? 00:00:00 /usr/sbin/saslauthd -a pam -c -m /var/run/saslauthd -n 5 root 6125 6123 0 13:21 ? 00:00:00 /usr/sbin/saslauthd -a pam -c -m /var/run/saslauthd -n 5 root 6127 6123 0 13:21 ? 00:00:00 /usr/sbin/saslauthd -a pam -c -m /var/run/saslauthd -n 5 root 6128 6123 0 13:21 ? 00:00:00 /usr/sbin/saslauthd -a pam -c -m /var/run/saslauthd -n 5 Then when I check after restarting if saslauthd socket is created I don't see anything (don't know if it's normal) root@xa-12345:/home/vmail# ls -lh /var/spool/postfix/var/run/saslauthd total 0 /etc/postfix/sasl/smtpd.conf: ----------------------------- pwcheck_method: saslauthd /etc/postfix/main.cf: --------------------- myorigin = /etc/mailname smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu) biff = no append_dot_mydomain = no # TLS parameters smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key smtpd_use_tls=yes smtpd_tls_session_cache_database = btree:${queue_directory}/smtpd_scache smtp_tls_session_cache_database = btree:${queue_directory}/smtp_scache myhostname = mail.foobar.com alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases myorigin = foobar.com mydestination = xa-12345.dadibox.com, localhost.dadibox.com, localhost relayhost = mynetworks = 127.0.0.0/8 80.190.190.190 mailbox_size_limit = 0 recipient_delimiter = + inet_interfaces = all #virtual domains virtual_mailbox_domains = mysql:/etc/postfix/mysql-virtual-mailbox-domains.cf virtual_mailbox_base = /home/vmail virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual-mailbox-maps.cf virtual_uid_maps = static:5000 virtual_gid_maps = static:5000 virtual_alias_maps = mysql:/etc/postfix/mysql-virtual-alias-maps.cf # Dovecot LDA virtual_transport = dovecot dovecot_destination_recipient_limit = 1 debug_peer_level = 2 debug_peer_list = 127.0.0.1 smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth smtpd_sasl_auth_enable = yes smtpd_recipient_restrictions = permit_mynetworks,permit_sasl_authenticated,reject_unauth_destination smtpd_sasl_application_name = smtpd broken_sasl_auth_clients = yes /etc/dovecot/conf.d/10-auth.conf: -------------------------------------- disable_plaintext_auth = no !include auth-sql.conf.ext !include auth-static.conf.ext /etc/dovecot/conf.d/auth-static.conf.ext: ---------------------------------------- userdb { driver = static args = uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes } /etc/dovecot/conf.d/auth-sql.conf.ext: -------------------------------------- passdb { driver = sql args = /etc/dovecot/dovecot-sql.conf } /etc/dovecot/dovecot-sql.conf: ------------------------------ driver = mysql connect = host=127.0.0.1 dbname=mailserver user=myuser password=mypassword default_pass_scheme = CRAM-MD5 password_query = SELECT email as user, password FROM view_users WHERE email='%u'; /etc/dovecot/conf.d/10-master.conf: ---------------------------------- service imap-login { inet_listener imap { } inet_listener imaps { } } service pop3-login { inet_listener pop3 { } inet_listener pop3s { } } service lmtp { unix_listener lmtp { } } service imap { } service pop3 { } service auth { unix_listener auth-userdb { mode = 0600 user = vmail #group = } # Postfix smtp-auth unix_listener /var/spool/postfix/private/auth { mode = 0777 } } service auth-worker { } service dict { unix_listener dict { mode = 0600 #user = group = vmail } }

2 2

[Dovecot] Quota Calculation seems to be wrong when using dsync
by Thomas Leuxner 12 Feb '12

12 Feb '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Recently I encountered odd quota increases when using 'dsync' with the latest and greatest: 2.0.8 (89936539e3b8). Say you got something in place like this: plugin { quota = dict:user::file:%h/mdbox/dovecot-quota quota_rule = *:storage=1GB quota_rule2 = Trash:storage=+10%% } Kick off a manual backup: $ dsync -u user(a)domain.tld backup mdbox:/<path to backup>/mdbox This results in doubling the quota for the backed up user. It doesn't seem to matter whether 'mirror' or 'backup' mode is used, both increase the "source" quota. Doesn't sound right to me. You can only get to the "real" usage by running a recalc manually: $ doveadm quota recalc -u user(a)domain.tld Anyone else seen this? Regards Thomas P.S. Merry Christmas -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.16 (Darwin) iEYEARECAAYFAk0VtH8ACgkQ+meF/S97aXjUkwCfdZFpUPCOY9UiukT+G68jCHHr mmMAnRHz56BXMzpC84CIYvUn4KHpl8OA =M0AZ -----END PGP SIGNATURE-----

2 9

[Dovecot] Migration to mdbox from Maildir, missing folders!
by Giles Coochey 12 Feb '12

12 Feb '12

So I went and migrated a mailbox from mdbox from maildir format. All seemed ok, but I've found that I now have some missing folders. The mailbox in maildir format had some folders which contained an '&' sign, these appear to have been omitted... What can be done? (I have a backup of the maildir box). Note though that mdbox is now a live mailbox and has sent and received mails since the migration... -- Message sent via my webmail account.

2 1

[Dovecot] folder hierarchies with migration from cyrus to dovecot2
by Wolfgang Rosenauer 12 Feb '12

12 Feb '12

Hi, I finally migrated my IMAP server from cyrus to dovecot2. I have been using cyrus since many years and have not much experience with dovecot yet though. I've converted my imap server using cyrus2dovecot (several times until I thought it was correct) but there is one thing left which confuses me and I'm not sure what I can or need to do to change it. With Cyrus I used unixhierarchysep: yes and subfolders within Cyrus are always below INBOX. I'm used to that in my IMAP clients and wanted to preserve it with Dovecot. So during migration I finally made sure to create the subfolder again below INBOX wich looks fine in Thunderbird for example. But my mobile devices (Android based with K9) were displaying the folders with Cyrus just with their name w/o the INBOX prefix. (Mobile clients are bad in displaying folder hierarchies so it was convenient to have them looking like they were in parallel to the Inbox.) Now I get the folders displayed as INBOX.whatever and my Android mail clients fail to map them to the special (and localized) folders like Trash. While that seems consistent to my current hierarchy it's not what I wanted. So basically my two questions are: - Can I configure Dovecot in a way that it looks like Cyrus? Having subfolders below Inbox but let clients like those on Android display them besides Inbox? - If that's not possible, can I move the subfolders up one level so they are next to the Inbox? How would I do that? Sorry for the beginner questions. I played around with Dovecot before but using it in production environment disclosed some fine differences. Thanks, Wolfgang

2 1

[Dovecot] [PATCH] Allow verification of user's hash in doveadm-pw
by Spack 12 Feb '12

12 Feb '12

Hi, It may be useful for testing purpose to know if a generated password hash correspond to a given clear password. This can be useful to check if a hash generated by another program can be verified by Dovecot without any errors. This patch adds the ability the verify a password hash using `doveadm pw` via the `-V` option. $ doveadm pw -s SSHA.hex Enter new password: Retype new password: {SSHA.HEX}58b910d947c60b35be3e12b0d9897c1f87dfa450e6d5a75c $ doveadm pw -s SSHA.hex -V{SSHA.HEX}58b910d947c60b35be3e12b0d9897c1f87dfa450e6d5a75c Enter new password: Retype new password: {SSHA.HEX}4fdf801f57870fb624bee60895c2308187837dfb3987ca06 (verified) When the user specify a hash, it is checked in place of the usual verification process. This works with all schemes. Just be sure to escape special characters or use simple quotes. $ doveadm pw -s MD5-CRYPT -V'{MD5-CRYPT}$1$R7thDyN.$E0G0czPE/h4S0Hn/b5oVW1' Enter new password: Retype new password: {MD5-CRYPT}$1$rp8nVSqq$gDAPM5iqv1yhBoDZIWsQ4/ (verified) Lets print a failed check: doveadm pw -s CRYPT -V{CRYPT}/uuE/AAAAAAAA Enter new password: Retype new password: reverse password verification check failed FYI the word used for those test cases was "password". Regards, ___ Jimmy Thrasibule <spack.world(a)gmail.com>

2 1

[Dovecot] Can't view all sub folders or e-mail using Dovecot with Maildir.
by Glen Johnson 11 Feb '12

11 Feb '12

I have an IMAP mail server running Postfix, and Dovecot. I have an old Notebook computer which I can view all e-mails. The problem I am having is when I try to use any other computer on the network to view the e-mail I can not see the contents of all the folders. I can see some of the folders and their content but not all. To answer a couple of preliminary questions: dovecot version 2.0.13, postfix version 2.8.3 dovecot.conf ------------------ # 2.0.13: /usr/pkg/etc/dovecot/dovecot.conf # OS: NetBSD 4.0.1 i386 auth_debug = yes auth_verbose = yes disable_plaintext_auth = no listen = * log_path = /var/log/dovecot.log mail_location = maildir:~/Maildir/ passdb { driver = passwd } passdb { args = /usr/pkg/etc/dovecot/passwd driver = passwd-file } protocols = imap service auth { user = root } service imap-login { executable = /usr/pkg/libexec/dovecot/imap-login } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = passwd } protocol lda { postmaster_address = postmaster(a)denisecir.com }

2 1

[Dovecot] doveadm index
by Daniel L. Miller 10 Feb '12

10 Feb '12

Does "doveadm index -A INBOX" reindex everything? What about users with multiple folders, both subbed & not subbed under INBOX? -- Daniel

3 6

[Dovecot] Postfix + LMTP with virtual users: how to strip domain from LMTP RCPT TO
by Mildred Ki'Lya 10 Feb '12

10 Feb '12

Hi, I am trying to set up my own mail server (to get off Google) and I have a problem with mail delivery. I'm using Postfix as a SMTP front-end, and use the LMTP server included in dovecot to receive mail from postfix. I have a setup which works with the dovecot LDA, it involves calling dovecot-lda with the -d flag. Postfix computes the username by removing what's after the recipient_delimiter and the domain from the mail address, and gives this username to dovecot. But, I'd prefer using LMTP, as it is possible to reject unknown e-mails without having to duplicate the user database (it is explained here: http://wiki2.dovecot.org/LDA/Postfix ) I set up LMTP so that postfix uses the socket provided by dovecot, and it works. Only I get the following error message in the logs: Feb 10 18:05:53 ashley postfix/smtpd[9298]: NOQUEUE: reject: RCPT from mail-wi0-f179.google.com[209.85.212.179]: 450 4.1.1 <mildred(a)mildred.fr>: Recipient address rejected: unverified address: host mail.mildred.fr[private/dovecot-lmtp] said: 550 5.1.1 <mildred(a)mildred.fr> User doesn't exist: mildred(a)mildred.fr(in reply to RCPT TO command); from=< shanti(a)sogilis.com> to=<mildred(a)mildred.fr> proto=ESMTP helo=< mail-wi0-f179.google.com> Feb 10 18:06:52 ashley postfix/smtpd[9298]: NOQUEUE: reject: RCPT from mail-wi0-f179.google.com[209.85.212.179]: 450 4.1.1 <mildred-test(a)mildred.fr>: Recipient address rejected: unverified address: host mail.mildred.fr[private/dovecot-lmtp] said: 550 5.1.1 <mildred-test(a)mildred.fr> User doesn't exist: mildred-test(a)mildred.fr (in reply to RCPT TO command); from=< shanti(a)sogilis.com> to=<mildred-test(a)mildred.fr> proto=ESMTP helo=< mail-wi0-f179.google.com> I followed the explanations here: http://wiki2.dovecot.org/HowTo/PostfixDovecotLMTP The problem is that my passwd-like file only contains a user named "mildred". I tried to add a user mildred(a)mildred.fr and mildred%mildred.frbut it doesn't work either. Do you know how I could tell dovecot to guess the username correctly ? Thanks, Mildred -- Mildred Ki'Lya http://mildred.fr

2 1

[Dovecot] dsync deleting too many emails (sdbox)
by Asheesh Laroia 09 Feb '12

09 Feb '12

I'm using dsync to synchronize emails on a laptop where wifi connectivity sometimes fails in the middle of a sync. I have a shell script that runs dsync, and here is one line of it including the output of dsync: + dsync -f -m realmail mirror /home/paulproteus/projects/ssh-attach/run ssh rose.makesad.us dsync dsync-local(paulproteus): Error: dbox /home/paulproteus/Maildir/dbox/mailboxes/realmail/dbox-Mails: Unexpectedly lost uid=337460 dsync-local(paulproteus): Error: msg guid lookup failed: Internal error occurred. Refer to server log for more information. [2012-02-02 11:02:12] dsync-local(paulproteus): Warning: sdbox /home/paulproteus/Maildir/dbox/mailboxes/realmail/dbox-Mails: Rebuilding index dsync-local(paulproteus): Warning: sdbox /home/paulproteus/Maildir/dbox/mailboxes/realmail/dbox-Mails: Ignoring invalid filename 130608.broken dsync-local(paulproteus): Warning: sdbox /home/paulproteus/Maildir/dbox/mailboxes/realmail/dbox-Mails: Ignoring invalid filename 66159.broken dsync-local(paulproteus): Error: Corrupted dbox file /home/paulproteus/Maildir/dbox/mailboxes/realmail/dbox-Mails/u.66159 (around offset=16): EOF reading msg header (got 0/30 bytes) dsync-local(paulproteus): Error: link(/home/paulproteus/Maildir/dbox/mailboxes/realmail/dbox-Mails/u.66159, /home/paulproteus/Maildir/dbox/mailboxes/realmail/dbox-Mails/u.66159.broken) failed: File exists dsync-local(paulproteus): Error: Corrupted dbox file /home/paulproteus/Maildir/dbox/mailboxes/realmail/dbox-Mails/u.66159 (around offset=16): EOF reading msg header (got 0/30 bytes) dsync-local(paulproteus): Warning: sdbox: Skipping unfixable file: /home/paulproteus/Maildir/dbox/mailboxes/realmail/dbox-Mails/u.66159 dsync-local(paulproteus): Warning: sdbox /home/paulproteus/Maildir/dbox/mailboxes/realmail/dbox-Mails: Ignoring invalid filename 336269.broken dsync-local(paulproteus): Error: Corrupted dbox file /home/paulproteus/Maildir/dbox/mailboxes/realmail/dbox-Mails/u.130608 (around offset=16): EOF reading msg header (got 0/30 bytes) dsync-local(paulproteus): Error: link(/home/paulproteus/Maildir/dbox/mailboxes/realmail/dbox-Mails/u.130608, /home/paulproteus/Maildir/dbox/mailboxes/realmail/dbox-Mails/u.130608.broken) failed: File exists dsync-local(paulproteus): Error: Corrupted dbox file /home/paulproteus/Maildir/dbox/mailboxes/realmail/dbox-Mails/u.130608 (around offset=16): EOF reading msg header (got 0/30 bytes) dsync-local(paulproteus): Warning: sdbox: Skipping unfixable file: /home/paulproteus/Maildir/dbox/mailboxes/realmail/dbox-Mails/u.130608 dsync-remote(paulproteus): Error: proxy server timed out dsync-local(paulproteus): Error: Corrupted dbox file /home/paulproteus/Maildir/dbox/mailboxes/realmail/dbox-Mails/u.336269 (around offset=16): EOF reading msg header (got 0/30 bytes) dsync-local(paulproteus): Error: link(/home/paulproteus/Maildir/dbox/mailboxes/realmail/dbox-Mails/u.336269, /home/paulproteus/Maildir/dbox/mailboxes/realmail/dbox-Mails/u.336269.broken) failed: File exists dsync-local(paulproteus): Error: Corrupted dbox file /home/paulproteus/Maildir/dbox/mailboxes/realmail/dbox-Mails/u.336269 (around offset=16): EOF reading msg header (got 0/30 bytes) dsync-local(paulproteus): Warning: sdbox: Skipping unfixable file: /home/paulproteus/Maildir/dbox/mailboxes/realmail/dbox-Mails/u.336269 dsync-local(paulproteus): Warning: Transaction log file /home/paulproteus/Maildir/dbox/mailboxes/realmail/dbox-Mails/dovecot.index.log was locked for 1528 seconds That seemed problematic, but not dangerous. Then I ran a fresh sync, and found 3000 (of 60,000) messages had been deleted and expunged from the "realmail" box. I'm guessing this is some bad interaction with sdbox and partial file downloads? I haven't read the code for this, but I would guess the dsync process isn't being atomic about file transfers, so it is leaving half-completed transfers in place, which results in corrupt files when they're next examined. dovecot -n output: # 2.0.15: /etc/dovecot/dovecot.conf # OS: Linux 3.0.0-2-amd64 x86_64 Debian wheezy/sid mail_location = sdbox:~/Maildir/dbox passdb { driver = pam } protocols = " imap" ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = passwd } -- Asheesh.

3 3

[Dovecot] Strange behavior from shared namespaces and INBOX, probably a bug
by Christoph Bussenius 09 Feb '12

09 Feb '12

Hi, we have experienced some erratic behavior from Dovecot 2.0.15 if a user's INBOX is shared. Some folders of user1, including the INBOX, have been shared using these IMAP commands: . login user1 XXXXXX . setacl INBOX user2 lrwstiekx . setacl box-a user2 lrwstiekx Now if we use telnet to log in as user2 and select "shared/user1", it will contain the same mails as "shared/user1/INBOX". The really strange thing is that "SELECT"-ing "shared/user1" succeeds only if it is the first command afted logging in. If it not the first command (if e. g. the "LIST" or "SELECT" command has already been used), then dovecot will report that the mailbox does not exist. As a result, user agents like Thunderbird will behave very erratically in this setup. They may show both mailboxes ("shared/user1" and "shared/user1/INBOX") with the same mails, but will not always succeed to download mails for "shared/user1". We were able to reproduce this behavior with a quite simple configuration (see further below), so I doubt that the problem is in the configuration. So, is this a bug in Dovecot? I am not quite sure how exactly it should behave, but it definitely does not seem right this way. Below are the results from telnet: Sending: . login user2 XXXXXX . select shared/user1 Receiving: * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 5 EXISTS * 0 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1316698162] UIDs valid * OK [UIDNEXT 6] Predicted next UID * OK [HIGHESTMODSEQ 1] Highest . OK [READ-WRITE] Select completed. Sending: . fetch 1:2 (internaldate rfc822.size) Receiving: * 1 FETCH (INTERNALDATE "25-Apr-2006 23:09:07 +0200" RFC822.SIZE 5660) * 2 FETCH (INTERNALDATE "25-Apr-2006 23:11:01 +0200" RFC822.SIZE 6612) . OK Fetch completed. Sending: . select shared/user1/INBOX Receiving: * OK [CLOSED] Previous mailbox closed. * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 5 EXISTS * 0 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1316698162] UIDs valid * OK [UIDNEXT 6] Predicted next UID * OK [HIGHESTMODSEQ 1] Highest . OK [READ-WRITE] Select completed. Sending: . fetch 1:2 (internaldate rfc822.size) Receiving: (Note that these mails are the same as those above) * 1 FETCH (INTERNALDATE "25-Apr-2006 23:09:07 +0200" RFC822.SIZE 5660) * 2 FETCH (INTERNALDATE "25-Apr-2006 23:11:01 +0200" RFC822.SIZE 6612) . OK Fetch completed. Now we select the first mailbox again: Sending: . select shared/user1 Receiving: . NO Mailbox doesn't exist: shared/user1 * OK [CLOSED] Previous mailbox closed. The same command did not fail earlier. Listing the mailboxes shows the following: Sending: . list "" * Receiving: * LIST (\HasNoChildren) "/" "INBOX" * LIST (\Noselect \HasChildren) "/" "shared/user1" * LIST (\HasNoChildren) "/" "shared/user1/box-a" * LIST (\HasNoChildren) "/" "shared/user1/INBOX" . OK List completed. I can reproduce this behavior using the following setup: Virtual users on an ext4 filesystem in /mail/users/{user1,user2} configured in a passwd file (/usr/local/dovecot/etc/dovecot/users): user1:{plain}XXXXXX:::user1:/mail/users/user1:: user2:{plain}XXXXXX:::user2:/mail/users/user2:: Output of doveconf -n: # 2.0.15: /usr/local/dovecot/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-33-server x86_64 Ubuntu 10.04.3 LTS disable_plaintext_auth = no mail_gid = vmail mail_plugins = acl mail_uid = vmail namespace { inbox = yes location = maildir:~/Maildir prefix = separator = / } namespace { list = children location = maildir:%%h/Maildir prefix = shared/%%u/ separator = / subscriptions = no type = shared } passdb { args = scheme=CRYPT username_format=%u /usr/local/dovecot/etc/dovecot/users driver = passwd-file } plugin { acl = vfile acl_shared_dict = file:/mail/shared-mailboxes } protocols = imap service auth { unix_listener auth-userdb { group = vmail mode = 0660 } } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { args = username_format=%u /usr/local/dovecot/etc/dovecot/users driver = passwd-file } protocol imap { mail_plugins = acl imap_acl } Cheers, Christoph Bußenius -- Christoph Bußenius Rechnerbetriebsgruppe der Fakultäten Informatik und Mathematik TU München +49 89-289-18519 <> Raum 00.05.055 <> Boltzmannstr. 3 <> Garching

2 1

[Dovecot] Segfaul probably during dsync
by Matthias Rieber 09 Feb '12

09 Feb '12

Hi, I get core dumps, probably during dsync: Core was generated by `dovecot/imap postlogin'. Program terminated with signal 6, Aborted. [New process 7727] #0 0x00002ba911c04ed5 in raise () from /lib/libc.so.6 #0 0x00002ba911c04ed5 in raise () from /lib/libc.so.6 No symbol table info available. #1 0x00002ba911c063f3 in abort () from /lib/libc.so.6 No symbol table info available. #2 0x00002ba91157d775 in default_fatal_finish (type=<value optimized out>, status=0) at failures.c:187 backtrace = 0xcebd838 "/usr/local/lib/dovecot/libdovecot.so.0 [0x2ba91157d762] -> /usr/local/lib/dovecot/libdovecot.so.0 [0x2ba91157d7c6] -> /usr/local/lib/dovecot/libdovecot.so.0(i_error+0) [0x2ba91157dbb8] -> /usr/local/l"... #3 0x00002ba91157d7c6 in i_internal_fatal_handler (ctx=0x7fffadba32a0, format=<value optimized out>, args=<value optimized out>) at failures.c:645 status = 0 #4 0x00002ba91157dbb8 in i_panic (format=<value optimized out>) at failures.c:259 ctx = {type = LOG_TYPE_PANIC, exit_status = 0, timestamp = 0x0} args = {{gp_offset = 40, fp_offset = 48, overflow_arg_area = 0x7fffadba3370, reg_save_area = 0x7fffadba32b0}} #5 0x00002ba9112b4018 in index_search_result_update_flags (result=0xdebe3e0, uids=0x7fffadba3640) at index-search-result.c:87 search_arg = {next = 0xd25b098, type = SEARCH_UIDSET, value = {subargs = 0x0, seqset = {arr = {buffer = 0xcebd640, element_size = 8}, v = 0xcebd640, v_modifiable = 0xcebd640}, str = 0x0, time = 0, size = 0, flags = 0, search_flags = 0, date_type = 0, thread_type = MAIL_THREAD_NONE, keywords = 0x0, modseq = 0x0, search_args = 0x0, search_result = 0x0, mailbox_glob = 0x0}, context = 0x0, hdr_field_name = 0x0, not = 0, match_always = 0, nonmatch_always = 0, result = -1} ret = <value optimized out> __FUNCTION__ = "index_search_result_update_flags" #6 0x00002ba91276ac92 in virtual_sync_backend_box (ctx=0xdebcdb0, bbox=0xdcb8e38) at virtual-sync.c:725 sync_flags = <value optimized out> status = {messages = 121, recent = 0, unseen = 111, uidvalidity = 1225530594, uidnext = 182153, first_unseen_seq = 0, first_recent_uid = 182152, highest_modseq = 0, virtual_size = 0, keywords = 0x0, cache_fields = 0x0, nonpermanent_modseqs = 0} ret = <value optimized out> __FUNCTION__ = "virtual_sync_backend_box" #7 0x00002ba91276b661 in virtual_storage_sync_init (box=0xcf524c0, flags=MAILBOX_SYNC_FLAG_FIX_INCONSISTENT) at virtual-sync.c:1400 sync_ctx = <value optimized out> ret = <value optimized out> #8 0x00002ba911299b71 in mailbox_sync_init (box=0xcf524c0, flags=MAILBOX_SYNC_FLAG_FIX_INCONSISTENT) at mail-storage.c:947 _data_stack_cur_id = 0 ctx = <value optimized out> #9 0x00002ba91129a337 in mailbox_sync (box=0x1e2f, flags=7727) at mail-storage.c:993 ctx = <value optimized out> status = {sync_delayed_expunges = 0} #10 0x0000000000417602 in imap_status_get (cmd=0xcf00410, ns=0xcefccd0, mailbox=0xcebd330 "rapidsolution", items=0x7fffadba3a50, result_r=0x7fffadba39e0, error_r=0x7fffadba3a38) at imap-status.c:85 client = (struct client *) 0xceffca0 box = (struct mailbox *) 0x1e2f error = <value optimized out> ret = <value optimized out> #11 0x000000000040e763 in cmd_status (cmd=0xcf00410) at cmd-status.c:52 client = (struct client *) 0xceffca0 status = MAILBOX_NAME_EXISTS_MAILBOX args = (const struct imap_arg *) 0xcf02c68 list_args = (const struct imap_arg *) 0xcf02da8 items = {mailbox_items = 17, guid = 0} result = {status = {messages = 124, recent = 0, unseen = 0, uidvalidity = 1301953092, uidnext = 1, first_unseen_seq = 0, first_recent_uid = 0, highest_modseq = 0, virtual_size = 48005140525491, keywords = 0x0, cache_fields = 0x80, nonpermanent_modseqs = 0}, mailbox_guid = "{µW\021©+\000\000\200\000\000\000\000\000\000"} ns = <value optimized out> mailbox = 0xcf02d58 "virtual.rapidsolution" storage_name = 0xcebd330 "rapidsolution" error = <value optimized out> #12 0x000000000041055c in client_command_input (cmd=0xcf00410) at imap-client.c:672 client = (struct client *) 0xceffca0 command = <value optimized out> __FUNCTION__ = "client_command_input" #13 0x000000000041060d in client_command_input (cmd=0xcf00410) at imap-client.c:722 client = (struct client *) 0xceffca0 command = (struct command *) 0x6 __FUNCTION__ = "client_command_input" #14 0x0000000000410785 in client_handle_input (client=0xceffca0) at imap-client.c:763 _data_stack_cur_id = 3 ret = 54 remove_io = <value optimized out> handled_commands = false __FUNCTION__ = "client_handle_input" #15 0x00000000004111a2 in client_input (client=0xceffca0) at imap-client.c:814 cmd = <value optimized out> output = (struct ostream *) 0xcf00288 bytes = <value optimized out> __FUNCTION__ = "client_input" #16 0x00002ba911588e38 in io_loop_call_io (io=0xcf00320) at ioloop.c:384 ioloop = (struct ioloop *) 0xcec5620 t_id = 2 #17 0x00002ba911589dc2 in io_loop_handler_run (ioloop=<value optimized out>) at ioloop-epoll.c:213 ctx = (struct ioloop_handler_context *) 0xcec5850 event = (const struct epoll_event *) 0xcec58c0 list = (struct io_list *) 0xcf00370 io = (struct io_file *) 0x1e2f tv = {tv_sec = 4, tv_usec = 514891} msecs = <value optimized out> ret = <value optimized out> call = false #18 0x00002ba911588dc8 in io_loop_run (ioloop=0xcec5620) at ioloop.c:405 No locals. #19 0x00002ba911576c93 in master_service_run (service=0xcec54f0, callback=0x1e2f) at master-service.c:478 No locals. #20 0x0000000000419401 in main (argc=2, argv=0xcec5370) at main.c:375 service_flags = <value optimized out> storage_service_flags = <value optimized out> postlogin_socket_path = 0xcebd080 "/usr/local/var/run/dovecot/postlogin" username = 0x0 c = <value optimized out> set_roots = {0x41c680, 0x0} Logfile: Apr 10 13:49:34 shrike dovecot: imap-login: Login: user=<matthias>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=14235, secured Apr 10 13:49:34 shrike dovecot: (null)Error: rawlog_open: open() failed for /home/matthias/dovecot.rawlog/20110410-134934-14237.in: Permission denied Apr 10 13:49:43 shrike dovecot: imap(matthias): Panic: file index-search-result.c: line 87 (search_result_update_search): assertion failed: (next_uid == mail->uid) Apr 10 13:49:43 shrike dovecot: imap(matthias): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0 [0x2b4df76ce762] -> /usr/local/lib/dovecot/libdovecot.so.0 [0x2b4df76ce7c6] -> /usr/local/lib/dovecot/libdovecot.so.0(i_error+0) [0x2b4df76cebb8] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(index_search_result_update_flags+0x2d8) [0x2b4df7405018] -> /usr/local/lib/dovecot/lib20_virtual_plugin.so [0x2b4df88bbc92] -> /usr/local/lib/dovecot/lib20_virtual_plugin.so(virtual_storage_sync_init+0x871) [0x2b4df88bc661] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x31) [0x2b4df73eab71] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x27) [0x2b4df73eb337] -> dovecot/imap(imap_status_get+0x92) [0x417602] -> dovecot/imap(cmd_status+0x163) [0x40e763] -> dovecot/imap [0x41055c] -> dovecot/imap [0x41060d] -> dovecot/imap(client_handle_input+0x45) [0x410785] -> dovecot/imap(client_input+0x62) [0x4111a2] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x48) [0x2b4df Apr 10 13:49:43 shrike dovecot: master: Error: service(imap): child 14235 killed with signal 6 (core dumped) # dovecot --version 2.0.11 (cef23de90ff1) Matthias

2 3

[Dovecot] 2.1.rc1 (8a63f621bd2e): SiS permission issue + crash
by Pascal Volk 09 Feb '12

09 Feb '12

Since changeset 8a63f621bd2e I'm one step closer to the perfect working setup. I'm sharing one GID per domain, all it's alias names and accounts. So I can use: mail_attachment_dir = /srv/mail/.SiS/%{gid} In order to avoid permission trouble I've set fs ACL on the .SiS dir: ,--[ getfacl srv/mail/.SiS ]-- | # file: srv/mail/.SiS | # owner: root | # group: root | user::rwx | group::--x | mask::--x | other::-wx | default:user::rwx | default:group::rwx | default:mask::rwx | default:other::--- `-- OK, lets test the setup: dsync -u test-0(a)example.com mirror maildir:/tmp/Maildir rm -rf Maildir && cp -a Maildir_org Maildir && chown -R 70010:70002 Maildir dsync -vu test-1(a)example.com mirror maildir:/tmp/Maildir dsync(test-1(a)example.com): Info: Drafts: only in dest (guid=b6a53627f3cbe24e33030000850d2fad) dsync(test-1(a)example.com): Info: Sent: only in dest (guid=b7a53627f3cbe24e33030000850d2fad) dsync(test-1(a)example.com): Info: Junk-E-Mail: only in dest (guid=b8a53627f3cbe24e33030000850d2fad) dsync(test-1(a)example.com): Info: Trash: only in dest (guid=b9a53627f3cbe24e33030000850d2fad) dsync(test-1(a)example.com): Info: INBOX: only in dest (guid=baa53627f3cbe24e33030000850d2fad) dsync(test-1(a)example.com): Error: stat(/srv/mail/.SiS/70002/a2/7b/.temp.blau.819.4f06409857c627e0) failed: Permission denied dsync(test-1(a)example.com): Error: safe_mkstemp(/srv/mail/.SiS/70002/a2/7b/.temp.blau.819.) failed: Permission denied dsync(test-1(a)example.com): Panic: file dsync-worker-local.c: line 1644 (local_worker_save_msg_continue): assertion failed: (ret == -1) dsync(test-1(a)example.com): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x4faf1) [0x7f4db31f4af1] -> /usr/local/lib/dovecot/libdovecot.so.0(default_error_handler+0) [0x7f4db31f4b7d] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f4db31f4e01] -> dsync() [0x416af8] -> dsync() [0x416e46] -> dsync(dsync_worker_msg_save+0x82) [0x412cb2] -> dsync() [0x40b7e0] -> dsync() [0x417286] -> dsync() [0x417324] -> dsync(dsync_worker_msg_get+0xa8) [0x412dd4] -> dsync() [0x40bbf3] -> dsync() [0x40bd62] -> dsync() [0x40c106] -> dsync() [0x40c318] -> dsync(dsync_brain_msg_sync_new_msgs+0x1c) [0x40c336] -> dsync(dsync_brain_msg_sync_more+0x1ae) [0x40b15e] -> dsync() [0x409b88] -> dsync(dsync_brain_sync+0x231) [0x40a074] -> dsync() [0x4084fb] -> dsync() [0x408729] -> dsync(dsync_brain_sync+0x1a7) [0x409fea] -> dsync() [0x408238] -> dsync() [0x408388] -> dsync(dsync_brain_sync+0x10b) [0x409f4e] -> dsync(dsync_brain_sync_all+0x24) [0x40a16b] -> dsync(main+0x680) [0x407b2b ] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7f4db2e3fead] -> dsync() [0x406e09] Aborted (core dumped) Looks like Dovecot ignores the ACL. I think a mail_attachment_dir_mode setting could help to work around this problem. Dunno what would be a good default value. But I would set mail_attachment_dir_mode = 0770 The attachment files have mode 0660, that's perfect in my setup. Regards, Pascal -- The trapper recommends today: c01dcafe.1134404(a)localdomain.org

2 2

Re: [Dovecot] Crash on mail folder delete
by Daniel L. Miller 09 Feb '12

09 Feb '12

On 1/25/2012 3:43 PM, Daniel L. Miller wrote: > On 1/25/2012 3:42 PM, Timo Sirainen wrote: >> On 26.1.2012, at 1.37, Daniel L. Miller wrote: >> >>> Attempting to delete a folder from within the trash folder using >>> Thunderbird. I see the following in the log: >> Dovecot version? >> > 2.1.rc3. I'm compiling rc5 now... > Error still there on rc5. Jan 25 16:03:47 bubba dovecot: imap(dmiller(a)amfes.com): Panic: file mailbox-list-fs.c: line 156 (fs_list_get_path): assertion failed: (mailbox_list_is_valid_pattern(_list, name)) Jan 25 16:03:47 bubba dovecot: imap(dmiller(a)amfes.com): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x3f1ba) [0x7f7c3f0331ba] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x3f206) [0x7f7c3f033206] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x1804a) [0x7f7c3f00c04a] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0x47317) [0x7f7c3f2c0317] -> /usr/local/lib/dovecot/lib01_acl_plugin.so(+0x6c71) [0x7f7c3dc48c71] -> /usr/local/lib/dovecot/lib01_acl_plugin.so(+0x6d47) [0x7f7c3dc48d47] -> /usr/local/lib/dovecot/lib01_acl_plugin.so(acl_mailbox_allocated+0x9e) [0x7f7c3dc4c61e] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(hook_mailbox_allocated+0x62) [0x7f7c3f2b4662] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_alloc+0xb2) [0x7f7c3f2b3482] -> dovecot/imap [dmiller(a)amfes.com 192.168.0.91 delete](cmd_delete+0x72) [0x409972] -> dovecot/imap [dmiller(a)amfes.com 192.168.0.91 delete](command_exec+0x3d) [0x4109fd] -> dovecot/imap [dmiller(a)amfes.com 192.168.0.91 delete]() [0x40f9ce] -> dovecot/imap [dmiller(a)amfes.com 192.168.0.91 delete]() [0x40faad] -> dovecot/imap [dmiller(a)amfes.com 192.168.0.91 delete](client_handle_input+0x135) [0x40fcd5] -> dovecot/imap [dmiller(a)amfes.com 192.168.0.91 delete](client_input+0x5f) [0x4105ff] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x36) [0x7f7c3f03f5d6] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x9f) [0x7f7c3f04065f] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x28) [0x7f7c3f03f578] -> /usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f7c3f02c593] -> dovecot/imap [dmiller(a)amfes.com 192.168.0.91 delete](main+0x2a5) [0x418a55] -> /lib/libc.so.6(__libc_start_main+0xfe) [0x7f7c3ec8fd8e] -> dovecot/imap [dmiller(a)amfes.com 192.168.0.91 delete]() [0x408449] Jan 25 16:03:48 bubba dovecot: imap(dmiller(a)amfes.com): Panic: file mailbox-list-fs.c: line 156 (fs_list_get_path): assertion failed: (mailbox_list_is_valid_pattern(_list, name)) Jan 25 16:03:48 bubba dovecot: imap(dmiller(a)amfes.com): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x3f1ba) [0x7f9e52e211ba] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x3f206) [0x7f9e52e21206] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x1804a) [0x7f9e52dfa04a] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0x47317) [0x7f9e530ae317] -> /usr/local/lib/dovecot/lib01_acl_plugin.so(+0x6c71) [0x7f9e51a36c71] -> /usr/local/lib/dovecot/lib01_acl_plugin.so(+0x6d47) [0x7f9e51a36d47] -> /usr/local/lib/dovecot/lib01_acl_plugin.so(acl_mailbox_allocated+0x9e) [0x7f9e51a3a61e] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(hook_mailbox_allocated+0x62) [0x7f9e530a2662] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_alloc+0xb2) [0x7f9e530a1482] -> dovecot/imap [dmiller(a)amfes.com 192.168.0.91 delete](cmd_delete+0x72) [0x409972] -> dovecot/imap [dmiller(a)amfes.com 192.168.0.91 delete](command_exec+0x3d) [0x4109fd] -> dovecot/imap [dmiller(a)amfes.com 192.168.0.91 delete]() [0x40f9ce] -> dovecot/imap [dmiller(a)amfes.com 192.168.0.91 delete]() [0x40faad] -> dovecot/imap [dmiller(a)amfes.com 192.168.0.91 delete](client_handle_input+0x135) [0x40fcd5] -> dovecot/imap [dmiller(a)amfes.com 192.168.0.91 delete](client_input+0x5f) [0x4105ff] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x36) [0x7f9e52e2d5d6] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x9f) [0x7f9e52e2e65f] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x28) [0x7f9e52e2d578] -> /usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f9e52e1a593] -> dovecot/imap [dmiller(a)amfes.com 192.168.0.91 delete](main+0x2a5) [0x418a55] -> /lib/libc.so.6(__libc_start_main+0xfe) [0x7f9e52a7dd8e] -> dovecot/imap [dmiller(a)amfes.com 192.168.0.91 delete]() [0x408449] Jan 25 16:03:48 bubba dovecot: imap(dmiller(a)amfes.com): Fatal: master: service(imap): child 3300 killed with signal 6 (core dumps disabled) Jan 25 16:03:48 bubba dovecot: imap(dmiller(a)amfes.com): Fatal: master: service(imap): child 3267 killed with signal 6 (core dumps disabled) -- Daniel

2 1

[Dovecot] BUG(?): Incorrect responses for ACL prohibited actions
by Michael M Slusarz 09 Feb '12

09 Feb '12

In a mailbox that has ACL restrictions on both DELETE and EXPUNGE (i.e. no 'e' or 't' rights), I see the following: 3 UID STORE 3173 (UNCHANGEDSINCE 353) +FLAGS \deleted 3 OK Store completed. (UID 3173 is not flagged \deleted) [...] 6 UID EXPUNGE 1:* 6 OK Expunge completed. (At least 1 UID is flagged \deleted in mailbox) Shouldn't these commands be returning "NO" instead of "OK"? RFC 3501 [6.4.6] for STORE: NO - store error: can't store that data and RFC RFC 3501 [6.4.3] for EXPUNGE: NO - expunge failure: can't expunge (e.g., permission denied) Additionally, RFC 5530 [3] provides the NOPERM response code: NOPERM The access control system (e.g., Access Control List (ACL), see [RFC 4314]) does not permit this user to carry out an operation, such as selecting or creating a mailbox. C: f select "/archive/projects/experiment-iv" S: f NO [NOPERM] Access denied My reading of this is that NOPERM should be returned for ANY ACL prohibited action, not just for selecting or creating a mailbox. Dovecot 2.0.12 does not return NOPERM for DELETE/EXPUNGE actions (at a minimum) that are prohibited. Thoughts? michael

2 3

[Dovecot] [dovecot] Getting duplicates when using snarf plugin with mbox backend
by Jonathan SIegle 09 Feb '12

09 Feb '12

Running dovecot version 2.0.11. To reproduce, open two imap sessions and issue a check command from each at the same time with new mail in the queue. 0 login testuser testpw 1 select inbox -- Deliver mail -- 2 check Thanks, Jonathan

2 1

[Dovecot] POP3 UIDLs with virtual INBOX and migration from maildir->mdbox
by Peter Mogensen 09 Feb '12

09 Feb '12

Hi, Considering the scenario, where you have some old account with a different POP3 UIDL format and you migrate them to dovecot. So these old UIDLs would be saved to dovecot-uidlist. At some later time you want to introduce a virtual POP3 INBOX like described on: http://wiki.dovecot.org/Plugins/Virtual So you decide to make the new UIDL format "%f" - to make them unique across folders. So far so good. But then you decide to migrate to mdbox with all your old UIDLs. The docs says that saving old UIDLs is only supported in Maildir and that %f is only supported in Maildir. So is this at all possible? Would pop3_uidl_format = %g solve this (except for the old legacy UIDL's) ? /Peter

2 1

[Dovecot] vsz_limit
by Héctor Moreno Blanco 09 Feb '12

09 Feb '12

Hello Timo and dovecot teamwork, We have dovecot 2.0.10 installed with this configuration: # dovecot -n # 2.0.10: /usr/local/dovecot/etc/dovecot/dovecot.conf # OS: Linux 2.6.18-92.1.18.el5 x86_64 Scientific Linux SL release 5.2 (Boron) auth_cache_size = 500 k auth_cache_ttl = 1000 secs disable_plaintext_auth = no first_valid_uid = 501 lock_method = dotlock mail_fsync = always mail_gid = vmail mail_location = maildir:%h/Maildir mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = quota autocreate mail_uid = vmail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date mmap_disable = yes namespace { inbox = yes location = prefix = separator = . type = private } namespace { hidden = yes inbox = no list = no location = prefix = INBOX. separator = . type = private } namespace { location = maildir:%h/Maildir/_backup prefix = _backup. separator = . type = private } passdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } plugin/autocreate = Spam plugin/autosubscribe = Spam plugin/quota = maildir:_backup:ns= plugin/quota_warning = storage=75%% quota-warning 75 %u plugin/quota_warning2 = storage=90%% quota-warning 90 %u plugin/sieve = %h/.dovecot.sieve plugin/sieve_dir = %h/sieve protocols = imap pop3 sieve service anvil { client_limit = 5000 } service auth { client_limit = 9000 unix_listener auth-master { group = vmail mode = 0700 user = vmail } user = root vsz_limit = 2 G } service imap-login { executable = /usr/local/dovecot/libexec/dovecot/imap-login inet_listener imap { address = * port = 143 } inet_listener imaps { address = * port = 993 } process_limit = 2048 process_min_avail = 20 user = vmail } service imap { executable = /usr/local/dovecot/libexec/dovecot/imap process_limit = 2048 } service managesieve-login { executable = /usr/local/dovecot/libexec/dovecot/managesieve-login inet_listener sieve { address = * port = 4190 } inet_listener sieve_deprecated { address = * port = 12000 } user = vmail } service managesieve { executable = /usr/local/dovecot/libexec/dovecot/managesieve } service pop3-login { executable = /usr/local/dovecot/libexec/dovecot/pop3-login inet_listener pop3 { address = * port = 110 } inet_listener pop3s { address = * port = 995 } process_limit = 2048 process_min_avail = 20 user = vmail } service pop3 { executable = /usr/local/dovecot/libexec/dovecot/pop3 process_limit = 2048 } service quota-warning { executable = script /usr/local/dovecot/bin/quota-warning.sh unix_listener quota-warning { group = vmail mode = 0700 user = vmail } } ssl_cert = </etc/ssl/correo_xxxx.crt ssl_key = </etc/ssl/correo_xxxx.pem syslog_facility = local3 userdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } valid_chroot_dirs = /buzones/ protocol imap { imap_client_workarounds = mail_plugin_dir = /usr/local/dovecot/lib/dovecot mail_plugins = quota autocreate imap_quota } protocol pop3 { mail_plugin_dir = /usr/local/dovecot/lib/dovecot mail_plugins = quota autocreate pop3_uidl_format = %08Xu%08Xv } protocol lda { auth_socket_path = /usr/local/dovecot/var/run/dovecot/auth-master hostname = buzon.xxxx.es mail_plugin_dir = /usr/local/dovecot/lib/dovecot mail_plugins = quota autocreate sieve postmaster_address = postmaster(a)xxxx.es quota_full_tempfail = no rejection_reason = Su mensaje para <%t> fue rechazado automaticamente por nuestro sistema :%n%r rejection_subject = Rechazado: %s sendmail_path = /usr/sbin/exim } protocol sieve { managesieve_implementation_string = dovecot Pigeonhole managesieve_logout_format = bytes ( in=%i : out=%o ) managesieve_max_line_length = 65536 } The problem is at the moment of maximum load of the system. We can see many imap sessions but there are also many imap-login processes, which is weird. Has it something to do with any parameter of our configuration? We think is something with the vsz_limit parameter. How can we tune it? Thank you very much in advanced. Kind regards. ________________________________ [cid:image001.gif@01CCE647.65B8FB30] Héctor Moreno Blanco División de Seguridad e Infraestructuras / Security and Infrastructures Division GMV Isaac Newton, 11 P.T.M. Tres Cantos E-28760 Madrid Tel. +34 91 807 21 00 Fax +34 91 807 21 99 www.gmv.com <http://www.gmv.com/> [cid:image002.gif@01CCE647.65B8FB30]<http://www.gmv.com/b2_gmv> [cid:image003.gif@01CCE647.65B8FB30]<http://www.facebook.com/infoGMV> [cid:image004.gif@01CCE647.65B8FB30]<http://www.twitter.com/infoGMV_es> [cid:image005.gif@01CCE647.65B8FB30]<http://www.youtube.com/infoGMV> ______________________ This message including any attachments may contain confidential information, according to our Information Security Management System, and intended solely for a specific individual to whom they are addressed. Any unauthorised copy, disclosure or distribution of this message is strictly forbidden. If you have received this transmission in error, please notify the sender immediately and delete it. ______________________ Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede contener informacion clasificada por su emisor como confidencial en el marco de su Sistema de Gestion de Seguridad de la Informacion siendo para uso exclusivo del destinatario, quedando prohibida su divulgacion copia o distribucion a terceros sin la autorizacion expresa del remitente. Si Vd. ha recibido este mensaje erroneamente, se ruega lo notifique al remitente y proceda a su borrado. Gracias por su colaboracion. ______________________

3 5

[Dovecot] fts (lucene): indexing of virtual mailboxes?
by Lutz Preßler 09 Feb '12

09 Feb '12

Hello, (recent 2.1alpha2 variant - my test setup known to Timo). No time to diagnose in depth at the moment, but I just noticed that SEARCHing in virtual mailboxes seems not to create lucene index content of its own but use those of referenced mailboxes? The problem is that no new indexing takes place. Example: with INBOX INBOX.in% all in dovecot-virtual, for a given query I only get matches from those mailboxes searched in previously. Regards, Lutz

2 2

Re: [Dovecot] Performance of Maildir vs sdbox/mdbox
by Lee Standen 09 Feb '12

09 Feb '12

On 18.01.2012 21:54, Timo Sirainen wrote: > On Wed, 2012-01-18 at 20:44 +0800, Lee Standen wrote: > >> I've been desperately trying to find some comparative performance >> information about the different mailbox formats supported by Dovecot >> in >> order to make an assessment on which format is right for our >> environment. > > Unfortunately there aren't really any. Everyone who seems to switch > to > sdbox/mdbox usually also change their hardware at the same time, so > there aren't really any before/after metrics. I've of course some > unrealistic synthetic benchmarks, but I don't think they are very > useful. > > So, I would also be very interested in seeing some before/after > graphs > of disk IO, CPU and memory usage of Maildir -> dbox switch in same > hardware. > > Maildir is anyway definitely worse performance then sdbox or mdbox. > mdbox also uses less NFS operations, but I don't know how much faster > (if any) it is with Netapps. We have bought new hardware for this project too, so we might not be able to help out massively on that front... we do have NFS operations monitored though so we should at least be able to compare that metric since the underlying storage operating system is the same. All NetApp hardware runs their Data ONTAP operating system, so the metrics are assured to be the same :) How about this... are there any tools available (that you know of) to capture real live customer POP3/IMAP traffic and replay it against a separate system? That might be a feasible option for doing a like-for-like comparison in our environment? We could probably get something in place to simulate the load if we can do something like that... >> * All mail storage presented via NFS over 10Gbps Ethernet (Jumbo >> Frames) >> >> * Postfix will feed new email to Dovecot via LMTP >> >> * Dovecot servers have been split based on their role >> >> - Dovecot LDA Servers (running LMTP protocol) >> >> - Dovecot POP/IMAP servers (running POP/IMAP protocols) > > You're going to run into NFS caching troubles with the above split > setup. I don't recommend it. You will see error messages about index > corruption with it, and with dbox it can cause metadata loss. > http://wiki2.dovecot.org/NFS http://wiki2.dovecot.org/Director That might be the one thing (unfortunately) which prevents us from going with the dbox format. I understand the same issue can actually occur on Dovecot Maildir as well, but because Maildir works without these index files, we were willing to just go with it. I will raise it again, but there has been a lot of push back about introducing a single point of failure, even though this is a perceived one. The biggest challenge I have at the moment if I try to sell the dbox format is providing some kind of data on the expected gains from this. If it's only a 10% reduction in NFS operations for the typical user, then it's probably not worth our while. > >> - LDA & POP/IMAP servers are segmented into geographically split >> groups >> (so no server sees every single mailbox) >> >> - Nginx proxy used to terminate customer connections, connections >> are >> redirected to the appropriate geographic servers > > Can the same mailbox still be accessed via multiple geographic > servers? > I've had some plans for doing this kind of access/replication using > dsync.. No, we're using the nginx proxy layer to ensure that if a user in Sydney (for example) tries to access a Perth mailbox, their connection is redirected (by nginx) to the Perth POP/IMAP servers. Postfix configuration is handling the same thing on the LMTP side. The requirement here is for all users to have the same settings regardless of location, but still be able to locate the email servers and data close to the customer. > >> * Apache Lucene indexes will be used to accelerate IMAP search for >> users > > Dovecot's fts-solr or fts-lucene? fts-solr. I've been using Lucene/Solr interchangeably when discussing this project with my peers :) > >> Our closest current live configuration (Qmail SMTP, Courier IMAP, >> Maildir) >> has 600K mailboxes and pushes ~ 35,000 NFS operations per second at >> peak >> >> Some of the things I would like to know: >> >> * Are we likely to see a reduction in IOPS/User by using Maildir >> alone under >> Dovecot? > > If you have webmail type of clients, definitely. For > Outlook/Thunderbird > you should still see improvement, but not necessarily as much. > > You didn't mention POP3. That isn't Dovecot's strong point. Its > performance should be about the same as Courier-POP3, but could be > less > than QMail-POP3. Although if many of your POP3 users keep a lot of > mails > on server it > Our existing systems run with about 21K concurrent IMAP connections at any one point in time, not counting Webmail POP3 runs at about 3600 concurrent connections, but since those are not long lived it's not particularly indicative of customer numbers. Vague recollection is something like 25% IMAP, 55-60% POP3, rest < 20% Webmail. I'd have to go back and check the breakdown again. >> * If someone can give some technical reasoning behind why mdbox does >> less >> IOPS than Maildir? > > Maildir renames files a lot. From new/ -> to cur/ and then every time > message flag changes. That's why sdbox is faster. Why mdbox should be > faster than sdbox is because mdbox puts (or should put) more mail > data > physically closer in disks to make reading it faster. > >> I understand some of the reasons for the mdbox IOPS question, but I >> need >> some more information so we can discuss internally and make a >> decision as to >> whether we're comfortable going with mdbox from day one. We're very >> familiar with Maidlir, and there's just some uneasiness internally >> around >> going to a new mail storage format. > > It's at least safer to first switch to Dovecot+Maildir to make sure > that > any problems you might find aren't related to the mailbox format.. Yep, I'm considering that. The flip side is that it's actually going to be difficult for us to change mail format once we've migrated into this system, but we have an opportunity for (literally) a month long testing phase beginning in Feb/March which will let us test as many possibilities as we can.

4 16

[Dovecot] [PATCH] Bad boundary check in client_find_namespace
by Christoph Bussenius 09 Feb '12

09 Feb '12

Hi, while trying to investigate the bug I reported last week, I found that there is a broken boundary check in client_find_namespace in src/imap/imap-commands-util.c. The code is: /* make sure two hierarchy separators aren't next to each others */ for (p = storage_name+1; *p != '\0'; p++) { if (p[0] == ns->real_sep && p[-1] == ns->real_sep) { client_send_tagline(cmd, "NO Invalid mailbox name."); return NULL; } } The loop iterates over the string storage_name starting from its second byte. However, the string may be "". This is the case if you select the root of a namespace, like in "SELECT shared" or "SELECT shared/user1". In that case, the code will read past the end of the buffer from random memory until it finds a zero byte or a duplicate separator. This would fix it: diff -ru dovecot-2.0.15.orig/src/imap/imap-commands-util.c dovecot-2.0.15/src/imap/imap-commands-util.c --- dovecot-2.0.15.orig/src/imap/imap-commands-util.c 2011-08-02 12:29:37.000000000 +0200 +++ dovecot-2.0.15/src/imap/imap-commands-util.c 2011-09-26 18:33:16.121917759 +0200 @@ -81,7 +81,9 @@ } /* make sure two hierarchy separators aren't next to each others */ - for (p = storage_name+1; *p != '\0'; p++) { + for (p = storage_name; *p != '\0'; p++) { + if (p == storage_name) + continue; if (p[0] == ns->real_sep && p[-1] == ns->real_sep) { client_send_tagline(cmd, "NO Invalid mailbox name."); return NULL; Cheers, Christoph Bußenius -- Christoph Bußenius Rechnerbetriebsgruppe der Fakultäten Informatik und Mathematik TU München +49 89-289-18519 <> Raum 00.05.055 <> Boltzmannstr. 3 <> Garching

3 2

[Dovecot] 2.0.14 doveadm proxy list segfault
by Tom Pawlowski 09 Feb '12

09 Feb '12

Hi Timo, Periodic segfaults with doveadm proxy list: root@director1:~) doveadm proxy list doveadm(root): Error: LIST failed: Disconnected Segmentation fault (core dumped) Sometimes it's just the 'LIST failed' error, other times it's the error with the segfault. Usually the first attempt to call it works, subsequent attempts fail. I've attached a strace log of it in action. -- Tom Pawlowski OIT-CSS System Administrator office: Hill 147 email: tompru(a)jla.rutgers.edu phone: (732) 445-2634

2 1

[Dovecot] Syncing shared mailboxes
by Knud Dombrowsky 09 Feb '12

09 Feb '12

Hi, while trying to sync the mailboxes of several users who use and share their mailboxes dsync prints this message: dsync-local(<user-who-uses-shared-mailbox>): Warning: Subscriptions file /home/<user-who-uses-shared-mailbox>/Maildir/subscriptions: Removing invalid entry: shared/<sharing-user>/<shared-folder> The problem is: Every user has to subscribe the shared folder again after each run of dsync... Is dsync capable of syncing shared mailboxes? Are there any preliminaries to do so? thanks in advance, Knud

2 1

[Dovecot] crash on shared folders if remote user has empty $home
by Peer Heinlein 09 Feb '12

09 Feb '12

Hi, in seldom cirumstances it's possible that the imap-process is crashing without write something usefule into the logfile. a) User foo exists, is happy and everything's alright b) He had a shared folder given from bar c) In our setup we have mailforwarding adresses without a valid $home in LDAP c) if user bar is changed from a user with into a mailforwarding adress, the user foo won't have an entry for $home any more, but still exists in LDAP. d) If foo logs in, dovecot's exploring the shared folders given from the non-existing user bar. But bar's entry in LDAP doesn't have $home any more. imap crashes and closes the TCP-connection immediately. root@dobby2:/etc/dovecot# telnet xxxxxxxx 143 Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE ACL UIDPLUS STARTTLS AUTH=PLAIN AUTH=LOGIN AUTH=CRAM-MD5 AUTH=DIGEST-MD5] Dovecot ready. Testing. a LOGIN foo xxxxx a OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS ACL UIDPLUS QUOTA ACL RIGHTS=texk] Logged in a LIST "" "*" * BYE Internal error occurred. Refer to server log for more information. Connection closed by foreign host. Dec 22 21:57:41 dobby2 dovecot: master: Error: service(imap): child 18095 killed with signal 11 (core dumps disabled) e) This happens if mail_location=mdbox:%%h/mdbox is set in the shared folder namespace. If I set "mail_location=auto:" then Dovecot logs an error message, but is still possible to continue without any problems. Dec 22 21:33:59 dobby2 dovecot: imap(bar): Error: Namespace 'shared/bar/': Autodetection failed for auto: (home=/mail/foo/) -- Heinlein Professional Linux Support GmbH Linux: Akademie - Support - Hosting http://www.heinlein-support.de Tel: 030 / 40 50 51 - 0 Fax: 030 / 40 50 51 - 19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

2 2

[Dovecot] LSUB and subscribed folders
by Peer Heinlein 09 Feb '12

09 Feb '12

I have a strange behavior on a customer's server and I don't understand that: User "bar" has some folders and one shared folder from "foo" if I use the "LIST"-command, which should list AFAIK *all* folders: # telnet localhost 143 a login bar xxxx a OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS ACL RIGHTS=texk] Logged in a LIST "" "*" * LIST (\HasNoChildren) "/" "Gesendete Objekte" * LIST (\HasNoChildren) "/" "Papierkorb" * LIST (\HasNoChildren) "/" "INBOX" * LIST (\HasNoChildren) "/" "Trash" * LIST (\HasNoChildren) "/" "Entw&APw-rfe" * LIST (\HasNoChildren) "/" "Spam" * LIST (\Noselect \HasChildren) "/" "shared/foo" * LIST (\HasNoChildren) "/" "shared/foo/INBOX" a OK List completed. Using the LSUB-command, which should only list subscribed folders I can see some more shared folders. AFAIK the output of LSUB must be always less then LIST: a LSUB "" "*" * LSUB () "/" "Entw&APw-rfe" * LSUB () "/" "Gesendete Objekte" * LSUB () "/" "INBOX" * LSUB () "/" "Papierkorb" * LSUB () "/" "Spam" * LSUB () "/" "Trash" * LSUB (\Noselect) "/" "shared/amerkel" * LSUB () "/" "shared/foo/Papierkorb/Ungelesene Mails" * LSUB () "/" "shared/foo/INBOX" * LSUB () "/" "shared/foo/INBOX/abc/Unterebene 1" * LSUB () "/" "shared/foo/INBOX/abc/Unterebene 1/Test6789" * LSUB () "/" "shared/foo/INBOX/abc/Unterebene 1/Test Unterornder" * LSUB () "/" "shared/foo/INBOX/abc/Unterebene 1/Tsfgnksfgnk" a OK Lsub completed. a logout * BYE Logging out a OK Logout completed. And why is /shared/foo/INBOX listed with "HasNoChildren"? IMHO that's looking buggy. And, btw: Looks like's not possible to use the "doveadm"-command to get a list of a user's complete folder list. Maybe "doveadm mailbox" should get some extra parameters to geht all folders / only subscribe folders / only shared folders: # doveadm mailbox list -u bar Gesendete Objekte Papierkorb INBOX Trash Entwürfe Spam -- Heinlein Professional Linux Support GmbH Linux: Akademie - Support - Hosting http://www.heinlein-support.de Tel: 030/405051-42 Fax: 030/405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

3 2

[Dovecot] doveadm altmove fails to pack messages?
by Lauri Alanko 09 Feb '12

09 Feb '12

Hello again. When I use doveadm altmove, I notice that it may result in some very small storage files in either the primary or the alternate storage location. I'm not quite sure, but it almost seems like every storage file that contains messages to be moved is simply split into two parts, even if a part might only contain a single message. This seems quite curious, since the idea of mdbox is after all to store as many messages in a single file as fits in mdbox_rotate_size, and dovecot-lda can quite successfully append messages to existing storage files. So why can't doveadm altmove? Is this the expected behavior, or is there something wrong with my setup? Thanks again, Lauri

2 1

[Dovecot] force-resync fails to recover all messages in mdbox
by Lauri Alanko 09 Feb '12

09 Feb '12

To my understanding, when using mdbox, doveadm force-resync should be able to recover all the messages from the storage files alone, though of course losing all metadata except the initial delivery folder. However, this does not seem to be the case. For me, force-resync creates only partial indices that lose messages. The message contents are of course still in the storage files, but dovecot just doesn't seem to be aware of some of them after recreating the indices. Here is an example. I created a test mdbox by syncing a mailing list folder from a mbox location: $ dsync -m haskell-cafe backup mdbox:~/dbox Then I switched the location to the new mdbox: $ /usr/sbin/dovecot -n # 2.0.15: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-0.bpo.1-amd64 x86_64 Debian wheezy/sid mail_fsync = never mail_location = mdbox:~/dbox mail_plugins = zlib passdb { driver = pam } plugin { sieve = ~/etc/sieve/dovecot.sieve sieve_dir = ~/etc/sieve zlib_save = bz2 zlib_save_level = 9 } protocols = " imap" ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = passwd } protocol lda { mail_plugins = zlib sieve } Then I checked the number of messages we had in the new location: $ doveadm search all | wc 93236 186472 3625098 This was indeed the correct number, so the sync was fine: $ grep -c '^From .*..:..:.. ....$' ../mbox/haskell-cafe 93237 Then I removed all the indices and rebuilt them: $ mkdir bak $ mv mailboxes bak $ mv storage/dovecot.map.index* bak/ $ doveadm force-resync inbox doveadm(la): Warning: mdbox /home/la/dbox/storage: rebuilding indexes And what have we now: $ doveadm search all | wc 43864 87728 1699590 Somehow dovecot lost over half of the messages! This is really worrisome. It should always be possible to extract the plain mail content out from the storage, but currently it only _looks_ like it is possible: you get a problem in the indices, rebuild them, and then later migrate somewhere else. If you don't notice that you are missing mails, you may then eventually destroy the original mdbox storage files, thinking that their content is now safely elsewhere, when it really isn't. Lauri

2 3

[Dovecot] Fedora 16 configuration
by Cliff Hayes 08 Feb '12

08 Feb '12

Hello, I am trying to get dovecot to work on a fedora 16 install with sendmail. I have been able to get it to work in the past with dovecot.conf but not with the new conf.d directory and associated config files. I keep seeing this in maillog: Feb 7 14:28:59 sendmail dovecot: pop3-login: Aborted login (no auth attempts): rip=x.x.x.x, lip=x.x.x.x And the mail client comes back with username or password invalid. Is there instructions somewhere regarding fedora 16 installs? I found this one and tried it to no avail: http://www.server-world.info/en/note?os=Fedora_16&p=mail&f=2 Thanks in advance, Cliff

2 1

[Dovecot] openbsd and dovecot
by User Max 08 Feb '12

08 Feb '12

I'm setting up dovecot in OpenBSD OS. The problem is that I can't set up dovecot to use kerberos authentication via bsdauth which is "similar to pam" I try to test dovecot via telnet: telnet localhost pop3 user test +OK pass password -ERR [IN-USE] Temporary authentication failure and some strings from logs Feb 3 15:02:37 srv-mx-00 dovecot: auth: Error: bsdauth(rodin.m,127.0.0.1): getpwnam() failed: Operation not permitted Feb 3 15:02:46 srv-mx-00 dovecot: pop3-login: Disconnected (auth failed, 1 attempts): user=<rodin.m>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Feb 3 15:29:13 srv-mx-00 dovecot: auth: Error: bsdauth(test,127.0.0.1): getpwnam() failed: Operation not permitted What am I doing wrong? Here is the output of dovecot -n auth_krb5_keytab = /etc/kerberosV/krb5.keytab auth_mechanisms = plain login default_internal_user = _dovecot default_login_user = _dovenull disable_plaintext_auth = no first_valid_gid = 2000 first_valid_uid = 2000 last_valid_gid = 2000 last_valid_uid = 2000 mail_gid = vmail mail_location = maildir:/var/vmail/%u%Ud/Maildir mail_uid = vmail mbox_write_locks = fcntl mmap_disable = yes passdb { driver = bsdauth } service auth { unix_listener /var/spool/postfix/private/auth { group = _postfix mode = 0666 user = _postfix } } ssl_cert = </etc/ssl/dovecotcert.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = passwd } userdb { args = uid=2000 gid=2000 home=/var/mail/%Lu driver = static } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags } protocol pop3 { pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv }

3 3

[Dovecot] Slightly more intelligent way of handling issues in sdbox?
by Mark Zealey 08 Feb '12

08 Feb '12

Hi there, I was doing some testing on sdbox yesterday. Basically I did the following procedure: 1) Create new sdbox; deliver 2 messages into it (u.1, u.2) 2) Create a copy of the index file (no cache file created yet) 3) deliver another message to the mailbox (u.3) 4) copy back index file from stage (2) 5) deliver new mail Then the message delivered in stage 3 ie u.3 gets replaced with the message delivered in (5) also called u.3. Is it possible to try an open/access call on the mail file before overwriting it with the new message in case we have an issue where an older version of the index file is present (eg due to nfs latencies) ? I notice when you are expunging files you very carefully open them and read the header contents to make sure the guid is the same as in the index - any reason that this is not done when delivering? This is with lmtp on dovecot 2.0.16. I also noticed that index corruption in sdbox does not get automatically repaired. I know this is because the flags are stored in the index files so you'd get some loss of flags, but in many situations for us this auto-repair with flag loss would be better than having the mailbox locked out until we manually do a force-resync on it. (speaking of which, it would be great if force-resync also rebuilt the cache files if there are valid cache files around, rather than just doing away with them) Thanks, Mark

3 4

[Dovecot] user login on behalf of another user
by rog7993＠web.de 07 Feb '12

07 Feb '12

Hello, we are searching for a possibility to configure a user login on behalf of another user with a PAM backend. This reminds to the behavior of a master user. But a master user can access the mailboxes of all users. We need this more restricted. Example: User "user1" and "user2" shall get access to the mailbox "info". We define the accounts "info~user1" and "info~user2" with the same home directory like "info". Until now, we use a passwd-file backend. With this setup we can simply copy the password hash from "user1" to "info~user1" and from "user2" to "info~user2". But we intend to change the passdb backend from a flat file to PAM for authentication against Active Directory. This seems to be simple with pam_krb5. But then we can't simply copy password hashes anymore. Is their another possibility for configuring this? Surely the preferable alternative would be the use of ACLs to give acccess to other users mailboxes. But we started this setup with Dovecot 1.0 or 1.1. And with these versions, ACLs weren't available. And now we have too much accounts and clients, which are configured this way and can't change this for the short term. The passdb/userdb file from the above example looks like this: info:!:501:501:Info:/home/mail01/info:: info~user1:PASSWORD_USER1:501:501:Info:/home/mail01/info:: \ userdb_mail=maildir:~/Maildir: \ INDEX=/srv/dovecot/index/info: \ CONTROL=/srv/dovecot/control/info info~user2:PASSWORD_USER2:501:501:Info:/home/mail01/info:: \ userdb_mail=maildir:~/Maildir: \ INDEX=/srv/dovecot/index/info: \ CONTROL=/srv/dovecot/control/info user1:PASSWORD_USER1:501:501:Info:/home/mail01/user1:: user2:PASSWORD_USER2:501:501:Info:/home/mail01/user2:: Ingo Rogalsky

4 5

[Dovecot] Multiple userdb possible?
by Nikolaos Milas 07 Feb '12

07 Feb '12

Hello, I am running v2.0.13. In my dovecot.conf I have: userdb { args = /etc/dovecot/dovecot-usrdb-ldap.conf driver = ldap } passdb { args = /etc/dovecot/dovecot-passdb-ldap.conf driver = ldap } Is it legitimate to include multiple ldap userdb's, like: userdb { args = /etc/dovecot/dovecot-usrdb-ldap1.conf driver = ldap } passdb { args = /etc/dovecot/dovecot-passdb-ldap1.conf driver = ldap } userdb { args = /etc/dovecot/dovecot-usrdb-ldap2.conf driver = ldap } passdb { args = /etc/dovecot/dovecot-passdb-ldap2.conf driver = ldap } If it is legitimate (in case configuration is different, please correct me), in which sequence userdb's are evaluated? Thanks, Nick

2 2

[Dovecot] Configuration problem?
by Anne Wilson 07 Feb '12

07 Feb '12

I have a new Scientific Linux 6.1 mail server (dovecot -n below) and am seeing the following in the logs, with no idea what is happening: --------------------- Dovecot Begin ------------------------ Dovecot was killed, and not restarted afterwards. **Unmatched Entries** dovecot: imap(anne): Connection closed bytes=205614/894243: 1 Time(s) dovecot: imap(anne): Disconnected: Logged out bytes=24296/89310: 1 Time(s) dovecot: imap(anne): Disconnected: Logged out bytes=24526/76772: 1 Time(s) dovecot: imap(anne): Disconnected: Logged out bytes=26254/75778: 1 Time(s) dovecot: imap(anne): Disconnected: Logged out bytes=27948/134120: 1 Time(s) dovecot: imap(anne): Disconnected: Logged out bytes=29304/116087: 1 Time(s) dovecot: imap(anne): Disconnected: Logged out bytes=34802/914087: 1 Time(s) dovecot: imap(anne): Disconnected: Logged out bytes=4457/11719: 1 Time(s) dovecot: imap(anne): Disconnected: Logged out bytes=5322/184434: 1 Time(s) dovecot: imap(anne): Disconnected: Logged out bytes=61388/106618: 1 Time(s) dovecot: imap(anne): Disconnected: Logged out bytes=6164/21347: 1 Time(s) dovecot: imap(anne): Disconnected: Logged out bytes=7914/89868: 1 Time(s) dovecot: imap: Server shutting down. bytes=1309821/4473013: 1 Time(s) dovecot: imap: Server shutting down. bytes=14215/97371: 1 Time(s) dovecot: imap: Server shutting down. bytes=1459/9382: 1 Time(s) dovecot: imap: Server shutting down. bytes=1688/26161: 1 Time(s) dovecot: imap: Server shutting down. bytes=1705/5038: 1 Time(s) dovecot: imap: Server shutting down. bytes=3146/79269: 1 Time(s) dovecot: master: Dovecot v2.0.9 starting up (core dumps disabled): 1 Time(s) ---------------------- Dovecot End ------------------------- dovecot -n # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-131.0.15.el6.x86_64 x86_64 Scientific Linux release 6.1 (Carbon) mail_location = maildir:~/Maildir/ mbox_write_locks = fcntl passdb { driver = pam } protocols = imap ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } /etc/dovecot/dovecot.conf: - everything being defaults, as far as I can see, apart from these lines: # Protocols we want to be serving. protocols = imap listen = *, :: mail_location = maildir:~/Maildir/ maildir_copy_with_hardlinks = yes Is it really expecting an mbox file? I'm completely bogged down with this - my previous setup was fine, but the old config file doesn't work with this system. Any help and/or pointers would be greatly appreciated. Anne

2 4

[Dovecot] dsync error Mailbox has children, delete them first
by Jürgen Obermann 07 Feb '12

07 Feb '12

Hi, I use dsync to backup mailboxes from mbox format to mdbox on a remote system. The first run for a user with dsync is OK, but during the second there are lots of the following errors: dsync-remote(user): Error: Can't delete mailbox directory Example: Mailbox has children, delete them first I see no way how I could influence the order dsync deletes mailboxes. This happens with dovecot version 2.0.16 Thank you, Juergen Obermann

1 1

[Dovecot] ENVELOPE mishandling of Subject lines with quote(s)?
by Dinh Le 06 Feb '12

06 Feb '12

Hi, I am running dovecot version 1.2.9 on a Ubuntu 10.04 server. To obtain the message's header info from this dovecot imap server, I run the following imap command on a client side's imap session: . fetch 88:90 (envelope) which returns (in this case) ------------------------------------------------------------- * 88 FETCH (ENVELOPE ("Tue, 28 Oct 2008 15:45:35 -0500" "Linear Actuators Bring Flexibility to Packaging" (("Design World" NIL "subscription" "designworldonline.com")) (("Design World" NIL "subscription" "designworldonline.com")) (("Design World" NIL "subscription" "designworldonline.com")) ((NIL NIL "dinh" "flic.net")) NIL NIL NIL "<490779CF.00000E7D(a)ak119.mta.exacttarget.com>")) * 89 FETCH (ENVELOPE ("29 Oct 2008 15:44:03 -0500" {65} 2nd Edition of Brennesholtz/Stupp "Projection Displays" Available (("Insight Media" NIL "administrator" "insightmedia.info")) (("Insight Media" NIL "administrator" "insightmedia.info")) (("Insight Media" NIL "administrator" "insightmedia.info")) ((NIL NIL "dinh" "flic.net")) NIL NIL NIL "<20081029154358.0C359AE169595F1B(a)insightmedia.info>")) * 90 FETCH (ENVELOPE ("Thu, 30 Oct 2008 04:24:31 +0800 (SGT)" "6 new products Now Online!" (("Global Sources Product Alert" NIL "paservices" "globalsources.com")) (("Global Sources Product Alert" NIL "paservices" "globalsources.com")) (("Global Sources Product Alert" NIL "paservices" "globalsources.com")) (("Dinh Le" NIL "dinh" "flic.net")) NIL NIL NIL "<352725277.1225311871753.JavaMail.web(a)fuchsia3.globalsources.com>")) . OK Fetch completed. -------------------------------------------------------------- Notice that message 89's Subject line Subject: 2nd Edition of Brennesholtz/Stupp "Projection Displays" Available has quotes and this dovecot's ENVELOPE response failed to get parsed by a popular Perl module (Mail::IMAPClient::BodyStructure::Envelope). I have a hunch that this is dovecot's fault but I could be wrong. How should dovecot (or any imap server) deal with Subject lines with quotes inside ENVELOPE? ENVELOPE seems to encapsulate most of the important information and its format can be parsed cleanly and quickly. I prefer to fetch ENVELOP, at this point, rather than the other alternatives. Thanks for your help, Dinh

4 7

[Dovecot] Question about quota configuration
by przemek.orzechowski＠makolab.pl 06 Feb '12

06 Feb '12

Hi This is my first post here so i will be as precise as i can I'm trying to setup a quota system using dovecot postfix and procmail dovecot version 1.2.9 postfix version 2.7.0 I have succesfully modified dovecot config to use fs quota system (so far imap and pop3) It reports correct quotas to imap and pop3 clients (both user and group) What im tryin to do now is to modify postfix->procmail->dovecot config in a way that if user is over quota mail delivery is delayed instead of bouncing. (is this possible?) Second thing i would like to achive is that when authenticated users close to quota/group quota for example 10MB to quota limit try sending email theyr mail is rejected and preferably an email is generated telling them to free some space for new mails first. (is such a thing possible?) MS Exchange servers have such a feature and I would like to get such a functionality on my linux mailserver I'm trying to prevent a situation when mails are lost due to quota problems. This setup was initially a typical virtualmin installation with a system on single partition. Thanks in advance for all Your suggestions

7 8

[Dovecot] dovecot-antispam 1.3 and dovecot 1.2.17 fails with spool2dir
by Benny Pedersen 06 Feb '12

06 Feb '12

or have i missed something in compile or configure in dovecot.conf ? running on gentoo so i can compile if need another option, i just like to have it working so each user can train bayes global db no matter what user agent users using

1 0

[Dovecot] doveadm purge on shared storage
by Jan-Frode Myklebust 06 Feb '12

06 Feb '12

We've finally (!) started to put some users on mdbox instead of maildir, and now I'm wondering about the purge step. As we're running GPFS for the mailboxes (and dovecot director in front of every dovecot service), is it important to run the "doveadm purge -u $user" on the same host as $user is logged into to avoid index corruption ? If so, will we need to run the "doveadm purge" trough the dovecot director as well? -jf

2 1

Re: [Dovecot] Sieve notify messages
by Stephan Bosch 05 Feb '12

05 Feb '12

On 2/5/2012 4:57 PM, Andreas Muehlemann wrote: > Hi Stephan > > Thank you very much, the encodeurl and ?body= are the trick! > For posterity, please reply to the mailing list as well, especially when it is a success message ;) Regards, Stephan. > > On 02/05/2012 04:46 PM, Stephan Bosch wrote: >> On 2/5/2012 4:00 PM, Andreas Muehlemann wrote: >>> Hi All >>> >>> I'm using dovecot 2.0.16 with the pigeonhole plugin 0.25. >>> >>> I'm trying to use the notifiy mechanism from sieve to send >>> notifications when a mail arrives in the mailbox. The message is >>> checked to be a 8bit message, otherwise it is replaced by the >>> default message "Notification of new message." How can I create a >>> 8bit message body within the sieve script that is accepted by the >>> notification process? >>> >>> e.g. >>> notify >>> :message "Subject: ${subject}" >>> "mailto:email@domain.com"; >>> >>> Do I have to put the message body into the :message string? Or how >>> can I define a custom message body that is accepted by notify? >> >> If I understand you correctly, the following should be the solution >> for your issue: >> >> <SCRIPT> >> require "enotify"; >> require "variables"; >> require "encoded-character"; >> >> # Percent-encode the UTF-8 message >> # (I'm using encoded-character here, but you can use UTF8 directly of >> course) >> set :encodeurl "message" "In ${unicode:d6}sterreich m${unicode:e4}ht >> Herr M${unicode:fc}ller seinen Rasen ${unicode:fc}brigens auch >> ${unicode:fc}ber dem Durchschnitt schnell."; >> >> # Send the notification >> notify :message "Herr M${unicode:fc}ller m${unicode:e4}ht seinen >> Rasen" "mailto:user@example.com?body=${message}"; >> </SCRIPT> >> >> This sends the following message: >> >> <MESSAGE> >> X-Sieve: Pigeonhole Sieve 0.3.0 >> Message-ID: <dovecot-sieve-1328456217-863910-0(a)host.example.com> >> Date: Sun, 05 Feb 2012 16:36:57 +0100 >> Subject: Herr =?utf-8?q?M=C3=BCller_m=C3=A4ht?= seinen Rasen >> From: Postmaster <postmaster(a)example.com> >> To: user(a)example.com >> Auto-Submitted: auto-notified; >> owner-email="234234234234(a)ext2.domain.tld" >> Precedence: bulk >> X-Priority: 3 (Normal) >> Importance: Normal >> MIME-Version: 1.0 >> Content-Type: text/plain; charset=UTF-8 >> Content-Transfer-Encoding: 8bit >> >> In Österreich mäht Herr Müller seinen Rasen übrigens auch über dem >> Durchschnitt schnell. >> </MESSAGE> >> >> Regards, >> >> Stephan >

1 0

[Dovecot] Sieve notify messages
by Andreas Muehlemann 05 Feb '12

05 Feb '12

Hi All I'm using dovecot 2.0.16 with the pigeonhole plugin 0.25. I'm trying to use the notifiy mechanism from sieve to send notifications when a mail arrives in the mailbox. The message is checked to be a 8bit message, otherwise it is replaced by the default message "Notification of new message." How can I create a 8bit message body within the sieve script that is accepted by the notification process? e.g. notify :message "Subject: ${subject}" "mailto:email@domain.com"; Do I have to put the message body into the :message string? Or how can I define a custom message body that is accepted by notify? Best regards Andreas

2 1

[Dovecot] What does this /var/log/maillog message means?
by Andre Lopes 04 Feb '12

04 Feb '12

Hi, I'm, trying to configure Devcot(2.0.9). Here is my dovecot.conf: [code] protocols = imap pop3 lmtp log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/home/vmail/%d/%n/Maildir ssl_cert = /etc/pki/dovecot/certs/dovecot.pem ssl_key = /etc/pki/dovecot/private/dovecot.pem namespace { type = private separator = . prefix = INBOX. inbox = yes } protocol lda { log_path = /home/vmail/dovecot-deliver.log auth_socket_path = /var/run/dovecot/auth-master postmaster_address = postmaster(a)mailserver.com } service auth { user = root } passdb { driver = sql args = /etc/dovecot/dovecot-sql.conf } userdb { driver = static args = uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes } [/code] I can start the service correctly: [code] [root@mailserver dovecot]# service dovecot start Starting Dovecot Imap: [ OK ] [/code] But when I go to "/var/log/maillog" I get this: [code] Feb 3 14:37:59 www dovecot: master: Warning: Killed with signal 15 (by pid=16757 uid=0 code=kill) Feb 3 14:38:03 www dovecot: master: Dovecot v2.0.9 starting up (core dumps disabled) [/code] What does this mean? I'm doing something that is not correct? Best Regards,

2 1

[Dovecot] Managesieve Build failure
by Ralf Hildebrandt 03 Feb '12

03 Feb '12

I pulled the recent dovecot-2.0-pigeonhole and dovecot 2.0.x trees and rebuild, got this error today: ... make[3]: Leaving directory /usr/src/dovecot-2.0/dovecot-2.0-pigeonhole/src/managesieve' make[2]: Leaving directory /usr/src/dovecot-2.0/dovecot-2.0-pigeonhole/src/managesieve' Making install in managesieve-login make[2]: Entering directory /usr/src/dovecot-2.0/dovecot-2.0-pigeonhole/src/managesieve-login' /bin/bash ../../libtool --tag=CC --mode=link gcc -I/usr/src/dovecot-2.0/dovecot-2.0/src/config -DPKG_LIBEXECDIR=\""/usr/local/libexec/dovecot"\" -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 -module -avoid-version -g -Wl,--as-needed -o libmanagesieve_login_settings.la -rpath /usr/local/lib/dovecot/settings libmanagesieve_login_settings_la-managesieve-login-settings.lo libmanagesieve_login_settings_la-managesieve-login-settings-plugin.lo -lrt gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/src/dovecot-2.0/dovecot-2.0 -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-dict -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-dns -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-mail -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-imap -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-fs -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-charset -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-index -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-storage -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-storage/index -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-storage/index/raw -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-master -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-settings -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-auth -I/usr/src/dovecot-2.0/dovecot-2.0/src/login-common -I../.. -I../../src/lib-managesieve -g -Wl,--as-needed -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 -MT managesieve-proxy.o -MD -MP -MF .deps/managesieve-proxy.Tpo -c -o managesieve-proxy.o managesieve-proxy.c managesieve-proxy.c: In function ‘managesieve_proxy_parse_line’: managesieve-proxy.c:334:19: error: ‘const struct login_settings’ has no member named ‘verbose_auth’ make[2]: *** [managesieve-proxy.o] Error 1 -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de

2 1

[Dovecot] Vacation via database
by list＠airstreamcomm.net 03 Feb '12

03 Feb '12

We are moving our inbound mail to use dovecot LMTP in the near future and we are looking for suggestions on how to implement a mysql based vacation system. If anyone has experience with this, good or bad please let us know.

5 6

[Dovecot] LDAP auth improvements
by Timo Sirainen 03 Feb '12

03 Feb '12

v2.1 supports now multiple LDAP fields in a template e.g.: user_attrs = \ homeDirectory=home, \ uidNumber=uid, \ gidNumber=gid, \ =mail=%{ldap:mailboxFormat}:%{ldap:homeDirectory} which is the same as: user_attrs = \ =home=%{ldap:homeDirectory}, \ =uid=%{ldap:uidNumber}, \ =gid=%{ldap:gidNumber}, \ =mail=%{ldap:mailboxFormat}:%{ldap:homeDirectory} I was also thinking about adding an alternative simplified syntax for this: user_attrs { home = %{ldap:homeDirectory} uid = %{ldap:uidNumber} gid = %{ldap:gidNumber} mail = %{ldap:mailboxFormat}:%{ldap:homeDirectory} } Any ideas for further improvements before I do this change? One thing I'm still wondering about is what I should do when LDAP returns multiple values. Like perhaps: acl_groups = %{ldap:aclGroups:,} Which would mean that all the aclGroups values would be joined together separated by "," characters. And a bit more complex with multiple gidNumbers: gid = %{ldap:gidNumber[0]} mail_access_groups = %{ldap:gidNumber[1:]:,}

2 1

[Dovecot] Errors starting Dovecot
by Andre Lopes 03 Feb '12

03 Feb '12

Hi, I'm new to Dovecot. I'm trying to start Dovecot(2.0.9) but I'm getting an error. I think the error is because I'm doing a tutorial for an old version of Devcot(1.x.x). What I get is the following: [code] [root@mailserver dovecot]# service dovecot start Starting Dovecot Imap: doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:1: protocols=imaps is no longer necessary, remove it doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:1: protocols=pop3s is no longer necessary, remove it doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:5: ssl_cert_file has been replaced by ssl_cert = <file doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:6: ssl_key_file has been replaced by ssl_key = <file doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:8: namespace private {} has been replaced by namespace { type=private } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:24: add auth_ prefix to all settings inside auth {} and remove the auth {} section completely doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:25: auth_user has been replaced by service auth { user } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:27: passdb sql {} has been replaced by passdb { driver=sql } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:31: userdb static {} has been replaced by userdb { driver=static } [ OK ] [/code] My dovecot.conf have the following: [code] protocols = imap imaps pop3 pop3s log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/home/vmail/%d/%n/Maildir ssl_cert_file = /etc/pki/dovecot/certs/dovecot.pem ssl_key_file = /etc/pki/dovecot/private/dovecot.pem namespace private { separator = . prefix = INBOX. inbox = yes } protocol lda { log_path = /home/vmail/dovecot-deliver.log auth_socket_path = /var/run/dovecot/auth-master postmaster_address = postmaster(a)example.com } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } auth default { user = root passdb sql { args = /etc/dovecot-sql.conf } userdb static { args = uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes } socket listen { master { path = /var/run/dovecot/auth-master mode = 0600 user = vmail } client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } } [/code] Any clues on how can I adapt this configuration file to Dovecot 2.0.9? Best Regards,

1 0

[Dovecot] Doubts about dsync, mdbox, SIS
by Jan-Frode Myklebust 03 Feb '12

03 Feb '12

I've been running continous dsync backups of our Maildirs for a few weeks now, with the destination dsync server using mdbox and SIS. The idea was that the destination server would act as a warm copy of all our active users data. The active servers are using Maildir, and has: $ df -h /usr/local/atmail/users/ Filesystem Size Used Avail Use% Mounted on /dev/atmailusers 14T 12T 2.2T 85% /usr/local/atmail/users $ df -hi /usr/local/atmail/users/ Filesystem Inodes IUsed IFree IUse% Mounted on /dev/atmailusers 145M 113M 33M 78% /usr/local/atmail/users very little of this is compressed (zlib plugin enabled during christmas). I'm surprised that the destination server is so large, was expecting zlib and mdbox and SIS would compress it down to much less than what we're seeing (12TB -> 5TB): $ df -h /srv/mailbackup Filesystem Size Used Avail Use% Mounted on /dev/mapper/mailbackupvg-mailbackuplv 5.7T 4.8T 882G 85% /srv/mailbackup Lots and lots of the attachement storage is duplicated into identical files, instead of hard linked. When running "doveadm purge -u $user", we're seeing lots of Error: unlink(/srv/mailbackup/attachments/c3/17/c317b32b97688c16859956f11b803e3bba434349-057274283bb51f4f917e0000bf34f6ab) failed: No such file or directory "/srv/mailbackup/attachments/c3/17/c317b32b97688c16859956f11b803e3bba434349-057274283bb51f4f917e0000bf34f6ab" is missing, but there are 205 other copies of this file named /srv/mailbackup/attachments/c3/17/c317b32b97688c16859956f11b803e3bba434349-* with identical sha1sum. Also we see corrupted indexes during the purge. This makes me quite uncertain if dsync is a workable backup solution.. or if we can trust mdboxes. Also on the source side, during dsync, we see too many problems. Some samples: Error: Mailboxes don't have unique GUIDs: 08b46439069d3d4db0490000e671bf84 is shared by INBOX and INBOX Error: command BOX-LIST failed Error: Worker server's mailbox iteration failed Error: read() from worker server failed: EOF Error: Failed to sync mailbox INBOX.ferie 2006.: Invalid mailbox name Error: read() from proxy client failed: EOF Error: Unexpected finish reply: 1 596fec275888dbd89f6d1f5356c22db6 3720 0 \dsync-expunged 0 Error: Unexpected reply from server: 1 12200572a70726fca946da6f9378dc03 3721 0 \dsync-expunged 0 Error: Failed to sync mailbox INBOX.INBOX.Gerda: Mailbox doesn't exist: INBOX/Gerda Error: command BOX-LIST failed Error: read() failed: Broken pipe Panic: file dsync-worker-local.c: line 1678 (local_worker_save_msg_continue): assertion failed: (ret == -1) Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0 [0x367703c680] -> /usr/lib64/dovecot/libdovecot.so.0(default_fatal_handler+0x35) [0x367703c765] -> /usr/lib64/dovecot/libdovecot.so.0 [0x367703bb93] -> /usr/bin/dsync [0x40f48d] -> /usr/bin/dsync [0x40f589] -> /usr/bin/dsync(dsync_worker_msg_save+0x8e) [0x40eb3e] -> /usr/bin/dsync [0x40d71a] -> /usr/bin/dsync [0x40cdbf] -> /usr/bin/dsync [0x40d105] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x48) [0x3677047278] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0xd5) [0x36770485c5] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x2d) [0x367704720d] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x3677035a83] -> /usr/bin/dsync(main+0x71e) [0x406c4e] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x3e3941d994] -> /usr/bin/dsync [0x406369] Do you have any idea for what our problems might be? Should we: avoid SIS ? avoid doing Maildir on one side and mdbox on the other? try other dovecot version for dsync? anything else? -jf ------------- destination server, running dovecot v2.0.14 -------- mail_attachment_dir = /srv/mailbackup/attachments mail_location = mdbox:~/mdbox mail_plugins = zlib mdbox_rotate_size = 5 M namespace { inbox = yes location = prefix = INBOX. separator = . type = private } passdb { driver = static } plugin { zlib_save = gz zlib_save_level = 9 } protocols = service auth-worker { user = $default_internal_user } service auth { unix_listener auth-userdb { mode = 0600 user = mailbackup } } ssl = no userdb { args = home=/srv/mailbackup/%256Hu/%d/%n driver = static } -------------/destination server -------- -jf

3 7

[Dovecot] Feature request - search and tag protocol - notmuch-alike approach
by Kirill A. Shutemov 03 Feb '12

03 Feb '12

Hi all, notmuch[1] becomes more and more popular. At least in geek community. But notmuch is local-only (except ssh)... It looks like it's hard (if even possible) to use IMAP as transport for notmuch-alike work flow. I think it would be great to create a new protocol based global search and message tagging. All core notmuch operations (search, show, count, tag) can be mapped to the new protocol (more or less) directly. Search syntax can be reused as is, I think. The tricky part is initial tagging. It requires some kind of transaction to be able to tag new messages without racing with upcoming messages. Request (command) syntax can be similar to unix command. This way we can reuse notmuch syntax even deeper. Like: search --limit 10 --sort=oldest-first tag:to-me tag:unread Replies are often structured. I think it's reasonable to use JSON for all replies. Any ideas? I've started to write a proof-of-concept, but it moves too slow, since my knowledge of dovecot internals is poor and it's hard to find time for the project. I hope somebody else has similar idea in mind and just wait opportunity to discuss the idea and start to write code. ;) [1] http://notmuchmail.org/ -- Kirill A. Shutemov

1 0

[Dovecot] converting from mbox to maildir ?
by Frank Bonnet 02 Feb '12

02 Feb '12

Hello We are planning to convert our mailhub ( freebsd 7.4 ) from mbox format to maildir format. I've read the documentation and performed some tests on another machine it is a bit long ... I would like some feedback from guys who did this operation and need some advice on what to convert first ? - first convert INBOX then convert IMAP folders ? - first convert IMAP folders then convert INBOX ? the machine use real users thru openldap ( pam_ldap + nss_ldap ) another problem is disk space. The users's email data takes about 2 Terabytes of data and I cannot duplicate as I only have 3 Tb on the raid array of the server. My idea is to use one of our NFS netapp filer during the convertion to throw the result of the convertion on an NFS mounted directory. Anyone did this before ? If yes I would be greatly interrested by their experience Thank you

2 6

[Dovecot] locking problem
by myron 02 Feb '12

02 Feb '12

I have one user who can't read his e-mail. The /var/log/mail.log file has this statement. dovecot: IMAP(<user>): Timeout while waiting for lock for transaction log file /users/<user>/mail/.imap/INBOX/dovecot.index.log I tried killing the imap daemons and removing the lock file, but it keeps coming back. Any idea what else to do? This is the dovecot file: dovecot -n # 1.2.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-28-server x86_64 Ubuntu 10.04.3 LTS log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s ssl_cert_file: /etc/ssl/certs/ssl-cert-snakeoil.pem ssl_key_file: /etc/ssl/private/ssl-cert-snakeoil.key disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login mail_privileged_group: mail mail_location: mbox:~/mail:INBOX=/var/mail/%u mbox_write_locks: fcntl dotlock 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 auth default: mechanisms: plain login passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth-client mode: 432 user: postfix group: postfix --myron ================================= Myron Kowalski MoCoSIN Network/Systems Administrator Moravian College myron(a)moravian.edu (610) 861-1441

2 4

[Dovecot] Renaming user account / mailbox
by Nikolaos Milas 02 Feb '12

02 Feb '12

Hello, I am running dovecot-2.0.13-1_128.el5 x86_64 RPM on CentOS 5.7. All accounts are virtual, hosted on LDAP Server. We are using Maildir mailboxes. The question: What is the process to rename an existing account/mailbox? I would like to rename userx with email: userx(a)example.com to ux(a)example.com with a mailbox of ux (currently: userx) Of course the idea is that new mail will continue to be delivered to the same mailbox, although it has been renamed. How can I achieve it? Would it be enough (after changing the associated data in the associated LDAP entry) to simply rename the virtual user directory name, e.g. from /home/vmail/userx to /home/vmail/ux ? Thanks in advance, Nick

2 2

[Dovecot] Site-wide configurable Sieve
by Gedalya 01 Feb '12

01 Feb '12

Hi, I need some sieve actions to be specified per-user, but exposing actual sieve scripts to users is of the question. For example, I need to be able to either put spam messages into a spam folder, or discard them, based on user preference. Presumably this would be done using Sieve. As I understand, it's not possible to query a database from within a sieve script. If I can't use a single global script, I can imagine automatically generating per-user scripts when settings are saved in a GUI (e.g. webmail) and store them on the dovecot machine. This would work but I would love to hear if someone has a smarter, more robust idea. Thanks, Gedalya

1 0

[Dovecot] question of different type of Mailbox
by ml 01 Feb '12

01 Feb '12

hi folks hi timo hi master of "Fu" I just migrate my emails from one type of Maildir to Mailbox I did as I was having problems reading speed with my webmail. I did it in order to optimize when do you my current config work for me sincerely -- http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC2626742 gpg --keyserver pgp.mit.edu --recv-key C2626742 http://urlshort.eu fakessh @ http://gplus.to/sshfake http://gplus.to/sshswilting http://gplus.to/john.swilting https://lists.fakessh.eu/mailman/ This list is moderated by me, but all applications will be accepted provided they receive a note of presentation

2 1

[Dovecot] LMTP : Can't handle mixed proxy/non-proxy destinations
by Alexis Lelion 01 Feb '12

01 Feb '12

Hello, In my current setup, I uses two mailservers to handle the users connections, and my emails are stored on a distant server using NFS (maildir architecture) Dovecot is both my IMAP server and the delivery agent (LMTP via postfix) To avoid indexing issues related to NFS, proxying is enabled both on IMAP and LMTP. But when a mail is sent to users that are shared between the servers, I got the subject mentionned error in the logs : Jan 25 09:05:12 mail01 postfix/lmtp[23934]: A92709300DB: to=< user_on_mail02(a)domain.com>, relay=mail01.domain.com[private/dovecot-lmtp], delay=0.07, delays=0.01/0/0/0.06, dsn=4.3.0, status=deferred (host mail01.domain.com[private/dovecot-lmtp] said: 451 4.3.0 < user_on_mail02(a)domain.com> Can't handle mixed proxy/non-proxy destinations (in reply to RCPT TO command)) >From what I saw, the mail is then put in the queue, and wait until the next time Postifx will browse the queue. The mail will then be correctly delivered on "mail02". However, the "queue_run_delay" postfix parameter is set to 900, which means that the mail will be delivered with a lag of 15 minutes. I was wondering if there was another way of handling this, for example by triggering an immediate queue lookup from postfix or forwarding a copy of the mail to the other server. Note that the postfix "queue_run_delay" was increased to 15min on purpose, so I cannot change that. I'm using dovecot 2.0.15 on Debian Squeeze, kernel 2.6.32-5-amd64. Thanks, Alexis

2 3

[Dovecot] Issues w/ Apple devices after migration to dovecot
by Armistead, Kurt 01 Feb '12

01 Feb '12

Hi guys. Recently we've moved our old (and I mean _really_ old) mailserver to a new hardware. Since I had quite some time on my hands, I decided to switch from courier to dovecot. Transition went pretty smoothly and the users experienced just a few hours' blackout. Only trouble now is that, after re-configuring some IOS handsets and tablets, not all messages are displayed correctly. For example, I had a long existing mailbox (roughly 1600 emails in INBOX and about a dozen other folders) that showed up perfectly on my iphone. Now it's been synced to the new dovecot server via imap and a whole month of messages seems to be missing. I checked on the server, via webmail and with outlook and everything is where it should be. The problem shows up on Apple devices (same thing happened on a couple of ipads). I haven't tried rebuilding the index or wiping out a phone to see if that resolves the problem, but before I do that I'd like to know if anyone experienced the same issue and how they fixed it Thanks! Kurt

2 3

[Dovecot] Uncompressing dboxes
by Lauri Alanko 01 Feb '12

01 Feb '12

Hello. I have an mdbox directory that has been created with the zlib plugin active, using bzip2 compression. I would now like to convert these into uncompressed mdbox format. How do I do this? I have tried unsetting all zlib-related configuration options, but dsync still produces compressed mdbox at the other end, too. I guess I could convert to mbox, and then back to mdbox, but for certain reasons I'm not very enthusiastic about doing anything mbox-related with dovecot any more. (Incidentally, it's a bit funny that when the zlib plugin is enabled, dsync automatically creates compressed dboxes, and even compressed maildirs (which is pretty useless), but not compressed mboxes, although that's where compression would be most beneficial.) Thanks, Lauri

2 1