- dovecot - dovecot.org

[Dovecot] v2.1.2 released
by Timo Sirainen 16 Mar '12

16 Mar '12

http://dovecot.org/releases/2.1/dovecot-2.1.2.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.2.tar.gz.sig There are a ton of proxying related improvements in this release. You should now be able to do pretty much anything you want with Dovecot proxy/director. This release also includes the initial version of dsync-based replication. I'm already successfully using it for @dovecot.fi mails, but it still has some problems. See http://dovecot.org/list/dovecot/2012-March/064243.html for some details how to configure it. + Initial implementation of dsync-based replication. For now this should be used only on non-critical systems. + Proxying: POP3 now supports sending remote IP+port from proxy to backend server via Dovecot-specific XCLIENT extension. + Proxying: proxy_maybe=yes with host=<hostname> (instead of IP) works now properly. + Proxying: Added auth_proxy_self setting + Proxying: Added proxy_always extra field (see wiki docs) + Added director_username_hash setting to specify what part of the username is hashed. This can be used to implement per-domain backends (which allows safely accessing shared mailboxes within domain). + Added a "session ID" string for imap/pop3 connections, available in %{session} variable. The session ID passes through Dovecot IMAP/POP3 proxying to backend server. The same session ID is can be reused after a long time (currently a bit under 9 years). + passdb checkpassword: Support "credentials lookups" (for non-plaintext auth and for lmtp_proxy lookups) + fts: Added fts_index_timeout setting to abort search if indexing hasn't finished by then (default is to wait forever). - doveadm sync: If mailbox was expunged empty, messages may have become back instead of also being expunged in the other side. - director: If user logged into two directors while near user expiration, the directors might have redirected the user to two different backends. - imap_id_* settings were ignored before login. - Several fixes to mailbox_list_index=yes - Previous v2.1.x didn't log all messages at shutdown. - mbox: Fixed accessing Dovecot v1.x mbox index files without errors.

4 4

[Dovecot] problems with SSH-based clustering dovecot 2.1.1
by Michescu Andrei 16 Mar '12

16 Mar '12

Hello, I'm using dovecot 2.1.1 with vpopmail 5.4.30 with multiples domains and I have problems setting up synchronization in between multiple computers. All act like master (my clients can connect to any of the them and read their emails either via POP3 either via IMAP, inbound email gets on any of the machines). Each machine is on a different continent, there is no shared drive in between and the synchronization is supposed to be asynchronous via cron scripts. To simplify the case, let's consider 2 machines (mx1.a and mx2.a) with 3 virtual domains (a and b and c). On both machine domain a is the default domain (needs only username to connect to imap). Initially I synchronize mx1.a with mx2.a using rsync. I check that I can login using dovecot. I tried any of the following commands to synchronize the 2 machines: mx1.a$ doveadm -Dv sync -u user1@a -f ssh mx2.a doveadm dsync-server -u user1@a mx1.a$ doveadm -Dv sync -u user1@a ssh mx2.a doveadm -u user1@a mx1.a$ doveadm -Dv sync -u user1@a user1@a The only thing that happens is that the on each machine the folders get doubled with some random extension (eg. Inbox becomes Inbox_3e3ff3g3gb3bb3b22). Also, another bug, if there is a domain setup as default (auth_default_realm) dsync simply ignores the specified -u <user> and attempts to sync the first email in the default domain. Please advise. # 2.1.1: /etc/dovecot/dovecot/dovecot.conf # OS: Linux 2.6.38-b i686 Slackware 13.0.0.0.0 auth_debug = yes auth_debug_passwords = yes auth_default_realm = a first_valid_gid = 89 first_valid_uid = 89 last_valid_gid = 89 last_valid_uid = 89 listen = * log_path = /dev/stderr login_greeting = A login_trusted_networks = 192.168.20.64/26 mail_debug = yes mail_gid = vchkpw mail_location = maildir:~/Maildir mail_privileged_group = vchkpw mail_uid = vpopmail passdb { driver = vpopmail } protocols = imap pop3 service auth-worker { unix_listener auth-worker { user = vpopmail } user = vpopmail } service auth { user = vpopmail } service imap-login { user = vpopmail } service pop3-login { user = vpopmail } ssl = no userdb { driver = vpopmail }

5 24

[Dovecot] Compiler warnings in dovecot-2.1.2 and pigeonhole 0.3.0
by Tom Talpey 16 Mar '12

16 Mar '12

I'm seeing a few warnings emitted when building for x86. They're pretty obvious, but if you want the configure options etc, I can provide those. In Dovecot 2.1.2 (I also see some of these in 2.1.1): 1) src/lib-index/mail-cache-fields.c (comparison between two last_used fields) mail-cache-fields.c: In function 'mail_cache_header_fields_read': mail-cache-fields.c:406: warning: comparison between signed and unsigned 2) src/director/user-directory.c (comparison with ioloop_time) user-directory.c: In function 'user_directory_user_is_recently_updated': user-directory.c:147: warning: comparison between signed and unsigned 3) src/replication/replicator/replicator-brain.c (comparison with ioloop_time) replicator-brain.c: In function 'doveadm_replicate': replicator-brain.c:113: warning: comparison between signed and unsigned 4) src/replication/replicator/replicator-queue.c (comparison with ioloop_time) replicator-queue.c: In function 'replicator_queue_pop': replicator-queue.c:201: warning: comparison between signed and unsigned In Pigeonhole 0.3.0: 5) src/managesieve-login/client-authenticate.c (passing size_t * not uoff_t *) client-authenticate.c: In function 'managesieve_client_auth_read_response': client-authenticate.c:214: warning: passing argument 3 of 'i_stream_get_size' from incompatible pointer type

3 3

[Dovecot] 2.1.1: doveadm backup errors
by e-frog 15 Mar '12

15 Mar '12

Hello Timo, I'm experimenting with 'doveadm backup' on 2.1.1 (latest hg, full dovecot -n output attached) and haven't managed to get it working. This is what I have done: 1. Create the directory /tmp/backup which is empty 2. Run doveadm -v backup -u testuser(a)ubuntu-test.localdomain mdbox:/tmp/backup/ Then I see the following errors: doveadm -v backup -u testuser(a)ubuntu-test.localdomain mdbox:/tmp/backup/ dsync(testuser(a)ubuntu-test.localdomain): Error: Can't delete mailbox INBOX: INBOX can't be deleted. dsync(testuser(a)ubuntu-test.localdomain): Info: INBOX: only in dest (guid=9e4b88178b905f4f456e0000381555a6) dsync(testuser(a)ubuntu-test.localdomain): Info: INBOX: only in source (guid=bd05451f2fbb574d40600000ec8d17cd) dsync(testuser(a)ubuntu-test.localdomain): Error: Trying to open a non-listed mailbox with guid=9e4b88178b905f4f456e0000381555a6 dsync(testuser(a)ubuntu-test.localdomain): Error: msg iteration failed: Couldn't open mailbox 9e4b88178b905f4f456e0000381555a6 dsync(testuser(a)ubuntu-test.localdomain): Error: Trying to open a non-listed mailbox with guid=9e4b88178b905f4f456e0000381555a6 dsync(testuser(a)ubuntu-test.localdomain): Error: Mailbox INBOX changed its GUID (bd05451f2fbb574d40600000ec8d17cd -> 9e4b88178b905f4f456e0000381555a6) dsync(testuser(a)ubuntu-test.localdomain): Error: msg iteration failed: Couldn't open mailbox bd05451f2fbb574d40600000ec8d17cd dsync(testuser(a)ubuntu-test.localdomain): Error: Mailbox INBOX changed its GUID (bd05451f2fbb574d40600000ec8d17cd -> 9e4b88178b905f4f456e0000381555a6) It somehow finds INBOX in destination however the backup directory is newly created and empty. Thanks, e-frog

2 5

[Dovecot] Multiple locations, 2 servers - planning questions...
by Charles Marcus 15 Mar '12

15 Mar '12

Hello all/Timo, Up until now, my main Clients office has consisted of a single location, and I have never had to deal with the situation of multiple locations for a single company. They have just told me that they are acquiring an additional floor at a building that is about 4 minutes away - but obviously far enough away that I now have to deal with supporting users in the same domain but at two disparate physical locations. These two locations will be connected via a private Gb ethernet connection, and each location will have its own internet connection (I think - still waiting on some numbers to present to the owner to see what he wants to do in that regard, but that will be my recommendation), so bandwidth for replication won't be an issue. I have a couple of months to get this done, and I am already planning on hiring Timo's new commercial support company to help with the final and actual design and implementation, but obviously first I need to know what my actual options are. Just a rough idea of what I'd like to do is: 1. Set up one dovecot server at each location (these will be VMs), so users at each location are accessing the local server for that office 2. Full replication between the two for the mail/indexes, and configure them such that each can act as a failover for the other in case one goes down for whatever reason This is my first/main question... I recall that 'dsync based replication' is actually on the map for 2.1, but, since apparently dsync can't do this now, Timo, do you have even a rough idea how much work this would be to get it working for only 2 locations (assuming it *may* be easier to get the initial support for only 2 locations, my client may be willing to pay for it if it isn't a huge amount - feel free to reply privately to this question), then you could revisit it later to make it more scalable? Or, if it is going to take more work than my client is willing to pay for (I'm hoping not, since you said it was on the map for 2.1, not 2.2+), maybe the notify plugin could be leveraged in some way to provide something 'close enough' until it is fully implemented in dsync? On that note (something 'close enough' until dsync fully supports this natively), would setting up a dsync cron job, say, every 5 or 10 minutes, be asking for trouble? Our mail server is not all that busy, really, so in 5 or 10 minutes, there wouldn't be many changes at all. If that is not recommended, although I want to avoid the hassles of NFS if at all possible, maybe there is another shared filesystem that will work ok - or... since I will be forcing users to a single server always anyway, maybe NFS or some other shared filesystem is really the best option here, and just let it take care of the syncing? and 3. Configure things such that each offices users are directed to the local server for that office, but connections will fail-over to the remote server in the case of one of them going down for whatever reason? I'm fairly sure that some combination of Dovecot Proxy/Director will accomplish this, but one concern is - for internal users, my understanding is it will redirect them via the private IP, but that would result in lots of traffic across the Gb connection between the two locations, and I'd like to eliminate that if possible - so how will this work when they are accessing it from outside the office, where each office has its own public IP? I'd prefer to not rely on users using the correct hostname (currently, we just use 'mail.example.com', and I know I could set up two new ones - office1.example.com and office2.example.com - but then I'd be relying on the users to get it right, and I'd prefer to avoid that can of worms). I guess a worst case scenario (if there is no better way) would be to do it that way, then watch the logs for users who get it wrong and are using the inter-office connection, and deal with them on a case by case basis. Thanks to any/all for reading this far and for any thoughts, suggestions and/or ideas... -- Best regards, Charles

9 19

[Dovecot] director lmtp -> smtp problem
by Jim Lawson 15 Mar '12

15 Mar '12

Hi Timo & Dovecot users, We have a 2-node director setup which front-ends for 4 nodes which share a clustered filesystem (GFS). All nodes run Dovecot 2.0.18. Approximately 40k users, but typically only a few thousand active at any time. The director nodes run sendmail, which deliver mail "locally" using LMTP to the director, which then feeds to SMTP on the real servers (also sendmail.) Why sendmail? Because procmail is used for mail filtering and as the delivery agent. Here's the problem, on the director: Mar 14 20:40:08 imapdir2 dovecot: lmtp(10692): Connect from local Mar 14 20:40:38 imapdir2 dovecot: lmtp(10692): Panic: file lmtp-proxy.c: line 376 (lmtp_proxy_output_timeout): assertion failed: (proxy->data_input ->eof) Mar 14 20:40:38 imapdir2 dovecot: lmtp(10692): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x3d99a) [0x7f79156c499a] -> /usr/lib/doveco t/libdovecot.so.0(+0x3d9e6) [0x7f79156c49e6] -> /usr/lib/dovecot/libdovecot.so.0(i_error+0) [0x7f791569df8f] -> dovecot/lmtp() [0x406e77] -> /usr/l ib/dovecot/libdovecot.so.0(io_loop_handle_timeouts+0xd4) [0x7f79156d0044] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x5b) [0x7f79156d 0c3b] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x28) [0x7f79156cfca8] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f7915 6bdfc3] -> dovecot/lmtp(main+0x154) [0x403f84] -> /lib64/libc.so.6(__libc_start_main+0xfd) [0x7f7914ef8cdd] -> dovecot/lmtp() [0x403d69] Mar 14 20:40:38 imapdir2 sendmail[6905]: q2D8KodI018432: SYSERR(root): timeout writing message to localhost: Broken pipe Most mail goes through OK, but some messages do not and end up queued until they run into the queue time limit. So far as I have been able to tell, all of the messages have this failure when the following conversation takes place between sendmail (on director), the Dovecot LMTP proxy, and sendmail on the backend node (SMTP): (names mangled to protect the guilty) (first, sendmail -> director LMTP) > [root@imapdir2 ~]# sendmail -qIq2EFZt1p004708 -v > > Running /var/spool/mqueue/qd2/q2EFZt1p004708 (sequence 1 of 1) > <ntssdfwe(a)pobox2.uvm.edu>... Connecting to > /var/lib/dovecot/lmtp-socket via cyrusv2... > 220 imapdir2.uvm.edu Dovecot LMTP ready > >>> LHLO imapdir2.uvm.edu > 250-imapdir2.uvm.edu > 250-8BITMIME > 250-ENHANCEDSTATUSCODES > 250 PIPELINING > >>> MAIL From:<owner-dasfqeiuasd*Abrasf*-Gorpwe**UVM*-EDU(a)LIST.UVM.EDU> > 250 2.1.0 OK > >>> RCPT To:<ntssdfwe> > >>> DATA > 250 2.1.5 OK > 354 OK > timeout writing message to localhost: Broken pipe > <ntssdfwe(a)pobox2.uvm.edu>... Deferred > Closing connection to localhost The conversation between the director (LMTP) and the backend (sendmail SMTP) goes like this: > 250-penguinc.uvm.edu Hello imapdir2.uvm.edu [132.198.100.150], pleased > to meet you > 250-ENHANCEDSTATUSCODES > 250-PIPELINING > 250-8BITMIME > 250-SIZE 10485760 > 250-ETRN > 250-AUTH DIGEST-MD5 CRAM-MD5 > 250-DELIVERBY > 250 HELP > MAIL FROM:<owner-dasfqeiuasd*Abrasf*-Gorpwe**UVM*-EDU(a)LIST.UVM.EDU> > 250 2.1.0 <owner-dasfqeiuasd*Abrasf*-Gorpwe**UVM*-EDU(a)LIST.UVM.EDU>... > Sender ok > RCPT TO:<ntssdfwe> > 552 5.2.2 User ntssdfwe mailbox is full At this point Dovecot should return the failed RCPT TO: status back to sendmail over LMTP, but instead it sits there (waiting for a timeout to expire?) and eventually dies. doveconf -n output: # 2.0.18: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-220.4.2.el6.x86_64 x86_64 Red Hat Enterprise Linux Server release 6.2 (Santiago) base_dir = /var/run/dovecot/ default_client_limit = 6000 default_process_limit = 10240 director_mail_servers = penguina.uvm.edu penguinb.uvm.edu penguinc.uvm.edu penguind.uvm.edu director_servers = imapdir1.uvm.edu imapdir2.uvm.edu lmtp_proxy = yes login_trusted_networks = [REDACTED] passdb { args = proxy=y nopassword=y protocol=smtp driver = static } service anvil { client_limit = 40000 } service auth { client_limit = 45960 unix_listener auth-userdb { group = mail mode = 0660 user = dovecot } } service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { port = 9090 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director service_count = 0 } service imap { process_limit = 10240 vsz_limit = 1 G } service lmtp { client_limit = 1 inet_listener lmtp { port = 24 } unix_listener /var/lib/dovecot/lmtp-socket { group = root mode = 0600 user = root } } service pop3-login { executable = pop3-login director service_count = 0 } service pop3 { process_limit = 5000 } shutdown_clients = no ssl_cert = <[REDACTED].pem ssl_key = <[REDACTED].key userdb { driver = passwd } verbose_proctitle = yes version_ignore = yes protocol lmtp { auth_socket_path = director-userdb } protocol imap { mail_max_userip_connections = 100 } Hope you can help, Jim Lawson

2 6

[Dovecot] v2.0.19 released
by Timo Sirainen 15 Mar '12

15 Mar '12

http://dovecot.org/releases/2.0/dovecot-2.0.19.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.19.tar.gz.sig Hopefully one of the last v2.0.x releases. - IMAP: ENABLE CONDSTORE/QRESYNC + STATUS for a mailbox might not have seen latest external changes to it, like new mails. - imap_id_* settings were ignored before login. - doveadm altmove did too much work sometimes, retrying moves it had already done. - mbox: Fixed accessing Dovecot v1.x mbox index files without errors.

1 0

[Dovecot] sieve.before script is taking preceedence over user defined rules
by Alexis Lelion 15 Mar '12

15 Mar '12

Hello, In my current setup, I have a spam filter upstream that adds a specific header - X-Spam-Level on every incoming mail. Based on this level, the mail will be moved to the user spam folder using sieve by doing "fileinto :create 'spam';" Unfortunately, some legitimate email may end up in this spam folder, so I have kind of a whitelist that performs an explicit keep over specific trusted domains. So, my complete spam filtering rule is : if address :domain :contains "From" ["mycompany.tld", "trusted.tld" ]{ keep; elseif header :contains "X-Spam-Level" ["0","1","2"] { fileinto :create "__spam__"; } This rule is stored in "/var/lib/dovecot/sieve/before.sieve", which is my "sieve_before" file as defined in /etc/dovecot/conf.d/90-sieve.conf This works as expected except that it doesn't take into account users filtering for domains that were matched for the explicit keep. For example, I have the following rule : if address :domain "From" "trusted.tld" { fileinto "trusted" } But mail coming from that domain are still delivered in my mailbox. Is there something I'm missing here? I guess yes, otherwise it would work as I want ^_^ Any help/comment is appreciated Thanks! Alexis

2 4

Re: [Dovecot] doveadm -A stops processing at first uid<first_valid_uid
by Joseph Tam 15 Mar '12

15 Mar '12

On Sun, 4 Mar 2012, Timo Sirainen writes: > > I would like to run various doveadm commands that involves all (mail) users like > > > > doveadm expunge -A mailbox Trash savedbefore 30d > > > > but any doveadm command that uses "-A" to iterate through all users will > > stop processing at the first account with UID<first_valid_uid. > > What userdb are you using? userdb passwd should already skip users that > aren't in the valid range. And what Dovecot version are you using? passwd-file under dovecot 2.0.16. > And one more thing: Does it really even stop there? Looking at the code > it's supposed to log an error and continue to next user. Note that it says > "Failed to iterate through SOME users". The wording did not escape my notice, which is why I suspect it's not doing what it was designed to do. This is my test: # Command doveadm mailbox list -A # Start of password file sysdaemon:*:500:500:System daemon:/:/dev/null ... and the rest ... # dovecot.conf ... first_valid_uid = 10000 first_valid_gid = 10000 ... In this situation, doveadm will exit immediately with an UID error message. If I change the UID>10000, it will produce the analogous GID error message. If I satify both UID and GID constraints, it will fail on the next daemon entry. If I move the sysdaemon entry all the way to the bottom of the pasword file, I get user1 saved-messages user1 sent-mail user1 postponed-msgs user1 temp user1 temp/temp user1 INBOX user2 sent-mail user2 101 user2 345 user2 ckf ... all user's mailbox with UID>10000, then ... doveadm(sysdaemon): Error: user sysdaemon: Couldn't drop privileges: Mail access for users with UID 500 not permitted (see first_valid_uid in config file, uid from userdb lookup). doveadm(sysdaemon): Error: User init failed doveadm: Error: Failed to iterate through some users > Oh, it says about first_valid_gid. Is sysdaemon's UID within valid range? Sorry for this error mismatch -- I cut&pasted the wrong test output; however, the problem I witnessed applies to both UID and GID (if either constraint is not met, user iteration terminates). > I also added this today: http://hg.dovecot.org/dovecot-2.1/rev/85a8d582d37f It looks like I'll be upgrading. Oh, I just spotted this in the ChangeLog -- maybe you are undoing this? (2010-10-21) * src/auth/auth-settings.c, src/auth/auth-settings.h, src/auth/userdb- passwd.c: auth: userdb passwd iteration now lists only users within first_valid_uid..last_valid_uid range. [745ef289b0ea] Joseph Tam <jtam.home(a)gmail.com>

2 1

[Dovecot] Shared folder prefix listed multiple times with dovecot 2.1.1
by Markus Petri 15 Mar '12

15 Mar '12

Hi, after upgrading from 2.0.18 to 2.1.1 I noticed that I could not use shared folders with mutt anymore. 2.1 lists the shared namespace prefix once per user sharing an folder in LIST "" "%". I also noticed, that with 2.1 the user folder (Shared/<username>) is no longer tagged as \NoSelect. Is this the intended behaviour and mutt simply cannot cope with it or is it a dovecot problem? Here an example with three users sharing a folder to the logged in user with Dovecot 2.1.1: 2 LIST "" "*" * LIST (\HasNoChildren) "/" "INBOX" * LIST (\HasChildren) "/" "Shared/test" * LIST (\HasNoChildren) "/" "Shared/test/Share" * LIST (\HasChildren) "/" "Shared/test2" * LIST (\HasNoChildren) "/" "Shared/test2/Share2" * LIST (\HasChildren) "/" "Shared/test3" * LIST (\HasNoChildren) "/" "Shared/test3/Share3" 2 OK List completed. 2 LIST "" "%" * LIST (\HasNoChildren) "/" "INBOX" * LIST (\Noselect \HasChildren) "/" "Shared" * LIST (\Noselect \HasChildren) "/" "Shared" * LIST (\Noselect \HasChildren) "/" "Shared" 2 OK List completed. The same three users and config with Dovecot 2.0.18: 2 LIST "" "*" * LIST (\HasNoChildren) "/" "INBOX" * LIST (\Noselect \HasChildren) "/" "Shared/test" * LIST (\Noselect \HasChildren) "/" "Shared/test2" * LIST (\Noselect \HasChildren) "/" "Shared/test3" * LIST (\HasNoChildren) "/" "Shared/test/Share" * LIST (\HasNoChildren) "/" "Shared/test2/Share2" * LIST (\HasNoChildren) "/" "Shared/test3/Share3" 2 OK List completed. 2 LIST "" "%" * LIST (\HasNoChildren) "/" "INBOX" * LIST (\Noselect \HasChildren) "/" "Shared" 2 OK List completed. Markus # 2.1.1: /opt/dovecot-2.1/etc/dovecot/dovecot.conf # OS: Linux 3.2.0-1-amd64 x86_64 Debian wheezy/sid auth_mechanisms = plain login disable_plaintext_auth = no listen = 192.168.56.11 mail_location = maildir:~/Maildir mail_plugins = acl 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 = yes location = prefix = separator = / subscriptions = yes type = private } namespace { inbox = no list = children location = maildir:%%h/Maildir:INDEX=~/Maildir/index/shared/%%u prefix = Shared/%%u/ separator = / subscriptions = no type = shared } passdb { args = /opt/dovecot-2.1/etc/dovecot/passwd driver = passwd-file } plugin { acl = vfile acl_anyone = allow acl_shared_dict = file:/var/lib/vdovecot/shared-mailboxes.db } protocols = imap service auth { unix_listener auth-userdb { mode = 0600 user = vdovecot } } ssl = no userdb { args = /opt/dovecot-2.1/etc/dovecot/passwd driver = passwd-file } verbose_proctitle = yes protocol imap { mail_plugins = acl imap_acl }

2 3

Re: [Dovecot] Dovecot 2.1 with custom OpenSSL fails to build
by Andreas M. Kirchwitz 15 Mar '12

15 Mar '12

Timo Sirainen <tss(a)iki.fi> wrote: >> There seems to be a new dependency in some modules (eg, lib-storage, >> libdovecot-lda, libdovecot-ssl) on OpenSSL. In Dovecot 2.0, those >> modules didn't require OpenSSL, but 2.1 does. >> >> For the linking process the path to the OpenSSL library isn't >> specified properly (SSL_LIBS). Dovecot fails to build if OpenSSL >> is in a non-standard path. (Haven't checked if SSL_CFLAGS isn't >> properly used as well.) > > Maybe http://hg.dovecot.org/dovecot-2.1/rev/c07415305d9e fixes > everything? That's the way to go. Makes things better, but I've found three more dependencies. This patch is against the daily snapshot 20120228. (Sorry for the changes to Makefile.in which you won't need. But this way I don't have to rebuild Makefile.in from Makefile.am when compiling. ;-) diff -ur dovecot-20120228.original/src/auth/Makefile.am dovecot-20120228/src/auth/Makefile.am --- dovecot-20120228.original/src/auth/Makefile.am 2012-02-26 04:00:02.000000000 +0100 +++ dovecot-20120228/src/auth/Makefile.am 2012-02-29 01:38:41.000000000 +0100 @@ -167,7 +167,7 @@ libauthdb_imap_la_LIBADD = \ ../lib-imap-client/libimap_client.la \ ../lib-ssl-iostream/libssl_iostream.la \ - $(LIBDOVECOT) + $(LIBDOVECOT) $(SSL_LIBS) libauthdb_imap_la_CPPFLAGS = \ $(AM_CPPFLAGS) \ -I$(top_srcdir)/src/lib-imap \ diff -ur dovecot-20120228.original/src/auth/Makefile.in dovecot-20120228/src/auth/Makefile.in --- dovecot-20120228.original/src/auth/Makefile.in 2012-02-28 04:00:12.000000000 +0100 +++ dovecot-20120228/src/auth/Makefile.in 2012-02-29 01:38:44.000000000 +0100 @@ -499,7 +499,7 @@ libauthdb_imap_la_LIBADD = \ ../lib-imap-client/libimap_client.la \ ../lib-ssl-iostream/libssl_iostream.la \ - $(LIBDOVECOT) + $(LIBDOVECOT) $(SSL_LIBS) libauthdb_imap_la_CPPFLAGS = \ $(AM_CPPFLAGS) \ diff -ur dovecot-20120228.original/src/lib-storage/Makefile.am dovecot-20120228/src/lib-storage/Makefile.am --- dovecot-20120228.original/src/lib-storage/Makefile.am 2012-02-10 04:00:02.000000000 +0100 +++ dovecot-20120228/src/lib-storage/Makefile.am 2012-02-29 01:38:21.000000000 +0100 @@ -85,7 +85,7 @@ pkglib_LTLIBRARIES = libdovecot-storage.la libdovecot_storage_la_SOURCES = -libdovecot_storage_la_LIBADD = $(shlibs) $(MODULE_LIBS) +libdovecot_storage_la_LIBADD = $(shlibs) $(MODULE_LIBS) $(SSL_LIBS) libdovecot_storage_la_DEPENDENCIES = $(shlibs) libdovecot_storage_la_LDFLAGS = -export-dynamic diff -ur dovecot-20120228.original/src/lib-storage/Makefile.in dovecot-20120228/src/lib-storage/Makefile.in --- dovecot-20120228.original/src/lib-storage/Makefile.in 2012-02-28 04:00:15.000000000 +0100 +++ dovecot-20120228/src/lib-storage/Makefile.in 2012-02-29 01:38:21.000000000 +0100 @@ -397,7 +397,7 @@ pkglib_LTLIBRARIES = libdovecot-storage.la libdovecot_storage_la_SOURCES = -libdovecot_storage_la_LIBADD = $(shlibs) $(MODULE_LIBS) +libdovecot_storage_la_LIBADD = $(shlibs) $(MODULE_LIBS) $(SSL_LIBS) libdovecot_storage_la_DEPENDENCIES = $(shlibs) libdovecot_storage_la_LDFLAGS = -export-dynamic test_programs = \ diff -ur dovecot-20120228.original/src/login-common/Makefile.am dovecot-20120228/src/login-common/Makefile.am --- dovecot-20120228.original/src/login-common/Makefile.am 2011-11-09 04:00:01.000000000 +0100 +++ dovecot-20120228/src/login-common/Makefile.am 2012-02-29 01:38:21.000000000 +0100 @@ -40,6 +40,6 @@ pkglib_LTLIBRARIES = libdovecot-login.la libdovecot_login_la_SOURCES = -libdovecot_login_la_LIBADD = liblogin.la ../lib-ssl-iostream/libssl_iostream.la ../lib-dovecot/libdovecot.la +libdovecot_login_la_LIBADD = liblogin.la ../lib-ssl-iostream/libssl_iostream.la ../lib-dovecot/libdovecot.la $(SSL_LIBS) libdovecot_login_la_DEPENDENCIES = liblogin.la libdovecot_login_la_LDFLAGS = -export-dynamic diff -ur dovecot-20120228.original/src/login-common/Makefile.in dovecot-20120228/src/login-common/Makefile.in --- dovecot-20120228.original/src/login-common/Makefile.in 2012-02-28 04:00:18.000000000 +0100 +++ dovecot-20120228/src/login-common/Makefile.in 2012-02-29 01:38:21.000000000 +0100 @@ -320,7 +320,7 @@ pkginc_lib_HEADERS = $(headers) pkglib_LTLIBRARIES = libdovecot-login.la libdovecot_login_la_SOURCES = -libdovecot_login_la_LIBADD = liblogin.la ../lib-ssl-iostream/libssl_iostream.la ../lib-dovecot/libdovecot.la +libdovecot_login_la_LIBADD = liblogin.la ../lib-ssl-iostream/libssl_iostream.la ../lib-dovecot/libdovecot.la $(SSL_LIBS) libdovecot_login_la_DEPENDENCIES = liblogin.la libdovecot_login_la_LDFLAGS = -export-dynamic all: all-am

2 3

[Dovecot] .mailboxlist -> .subscriptions
by Steve Campbell 15 Mar '12

15 Mar '12

I've mostly finished a conversion from an old Centos 3 UW-Imap server to a new Centos 6 dovecot server. I did not copy the old ~/.mailboxlist file to ~/mail/.subscriptions file, but notice some users have the latter file now. These are all mbox folders on the old and new server. I'm getting ready to do the same to another old/new pair of servers and I'm wondering if there is an advantage of doing the copy. I'm assuming the .subscription files are created when they access their account through our webmail application, but I'm not sure if it was automatic or due to a "subscribe" action done manually. There are 49 accounts with a .mailboxlist file and only 4 with the new .subscriptions file. So either our webmail application isn't being used a lot or there's a problem with it due to the missing .subscriptions file, but the phone usually rings pretty quickly when problems arise. One last question, please. Over the years, some imap accounts had their folders directly in their home directory and the contents of the .mailboxlist file would have an entry with just the name of the folder in it (Trash, eg), and most had the folders in their ~/mail folder with an entry like "mail/Trash". Our webmail app, Horde/Imp, always seemed to take care of this. If I create the .subscription file for the users during the move to the new server, should I move the folders to the mail directory and amend their .subscriptions file to reflect that change on these odd ball accounts, and will that affect how their client is seeing these? The first server conversion was a bear due to my lack of dovecot knowledge. I've since learned a little more, and mostly found out that dovecot is a more complex application than the old imap application. There's so much more that can be done with dovecot, whereas the old imap server was mostly just load-and-go. Seems like no matter how much I read, the more I discovered I didn't know. Anyway, thanks for all the past help and any opinions anyone might decide to offer on this post. steve campbell

3 6

[Dovecot] 2.1: timeout waiting for lock?
by Ralf Hildebrandt 15 Mar '12

15 Mar '12

Mar 15 09:46:11 postamt dovecot: pop3(username): Error: Couldn't open INBOX: Timeout while waiting for lock Mar 15 09:46:11 postamt dovecot: pop3(username): Couldn't open INBOX top=0/0, retr=0/0, del=0/0, size=0 Mar 15 09:47:26 postamt dovecot: pop3(username): Error: Couldn't open INBOX: Timeout while waiting for lock Mar 15 09:47:26 postamt dovecot: pop3(username): Couldn't open INBOX top=0/0, retr=0/0, del=0/0, size=0 Mar 15 09:51:01 postamt dovecot: pop3(username): Error: Couldn't open INBOX: Timeout while waiting for lock Mar 15 09:51:01 postamt dovecot: pop3(username): Couldn't open INBOX top=0/0, retr=0/0, del=0/0, size=0 during that time, I wasn't able to access the mailbox using imap. I then issued doveadm kick username and all over sudden the mailbox was accessible (via IMAP) # doveadm kick username kicked connections from the following users: username # /usr/local/scripts/find_abnormal_imap Mar 15 11:38:48 postamt dovecot: imap: Warning: Killed with signal 15 (by pid=24545 uid=0 code=kill) -- 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 4

Re: [Dovecot] .mailboxlist -> .subscriptions
by Joseph Tam 15 Mar '12

15 Mar '12

Steve Campbell <campbell(a)cnpapers.com> writes: > Their imap folders, the ones that they create using an imap client or > webmail, are either in ~ or ~/mail. Their original .mailboxlist is > always in ~. Based on that, I should probably copy any imap folders not > in ~/mail to that folder, duplicate ~/.mailboxlist to the file > ~/mail/.subscriptions, and amend any .subscriptions file contents to > just have the name of the folders (without any "mail/folder" reference > in it). > > My example would then be as follows > > /home/steve = folder > /home/steve/Drafts = original folder > /home/steve/AnyFolder = original folder > /home/steve/.mailboxlist = original file > /home/steve/mail = folder (either original or created) > /home/steve/mail/.subscriptions = copied contents of .mailboxlist > file > /home/steve/mail/Drafts = copied folder of original > /home/steve/mail/AnyFolder = copied folder of original > > Contents of original .mailboxlist and new .subscriptions: > > Drafts > AnyFolder > > If the imap folders were in ~/mail, then the original .mailboxlist would > have been > > mail/Drafts > mail/AnyFolder > > but after the corrections to the .subscriptions file, they would be as > above (without reference to the mail folder). > > Is this correct? That depends -- are you aliasing namespaces so that prefix={"", "mail/", etc.} all map to a user's ~/mail folder? You may be creating a confusing situation where a client with a null IMAP prefix has 2 copies of a mailbox. Joseph Tam <jtam.home(a)gmail.com>

2 1

[Dovecot] firefox dovecot-sieve
by paul 15 Mar '12

15 Mar '12

Send this to dovecot(a)dovecot.org, not dovecot-owner(a)dovecot.org On 14.3.2012, at 4.45, paul wrote: > HI. I have just started to play with sieve and everything seems ok when > logging on using telnet localhost 4190 and an encoded username/password. > If I try to connect with firefox at localhost:4190 I get > "IMPLEMENTATION" "Dovecot Pigeonhole" > "SIEVE" "fileinto reject envelope encoded-character vacation subaddress > comparator-i;ascii-numeric relational regex imap4flags copy include > variables body enotify environment mailbox date ihave" > "NOTIFY" "mailto" > "SASL" "PLAIN LOGIN" > "STARTTLS" > "VERSION" "1.0" > OK "Dovecot ready." > NO "Error in MANAGESIEVE command received by server." > NO "Error in MANAGESIEVE command received by server." > NO "Invalid characters in atom" > BYE "Too many invalid MANAGESIEVE commands." > my dovecot -n shows > # 2.0.18: /etc/dovecot/dovecot.conf > # OS: Linux 2.6.42.9-1.fc15.i686.PAE i686 Fedora release 15 (Lovelock) > auth_mechanisms = plain login > disable_plaintext_auth = no > mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u > 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 > mbox_write_locks = fcntl > passdb { > driver = pam > } > plugin { > sieve = ~/.dovecot.sieve > sieve_dir = ~/sieve > } > protocols = imap pop3 lmtp sieve > service managesieve-login { > inet_listener sieve { > port = 4190 > } > } > ssl_cert = </etc/pki/dovecot/certs/dovecot.pem > ssl_key = </etc/pki/dovecot/private/dovecot.pem > userdb { > driver = passwd > } > Have I missed something obvious or does Firefox clash with Managesieve? > Thanks. Paul >

2 1

[Dovecot] Login Failed
by Aydın Demirel 15 Mar '12

15 Mar '12

Hi; We are using scripts for login successes. Is there a feature for login failed status or can it be developed? Regards -- *Aydın Demirel Endersys Ltd. Sistem Destek Mühendisi/ System Support Engineer* * *<<Endersys is the first Advanced Business Partner of Red Hat in Turkey! http://www.europe.redhat.com/partners/endersys/>> Phone : +90 216 470 9423 | GSM : +90 530 401 8203 Fax : +90 216 470 9508 | Web : http://www.endersys.com <http://www.endersys.com/> Blog : http://blog.endersys.com <http://blog.endersys.com/> Twitter : http://www.twitter.com/endersys LPI : The #1 Linux Certification for IT Professionals LPI (Linux Professional Institute) Turkey http://www.lpi-turkey.com <http://www.lpi-turkey.com/>

2 1

[Dovecot] FTS crash
by Joan Moreau 14 Mar '12

14 Mar '12

Hi Timo, I updated my 2.1 from HG, and now the FTS (Squat) plugin makes a segmentation fault. When I remove the plugin from the dovecot.conf, all works fine. No debug available here, but let me know how can I help you. Joan

2 2

[Dovecot] RECENT status always 0
by Arnaud Abélard 14 Mar '12

14 Mar '12

Hello, we are using dovecot 2.0.13 with maildir++ (we migrated away from courrier just a few months ago) and the RECENT status doesn't seem to be working: . STATUS INBOX (MESSAGES UNSEEN RECENT) * STATUS "INBOX" (MESSAGES 35106 RECENT 0 UNSEEN 10) then 2 minutes later: . STATUS INBOX (MESSAGES UNSEEN RECENT) * STATUS "INBOX" (MESSAGES 35106 RECENT 0 UNSEEN 11) How can the UNSEEN count change without the RECENT count changing accordingly? Thanks in advance, Arnaud -- Arnaud Abélard (jabber: arnaud.abelard(a)univ-nantes.fr) Administrateur Système - Responsable Services Web Direction des Systèmes d'Informations Université de Nantes - ne pas utiliser: trapemail(a)univ-nantes.fr

2 1

[Dovecot] Thunderbird Archive to slower storage - sort of alternate storage
by Marcio Merlone 14 Mar '12

14 Mar '12

Hi people, When a user archives a message from Thunderbird it moves to an IMAP folder "Archives", everyone knows that. I use dovecot 1:1.2.9-1ubuntu6.5 on Ubuntu 10.04 and want to move that folder (and respective IMAP sub-folders) to a slower storage, link it to original location and my first idea for this is find -type d -name .Archives\* -print0 | \ while read -d $'\0' archive; do \ mv "$archive" /dead/Emails/jhon.doe/; \ ln -s "/dead/Emails/jhon.doe/$archive" .; done It works, given that the files are not locked. I could restart dovecot before so it would unlock the files, but there is no guarantee it does not get locked again before the find finishes. I took a look on mailling list archives, but could not find something like that and was wondering what you guys use (if any) for such task and what are the recommendations, best practices, solutions for that? Thanks in advance, best regards. -- *Marcio Merlone*

2 5

Re: [Dovecot] \NoSelect on missing folders in LIST
by Peter Mogensen 14 Mar '12

14 Mar '12

On 2012-03-05 16:36, Timo Sirainen wrote: >> Still curious about if Courier is doing something wrong which the scripts just happened to take advantage of. > > Neither behavior is wrong, just different. :) Ok... I were in doubt if I had missed something from the RFC. However... for testing, I tried to create "INBOX.INBOX" on dovecot. But then dovecot answers NO and complains that the folder already exists. Though it's still not on disk and dovecot still doesn't list it with "*". /Peter

2 1

[Dovecot] No passdbs specified in configuration file with passdb/userdb in protocol sections
by btb＠bitrate.net 13 Mar '12

13 Mar '12

hi- i have a configuration in which i'm using different passdb/userdb settings for each of imap, lmtp and smtp [without getting too far off on a tangent, this is so ldap group membership can be used to independently control authorization for receiving [lmtp], retrieving [imap], and sending [smtp/postfix] of email. each passdb/userdb uses a different search filter.] when i use this as my config: # 2.0.13: /etc/dovecot/dovecot.conf # OS: Linux 3.0.0-15-generic-pae i686 Ubuntu 11.10 auth_debug = yes first_valid_gid = 2000 first_valid_uid = 2000 log_timestamp = "%d.%m.%Y %H.%M.%S " login_greeting = dovecot ready mail_debug = yes protocols = " imap lmtp" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } service lmtp { inet_listener lmtp { address = 127.0.0.1 ::1 port = 10026 } } ssl_cert = </etc/dovecot/pki/mra.example.com-cert.pem ssl_key = </etc/dovecot/pki/mra.example.com-key.pem verbose_proctitle = yes protocol imap { mail_max_userip_connections = 20 passdb { args = /etc/dovecot/dovecot-ldap-imap.conf.ext driver = ldap } userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-ldap-imap.conf.ext driver = ldap } } protocol lmtp { userdb { args = /etc/dovecot/dovecot-ldap-lmtp.conf.ext driver = ldap } } protocol smtp { passdb { args = /etc/dovecot/dovecot-ldap-smsp.conf.ext driver = ldap } } dovecot complains: dovecot: auth: Fatal: No passdbs specified in configuration file. PLAIN mechanism needs one which is a little confusing, since there are multiple passdbs specified, in the various protocol sections. i found that adding another "global" passdb to the config allows dovecot to work - e.g.: # 2.0.13: /etc/dovecot/dovecot.conf # OS: Linux 3.0.0-15-generic-pae i686 Ubuntu 11.10 auth_debug = yes first_valid_gid = 2000 first_valid_uid = 2000 log_timestamp = "%d.%m.%Y %H.%M.%S " login_greeting = dovecot ready mail_debug = yes passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocols = " imap lmtp" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } service lmtp { inet_listener lmtp { address = 127.0.0.1 ::1 port = 10026 } } ssl_cert = </etc/dovecot/pki/mra.example.com-cert.pem ssl_key = </etc/dovecot/pki/mra.example.com-key.pem verbose_proctitle = yes protocol imap { mail_max_userip_connections = 20 passdb { args = /etc/dovecot/dovecot-ldap-imap.conf.ext driver = ldap } userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-ldap-imap.conf.ext driver = ldap } } protocol lmtp { userdb { args = /etc/dovecot/dovecot-ldap-lmtp.conf.ext driver = ldap } } protocol smtp { passdb { args = /etc/dovecot/dovecot-ldap-smsp.conf.ext driver = ldap } } the problem with this is that while each of the passdb/userdb configs for the various protocols does indeed work, if a result is not found in one of them, the global passdb appears to then function as a catch-all. how can i tell dovecot it doesn't need a global passdb? each of the protocols' passdb/userdb configs is functioning as desired, but having dovecot look elsewhere upon failure ends up defeating the purpose. thanks -ben

2 2

[Dovecot] invalid mailbox name
by Vincent Schut 13 Mar '12

13 Mar '12

Hi, while migrating all mail from our old to our new server (using offlineimap, imap -> imap), I get the following error for one of my user's mailboxes: ERROR: Folder 'Organisations.RS Env & IJRS'[local_hoekman] could not be created. Server responded: ('NO', ['Invalid mailbox name: Organisations.RS Env & IJRS']) I suppose this is because of the ampersand in the mailbox name? Because other folder with spaces in it go just fine... Is this a fixed thing? Why was my user able to create the folder once? And why is dovecot 1.2.15 refusing to create the folder now? Migration is from dovecot 1.1.11 to 1.2.15. Thanks, Vincent.

2 5

[Dovecot] upgrade convert omissions
by Nick Edwards 13 Mar '12

13 Mar '12

It did not convert over some things: protocol imap { listen = *:143 mail_plugins = quota imap_quota imap_client_workarounds = outlook-idle ssl_listen = *:993 } protocol pop3 { pop3_uidl_format = %f mail_plugins = quota pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } protocol lda { mail_plugins = quota cmusieve quota_full_tempfail = no log_path = /var/log/dovecot/deliver.log deliver_log_format = msgid=%m: from=%f: %$ auth_socket_path = /var/run/dovecot/auth-master } I ended up with service imap-login { inet_listener imap { address = * port = 143 } inet_listener imaps { address = * port = 993 } process_limit = 1024 service_count = 1 } service imap { process_limit = 1024 } service pop3-login { process_limit = 1024 service_count = 1 } service pop3 { process_limit = 1024 } It looks like service-foobar is replacing stuff inside protocol {} but protocol still exists in examples, kind of confusing. Oh what about service-pop3, different than examples and service-imap, where's pop3s ? I guess I'll just copy the service pop3 section from an example file. Does all this mean the protocol section is not needed? or everything inside of them I had is no longer valid? No LDA specific logging converted, it did not include the quota stuff in where it is needed (mail_plugins went MIA), but did inside converted plugin section. I did note the conversion warned that workarounds = outlook-idle is no longer needed, but nothing about the other stuff. Just concerns me if it ignored some needed stuff, what else did it ignore. Nik (who is rather reluctant to use series 2 and break everything and stay with 1.2) Below is the new conf file: auth_cache_negative_ttl = 0 auth_cache_ttl = 5 mins auth_mechanisms = plain login auth_verbose = yes disable_plaintext_auth = no first_valid_uid = 95 last_valid_uid = 95 listen = *,:: log_path = /var/log/dovecot/pop3.log login_log_format_elements = user=<%u> method=%m rip=%r %c mail_location = maildir:/vmail/%d/%n/Maildir mail_nfs_index = yes mail_nfs_storage = yes maildir_very_dirty_syncs = yes mmap_disable = yes passdb { args = /etc/dovecot-sql.conf driver = sql } plugin { quota = maildir quota_rule = *:storage=1000M quota_rule2 = Trash:storage=100M quota_rule3 = Junk:ignore quota_rule4 = Spam:ignore quota_warning = storage=90%% /usr/local/bin/quotawarn-90.sh quota_warning2 = storage=75%% /usr/local/bin/quotawarn-75.sh } pop3_lock_session = yes protocols = imap pop3 service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-master { mode = 0600 user = vmail } user = vmail } service imap-login { inet_listener imap { address = * port = 143 } inet_listener imaps { address = * port = 993 } process_limit = 1024 service_count = 1 } service imap { process_limit = 1024 } service pop3-login { process_limit = 1024 service_count = 1 } service pop3 { process_limit = 1024 } shutdown_clients = no ssl_cert = </etc/ssl/certs/mail.crt ssl_key = </etc/ssl/certs/mail.key userdb { args = /etc/dovecot-sql.conf driver = sql }

2 2

[Dovecot] Trouble adding sasl support via dovecot
by Richard Troy 12 Mar '12

12 Mar '12

Hello Folks, I've been the admin of a site that uses Postfix with Dovecot on RedHat since, oh, gosh, maybe 1996? It's been a long time. I've never built it from source, though, just used the rpms (and I wonder if maybe that's my problem now). It just works, is reliable, and lets me be a very-part-time administrator. Repeatedly over the last few years I've been asked to have our mail system "join the modern age" and provide mail sending capabilities for clients that aren't on our internal network - via their smart-phones, from home, etc. OK... Well, way back when the site was set up, smtp servers didn't do any kind of "auth", but along the way to solving this problem (trying to configure pop-before-smtp, someone mentioned that Postfix now has an auth mechanism that uses Dovecot and I should use that instead! Great! ... Except that I've spent between 16 and 20 hours on this with no joy, and while I hate having to ask for help, it's time to ask what things that are obvious to the less ignorant that I must be doing wrong... Certainly, given the solid history of Postfix and Dovecot, I must be the problem! My problem statement is simply, "it should be working", but doesn't, and I don't get any announcement of "auth" when testing connections to Postfix as per directions here: http://www.postfix.org/SASL_README.html#server_test At least I haven't broken the normal functionality! I'm building a new server on the latest Fedora Core (16), but it's lacking in some hardware and won't be ready for a while, so I'm working with FC 14, running Postfix 2.5.6, and Dovecot 1.2.8. It uses the "cram-md5" auth scheme (which works fine and I'd hate to change it if I don't have to). The system has been up and functional on these versions for a couple of years, and quite stable, we just can't send if we're not local. When I do "postconf-a" it indicates cyrus and dovecot, so I take it that means Postfix has been built with sasl support. (I presume this means I don't have to compile it from source.) First Dovecot. Its set up to provide all protocols, but only imaps and pop3s have ports forwarded through the firewall. Plain-text auth is disabled, ssl is set to yes, ssl_listen is not specified, and the cert and key files are in the default locations - and work. No cipher list is used. Dovecot's chrooted. The protocol sections imap and pop3 take ALL the defaults, as does lda (I've ignored sendmail_path = /usr/lib/sendmail) as I don't think it matters. "auth default {" has mechanisms set to cram-md5, digest-md5, plain, and login, with passdb passwd-file pointing to a file in /etc where the cram data goes. It's not using pam, and there's an OLD comment in the config: # Experience says we need an empty passdb - passwd group: which is followed by passdb passwd{}. Later, there's "userdb passwd {}. All of that was configured long ago and has been functional. The changes I've made to add sasl support primarily pertain to the "socket listen section of "auth default". There, the master section remains commented out while the client section has been uncommented, the path set to /var/spool/postfix/private/auth, mode set to 0660, and the user and group have been set to postfix. ...This is all as described here: http://www.postfix.org/SASL_README.html and http://wiki.dovecot.org/HowTo/PostfixAndDovecotSASL That's it for Dovecot. Now, to Postfix itself. >From the working environ, only listening on port 25, I simply added the following (as per directions already cited above): smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth smtpd_sasl_auth_enable = yes broken_sasl_auth_clients = yes smtpd_sasl_security_options = noanonymous, noplaintext smtp_sasl_security_options = noanonymous, noplaintext smtpd_sasl_tls_security_options = noanonymous smtp_sasl_tls_security_options = noanonymous And, of course, permit_sasl_authenticated was added to smtpd_recipient_restrictions. I got the impression from the baove sources that Postfix will then use Dovecot's authentication mechanism via a socket it finds in its private/auth subdirectory. NOT documented in any of those places, someone suggested I must turn on TLS. OK... The documentation found here: http://www.postfix.org/TLS_README.html claims (intimates) that it's not possible to run a site on a self-signed certificate, however, there's ZERO budget for a signed certificate, so unless I can get one for ten bucks somewhere, that could be a deal-breaker here. However, we've been using self-signed certificates for a while now and wonder why an "exception" mechanism wouldn't exist. As that web page talks about "Netscape" I suspect it's very old and may no longer apply. In any event, I tried this, too (after trying without). On the good side, an available Android phone, previously reading fine, but unable to send, no longer complained when the setup was changed to the imap username and password, same server address, TLS security type, and the server port of 25. HOWEVER, no mail has passed through it successfully, it just gives no error whatsoever, so far, while the server's log reports "Relay access denied." Notably, when setting up TLS, Postfix complained when the smtpd_tls_key_file was incorrect, but did not complain when it was provided properly, suggesting it's reading and accepting my self-signed certificate and private key. Ideas, please?! And, by the way, what's port 465 all about? Some clients propose that's what should be used to send... Thanks in advance for your help, Richard

2 2

[Dovecot] mdbox + gzip and rsync
by Jean-Daniel Beaubien 12 Mar '12

12 Mar '12

Hi, After reading the following paragraph from the dovecot doc, I've been wondering how it would affect rsync (when combined with gzip): "Expunging a message only decreases the message's refcount. The space is later freed in "purge" step. This is typically done in a nightly cronjob when there's less disk I/O activity. The purging first finds all files that have refcount=0 mails. Then it goes through each file and copies the refcount>0 mails to other mdbox files (to the same files as where newly saved messages would also go), updates the map index and finally deletes the original file. So there is never any overwriting or file truncation." How will the mailbox files (m.X) files be modified when I move or delete emails using mdbox+gzip. Will the resulting gzipped mdbox files be rsync-able or will they need a full re-upload? If I plan on using rsync for backups, am I better off not using the gzip feature (if i can spare the extra storage)??? Thanks, -JD

3 3

[Dovecot] dot named folders
by Micah Anderson 12 Mar '12

12 Mar '12

When a user makes a folder called 'x.y' it actually creates a folder called 'x' with a folder called 'y' inside, rather than a folder called 'x.y'. I'm guessing this has to do with an internal folder separator namespace configuration, but I'm a bit confused by how this works. I'm using 2.0.15 with mdbox and this is what I have configured for my namespaces: namespace { separator = . prefix = inbox = yes } namespace { separator = . prefix = INBOX. inbox = no hidden = yes list = no } I migrated from courier maildirs, so perhaps I no longer need some of these now that the conversion is finished? thanks for any suggestions, I've got my head mixed up on this issue, micah --

4 5

[Dovecot] Extracting mbox format from Dovecot IMAP (mdbox)
by Giles Coochey 12 Mar '12

12 Mar '12

Hi, I'm looking for a quick tool that can connect to my IMAP account grab all the messages in a particular folder and dump them to a mbox format file? Anyone know a quick easy tool to do that? This is a spam folder that I'd like to do some Bayes spam learning on, but since I've migrated to mdbox I don't think I can do this directly on the mailbox. Any thoughts appreciated. -- Best Regards, Giles Coochey NetSecSpec Ltd UK Mobile: +44 7983 877 438 Business Email: giles.coochey(a)netsecspec.co.uk Email/MSN/Live Messenger: giles(a)coochey.net Skype: gilescoochey

2 4

Re: [Dovecot] Question about folder creation/delete and logging
by Maria Arrea 12 Mar '12

12 Mar '12

mail_log plugin is just what we need, thank you for your support. Yes, we are using bacula+doveadm import for this project. If you are interested, we have in production an home-brew message-tracking system for our end-users. We parse qmail / postfix / clamav / spamassassin/ dovecot / sieve logs and insert them in a mysql database, and a logged user in our webapp can see what happened with her mails (sent mails or messages waiting for arrival). Affero GPL software, of course. Some screenshots (Spanish only, sorry) here: https://gestionproyectos.us.es/attachments/download/321/Seguimiento_de_mens… https://gestionproyectos.us.es/attachments/download/145/Captura_de_pantalla… https://gestionproyectos.us.es/attachments/download/156/Seguimiento_de_mens… URL of the project (Seguimiento, spanish word for "tracking"): https://gestionproyectos.us.es/projects/seguimiento Regards Maria ----- Original Message ----- From: Timo Sirainen Sent: 03/12/12 02:04 PM To: Maria Arrea Subject: Re: [Dovecot] Question about folder creation/delete and logging On Mon, 2012-03-12 at 12:56 +0100, Maria Arrea wrote: > > - Is there any way of Dovecot logging to write when a folder is > deleted or created? We do not want to increase too much our "normal" > logging level. We use Dovecot 2.0.18+mdbox+zlib You can configure mail_log plugin to only log mailbox creations and deletions. http://wiki2.dovecot.org/Plugins/MailLog > - Does anybody know of any other project to create an easy-restore > for Dovecot? I guess you're using "doveadm import"? So other than that, haven't heard of any.

1 0

[Dovecot] Question about folder creation/delete and logging
by Maria Arrea 12 Mar '12

12 Mar '12

Hello We are working in a web based restore system for our Dovecot users. In this web form a user must log-in and after successful login can estore a deleted folder from date X. We will release it under the GPL. I have a couple of questions: - Is there any way of Dovecot logging to write when a folder is deleted or created? We do not want to increase too much our "normal" logging level. We use Dovecot 2.0.18+mdbox+zlib - Does anybody know of any other project to create an easy-restore for Dovecot? Regards Maria

3 2

[Dovecot] Dovecot LDA breaking .qmail forwarding?
by Wouter van der Schagt 12 Mar '12

12 Mar '12

Good morning all, I've a problem, I'm using the Dovecot LDA in my .qmail file: |/var/qmail/bin/preline -f /usr/local/libexec/dovecot/deliver -d $EXT@$USER However when I add a forward, such as: |/var/qmail/bin/preline -f /usr/local/libexec/dovecot/deliver -d $EXT@$USER <mailto:&wouter@vdschagt.com> &wouter(a)vdschagt.com The mail isn't forwarded and stays in the queue on the mail server, the same is the case when I reverse the lines. The error in the log file is: @400000004f5de5f7033bc434 delivery 824026: deferral: qmail-inject:_fatal:_qq_trouble_creating_files_in_queue_(#4.3.0)/system_erro r_calling_qmail-inject/ When using another LDA, for example when specifying the Maildir, it works, but then i cannot use Sieve scripts. Any ideas? Am I doing anything wrong? Sincerely, - Wouter van der Schagt

1 0

[Dovecot] nfs error fcntl(read-lock) locking failed for file
by Rajesh M 10 Mar '12

10 Mar '12

hi i am using qmailtoaster with dovecot version 2 mailbox format is maildir i have a domain with around 5000 users which are distributed over 2 servers webmail (squirrelmail) runs using dovecot v2 is being used from server number one server number 2 had all the data stored in it and also has pop and smtp running from it. i am not using dovecot for pop as yet on the server with dovecot i get such errors in the log file access to data on server number 2 is via nfs on server number 1 i get errors as such Error: fcntl(read-lock) locking failed for file Input/output error squirrelmail gives error imap connection closed and i am not able to login so i set the parameters as such in the dovecot conf file and the error stopped mmap_disable=yes dotlock_use_excl = yes lock_method = dotlock can somebody please advise me if the above is correct ? or is it preferred to use fcntl with lockd (note that my mailbox is maildir format) thanks very much for your help rajesh

2 1

[Dovecot] Lock down Shared Mail Accounts?
by Charles Marcus 10 Mar '12

10 Mar '12

On 3/5/2012 1:30 PM, Steve Campbell wrote: > I've been looking at some documentation on shared mail accounts. > But I'm getting mixed thoughts on how this can or should be done. This brings up a question I have been meaning to ask. One thing I want to do on my new converted system is to implement shared mail. There will be two different scenarios - users sharing 'folders', which looks to be fairly simple using virtual ACL files - but for the other scenario, I'm not sure about a specific requirement we will have... I want to give multiple people shared access to some actual accounts with all of the special use folders, with the following requirements: 1. They can all read/reply to new messages as they come in, 2. They use shared \seen, \replied and \forwarded flags, so once someone else has read/dealt with a message, the others see that, 3. When they reply to/forward a message, the Sent message gets saved to that accounts 'Sent' folder, 4. They can *move* messages to other folders in that account (ie, 'file' them), and last (this is the tricky part) 5. No one other than a designated user or users (Master User(s)? Users in a specified Group?) can delete any messages in this account, in any of the folders. These emails deal with financial transactions (AP and AR issues) and Faxes, thus the requirement to not be able to delete them. Can this be accomplished with the current state of things? Or would this require some coding? If the latter, could it be done as a plug-in, or would it require changes to the core code? Thanks, -- Best regards, Charles

4 5

Re: [Dovecot] dovecot Digest, Vol 107, Issue 20 Fscking warnings
by Stephen Davies 10 Mar '12

10 Mar '12

Yes that is the google thread that I saw. I don't see the relevance of your reference to dsync. As I read the man pages for dsync it is used to sync separate servers, to make backups or to convert mailbox formats. When I upgraded from 1.2.15 to 2.1.1 I saw nothing in the doco to suggest that dsync was relevant to my scenario. In a previous thread here (Log sync errors), Timo suggested that the migration fix was to delete all .imap directories. My understanding was that this should fix any differences between 1.2.15 files and 2.1.1. If that were the case, mentioning the migration again would seem irrelevant. However, it seems that deleting the .imap files did not fix the log sync errors or the fscking warnings. Both are still happening continuously. Cheers, Stephen On Thu, 8 Mar 2012 08:26:55 PM dovecot-request(a)dovecot.org wrote: > Date: Wed, 07 Mar 2012 15:03:35 -0600 > From: Stan Hoeppner <stan(a)hardwarefreak.com> > To: dovecot(a)dovecot.org > Subject: Re: [Dovecot] Fscking warnings > Message-ID: <4F57CD27.3000207(a)hardwarefreak.com> > Content-Type: text/plain; charset=ISO-8859-1 > > On 3/6/2012 5:07 PM, Stephen Davies wrote: > > Google tells me that these "should go away" but they don't. > > > > > > > > Seems to happen continuously while a user is viewing email. > > Is this thread what "Google tells you"? > > http://dovecot.org/list/dovecot/2010-October/053909.html > > Timo is the creator of Dovecot, if you didn't know. So you can take his > words for gospel. Also note his last statement in that thread: > > "The next time you could do it with dsync to avoid these kind of > problems." > > It would seem you omitted a very important detail from your problem > report, which is that you recently performed a migration. Please don't > omit such critical details in future requests for help. Provide as much > relevant detail as possible. This speeds the process up for everyone, > and avoids guesswork on our part. > > -- > Stan > > > ------------------------------ > > Message: 10 > Date: Thu, 8 Mar 2012 00:26:55 +0100 > From: "Marc" <M.Roos(a)roosit.eu> > To: <dovecot(a)dovecot.org> > Subject: [Dovecot] FW: Centos 6 + dovecot 2 + mail.app + imap -- ============================================================================= Stephen Davies Consulting P/L Voice: 08-8177 1595 Adelaide, South Australia. Fax : 08-8177 0133 Records & Collections Management. Mobile:040 304 0583

2 1

[Dovecot] POP3C storage backend
by Tom Talpey 10 Mar '12

10 Mar '12

I see a new "POP3C" lib-storage client backend in dovecot 2.1, but I don't see anything in the 2.1 doc directory or in the wiki. Can this be used to synchronize dovecot with external pop servers? Doing away with my current fetchmail and lmtp solution for this would be quite interesting. Thanks for any pointers to configuring and using this, if so...

2 1

[Dovecot] Fscking warnings
by Stephen Davies 10 Mar '12

10 Mar '12

Google tells me that these "should go away" but they don't. Seems to happen continuously while a user is viewing email. Mar 7 09:29:52 server dovecot: imap(john): Warning: fscking index file /home/john/Mail/INBOX/.imap/Archive/dovecot.index Mar 7 09:29:52 server dovecot: imap(john): Warning: fscking index file /home/john/Mail/INBOX/.imap/Davies/dovecot.index Mar 7 09:29:52 server dovecot: imap(john): Warning: fscking index file /home/john/Mail/INBOX/.imap/FieldNET/dovecot.index Mar 7 09:29:52 server dovecot: imap(john): Warning: fscking index file /home/john/Mail/INBOX/.imap/Invoices Out/dovecot.index Mar 7 09:29:52 server dovecot: imap(john): Warning: fscking index file /home/john/Mail/INBOX/.imap/Lawrence and Hanson/dovecot.index Mar 7 09:29:52 server dovecot: imap(john): Warning: fscking index file /home/john/Mail/INBOX/.imap/Logger Call/dovecot.index Mar 7 09:29:52 server dovecot: imap(john): Warning: fscking index file /home/john/Mail/INBOX/.imap/Logger Reset/dovecot.index Mar 7 09:29:52 server dovecot: imap(john): Warning: fscking index file /home/john/Mail/INBOX/.imap/River Murray/dovecot.index Mar 7 09:29:52 server dovecot: imap(john): Warning: fscking index file /home/john/Mail/INBOX/.imap/SMS Emails/dovecot.index Mar 7 09:29:52 server dovecot: imap(john): Warning: fscking index file /home/john/Mail/INBOX/.imap/Soil Moisture Alert/dovecot.index Mar 7 09:29:52 server dovecot: imap(john): Warning: fscking index file /home/john/Mail/INBOX/.imap/Water Management Alarm/dovecot.index Mar 7 09:29:52 server dovecot: imap(john): Warning: fscking index file /home/john/Mail/INBOX/.imap/Water Usage/dovecot.index Mar 7 09:29:52 server dovecot: imap(john): Warning: fscking index file /home/john/Mail/INBOX/.imap/Weather Summaries/dovecot.index Mar 7 09:29:52 server dovecot: imap(john): Warning: fscking index file /home/john/Mail/INBOX/.imap/Zerna/dovecot.index -- ============================================================================= Stephen Davies Consulting P/L Voice: 08-8177 1595 Adelaide, South Australia. Fax : 08-8177 0133 Records & Collections Management. Mobile:040 304 0583

3 2

[Dovecot] Single instance storage
by Jean-Daniel Beaubien 10 Mar '12

10 Mar '12

I have read most of the doc on the dovecot website, and couldn't find any info on the single instance storage feature, so I'm posting my questions here. - Are these 3 parameters the only one necessary for single instance storage? I cannot find any doc on this feature on the website; is there anything specific I need to know about them? (the last one isn't exactly self-explanatory). - mail_attachment_dir = /srv/vmail/attachments - mail_attachment_hash = %{sha256} - mail_cache_min_mail_count = 2 - Is this feature ready for production? Thanks, -JD

2 1

[Dovecot] migrating/converting from system users -> virtual users
by Steve Platt 10 Mar '12

10 Mar '12

Hello all, We currently have a traditional mail server where all users have system accounts (ie entries in the NIS passwd map) and mbox-format mail folders in their (system) home directories. I'm trying to setup a dovecot server in which we want all users to have "virtual" accounts (in dovecot) and no entry in the passwd file at all (ie no access to the mail server). This is for security reasons, we want to imagine that users connecting to the mail server in future will not be able to access any resources on the server other than access their email messages. To this end we've set up a "vmail" user that owns all the messages in the Maildir directories. Most of this is working but I'm stuck on how to convert users' mail folders from the existing setup to the new one. I'm using the convert plugin but of course the problem is that the plugin executes as the "vmail" user and cannot access the existing mail folders that belong to the users: and I'd be worried if it could, of course! So I've converted a few users already by making copies of their old-world mailboxes, changing the ownership of the copies and pointing the convert plugin to these copies, instead of the originals. This works (modulo the dreaded "timeouted" error messages) but is very ugly. So I tried looking at the convert-tool but can't find a man page for it so am not sure what I'm doing with it! I have the idea that I should be able to run some command (as a privileged user) on the mail server and have it do the conversion for me, changing the ownership/permissions on the way. Can convert-tool do this? I'd prefer to go with the automatic (plugin) conversion if I can bodge the ownership issues somehow. Failing that, some tool or script may be the next best answer. This is Dovecot 1.2 by the way on Solaris 10. Any suggestions would be welcome! Steve Platt

2 3

[Dovecot] Whether the THREAD command support cross-mailbox thread?
by Andy YB Hu 10 Mar '12

10 Mar '12

In the real world, the mails which belongs to one thread could be dispersed in different mailbox, at least Inbox and SENT, so whether the command can search different mailboxes and grap them in one talk with dovecot? If Not, any other approach to do that? BTW, what the THREAD=REFS stands for? In the RFC, http://tools.ietf.org/html/rfc5256, i didn't find this algorithm.

2 1

[Dovecot] Advise on upgrading from a jurassic version - please help.
by Martin Mielke 10 Mar '12

10 Mar '12

Hi all, I have inherited an old Dovecot installation which is causing headaches almost every day. I know that one of the rules says "Don't bother asking questions about v0.99.x versions. They're no longer supported."...but please bear with me, this will be quick as I only need some advise from experienced Dovecot gurus out there. I have read the Dovecot documentation and there are instructions to upgrade from 0.99.x to 1.x and so on... my question is: can I upgrade from 0.99.11 to 2.x directly or is it a massive leap? If so, what do I have to keep in mind? This is a production system so I should not break anything... or at least have a rollback plan... Thanks a lot in advance! Regards, Martin

2 1

[Dovecot] sieve and utf-7 foldernames
by Andreas Schulze 10 Mar '12

10 Mar '12

Hi all, since many dovecot/pigeonhole versions I have an error: Mails are delivered into wrong folders if the foldername contain a german umlaut. ( ä, ö, ü ) setup: dovecot-2.1.1 / pigeonhole-0.3.0 postfix deliver to dovecot-lda .dovecot.sieve contains this: require ["fileinto","reject","vacation","relational","comparator-i;ascii-numeric","regex"]; if header :contains "To" "green(a)example.org" { fileinto "INBOX.gr&APw-n"; stop; } a mail to the mentioned address produces this logging: Mar 9 22:23:10 test dovecot: lda(foo): save: box=INBOX.gr&APw-n, uid=2, msgid=<4711(a)example.org>, size=4642 also a mail_debug=yes log no more lines related to the foldername but at the end I found the mail not in the expected folder. It places in "INBOX.gr&-APw-n" notice the extra minus after & I think it's pigeonholes fault but I may be wrong ... # doveconf -n # 2.1.1: /etc/dovecot/dovecot.conf # OS: Linux 2.6.26-2-686 i686 Debian 5.0.9 ext3 ... lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes listen = 127.0.0.1, ::1 protocols = " imap sieve" protocol lda { mail_plugins = quota notify mail_log sieve } ... Andreas

2 1

[Dovecot] Has dovecot 2.1.1 been built and tested on AIX 6.1???
by Bennett, Tony 09 Mar '12

09 Mar '12

I have downloaded and built dovecot 2.1.1 using gcc on AIX 6.1. (The output of "dovecot -n" is at the bottom of this email.) I'm trying "baby steps" to get it up, before I give it the final configuration. (My apologies: I was pointed to RFC3501 and told to get an IMAP server, build it, configure it, and bring it up) What is currently occurring when I start dovecot is: Error: service(pop3-login): listen(::, 110) failed: Address already in use Error: service(pop3-login): listen(::, 995) failed: Address already in use Error: service(imap-login): listen(::, 143) failed: Address already in use Error: service(imap-login): listen(::, 993) failed: Address already in use Fatal: Failed to start listeners Using TRUSS and recompiling with log messages I've determined that dovecot is successfully creating and binding to AF_INET sockets... but is failing when trying to do the "bind" the same port to an AF_INET6 socket. The failure is "EADDRINUSE". The logic in the dovecot sources seems driven off of the define of HAVE_IPV6 (defined in config.h by configure) So, the questions I have are: - Is this the correct behavior - If this is the correct behavior, has this been tested against AIX 6.1, and if so, does anyone have an idea of what I did wrong...??? If it has not been tested against AIX 6.1 and is NOT the correct behavior, should I just change "config.h", and undefined HAVE_IPV6 ... or is there a better way to move beyond this issue... (like a change to "configure")??? Thanks, -tony Here is the output of "dovecot -n": # 2.1.1: /attic/usr/local/etc/dovecot/dovecot.conf # OS: AIX 1 00C30F654C00 default_login_user = dovecot disable_plaintext_auth = no namespace { inbox = yes location = mailbox { special_use = \Drafts name = Drafts } mailbox { special_use = \Junk name = Junk } mailbox { special_use = \Sent name = Sent } mailbox { special_use = \Sent name = Sent Messages } mailbox { special_use = \Trash name = Trash } prefix = name = inbox } passdb { args = scheme=CRYPT username_format=%u /attic/usr/local/etc/dovecot/users driver = passwd-file } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap { name = imap-login } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { args = username_format=%u /attic/usr/local/etc/dovecot/users driver = passwd-file } protocol lmtp { service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap { name = imap-login } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } protocol lda { service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap { name = imap-login } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } protocol pop3 { service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap { name = imap-login } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } protocol imap { service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap { name = imap-login } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } }

2 2

Re: [Dovecot] disabling SSLv2 in dovecot 1.2.17
by Steve Platt 09 Mar '12

09 Mar '12

Hi Mark, I think I may not have been clear enough in my query, sorry! What I'm trying to do is to prevent SSLv2 connections being made to our IMAP server while allowing SSLv3 and TLSv1 connections. I think I've prevented the use of SSLv2 ciphers but this does not prevent SSLv2 protocol connections (as far as I can tell). (Once connected, the SSLv2 client finds it has no ciphers so the session fails at that point but this is not enough to satisfy our security audit. I want to disable the use of the SSLv2 protocol itself, not just the SSLv2 ciphers) steve.platt(a)mrc-bsu.cam.ac.uk said: > I see Dovecot2 had the following change a year or so ago, in file src/ > login-common/ssl-proxy-openssl.c: > > - SSL_CTX_set_options(ssl_ctx, SSL_OP_ALL); > + SSL_CTX_set_options(ssl_ctx, SSL_OP_ALL | SSL_OP_NO_SSLv2); > > I tried making the same change to dovecot1's src tree on our test system and > it seems to have the desired effect ... I'm testing this by using: openssl s_client -ssl2 -connect mailhost:993 This should fail immediately with "ssl handshake failure" (for a happy audit!). Thanks again, Steve

1 0

[Dovecot] seeking advice: dovecot versions; mailbox formats.
by Vincent Schut 09 Mar '12

09 Mar '12

Hi, I'm currently migrating our old (colocated) mail server (running a [terribly outdated, I know] dovecot 1.1.11) to a new VPS (virtual private server). The old server was running gentoo linux (which is mainly the culprit of the old dovecot version: gentoo was too much trouble to keep updating); the new server will run debian (stable: 6). Debian currently has dovecot 1.2.15 in its repositories; not that much newer... I read in the docs about the auto-generated-from-hg debian dovecot packages for 2.0, 2.1 and 2.2. Which leaves me to the choice what version to use... OK, 2.2 is development, which leaves the choice to: 1.2.15; 2.0.x, or 2.1.x. I would appreciate any consideration or thoughts on what version to choose. On a related note, there is the possibility to switch from maildir to dbox. I did not really find much pros or cons, except from performance and standards-compliance (ability to use e.g. mutt on the server itself). Any thoughts? About the server: we're just a small company. Think about 15 accounts, normal mail traffic, sometimes relatively large attachments (20mb+). Some accounts have many folders; some accounts are very large (5Gb+). Storage is on ext3, raid10. Performance has never been an issue; reliability and ease of maintenance is more important. Thanks, Vincent Schut.

5 7

[Dovecot] disabling SSLv2 in dovecot 1.2.17
by Steve Platt 09 Mar '12

09 Mar '12

I've set up a list of ciphers that excludes SSLv2 ciphers (and other weak ones) in the hope of preventing SSLv2 connections: ssl_cipher_list = TLSv1+HIGH : !SSLv2 : RC4+MEDIUM : !aNULL : !eNULL : !3DES : @STRENGTH However, this doesn't prevent the SSLv2 connection being allowed as our Nessus scans show and I'm tasked with trying to plug that "hole". I see Dovecot2 had the following change a year or so ago, in file src/login-common/ssl-proxy-openssl.c: - SSL_CTX_set_options(ssl_ctx, SSL_OP_ALL); + SSL_CTX_set_options(ssl_ctx, SSL_OP_ALL | SSL_OP_NO_SSLv2); I tried making the same change to dovecot1's src tree on our test system and it seems to have the desired effect; however I am very hesitant about putting this into our production system without seeking advice here first :-) Have I missed anything that's obviously bad about doing this please? Thanks again, Steve Platt

2 1

[Dovecot] [PATCH] Pop3 order in courier migration script
by Christoph Bußenius 08 Mar '12

08 Mar '12

Hi, I found a problem in the courier conversion script (courier-dovecot-migrate.pl). In some cases, it does not correctly preserve the order of POP3 UIDLs. Consider the following case, when courierpop3dsizelist contains: /2 9000 1327481629 AAA1:2,S 10000 21:1327481629 AAA2:2,S 10000 22:1327481629 AAA3:2,S 10000 23:1327481629 AAA4:2,S 10000 24:1327481629 AAA5:2,S 10000 25:1327481629 BBB11:2,S 10000 11:1327481629 BBB12:2,S 10000 12:1327481629 BBB13:2,S 10000 13:1327481629 BBB14:2,S 10000 14:1327481629 BBB15:2,S 10000 15:1327481629 and courierimapuiddb contains: 1 1327480919 9000 11 BBB11 12 BBB12 13 BBB13 14 BBB14 15 BBB15 16 CCC16 17 CCC17 18 CCC18 19 CCC19 20 CCC20 21 AAA1 22 AAA2 23 AAA3 24 AAA4 25 AAA5 then call courier-dovecot-migrate.pl --to-dovecot --convert and it will create dovecot-uidlist: 3 V1327480919 N9010 21 PUID21-1327481629 W10000 :AAA1:2,S 22 PUID22-1327481629 W10000 :AAA2:2,S 23 PUID23-1327481629 W10000 :AAA3:2,S 24 PUID24-1327481629 W10000 :AAA4:2,S 25 PUID25-1327481629 W10000 :AAA5:2,S 9000 :CCC17 9001 PUID12-1327481629 W10000 :BBB12:2,S 9002 :CCC16 9003 PUID15-1327481629 W10000 :BBB15:2,S 9004 :CCC20 9005 PUID14-1327481629 W10000 :BBB14:2,S 9006 PUID13-1327481629 W10000 :BBB13:2,S 9007 :CCC18 9008 PUID11-1327481629 W10000 :BBB11:2,S 9009 :CCC19 The problem here is that the BBB files are not in the same order as in courierpop3dsizelist, and will therefore have a different order in the UIDL response in POP3. Also, the CCC files are interleaved while they should appear at the end. The reason is how the script assigns new UIDs: It does not do this in the order of courierpop3dsizelist. In fact the order is random because it depends on how perl traverses hashes. The attached patch fixes this by sorting the messages: First the POP3 messages get their new UIDs in order of their appearance in courierpop3dsizelist (so that the UIDL order will really be the same as in Courier), after that, the IMAP-only messages will be checked for UID clashes. The patch also changes how the $prev_uid variable is handled because that was also needed to always get the order right. The algorithm could probably be optimized to reduce the number of UID re-assignments to a minimum, however this would complicate the code and would only be noticed in a few cases. The patched courier-dovecot-migrate.pl will create dovecot-uidlist like this: 3 V1327480919 N9010 21 PUID21-1327481629 W10000 :AAA1:2,S 22 PUID22-1327481629 W10000 :AAA2:2,S 23 PUID23-1327481629 W10000 :AAA3:2,S 24 PUID24-1327481629 W10000 :AAA4:2,S 25 PUID25-1327481629 W10000 :AAA5:2,S 9000 PUID11-1327481629 W10000 :BBB11:2,S 9001 PUID12-1327481629 W10000 :BBB12:2,S 9002 PUID13-1327481629 W10000 :BBB13:2,S 9003 PUID14-1327481629 W10000 :BBB14:2,S 9004 PUID15-1327481629 W10000 :BBB15:2,S 9005 :CCC16 9006 :CCC17 9007 :CCC18 9008 :CCC19 9009 :CCC20 Cheers, Christoph -- 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 3

[Dovecot] v2.1 latest hg: untagged reply to namespace command
by e-frog 08 Mar '12

08 Mar '12

Hello Timo, There seems to be something broken in v2.1 latest hg version: # 2.1.1 (94de7605f50f) 1 namespace * NAMESPACE (("" "/")("virtual/" "/")) NIL NIL * OK Namespace completed. Please note that the "OK Namespace completed." is send untagged. It worked on below version: # 2.1.1 (315f0d8cc2b2) 1 namespace * NAMESPACE (("" "/")("virtual/" "/")) NIL NIL 1 OK Namespace completed. Thanks, e-frog

1 1

[Dovecot] Shared mboxes
by Steve Campbell 08 Mar '12

08 Mar '12

I've been looking at some documentation on shared mail accounts. But I'm getting mixed thoughts on how this can or should be done. I use mbox for all my pop and imap folders since I've converted from a uw-imap server. The first thing that makes me wonder about setup is that I've been told to not use maildir and mbox on the same machine, although I'm not really sure why since it seems this would work OK, but anyway, I'm guessing I should stick with mbox for the shared accounts. Secondly, I'm sure I'd need a namespace to use which ever format, so there's private, public, and shared types. Most of the stuff I'm reading seems to suggest "public" as a type instead of "shared". So what's shared for anyway? I want to use this shared account so that email can be sent to this account, and be shared by only a few people, but I'm reading where locks and such don't work with mbox, so in my mind, how do you avoid corruption and why not just make a normal account and let people hack away at the data? I've not even got to the questions in my mind about how to set up the account, but figured if I could get the above straight, I might be able to fuddle my way through it. Help would be truly appreciated. steve campbell

2 6

Re: [Dovecot] dsync replication available for testing
by Michael Grimm 08 Mar '12

08 Mar '12

Hi -- On 08.03.2012 12:35, Timo Sirainen wrote: > On Thu, 2012-03-08 at 11:26 +0100, Michael Grimm wrote: > You can do for example: > > service config { > unix_listener config { > user = vmail > } > } I will try that later. >> It seems to me, that whenever a larger number of mails arrive on >> both >> servers simultaneously, the replicator gets into trouble [1]. I am >> unsure if one can expect that a replicator should deal with such >> stress, >> though. Or? > > Were these mails delivered via LMTP or dovecot-lda? LMTP > The locks should prevent duplicates I think, so there's something > still > going wrong. Just to be sure that I didn't misunderstand your proposed configuration: @mx1: plugin { mail_replica = remote:vmail@mx2.example.tld } @mx2: plugin { mail_replica = remote:vmail@mx1.example.tld } I do need to define one mail_replica plugin at each server pointing to the other one, correct? Regards, Michael

1 0

[Dovecot] duplicates with multiple To/CC and sieve redirect copy
by Adam Szpakowski 08 Mar '12

08 Mar '12

Hi, In one installation we are using sieve "redirect :copy" to create copy of the incoming email (local boss gets copy of its employees mails). There is a problem when the incoming email has multiple To/CC entries with local users. Multiple copy/redirects are created (one for each employee) and there are multiple copies in "boss" account. Each of this emails has the same Message-ID. Is there a way to detect those duplicates and discard them when saving copies into boss account? There was a discussion on the list a while ago (Feb 10/11, 2011) mentioning this problem, but with no clear solution. We are using Dovecot 2.0.15. Mail is delivered via LMTP (MDA/postfix is on separate machine then MAA/dovecot). -- Adam Szpakowski

5 10

[Dovecot] Failing: doveadm sync <--remote host--> dsync mirror
by Michael Grimm 08 Mar '12

08 Mar '12

Hi -- I'm used to dsync my two mailservers running 2.0.16. Today, I did upgrade one server to 2.1, and doveadm sync is throwing to following error: mail> doveadm sync -f -u test ssh vmail(a)remote-host.tld dsync -v -f -u test doveadm(test): Fatal: All your namespaces have a location setting. It should be empty (default mail_location) in the namespace to be converted. Same error with old running command: vmail> dsync -v -f -u test mirror ssh vmail(a)remote-host.tld dsync -v -f -u test doveadm(test): Fatal: All your namespaces have a location setting. It should be empty (default mail_location) in the namespace to be converted. Here's an excerpt of my doveconf -n: mail> doveconf -n mail_home = /var/mail/homedirs/%n mail_location = mdbox:/var/mail/maildirs/%n passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf driver = sql } userdb { driver = prefetch } userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf driver = sql } Reverted back for the time being (production servers) until I do understand the issue. Searching Google with "Fatal: All your namespaces have a location setting." only shows closed bugs back in 2010. Do I have to upgrade both servers to get syncing running? Any hint, help is highly appreciated. Thanks, Michael

2 18

[Dovecot] FW: Centos 6 + dovecot 2 + mail.app + imap
by Marc 08 Mar '12

08 Mar '12

Anybody also experiencing that imap processes are kept running/open by mac osx mail.app, so eventually users are getting to the mail_max_userip_connections limit? Outlook / other clients seem to run fine. Thanks, Marc

1 0

[Dovecot] http://xi.rename-it.nl down?
by Jim Knuth 07 Mar '12

07 Mar '12

Hello, you knows, that http://xi.rename-it.nl is down? -- Mit freundlichen Grüßen, with kind regards, Jim Knuth --------- Die Oper ist eine hübsche Unterhaltung, die noch besser wäre, wenn nicht dabei gesungen würde. (Claude Debussy)

2 2

[Dovecot] Log sync errors (again)
by Stephen Davies 07 Mar '12

07 Mar '12

As suggested earlier, I deleted all .imap directories and the log sync errors stopped - for a while. They have now returned. It seems to happen for every mailbox that gets accessed. Dovecot version 2.1.1 with pidgeonhole 3.0.0 on Mandriva Linux. Could this interfere with sieve filters? Several users have filters but none of them seem to do anything. Mar 7 09:25:51 server dovecot: imap(john): Error: Log synchronization error at seq=2,offset=38708 for /home/john/Mail/INBOX/.imap/Weather Summaries/dovecot.index: Extension header update points outside header size Mar 7 09:25:51 server dovecot: imap(john): Error: Log synchronization error at seq=2,offset=41576 for /home/john/Mail/INBOX/.imap/Zerna/dovecot.index: Extension header update points outside header size Cheers and thanks, Stephen -- ============================================================================= Stephen Davies Consulting P/L Voice: 08-8177 1595 Adelaide, South Australia. Fax : 08-8177 0133 Records & Collections Management. Mobile:040 304 0583

1 0

[Dovecot] Master Users
by Kelsey Cummings 06 Mar '12

06 Mar '12

I have a setup where I need to use a Master User account to login on behalf of users normally authed via PAM. Is there any existing mechanism that will allow master users to be wired down to specific ip address rather than having these very magic user/pass combos be valid from any random host? It would be totally acceptable to be able to say that master logins were only valid from a specific list of hosts rather than wiring specific master users to specific hosts. -- Kelsey Cummings - kgc(a)corp.sonic.net sonic.net, inc. System Architect 2260 Apollo Way 707.522.1000 Santa Rosa, CA 95407

1 1

[Dovecot] Dovecot saves mails in "wrong" folder.
by Khoroshyy Petro 06 Mar '12

06 Mar '12

Hi all I have installed dovecot 1.2.15 and try to use it together with offlineimap and gnus. my problem is that it saves emails into /var/mail/petro instead of ~/Maildir Thanks. Petro. This is my .dovecot.conf default_mail_env = maildir:%h/Maildir And this is my .offlineimaprc [general] accounts = Gmail maxsyncaccounts = 1 [Account Gmail] localrepository = Local remoterepository = Remote [Repository Local] type = IMAP remotehost = localhost port = 143 remoteuser = petro [Repository Remote] type = IMAP remotehost = imap.gmail.com remoteuser = myname(a)gmail.com ssl = yes maxconnections = 1 realdelete = no folderfilter = lambda foldername: foldername in ['INBOX'] --

1 0

[Dovecot] LDAP auth_bind fails
by Pol Bettinger 06 Mar '12

06 Mar '12

Hello, I wanted to configure dovecot for using auth_bind but didn't succeed to me it seems like it does always an anonymous bind. Dovecot version 2.1.1 (I started with 2.1.0 and hoped 2.1.1 would fix it) I tried to play around with the base, pass_attrs,pass_filter to no avail but didn't succeed. Looking at a wireshark trace i only saw 7 packets and it seemed to me dovecot did only an anonymous bind. any help would appreciated Sincerely Pol Bettinger output of mail.log: Mar 6 12:16:34 Dell dovecot: auth: Debug: client in: AUTH#0112#011CRAM-MD5#011service=imap#011secured#011lip=192.168.16.27#011rip=192.168.16.20#011lport=993#011rport=51838 Mar 6 12:16:34 Dell dovecot: auth: Debug: client out: CONT#0112#011PDQ1NjgyMjE3NjYyMDk3NjkuMTMzMTAzMjU5NEBEZWxsPg== Mar 6 12:16:34 Dell dovecot: auth: Debug: client in: CONT<hidden> Mar 6 12:16:34 Dell dovecot: auth: Debug: password(arvi(a)arvoreen.net,192.168.16.20): passdb doesn't support credential lookups Mar 6 12:16:36 Dell dovecot: auth: Debug: client out: FAIL#0112#011user=arvi(a)arvoreen.net output of dovecot -n: # 2.1.1: /etc/dovecot/dovecot.conf # OS: Linux 3.0.0-15-generic i686 Ubuntu 11.10 ext4 auth_debug = yes auth_default_realm = arvoreen.net auth_mechanisms = plain digest-md5 cram-md5 auth_verbose = yes base_dir = /var/run/dovecot/ mail_location = maildir:/var/mail/%d/%1n/%n:INDEX=/var/indexes/%d/%1n/%n 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 { auto = create special_use = \Archive } mailbox Drafts { auto = create special_use = \Drafts } mailbox Junk { auto = create special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = create special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-ldap_pass.conf.ext driver = ldap } plugin { sieve = /var/sieve/%d/%1n/%n sieve_dir = /var/sieve/%d/%1n/%n } protocols = imap lmtp sieve service managesieve-login { inet_listener sieve { port = 4190 } } ssl_cert = </etc/ssl/certs/webmail.arvoreen.pem ssl_key = </etc/ssl/private/webmail.arvoreen.key userdb { args = /etc/dovecot/dovecot-ldap_user.conf.ext driver = ldap } protocol lmtp { mail_plugins = " sieve" } output of cat /etc/dovecot/dovecot-ldap_pass.conf.ext: hosts = 127.0.0.1:389 auth_bind = yes auth_bind_userdn = uid=%n,ou=Users,dc=arvoreen,dc=net base = ou=Users,dc=arvoreen, dc=net ldap_version = 3 olcAccess infomation: olcSuffix: dc=arvoreen,dc=net olcAccess: {0}to attrs=userPassword,shadowLastChange by self write by anonymou s auth by dn="cn=admin,dc=arvoreen,dc=net" write by * none olcAccess: {1}to dn.base="" by * read olcAccess: {2}to * by self write by dn="cn=admin,dc=arvoreen,dc=net" write by * read

2 1

[Dovecot] dovecot 2.1.1 + pigeonhole + avelsieve
by Frank Elsner 06 Mar '12

06 Mar '12

Hello all, I've squirrelmail-webmail-1.4.22, dovecot 2.1.1, dovecot-2.1-pigeonhole-0.3.0 installed and working. But I've problems to get the avelsieve plugin for squirrelmail working with dovecot. The "Message Filters" show up in "Options" of squirrelmail, but "Could not log on to timsieved daemon on your IMAP server ........." dovecot log shows: Mar 6 00:00:47 seymour dovecot: managesieve-login: Disconnected: Too many invalid commands. (no auth attempts in 0 secs): 192.168.28.53, secured Where to look for configuration error(s)? | root@seymour: /usr/local/dovecot/src<156> dovecot -n | # 2.1.1: /usr/local/dovecot/etc/dovecot/dovecot.conf | # OS: Linux 2.6.35.14-106.fc14.i686.PAE i686 Fedora release 14 (Laughlin) ext3 | default_vsz_limit = 512 M | disable_plaintext_auth = no | first_valid_uid = 200 | last_valid_uid = 65534 | listen = * | lmtp_save_to_detail_mailbox = yes | login_greeting = c64.shuttle.de - IMAPs Service (dovecot) ready. | login_log_format_elements = %u %r %c | mail_location = maildir:/var/spool/mail/%u | mail_log_prefix = "%Us(%u,%r): " | mail_plugin_dir = /usr/dovecot/lib/dovecot/ | mail_plugins = " notify quota" | 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 = dovecot | driver = pam | } | plugin { | mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename flag_change append | mail_log_fields = uid box from subject msgid size flags | mail_log_group_events = yes | quota = maildir:User quota | quota_rule = *:storage=2G | quota_rule2 = Trash:storage=+100M | sieve = ~/.sieve | sieve_dir = ~/sieve | } | postmaster_address = postmaster(a)moltke28.b.shuttle.de | protocols = imap sieve | service anvil { | client_limit = 1027 | } | service auth { | unix_listener auth-client { | group = exim | mode = 0660 | user = exim | } | } | service imap-login { | inet_listener imap { | port = 143 | } | inet_listener imaps { | port = 993 | ssl = yes | } | process_limit = 512 | process_min_avail = 10 | } | service imap-postlogin { | executable = script-login /usr/dovecot/bin/imap-post-login | } | service imap { | executable = imap imap-postlogin | } | service lmtp { | inet_listener lmtp { | address = 0.0.0.0 | port = 24 | } | } | service managesieve-login { | inet_listener sieve { | port = 4190 | } | } | service pop3-login { | inet_listener pop3 { | port = 110 | } | inet_listener pop3s { | port = 995 | ssl = yes | } | } | service pop3 { | process_limit = 1024 | } | ssl_cert = </usr/local/etc/c64.shuttle.de.CRT | ssl_cipher_list = ALL:!LOW:!SSLv2 | ssl_key = </usr/local/etc/c64.shuttle.de-dovecot.KEY | ssl_parameters_regenerate = 6 hours | userdb { | driver = passwd | } | verbose_proctitle = yes | protocol lmtp { | mail_plugins = " notify quota quota" | } | protocol lda { | mail_plugins = " notify quota quota" | } | protocol imap { | imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags | imap_logout_format = [%i/%o] | mail_max_userip_connections = 0 | mail_plugins = " notify quota mail_log quota imap_quota listescape" | } And the avelsieve config.php has: | /* **** NEW OPTION (as of 0.9.4) **** | * Space separated list of preferred SASL mechanisms for the authentication to | * timsieved */ | | $preferred_mech = "PLAIN"; Ok, looking forward for any tip, Frank Elsner

2 1

[Dovecot] Concurrent dovecot instances on same spool?
by Jacek Osiecki 06 Mar '12

06 Mar '12

Hi all, While reading the "Multiple locations, 2 servers - planning questions..." thread, it just hit me that I was planning to do something that seems to be a bit hazardous... I am setting up an high-availability server set, which consists of two (or more) servers with common disk space, all set behind redundant hardware load balancers. At first, there will be two servers and disk space will be kept on NFS server or on both servers using DRBD+OCFS2 filesystem (what creates kind of networked RAID1 storage space). This will be done mostly to keep WWW service available in case when one of servers fails. However, if we have everything redundant, why not have the same with SMTP and POP3/IMAP? But - won't anything fail if two (or more) dovecots are accessing the same disk space, both for IMAP/POP3 and LDA/LMTP? If it is possible, that would be a good solution for the mentioned thread. If not - where are possible dangers, and are there any plans to make it possible in the future? Greetings, -- Jacek Osiecki joshua(a)ceti.pl GG:3828944 I don't want something I need. I want something I want.

3 4

[Dovecot] testing fts-solr?
by Jean-Daniel Beaubien 05 Mar '12

05 Mar '12

hi everyone, However, how can I verify that solr is working properly? Background: - I'm trying to setup 2.1 with fts_solr and eventually test maildir/mdbox. - I used the following webpage as reference to setup solr: http://www.roessner-network-solutions.com/2012/02/19/full-text-search-with-… I'm looking at /var/log/tomcat6/catalina.out file, but see nothing telling me that it's being used (same for /var/log/mail.log, etc.) Any tips? Thanks

10 34

[Dovecot] \NoSelect on missing folders in LIST
by Peter Mogensen 05 Mar '12

05 Mar '12

Hi, I noticed a difference between courier and dovecot, and I'm not sure which of them is wrong wrt. RFC3501 - if any. I have a Maildir which has been accessed by an Apple Mail client, so it got folders like: INBOX INBOX.Trash INBOX.INBOX.folder INBOX.INBOX.folder.a INBOX.INBOX.folder.b The INBOX.INBOX folder does not exist on disk and is not subscribed. Courier responds to: . list "" "*" with * LIST (\Noselect \HasChildren) "." "INBOX.INBOX" But dovecot does not list that folder using "*". However, if you issue: . list "" "INBOX.%" Dovecot answers: * LIST (\Noselect \HasChildren) "." "INBOX.INBOX" This makes some clients using "*" to get the folder list ignore the folderes below "INBOX.INBOX". I know the recommended client way is to use "%", but I'm still curious about which is the correct behaviour. /Peter

2 3

[Dovecot] GSSAPI auth failing for kmail
by Mark Davies 05 Mar '12

05 Mar '12

Hi, have dovecot 2.0.13 running fine on a NetBSD box, with lots of clients happily authenticating to it with GSSAPI. I've just updated an ArchLinux box to latest new version which has meant its switched from using heimdal to using mit krb5 and its kmail is now also slightly newer. Thunderbird successfully authenticates to dovecot from this machine but kmail now fails. Kmail reports: Unable to authenticate via GSSAPI. The server ... replied: SASL(-1): generic failure: GSSAPI Error: Invalid token was supplied (Token header is malformed or corrupt) The dovecot log reports: Feb 27 13:42:18 bats dovecot: auth: GSSAPI(mark(a)ECS.VUW.AC.NZ,130.195.5.88): Invalid base64 data in continued response Any suggestions on how to track down what specifically has changed and how to fix it? cheers mark

2 11

Re: [Dovecot] testing fts-solr?
by Charles Marcus 05 Mar '12

05 Mar '12

On 2012-03-05 3:43 AM, kadafax(a)gmail.com <kadafax(a)gmail.com> wrote: > Le 02/03/12 13:40, Charles Marcus a écrit : >> On 2012-02-28 11:28 AM, Charles Marcus <CMarcus(a)Media-Brokers.com> wrote: >>> On 2012-02-28 11:05 AM, kfx <kadafax(a)gmail.com> wrote: >>>> Ok I feel ashame... it was a third party init scrip who was the >>>> problem :( >>> So... you're saying that Thunderbird now correctly uses server side >>> search? >> Please respond... I need to know whether or not I need to pursue this, >> since we use Thunderbird in house and will be switching soon to >> dovecot... > Yes, for me thunderbird correctly use server side search. Just got confirmation from the OP that his problem with Thunderbird indeed is now gone, so it was a 3rd party init script causing his problems... One less thing to worry about... -- Best regards, Charles

1 0

[Dovecot] 1.0beta to latest and greatest?
by Charles C 05 Mar '12

05 Mar '12

dear dovecot users, This is my first post and with a rather embarassing question. To soften the question up I just want to say I've been very pleased with Dovecot thus far and its low maintenance requirements - perhaps to pleased! I am running an ancient version of Dovecot, version 1.0.beta9. Do I risk corrupting indices etc by upgrading in one go to 2.1.2? Thanks for your input. Charles

2 1

[Dovecot] BlackBerry will not setup my POP3 email, all other mail clients fine
by Ian Solecki 05 Mar '12

05 Mar '12

Hello, hoping someone here might be able to help me or at least point me in the right direction. My company recently (last week) moved to a new dedicated server for website and email hosting. It is a fairly run-of-the-mill Linux machine running cPanel and Dovecot (with the BlackBerry Fastmail service enabled) as a mail server. When we first set up the server, I was able to create a mailbox, access it via any desktop mail client, webmail, AND by setting it up as a basic POP3 account on my BlackBerry. Mail was running fine to and from the BlackBerry, no problems. I deleted that account from my BlackBerry as it was a test account, and went to add my actual account but was unable to do so. Received the "Cannot log in. Verify your email address, user name and password. If the error persists, contact (my domain name)" message. I tried the test account that had been running successfully and sending/receiving emails not minutes earlier, and it would not set up either. I have since tried multiple accounts on multiple BlackBerry devices (different models) on multiple carriers on several of my different domains (all of which point to the same server, of course), to no avail. Yet, any of these accounts still work flawlessly in any desktop mail client (Outlook, OE, Thunderbird, iPad, iPhone, etc). Also, any of these BlackBerrys work flawlessly with any other mail server. The username to log in to these mailboxes is not standard, it's mailboxname+ example.com if the email address is mailboxname(a)example.com and the mail server is mail.example.com. So, I know I have to access the "Advanced Settings" in BlackBerry email setup in order to put this username in. Still, no effect. So, there is something wrong with how mail SETUP works (not sending/receiving, though that may also not work, I have no way of knowing now) between RIM and my server, and it's something that has changed since the server was set up a week ago. My carrier(s) are clueless, my dedicated server provider (Lunarpages) is clueless. Can anyone help?

3 2

[Dovecot] doveconf: Warning: Obsolete settings.... in /etc/dovecot/dovecot.conf: ...
by D Chen 05 Mar '12

05 Mar '12

Got duplicated Warnings from the "doveconf -n" output ! Can anyone explain and fix them ? thx! admin@server:/etc/dovecot$ doveconf -n # 2.0.13: /etc/dovecot/dovecot.conf 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:716: protocol managesieve {} has been replaced by protocol sieve { } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:888: add auth_ prefix to all settings inside auth {} and remove the auth {} section completely doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:926: passdb pam {} has been replaced by passdb { driver=pam } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:1039: userdb passwd {} has been replaced by userdb { driver=passwd } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:1101: auth_user has been replaced by service auth { user } 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:716: protocol managesieve {} has been replaced by protocol sieve { } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:888: add auth_ prefix to all settings inside auth {} and remove the auth {} section completely doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:926: passdb pam {} has been replaced by passdb { driver=pam } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:1039: userdb passwd {} has been replaced by userdb { driver=passwd } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:1101: auth_user has been replaced by service auth { user } # OS: Linux 3.0.0-16-server x86_64 Ubuntu 11.10 log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:~/Maildir 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 passdb { driver = pam - Ignored: } passdb { driver = pam } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap pop3 sieve service auth { unix_listener /var/spool/postfix/private/auth-client { group = postfix mode = 0660 user = postfix } unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } user = root } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_cipher_list = ALL:!LOW:!SSLv2:ALL:!aNULL:!ADH:!eNULL:!EXP:RC4+RSA:+HIGH:+MEDIUM ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = passwd } userdb { driver = passwd } protocol imap { imap_client_workarounds = delay-newmail mail_max_userip_connections = 10 } protocol pop3 { mail_max_userip_connections = 10 pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } protocol lda { deliver_log_format = msgid=%m: %$ mail_plugins = sieve postmaster_address = postmaster quota_full_tempfail = yes rejection_reason = Your message to <%t> was automatically rejected:%n%r }

4 4

[Dovecot] Log sybnch error
by Stephen Davies 05 Mar '12

05 Mar '12

My mail log has many entries like: Mar 2 12:34:13 server dovecot: imap(john): Error: Log synchronization error at seq=2,offset=4264 for /home/john/Mail/INBOX/.imap/SMS Emails/dovecot.index: Extension header update points outside header size Version 2.1.1 dovecot -n gives: # 2.1.1: /usr/etc/dovecot/dovecot.conf # OS: Linux 2.6.33.5-desktop-2mnb i686 Mandriva Linux 2010.2 mail_access_groups = mail mail_privileged_group = mail passdb { driver = pam } protocols = pop3 imap service anvil { chroot = empty client_limit = 0 drop_priv_before_exec = no executable = anvil extra_groups = group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 1 protocol = service_count = 0 type = anvil unix_listener anvil-auth-penalty { group = mode = 0600 user = } unix_listener anvil { group = mode = 0600 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service auth-worker { chroot = client_limit = 1 drop_priv_before_exec = no executable = auth -w extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 1 type = unix_listener auth-worker { group = mode = 0600 user = $default_internal_user } user = vsz_limit = 18446744073709551615 B } service auth { chroot = client_limit = 0 drop_priv_before_exec = no executable = auth extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener auth-client { group = mode = 0600 user = } unix_listener auth-login { group = mode = 0600 user = $default_internal_user } unix_listener auth-master { group = mode = 0600 user = } unix_listener auth-userdb { group = mode = 0666 user = } unix_listener login/login { group = mode = 0666 user = } user = root vsz_limit = 18446744073709551615 B } service config { chroot = client_limit = 0 drop_priv_before_exec = no executable = config extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = config unix_listener config { group = mode = 0600 user = } user = vsz_limit = 18446744073709551615 B } service dict { chroot = client_limit = 1 drop_priv_before_exec = no executable = dict extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = unix_listener dict { group = mode = 0600 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service director { chroot = . client_limit = 0 drop_priv_before_exec = no executable = director extra_groups = fifo_listener login/proxy-notify { group = mode = 00 user = } group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener director-admin { group = mode = 0600 user = } unix_listener login/director { group = mode = 00 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service dns_client { chroot = client_limit = 1 drop_priv_before_exec = no executable = dns-client extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = unix_listener dns-client { group = mode = 0666 user = } unix_listener login/dns-client { group = mode = 0666 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service doveadm { chroot = client_limit = 1 drop_priv_before_exec = no executable = doveadm-server extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 1 type = unix_listener doveadm-server { group = mode = 0600 user = } user = vsz_limit = 18446744073709551615 B } service imap-login { chroot = login client_limit = 0 drop_priv_before_exec = no executable = imap-login extra_groups = group = idle_kill = 0 inet_listener imap { address = port = 143 ssl = no } inet_listener imaps { address = port = 993 ssl = yes } privileged_group = process_limit = 0 process_min_avail = 0 protocol = imap service_count = 1 type = login user = $default_login_user vsz_limit = 18446744073709551615 B } service imap { chroot = client_limit = 1 drop_priv_before_exec = no executable = imap extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1024 process_min_avail = 0 protocol = imap service_count = 1 type = unix_listener login/imap { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } service indexer-worker { chroot = client_limit = 1 drop_priv_before_exec = no executable = indexer-worker extra_groups = group = idle_kill = 0 privileged_group = process_limit = 10 process_min_avail = 0 protocol = service_count = 0 type = unix_listener indexer-worker { group = mode = 0600 user = $default_internal_user } user = vsz_limit = 18446744073709551615 B } service indexer { chroot = client_limit = 0 drop_priv_before_exec = no executable = indexer extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener indexer { group = mode = 0666 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service ipc { chroot = empty client_limit = 0 drop_priv_before_exec = no executable = ipc extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener ipc { group = mode = 0600 user = } unix_listener login/ipc-proxy { group = mode = 0600 user = $default_login_user } user = $default_internal_user vsz_limit = 18446744073709551615 B } service lmtp { chroot = client_limit = 1 drop_priv_before_exec = no executable = lmtp extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = lmtp service_count = 0 type = unix_listener lmtp { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } service log { chroot = client_limit = 0 drop_priv_before_exec = no executable = log extra_groups = group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = log unix_listener log-errors { group = mode = 0600 user = } user = vsz_limit = 18446744073709551615 B } service pop3-login { chroot = login client_limit = 0 drop_priv_before_exec = no executable = pop3-login extra_groups = group = idle_kill = 0 inet_listener pop3 { address = port = 110 ssl = no } inet_listener pop3s { address = port = 995 ssl = yes } privileged_group = process_limit = 0 process_min_avail = 0 protocol = pop3 service_count = 1 type = login user = $default_login_user vsz_limit = 18446744073709551615 B } service pop3 { chroot = client_limit = 1 drop_priv_before_exec = no executable = pop3 extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1024 process_min_avail = 0 protocol = pop3 service_count = 1 type = unix_listener login/pop3 { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } service ssl-params { chroot = client_limit = 0 drop_priv_before_exec = no executable = ssl-params extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = startup unix_listener login/ssl-params { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } service stats { chroot = empty client_limit = 0 drop_priv_before_exec = no executable = stats extra_groups = fifo_listener stats-mail { group = mode = 0600 user = } group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener stats { group = mode = 0600 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } ssl_cert = </etc/pki/tls/certs/dovecot.pem ssl_key = </etc/pki/tls/private/dovecot.pem userdb { driver = passwd } -- ============================================================================= Stephen Davies Consulting P/L Voice: 08-8177 1595 Adelaide, South Australia. Fax : 08-8177 0133 Records & Collections Management. Mobile:040 304 0583

2 4

[Dovecot] doveadm -A stops processing at first uid<first_valid_uid
by Joseph Tam 04 Mar '12

04 Mar '12

I would like to run various doveadm commands that involves all (mail) users like doveadm expunge -A mailbox Trash savedbefore 30d but any doveadm command that uses "-A" to iterate through all users will stop processing at the first account with UID<first_valid_uid. doveadm(sysdaemon): Error: user sysdaemon: Couldn't drop privileges: Mail access for users with GID 5551 not permitted (see first_valid_gid in config file, gid from userdb lookup). doveadm(sysdaemon): Error: User init failed doveadm: Error: Failed to iterate through some users However, these accounts are system accounts (locked password, no shell) and are in userdb to provide UID<->name mapping for utilities like ls, chown, etc. There are various workaround like iterating manually, or setting first_valid_uid to zero, or even reordering users to put all system accounts at the end, but is there a better way to do this? Joseph Tam <jtam.home(a)gmail.com>

2 3

[Dovecot] Multiple namespaces seems to be used at the same time
by Steve Campbell 04 Mar '12

04 Mar '12

I've just converted from an old Centos 3 box to a Centos 6.2 box. I've switched from UW-imap to dovecot in the process. In my configurations, I've placed the multiple namespace sections as suggested by the "Backward compatability" part of the wiki. I use mbox since I mostly copied the home directories from the old to the new server. On some of the clients, it appears that the client is using multiple namespaces at the same time. When they view their subscribed folders, they see multiple "mail" folders instead of just the single "mail" folder under their home directory. The .subscription files are more than likely not correct (haven't looked yet, but will fix them as a user calls), but should this ever happen? I'm also sure the client's prefix isn't set since the old system never required it and there are just so many other things that are required right now on this conversion. Speaking of prefixes, I'd like to get the default of "" (nothing entered) to work for the majority of the users to avoid having to add this to the multiple users we have. Hopefully, by going through each user's home directory and copying the old .mailboxlist to a new .subscriptions file and ensuring the imap folders are in ~/mail will do this. Does this sound resonable? Thanks for any help. The learning curve is getting less steep, but it's still a ways off to the top of the hill. steve campbell

2 1

[Dovecot] doveadm fetch prints duplicate results in 2.1
by Christoph Bußenius 04 Mar '12

04 Mar '12

Hi, when the private namespace has "prefix = INBOX." and you use doveadm fetch to search for "mailbox INBOX", then it prints every message twice: # doveadm fetch -u testuser 'mailbox uid guid' mailbox INBOX mailbox: INBOX uid: 1 guid: 1757c403a4ec4d4fbf040000463889b5 mailbox: INBOX uid: 1 guid: 1757c403a4ec4d4fbf040000463889b5 Without "prefix = INBOX." in the configuration, the messages are only printed once. In 2.0, they were never printed twice. doveconf -n # 2.1.1: /usr/local/dovecot/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-35-server x86_64 Ubuntu 10.04.4 LTS disable_plaintext_auth = no mail_gid = vmail mail_location = mdbox:~/mdbox mail_plugins = acl mail_uid = vmail namespace { inbox = yes location = prefix = INBOX. separator = . } passdb { args = scheme=CRYPT username_format=%u /usr/local/dovecot/etc/dovecot/users driver = passwd-file } 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 -- 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 2

[Dovecot] 2.1.1: Incorrect quoting of RFC 2822 personal parts in ENVELOPE data
by Michael M Slusarz 04 Mar '12

04 Mar '12

I'm seeing this: 1 UID FETCH 31734 (ENVELOPE) * 23 FETCH (UID 31734 ENVELOPE ("Fri, 2 Mar 2012 19:05:24 -0500 (EST)" "XXXXXX" (({22} XXXXX \"X-XX\" XXXXXX NIL "XXXXXXX" "XXXXXXXXX.XXX")) (({22} XXXXX \"X-XX\" XXXXXX NIL "XXXXXXX" "XXXXXXXXX.XXXXXX.XXX")) ((NIL NIL "XXXXXXX" "XXXXXXXXX.XXX")) ((NIL NIL "slusarz" "curecanti.org")) NIL NIL NIL "<1109380587237.1109118788902.20323.7.35190001@scheduler>")) It should be: 1 UID FETCH 31734 (ENVELOPE) * 23 FETCH (UID 31734 ENVELOPE ("Fri, 2 Mar 2012 19:05:24 -0500 (EST)" "XXXXXX" (({20} XXXXX "X-XX" XXXXXX NIL "XXXXXXX" "XXXXXXXXX.XXX")) (({20} XXXXX "X-XX" XXXXXX NIL "XXXXXXX" "XXXXXXXXX.XXXXXX.XXX")) ((NIL NIL "XXXXXXX" "XXXXXXXXX.XXX")) ((NIL NIL "slusarz" "curecanti.org")) NIL NIL NIL "<1109380587237.1109118788902.20323.7.35190001@scheduler>")) since the RFC 2822 quoting characters must be removed. michael

2 1

[Dovecot] LIST-STATUS issue
by Michael M Slusarz 04 Mar '12

04 Mar '12

Looked at the hg commits since 2.1.1, but didn't see anything that was exactly on-point to this... UNSEEN counts seem to be broken when done in a LIST-STATUS call. I see this, for example: >> Timestamp: Thu, 01 Mar 2012 10:55:47 -0700 [...] C: 3 LIST "" (INBOX IN.dovecot) RETURN (STATUS (UNSEEN)) S: * LIST () "." "IN.dovecot" S: * STATUS "IN.dovecot" (UNSEEN 0) S: * LIST () "." "INBOX" S: * STATUS "INBOX" (UNSEEN 3) S: 3 OK List completed. 3 seconds later... >> Timestamp: Thu, 01 Mar 2012 10:55:50 -0700 S: * OK [CAPABILITY IMAP4rev1 LITERAL+ LOGIN-REFERRALS ID ENABLE AUTH=LOGIN XIMAPPROXY] Dovecot ready. C: [LOGIN Command - username: slusarz] S: * OK [XPROXYREUSE] IMAP connection reused by squirrelmail-imap_proxy S: 1 OK User logged in C: 2 EXAMINE IN.dovecot (QRESYNC (1254166849 25800 18484,20260,20393,20705,20860:20868)) S: * FLAGS (\Answered \Flagged \Deleted \Seen \Draft impflag1 impflag2 impflag0 Junk seen NonJunk) S: * OK [PERMANENTFLAGS ()] Read-only mailbox. S: * 13 EXISTS S: * 0 RECENT S: * OK [UNSEEN 5] First unseen. S: * OK [UIDVALIDITY 1254166849] UIDs valid S: * OK [UIDNEXT 20869] Predicted next UID S: * OK [HIGHESTMODSEQ 25800] Highest S: 2 OK [READ-ONLY] Select completed. [...] C: 7 SEARCH RETURN (COUNT) UNSEEN S: * ESEARCH (TAG "7") COUNT 8 S: 7 OK Search completed (0.000 secs). I can confirm that I did not receive 8 dovecot list messages in 3 seconds. :) Once the mailbox is accessed, I am seeing correct counts in LIST-STATUS return again: >> Timestamp: Thu, 01 Mar 2012 10:57:28 -0700 [...] C: 3 LIST "" (INBOX IN.dovecot) RETURN (STATUS (UNSEEN)) S: * LIST () "." "IN.dovecot" S: * STATUS "IN.dovecot" (UNSEEN 8) S: * LIST () "." "INBOX" S: * STATUS "INBOX" (UNSEEN 3) S: 3 OK List completed. I am using imapproxy for these connections, so all access are happening in the same Dovecot access. michael

2 8

[Dovecot] directly addressable public folders issues
by Tom Fernandes 04 Mar '12

04 Mar '12

Hi, I would like to have an address info(a)example.com whose mails are stored in a public folder. I also want certain users to be able to create sieve-filter-rules and subfolders. From what I understand it's a good idea to have a separate location for home and for mail_location. For my normal accounts I have: home = /var/vmail/<user> mail_location = ~/Maildir Is there a way to have the same for public folders? This are my current settings: namespace public { separator = / prefix = public/ location = maildir:/var/vmail/public subscriptions = no } user_attrs = homeDirectory=home=/var/vmail/%$, =mail=maildir:~/Maildir The LDAP-homeDirectory-attribute for info(a)example.com is "public/.info" Like this an incoming mail is stored below /var/vmail/public/.info/Maildir which is good. The MUA seems to read to read from /var/vmail/public/.info though. How can I make the MUA read from /var/vmail/public/.info/Maildir instead? And in case this works - is it possible to have only certain users modify the sieve-rule for this public folder or do I definitely need a passdb-entry for info(a)example.com? Modifying scripts via commandline is not an option... I'm using dovecot 1.2. regards, Tom Fernandes

2 1

[Dovecot] Dovecot clustering with dsync-based replication
by Timo Sirainen 03 Mar '12

03 Mar '12

This document describes a design for a dsync-replicated Dovecot cluster. This design can be used to build at least two different types of dsync clusters, which are both described here. Ville has also drawn overview pictures of these two setups, see http://www.dovecot.org/img/dsync-director-replication.png and http://www.dovecot.org/img/dsync-director-replication-ssh.png First of all, why dsync replication instead of block level filesystem replication? - dsync won't replicate filesystem corruption. - A cold restart of replication won't go through all of the data in the disks, but instead quickly finds out what has changed. - Split brain won't result in downtime or losing any data. If both sides did changes, the changes are merged without data loss. - If using more than 2 storages, the users' replicas can be divided among the other storages. So if one storage goes down, the extra load is shared by all the other storages, not just one. Replication mail plugin ----------------------- This is a simple plugin based on notify plugin. It listens for all changes that happen to mailboxes (new mails, flag changes, etc.) Once it sees a change, it sends an asynchronous (username, priority) notification to replication-notify-fifo. The priority can be either high (new mails) or low (everything else). Optionally the replication plugin can also support synchronous replication of new mail deliveries. In this way it connects to replication-notify UNIX socket, tells it to replicate the user with sync (=highest) priority and waits until it is done or replication_sync_timeout occurs. The IMAP/LMTP client won't see an "OK" reply until the mail is replicated (or the replication has failed). The synchronous replication probably adds a noticeable delay, so it might not be acceptable for IMAP, but might be for LMTP. So, what is listening in those replication-notify* sockets? It depends on if Dovecot is running on director-based setup or not. Aggregator ---------- When running in Dovecot director-based setup, all of the Dovecot backends (where replication plugin runs) also run "aggregator" process. Its job is very simple: It proxies the notifications from mail plugin and sends them via a single TCP connection to the replicator process running in Dovecot proxies. This is simply an optimization to avoid tons of short lived TCP connections directly from replication plugin to director server. When not running in Dovecot director setup (i.e. there is only a single Dovecot instance that handles all of the users), there is no point in having an aggregator proxy, because the replicator process is running on the same server. In this kind of setup the replicator process directly listens on the replication-notify* sockets. Replicator ---------- The initial design for replicator isn't very complex either: It keeps a priority queue of all users, and replicates those users at the top of the queue. Notifications about changes to user's mailboxes (may) move the user up in the priority queue. If the user at the top of the queue already has been replicated "recently enough", the replicator stops its work until new changes arrive or the "recently enough" is no longer that. dsync can do two types of syncs: quick syncs and full syncs. A quick sync trusts indexes and does the replication with the least amount of work and network traffic. A quick sync is normally enough to replicate all changes, but just in case something has gone wrong there's also the full sync option, which guarantees that the mailboxes end up being fully synced. A full sync is slower though, and uses more network traffic. The priority queue is sorted by: 1. Priority (updated by a notification from replication plugin) 2. If priority!=none: Last fast sync (those users are replicated first whose last replication time is oldest) 2. If priority=none: Last full sync (these users should already be fully synced, but do a full sync for them once in a while anyway) All users get added to the replication queue at replicator startup with "none" priority. The list of users is looked up via userdb iteration. If the previous replication state is found from a disk dump, it's used to update the priorities, last_*_sync timestamps and other replication state. Replicator process creates such dumps periodically [todo: every few mins? maybe a setting?]. Replicator starts replicating users at the top of the queue, setting their priorities to "none" before starting. This means that if another change notification arrives during replication, the priority is bumped up and no changes get lost. replication_max_conns setting specifies how many users are replicated simultaneously. If the user's last_full_sync is older than replication_full_sync_interval setting, a full sync is done instead of a fast sync. If the user at the top of the queue has "none" priority and the last_full_sync is newer than replication_full_sync_interval, the replication stops. [todo: it would be nice to prefer doing all the full syncs at night when there's hopefully less disk I/O] (A global replication_max_conns setting isn't optimal in proxy-based setup, where different backend servers are doing the replication. There it should maybe be a per-backend setting. Then again, it doesn't account for the replica servers that also need to do replication work. Also to properly handle this each backend should have its own replication queue, but this requires doing a userdb lookup for each user to find out their replication server, and this would need to be done periodically in case the backend changes, which can easily happen often with director-based setup. So all in all, none of this is being done in the initial implementation. Ideally the users are distributed in a way that a global replication queue would work well enough.) In director-based setup each director runs a replicator server, but only one of them (master) actually asks the backends to do the replication. The rest of them just keep track of what's happening, and if the master dies or hangs, one of the others becomes the new master. The server with lowest IP address is always the master. The replicators are connected to a ring like the directors, using the same director_servers setting. The communication between them is simply about notifications of what's happening to users' priorities. Preferably the aggregators would always connect to the master server, but this isn't required. In general there's not much that can go wrong, since it's not a problem if two replicators request a backend to start replication for the same user or if the replication queue states aren't identical. If the replication is running too slowly [todo: means what exactly?], log a warning and send an email to admin. So, how does the actual replication happen? Replicator connects to doveadm server and sends a "sync -u user@domain" command. In director-based setup the doveadm server redirects this command to the proper backend. doveadm sync ------------ This is an independent feature from all of the above. Even with none of it implemented, you could run this to replicate a user. Most of this is already implemented. The only problem is that currently you need to explicitly tell it where to sync. So, when the destination isn't specified, it could do a userdb lookup and use the returned "mail_replica" field as the destination. Multiple (sequentially replicated) destinations could be supported by returning "mail_replica2", "mail_replica3" etc. field. In NFS-based (or shared filesystem-based in general) setup the mail_replica setting is identical to mail_location setting. So your primary mail_location would be in /storage1/user/Maildir, while the secondary mail_replica would be in /storage2/user/Maildir. Simple. In non-NFS-based setup two Dovecot servers talk dsync protocol to each others. Currently dsync already supports SSH-based connections. It would also be easy to implement direct TCP-based connections between two doveadm servers. In future these connections could be SSL-encrypted. Initially I'm only supporting SSH-based connections, as they're already implemented. So what does the mail_replica setting look like in this kind of a setup? I'm not entirely sure. I'm thinking that it could be either "ssh:host" or "ssh:user@host", where user is the SSH login user (this is opposite of the current doveadm sync command line usage). In future then it could support also tcp:host[:port]. Both of these ssh: and tcp: prefixes would also be supported by doveadm sync command line usage (and perhaps the prefixless user@domain be deprecated). dsync can run without any long lived locking and it typically works fine. In case mailbox was modified during dsync, the replicas may not end up being identical, but nothing breaks. dsync currently usually notices this and logs a warning. When these conflicting changes was caused by imap/pop3/lda/etc. this isn't a problem, they've already notified replicator already to perform another sync that will fix it. Running two dsyncs at the same time is more problematic though, mainly related to new emails. Both dsyncs notice that mail X needs to be replicated, so both save it and it results in having a duplicate. To avoid this, there should be a dsync-lock. If this lock exists, dsync should wait until the previous dsync is done and then do it again, just in case there were more changes since the previous sync started. This should conclude everything needed for replication itself. High-availability NFS setup --------------------------- Once you have replication, it's of course nice if the system automatically recovers from a broken storage. In NFS-based setups the idea is to do soft mounts, so if the NFS server goes away things start failing with EIO errors, which Dovecot notices and switches to using the secondary storage(s). In v2.1.0 Dovecot already keeps track of mounted filesystems. Initially they're all marked as "online". When multiple I/O errors occur in a filesystem [todo: how many exactly? where are these errors checked, all around in the code or checking the log?] the mountpoint is marked as "offline" and the connections accessing that storage are killed [todo: again how exactly?]. Another job for replication plugin is to hook into namespace creation. If mail_location points to a mountpoint marked as "offline", it's replaced with mail_replica. This way the user can access mails from the secondary storage without downtime. If the replica isn't fully up to date, this means that some of the mails (or other changes) may temporarily be lost. These will come back again after the original storage has come back up and replication has finished its job. So as long as mails aren't lost in the original storage, there won't be any permanent mail loss. When an offline storage comes back online, its mountpoint's status is initially changed to "failover" (as opposed to "online"). During this state the replication plugin works a bit differently when the user's primary mail_location is in this storage: It first checks if the user is fully replicated, and if so uses the primary storage, otherwise it uses the replica storage. Long running IMAP protocesses check the replication state periodically and kill themselves once the user is replicated, to move back to primary storage. Once replicator notices that all users have been replicated, it tells the backends' to change the "failover" state to "online" (via doveadm server). High-availability non-NFS setup ------------------------------- One possibility is to use Dovecot proxies, which know which servers are down. Instead of directing users to those servers, it would direct them to replica servers. The server states could be handled similar to NFS setup's online vs. failover vs. offline states. Another possibility would be to do the same as above, except without separate proxy servers. Just make "mail.example.com" DNS point to two IP addresses, and if one Dovecot notices that it's not the user's primary server, it proxies to the secondary server, unless it's down. If one IP is down, clients hopefully connect to the other.

3 5

[Dovecot] keywords/flags questions
by Arnaud Abélard 03 Mar '12

03 Mar '12

Hello, I am currently using dovecot 2.0.13 and I have been working on keywords handling our webmail and I have a few questions about how dovecot handles them. First, if I am not mistaken keywords neeed to be UTF-7 encoded. That means I need to encode special caracters using values between & and - chars. UTF-7 encoding is case sensitive, &AOA- isn't the same chars as &aoa-. But docevot save keywords in lowercase or am I mistaken? For example: . STORE 1:1 flags &AOA-_refaire * 1 FETCH (FLAGS (&aoa-_refaire)) This makes retrieving the keyword properly impossible. What did I miss? My other question is about the permanent flags being displayed upon selecting a mailbox. I'm trying to understand why unused keywords are still showing up in there. Is there a way to force the definitive removal of a keyword from a mailbox? are old keywords kept undefinitely? Thanks in advance, Arnaud -- Arnaud Abélard jabber: arnaud.abelard(a)univ-nantes.fr / twitter: ArnY Administrateur Système DSI Université de Nantes -

3 2

[Dovecot] Desperately need help ! a default dovecot.conf and/or Ubuntu 11.10 postfix/dovecot server configuration issue!
by D Chen 03 Mar '12

03 Mar '12

When ungraded from Ubuntu 11.04 to 11.10, dovecot can't start successfully with lots of errors i.e. "dovecot: doveconf: Warning: ... 'imaps' protocol is no longer necessary, remove it"... At any rate, I want to setup a postfix(MTA)/dovecot(MDA) servers on Ubuntu 11.10, by following the Postfix installation and configuration instruction in Ubuntu Serverguide, in "1.4 Configuring SASL" section on page 190, after run "sudo apt-get install dovecot-common", it requires to edit the section of "auth default" and the "socket listen" option...,in the /etc/dovecot/dovecot.conf file, BUT my /etc/dovecot/dovecot.conf (only about 4k byes) CAN'T find the "auth default" "socket listen" ! I also checked into the /usr/share/doc/dovecot-common/dovecot/example-config, there is a dovecot.conf, it's also about 4k size, and there is no such "auth default" or "socket listen" words can be found ! where is the default dovecot.conf file I can get a copy ? BTW, there is the dovecot.conf.ucf file (what is this for?) which's about 50k and has the "auth default" and "socket listen" words there ! what is supposed the size for the /etc/dovecot/dovecot.conf ? i'm confused! Thx.

3 2

[Dovecot] fts size
by Jan-Frode Myklebust 02 Mar '12

02 Mar '12

Does anybody have any numbers for how large storage one will need for the fts indexing server? I see the wiki says 30% of mailbox size for Squat (partial=4 full=4). Is it similar for lucene/solr? Do I understand correctly if I think http://wiki2.dovecot.org/Plugins/FTS/Lucene will create an index for each user in his home directory? Will this be accounted for in the users' quota? -jf

3 5

[Dovecot] Thanks, was Re: need simpler instructions for user authentication
by David Benfell 02 Mar '12

02 Mar '12

Thanks to everyone who responded to my request. And I apologize that this message isn't properly threaded. I'm in trouble whenever I have to send mail from my gmail account because I automatically pull it down into the same place from which I send my regular mail (from benfell(a)parts-unknown.org ) and I haven't configured that to deal with the gmail account. That makes it difficult to reply properly to mail on this list which I have subscribed to with the gmail account so that I'd actually receive it even when I'm having problems with my main mail system. Timo Sirainen <tss(a)iki.fi> responded that I needed a userdb and offered that I should probably add the following to dovecot.conf : userdb { driver = passwd } As near as I can tell--and it's been over a day now--that solved the problem. Thanks!

1 0

[Dovecot] 2.1.1: subscriptions: Removing invalid entry
by Ralf Hildebrandt 01 Mar '12

01 Mar '12

Admittedly, it's not a valid folder name and dovecot is right in removing it: Feb 28 17:50:05 postamt dovecot: imap(kbaessle): Warning: Subscriptions file /home/k/b/kbaessle/Maildir/subscriptions: Removing invalid entry: Entw�rfe ...but when looking at the subscription file AFTER the removal, that file contained an empty line. I don't think that's correct. -- 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

3 2

[Dovecot] need simpler directions on user authentication
by David Benfell 01 Mar '12

01 Mar '12

Hi all, My situation is this: I have postfix running on a Linode under Arch Linux. A recent upgrade to dovecot broke the configuration. Now I get "Couldn't drop privileges: User is missing UID (see mail_uid setting)." I do not want virtual users. I do not particularly want SQL or LDAP. I do have multiple domains. I do use Maildir. I already have SSL certificates for the server which I did manage to get dovecot to quit complaining about. The documentation is driving me nuts. It keeps telling me about stuff I think I don't need. And I can't tell what I actually *do* need. All I want is for system users, including myself, to be able to get their mail. How do I do this? Thank you! David Benfell dbenfell(a)gmail.com

2 1

[Dovecot] need simpler instructions for user authentication
by David Benfell 01 Mar '12

01 Mar '12

Hi all, My situation is this: I have postfix running on a Linode under Arch Linux. A recent upgrade to dovecot broke the configuration. Now I get "Couldn't drop privileges: User is missing UID (see mail_uid setting)." I do not want virtual users. I do not particularly want SQL or LDAP. I do have multiple domains. I do use Maildir. I already have SSL certificates for the server which I did manage to get dovecot to quit complaining about. The documentation is driving me nuts. It keeps telling me about stuff I think I don't need. And I can't tell what I actually *do* need. All I want is for system users, including myself, to be able to get their mail. How do I do this? Thank you! David Benfell dbenfell(a)gmail.com

2 2

[Dovecot] Permission problems
by David Renstrom 01 Mar '12

01 Mar '12

Hi, I've set up a Postfix and Dovecot (only IMAP) combination using MySQL and Postfixadmin on Fedora. Almost everything works correctly now. The only thing bugging me right now is that I always have to change the access privileges of the directories in /var/run/dovecot/ manually to 777 to make it work. As you understand, I'm not particularly happy about this as it doesn't feel secure at all. And I also have to do this every time I reboot since Dovecot resets the old access priviliges (600). As you see I've got a vmail user who belongs to the mail group. Almost all directories under /var/run/dovecot belong to user root and group root. They all have the permissions rw--------. Below is some output from the log file dovecot.log: Mar 01 03:31:17 auth: Fatal: net_connect_unix(auth-worker) in directory /run/dovecot failed: Permission denied (euid=101(vmail) egid=12(mail) missing +r perm: /run/dovecot/auth-worker, dir owned by 0:97 mode=0755) Mar 01 03:31:17 master: Error: service(auth): command startup failed, throttling Mar 01 03:31:46 imap-login: Info: Disconnected (auth failed, 1 attempts): method=PLAIN, rip=94.254.99.6, lip=91.123.204.174 What is wrong here and how can I correct it? Thanks in advance! /David R.

3 2

[Dovecot] remove messages once downloaded
by Michael Sidoric 01 Mar '12

01 Mar '12

> > I need some help with the dovecot configuration. I want to remove > downloaded messages from Mail Server once the messages have been > successfully downloaded by pop3-clients, even when the clients have been > configured to save copy of messages in the Server. timo is quite correct -- consider imap instead, that's why the protocol exists.

5 5

[Dovecot] dovecot-2.1-pigeonhole-0.3.0 identifier redeclared: sieve_multiscript_run (patch)
by Piotr Tarnowski 29 Feb '12

29 Feb '12

Hi, I recently compiled dovecot-2.1.1 on Solaris 10 with Sun Studio, but when I want to compile Sieve for this version (dovecot-2.1-pigeonhole-0.3.0) I get an error: "sieve.c", line 578: identifier redeclared: sieve_multiscript_run and I see that declaration in sieve.h is different from definition in sieve.c, so compilation process fails with SunStudio cc compiler. I have done a quick hack to correct this, and then compiled successfully. Patch is included as attachment. Full output, OS and compiler versions below: libtool: compile: cc -DHAVE_CONFIG_H -I. -I../.. -I/home/soft/dovecot/dovecot-2.1.1 -I/home/soft/dovecot/dovecot-2.1.1/src/lib -I/home/soft/dovecot/dovecot-2.1.1/src/lib-dict -I/home/soft/dovecot/dovecot-2.1.1/src/lib-dns -I/home/soft/dovecot/dovecot-2.1.1/src/lib-mail -I/home/soft/dovecot/dovecot-2.1.1/src/lib-imap -I/home/soft/dovecot/dovecot-2.1.1/src/lib-fs -I/home/soft/dovecot/dovecot-2.1.1/src/lib-charset -I/home/soft/dovecot/dovecot-2.1.1/src/lib-index -I/home/soft/dovecot/dovecot-2.1.1/src/lib-storage -I/home/soft/dovecot/dovecot-2.1.1/src/lib-storage/index -I/home/soft/dovecot/dovecot-2.1.1/src/lib-storage/index/raw -I/home/soft/dovecot/dovecot-2.1.1/src/lib-lda -I/home/soft/dovecot/dovecot-2.1.1/src/lda -I/home/soft/dovecot/dovecot-2.1.1/src/lib-master -I/home/soft/dovecot/dovecot-2.1.1/src/lib-settings -DMODULEDIR=\"/usr/local/dovecot-2.1.1/lib/dovecot\" -I/usr/local/openldap/include -I/usr/local/ssl/include -I/usr/local/include -xO3 -xautopar -c sieve.c -KPIC -DPIC -o .libs/sieve.o "sieve-common.h", line 33: warning: useless declaration "/home/soft/dovecot/dovecot-2.1.1/src/lib-storage/mailbox-list.h", line 13: warning: useless declaration "sieve.c", line 578: identifier redeclared: sieve_multiscript_run current : function(pointer to struct sieve_multiscript {pointer to struct sieve_instance {..} svinst, pointer to struct sieve_result {..} result, pointer to const struct sieve_message_data {..} msgdata, pointer to const struct sieve_script_env {..} scriptenv, int status, _Bool active, _Bool keep, pointer to struct ostream {..} teststream}, pointer to struct sieve_binary {}, pointer to struct sieve_error_handler {pointer to struct pool {..} pool, int refcount, pointer to struct sieve_instance {..} svinst, pointer to struct sieve_error_handler {..} parent, unsigned int max_errors, unsigned int errors, unsigned int warnings, _Bool log_info, _Bool log_debug, pointer to function(..) returning void verror, pointer to function(..) returning void vwarning, pointer to function(..) returning void vinfo, pointer to function(..) returning void vdebug, pointer to function(..) returning void free}, unsigned int, _Bool) returning _Bool previous: function(pointer to struct sieve_multiscript {pointer to struct sieve_instance {..} svinst, pointer to struct sieve_result {..} result, pointer to const struct sieve_message_data {..} msgdata, pointer to const struct sieve_script_env {..} scriptenv, int status, _Bool active, _Bool keep, pointer to struct ostream {..} teststream}, pointer to struct sieve_binary {}, pointer to struct sieve_error_handler {pointer to struct pool {..} pool, int refcount, pointer to struct sieve_instance {..} svinst, pointer to struct sieve_error_handler {..} parent, unsigned int max_errors, unsigned int errors, unsigned int warnings, _Bool log_info, _Bool log_debug, pointer to function(..) returning void verror, pointer to function(..) returning void vwarning, pointer to function(..) returning void vinfo, pointer to function(..) returning void vdebug, pointer to function(..) returning void free}, enum sieve_runtime_flags {SIEVE_RUNTIME_FLAG_NOGLOBAL(1)}, _Bool) returning _Bool : "sieve.h", line 168 cc: acomp failed for sieve.c *** Error code 1 dmake: Fatal error: Command failed for target `sieve.lo' Current working directory /home/soft/dovecot/dovecot-2.1-pigeonhole-0.3.0/src/lib-sieve *** Error code 1 The following command caused the error: fail= failcom='exit 1'; \ for f in x $MAKEFLAGS; do \ case $f in \ *=* | --[!k]*);; \ *k*) failcom='fail=yes';; \ esac; \ done; \ dot_seen=no; \ target=`echo all-recursive | sed s/-recursive//`; \ list='plugins'; for subdir in $list; do \ echo "Making $target in $subdir"; \ if test "$subdir" = "."; then \ dot_seen=yes; \ local_target="$target-am"; \ else \ local_target="$target"; \ fi; \ (cd $subdir && dmake $local_target) \ || eval $failcom; \ done; \ if test "$dot_seen" = "no"; then \ dmake "$target-am" || exit 1; \ fi; test -z "$fail" dmake: Fatal error: Command failed for target `all-recursive' % uname -a SunOS soft 5.10 Generic_142909-17 sun4u sparc SUNW,Sun-Fire-V890 Solaris % version Machine hardware: sun4u OS version: 5.10 Processor type: sparc Hardware: SUNW,Sun-Fire-V890 The following components are installed on your system: Sun Studio 12 update 1 Sun Studio 12 update 1 C Compiler Sun Studio 12 update 1 C++ Compiler Sun Studio 12 update 1 Tools.h++ 7.1 Sun Studio 12 update 1 C++ Standard 64-bit Class Library Sun Studio 12 update 1 Garbage Collector Sun Studio 12 update 1 Fortran 95 Sun Studio 12 update 1 Debugging Tools (including dbx) Sun Studio 12 update 1 IDE Sun Studio 12 update 1 Performance Analyzer (including collect, ...) Sun Studio 12 update 1 Performance Library Sun Studio 12 update 1 Scalapack Sun Studio 12 update 1 LockLint Sun Studio 12 update 1 Building Software (including dmake) Sun Studio 12 update 1 Documentation Set Sun Studio 12 update 1 /usr symbolic links and GNOME menu item version of "/opt/sunstudio12.1/bin/../prod/bin/../../bin/cc": Sun C 5.10 SunOS_sparc 2009/06/03 version of "/opt/sunstudio12.1/bin/../prod/bin/../../bin/CC": Sun C++ 5.10 SunOS_sparc 2009/06/03 version of "/opt/sunstudio12.1/bin/../prod/bin/../../bin/f90": Sun Fortran 95 8.4 SunOS_sparc 2009/06/03 version of "/opt/sunstudio12.1/bin/../prod/bin/../../bin/dbx": Sun DBX Debugger 7.7 SunOS_sparc 2009/06/03 version of "/opt/sunstudio12.1/bin/../prod/bin/../../bin/analyzer": Sun Analyzer 7.7 SunOS_sparc 2009/06/03 version of "/opt/sunstudio12.1/bin/../prod/bin/../../bin/dmake": Sun Distributed Make 7.9 SunOS_sparc 2009/06/03 Regards -- [ Piotr Tarnowski piotr.tarnowski(a)us.edu.pl ] [ Unix Administrator at University of Silesia, Katowice, Poland ]

2 1

[Dovecot] What's behind the message ...
by Frank Elsner 29 Feb '12

29 Feb '12

... Warning: /media/Backup28a is no longer mounted. If this is intentional, remove it with doveadm mount Hello, the above message appeared when I restarted dovecot. What has dovecot to deal with my USB-Backup-Disk? Dovecot cares about filesystem without any relation to the mail system? Why this? What's bedind? Thanks in advance, Frank Elsner

2 2

[Dovecot] per-user limit?
by Peter Hessler 29 Feb '12

29 Feb '12

I am seeing a problem where users are limited to 6 imap logins total. One of my users has a bunch of phones and computers, and wants them all on at the same time. I'm looking through my configuration, and I cannot see a limit on how many times a single user can connect. He is connecting from different IPs. Any ideas? My logs show the following error when they attempt to auth for a 7th time: dovecot: imap-login: Disconnected (no auth attempts): rip=111.yy.zz.xx, lip=81.209.183.113, TLS $ dovecot -n # 2.0.16: /etc/dovecot/dovecot.conf # OS: OpenBSD 5.1 amd64 ffs auth_mechanisms = plain login base_dir = /var/dovecot/ listen = *, [::] mail_location = maildir:/usr/home/%u/Maildir 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 mbox_write_locks = fcntl passdb { driver = bsdauth } service auth { unix_listener /var/run/dovecot/auth-master { mode = 0600 } unix_listener /var/spool/postfix/private/auth { group = wheel mode = 0660 user = _postfix } user = root } service imap-login { process_limit = 128 process_min_avail = 6 service_count = 1 user = _dovecot } service pop3-login { process_limit = 64 process_min_avail = 6 service_count = 1 user = _dovecot } ssl_cert = </etc/ssl/dovecotcert.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = passwd } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } protocol lda { mail_plugins = sieve postmaster_address = postmaster(a)theapt.org } -- We are all in the gutter, but some of us are looking at the stars. -- Oscar Wilde

4 4

[Dovecot] Post-login scripting - Trash cleanup
by list＠airstreamcomm.net 29 Feb '12

29 Feb '12

We are considering using the post-login scripting to clear trash older than 90 days from user accounts. has anyone done this, and if so did this cause logins to slow down too much waiting for the trash to purge? One idea was to execute the trash purge script once a day by tracking their logins and seeing that it has already ran that day. Another idea was to call the trash purge script in the background and continue without acknowledging that it has finished to keep logins speedy.

3 4

[Dovecot] Master user
by Emiliano Rago 29 Feb '12

29 Feb '12

Hi, I'd like to have a master user that can read the other users mailboxes. I have only one user who read and write the mail (i.e. I use the static userdb) and I use namespace for public and shared mailboxes. I can authenticate to the server but I am not able to list the mailboxes: > emiliano@dovecot:~$ telnet localhost imap > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. > * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN] Dovecot ready. > 1 login user*master password > 1 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 > 5 LIST "" * > * LIST (\Unmarked) "." "INBOX" > * LIST (\Noselect \HasNoChildren) "." "shared" > * LIST (\Noselect \HasChildren) "." "public" > 5 OK List completed. > * BYE Server shutting down. > Connection closed by foreign host. This is my conf: > # 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) ext4 > auth_master_user_separator = * > disable_plaintext_auth = no > mail_location = maildir:/data/MAIL/MAILDIR/%u:INBOX=/data/MAIL/INBOX/%u:INDEX=/data/MAIL/METADATA/%u > mbox_write_locks = fcntl > namespace { > inbox = yes > location = > prefix = > separator = . > type = private > } > namespace { > list = yes > location = maildir:/data/MAIL/MAILDIR/%%u:INDEX=/data/MAIL/MAILDIR/shared/%u/%%u > prefix = shared.%%u. > separator = . > subscriptions = no > type = shared > } > namespace { > list = yes > location = maildir:/data/MAIL/SHARED > prefix = public. > separator = . > subscriptions = no > type = public > } > passdb { > driver = pam > } > passdb { > args = /etc/dovecot/master-shared > driver = passwd-file > master = yes > } > plugin { > acl = vfile:/etc/dovecot/global-acls:cache_secs=300 > acl_anyone = allow > acl_shared_dict = file:/var/lib/dovecot/shared-mailboxes.db > } > protocols = imap > service auth { > unix_listener auth-userdb { > group = mailreader > mode = 0600 > user = mailreader > } > } > ssl = no > ssl_cert = </etc/pki/dovecot/certs/dovecot.pem > ssl_key = </etc/pki/dovecot/private/dovecot.pem > userdb { > args = uid=mailreader gid=mailreader home=/ allow_all_users=yes > driver = static > } > protocol lda { > mail_plugins = acl > } > protocol imap { > mail_plugins = acl imap_acl > } And in /etc/dovecot/master-shared: > master:{PLAIN}password What I did wrong? Thanks, Emiliano

2 6

[Dovecot] quota warning script not working after upgrade to 2.1.1
by Ralf Hildebrandt 28 Feb '12

28 Feb '12

With 2.0.18 I was using a quota warning script like this: plugin { ... # Quota quota = maildir quota_rule = INBOX.Trash:storage=+2048M quota_warning = storage=99%% quota-warning 99 %u quota_warning2 = storage=95%% quota-warning 95 %u quota_warning3 = storage=90%% quota-warning 90 %u quota_warning4 = storage=85%% quota-warning 85 %u } # der schickt die Quota warnmails service quota-warning { executable = script /usr/local/scripts/quota-warning2.1 user = root unix_listener quota-warning { mode = 0666 user = vmail group = users } } -rwxr-xr-x 1 root staff 3081 Feb 28 16:56 /usr/local/scripts/quota-warning2.1 But now I'm gettting this in my log: Feb 28 19:19:03 postamt quota-warning2(phxxxpsu): writing message failed Feb 28 19:19:03 postamt dovecot: quota-warning: Fatal: master: service(quota-warning): child 15065 returned error 1 Feb 28 19:40:13 postamt quota-warning2(lxxxve): writing message failed Feb 28 19:40:13 postamt dovecot: quota-warning: Fatal: master: service(quota-warning): child 3318 returned error 1 What is failing here? #!/bin/sh # # Should be run by the Local Delivery Agent # #set -x SCRIPT_NAME="quota-warning2" MAIL_TO=$2 MAIL_FROM="postmaster(a)charite.de" MAIL_QUOTA_PERCENT=$1 MAIL_SUBJECT="Ihre Mailbox ist zu "$1"% voll!" BIN_CAT="/bin/cat" BIN_DATE="/bin/date" BIN_HOSTNAME="/bin/hostname" BIN_LOGGER="/usr/bin/logger" BIN_MV="/bin/mv" BIN_STAT="/usr/bin/stat" #set -x # set misc values HOSTNAME="`${BIN_HOSTNAME}`" # set mail value MAIL_DATE="`${BIN_DATE} '+%a, %d %b %Y %T %z (%Z)'`" MAIL_MESSAGE_ID="`${BIN_DATE} '+%Y%m%d%H%M%S'`@${HOSTNAME}" #To: ${MAIL_TO} # write out message ${BIN_CAT} << EOF | /usr/local/dovecot-2.1/libexec/dovecot/dovecot-lda -d $MAIL_TO -o "plugin/quota=maildir::noenforcing" From: ${MAIL_FROM} Subject: ${MAIL_SUBJECT} Message-Id: <${MAIL_MESSAGE_ID}> Date: ${MAIL_DATE} MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit some warning in german EOF [ "$?" -gt 0 ] && \ ${BIN_LOGGER} -p mail.error -t "${SCRIPT_NAME}(${MAIL_TO})" \ "writing message failed" && exit 1 # log warning attempt ${BIN_LOGGER} -p mail.info -t "${SCRIPT_NAME}(${MAIL_TO}) ${MAIL_QUOTA_PERCENT}%" "delivered!" echo "${MAIL_DATE}: ${SCRIPT_NAME}(${MAIL_TO}) ${MAIL_QUOTA_PERCENT}% delivered!" >> /home/${SCRIPT_NAME}.log -- 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

1 1

[Dovecot] Question: Is Server Side Search announced somehow via the IMAP CAPABILITY string?
by Charles Marcus 28 Feb '12

28 Feb '12

Hey Timo, Subject says it all... This question is a result of an ongoing discussion on the mozilla enterprise list... Is there a standard/reliable way for an IMAP client to determine that an IMAP server supports server side search (with indexes)? Thanks, -- Best regards, Charles

2 4

[Dovecot] Deny create folders
by S. Kremer 28 Feb '12

28 Feb '12

Hi all, is it possible to configure dovecot in that way that special folders do not create automatically by some imap clients? i.e: outlook or thunderbird creates a folder junk-mail i would like that such folders are not created automatically or by users Best regards Stefan

5 6

[Dovecot] ANN: automx - automated mail account provisioning
by Patrick Ben Koetter 28 Feb '12

28 Feb '12

automx I am pleased to announce automx a tool that makes setting up a mail account easy. All your users need to provide is real name, mail address and password. Their mail client and automx will safely handle the rest. Say goodbye to mistyped server settings! Put an end to endless phone calls trying to coach users to configure settings, whose dialogs they can't find. Raise user satisfaction, relieve support and regain time to work on other issues. automx unifies Microsofts and Mozillas mail account provisioning standards in one powerful Open Source tool. Choose from many backends, including LDAP and SQL, and let automx create standard and individualized profiles for multiple domains on the fly! See the details on http://automx.org. p@rick -- state of mind () Digitale Kommunikation http://www.state-of-mind.de Franziskanerstraße 15 Telefon +49 89 3090 4664 81669 München Telefax +49 89 3090 4666 Amtsgericht München Partnerschaftsregister PR 563

1 0

[Dovecot] POP/IMAP on proxy rip issue
by Tomislav Mihalicek 28 Feb '12

28 Feb '12

I have a proxy setup for pop/imap. The proxies are defined in login_trusted_networks = x.x.x.x and for the imap it works fine but for pop3 connections displays the ip address of proxy IP... Dovecots are both 1.2 from the debian repo deb http://xi.rename-it.nl/debian/ stable-auto/dovecot-1.2 main thanks -- View this message in context: http://old.nabble.com/POP-IMAP-on-proxy-rip-issue-tp33400491p33400491.html Sent from the Dovecot mailing list archive at Nabble.com.

2 3

[Dovecot] remove messages once downloaded
by julioarr＠fisica.uh.cu 28 Feb '12

28 Feb '12

I need some help with the dovecot configuration. I want to remove downloaded messages from Mail Server once the messages have been successfully downloaded by pop3-clients, even when the clients have been configured to save copy of messages in the Server. thanks, Julio

4 5

[Dovecot] LDA alias resolution problems..
by Nick Warr 28 Feb '12

28 Feb '12

I use postfix + dovecot LDA + mysql virtual users and up til friday, everything was working just fine. Dovecot is 2.0.beta6 (3156315704ef) Like I said, up til friday, when I added a vacation entry into postfix (which I have now removed to see if it was the reason) mails to the alias virusalert (which is aliased to me) went through just fine. Now I get these sort of errors from the LDA: Feb 27 11:54:03 cluster2 postfix/pipe[31267]: 866F0A41173: to=<virusalert(a)mobilia.it>, relay=dovecot, delay=357414, delays=357413/0.79/0/0.05, dsn=4.3.0, status=deferred (temporary failure. Command output: lda: Fatal: Unknown user ) Other aliases work perfectly, the only difference is that these emails are of local origin, (they're messages from Amavisd) I'm not sure why this has started to be a problem. Can anyone give me an idea where I should start looking? Nick

4 9

[Dovecot] iPhone and custom imap folders problem
by "Przemysław.Orzechowski" 27 Feb '12

27 Feb '12

Hi Im using Dovecot 1.0.10 and everything seems work ok except one client He is accessing his mailbox using iPhone There are several custom folders created and mail is directed to them using procmail The problem is iPhone mail app only sees changes in INBOX and when new mail arrives to other folders it will not see it unlers user accesses this particular folder Is there some kind of workaround for this? Im quite sure its iPhones fault as all other email clients are workin perfectly fine.

6 5

[Dovecot] value for client_limit
by ml 27 Feb '12

27 Feb '12

hello guys hello master Timo i build the last release of dovecot on my centos 5 work well and fine but what the correct value for client limit in service auth { client_limit=6000 } and service anvil { client_limit=6000 } my current dovecot -n ks37777 i386]# dovecot -n # 2.1.1: /etc/dovecot/dovecot.conf # OS: Linux 2.6.31.5-xxxx-rt14-ipv6-32 i686 CentOS release 5.7 (Final) auth_mechanisms = plain login base_dir = /var/run/dovecot/ lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes listen = [::] log_path = /var/log/maillog log_timestamp = %Y-%m-%d %H:%M:%S login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c mail_debug = yes mail_location = maildir:~/Maildir mail_max_userip_connections = 30 mail_plugins = " quota trash zlib" managesieve_notify_capability = mailto managesieve_sieve_capability = comparator-i;octet comparator-i;ascii-casemap fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date spamtest spamtestplus virustest namespace { inbox = yes location = prefix = separator = . } passdb { driver = pam } plugin { autocreate = Trash autocreate2 = Junk autocreate3 = Sent autocreate4 = Drafts autosubscribe = Trash autosubscribe2 = Junk autosubscribe3 = Sent autosubscribe4 = Drafts deleted_to_trash_folder = Trash plugin = $mail_plugins autocreate managesieve sieve quota quota = maildir:User quota quota_exceeded_message = Quota exceeded, please go to http://www.fakessh.eu/over_quota_help.html for instructions on how to fix this. quota_rule = *:storage=10GB quota_rule2 = Trash:storage=+10% quota_rule3 = Spam:storage=+20% quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = ~/.dovecot.sieve sieve_before = /var/sieve-scripts/roundcube.sieve sieve_dir = ~/sieve sieve_global_path = whatever trash = /etc/dovecot/dovecot-trash.conf.ext zlib_save = bz2 zlib_save_level = 9 } protocols = sieve imap pop3 service anvil { client_limit = 6000 } service auth { client_limit = 6000 process_limit = 1 unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0600 user = postfix } unix_listener auth-master { mode = 0666 } unix_listener auth-userdb { mode = 0666 } vsz_limit = 64 M } service imap-login { client_limit = 0 inet_listener imap { port = 0 } inet_listener imaps { address = * , [::] port = 993 } process_limit = 1024 service_count = 1 vsz_limit = 64 M } service imap { process_limit = 1024 process_min_avail = 0 service_count = 1 vsz_limit = 64 M } service managesieve-login { inet_listener managesieve-login { address = * , [::] port = 2000 } process_limit = 1 vsz_limit = 64 M } service pop3-login { inet_listener pop3 { port = 0 } inet_listener pop3s { address = * , [::] port = 995 } process_limit = 1 vsz_limit = 64 M } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { user = mail } user = dovecot } ssl_ca = </etc/pki/tls/certs/class3.crt ssl_cert = </etc/pki/tls/certs/ks37777.kimsufi.com.cert ssl_key = </etc/pki/tls/private/ks37777.kimsufi.com.key ssl_verify_client_cert = yes userdb { driver = passwd } userdb { driver = passwd } version_ignore = yes protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep imap_max_line_length = 64 k mail_plugins = " quota trash zlib autocreate quota imap_quota zlib imap_zlib" } protocol pop3 { mail_plugins = autocreate quota quota autocreate zlib deleted_to_trash pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s } protocol lda { hostname = r13151.ovh.net info_log_path = log_path = mail_plugins = autocreate sieve quota postmaster_address = postmaster(a)fakessh.eu sendmail_path = /usr/lib/sendmail } protocol sieve { managesieve_implementation_string = dovecot managesieve_logout_format = bytes ( in=%i : out=%o ) managesieve_max_line_length = 65536 } -- 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

3 2

[Dovecot] Mail delivery to subfolders via address extension, and prefered lda method
by Micha Krause 27 Feb '12

27 Feb '12

Hi, I want to deliver mails directly to subfolders, based on address extensions. Example: Emails sent to: micha+test(a)example.com Should be stored into user micha, folder INBOX.test I was able to reproduce this with exim and dovecot-lda: command = /usr/lib/dovecot/dovecot-lda -e -m "INBOX.${substr_1:$local_part_suffix}" But I was wondering if I could do this within dovecot, which would enable me to use LMTP instead of dovecot-lda. Which brings me to my second question: Which method is "better" for dovecot, lda or LMTP? Micha Krause

2 2

[Dovecot] Virtual Folders
by jacob＠alltechservices-ia.com 27 Feb '12

27 Feb '12

Hello, I am trying to get virtual folders to work properly, and I can't seem to. I will be as detailed as possible to remove confusion. Thank you in advance. Goal: Essentially, a gmail clone, but one that I can make work on cPanel hosts with roundcube and squirrel mail, etc. By default, cpanel creates user mail dir structure of (maildir++) inbox, drafts, sent, junk, and trash (with no dovecot specific files until first login) I would like to replace all those folders with virtual representations with more capabilities. I would like to achieve the conversation view that gmail has pulled off so well. cPanel, stock, generates the following dovecot -n: (i am still not sure how it negotiates mail_location yet) # 1.2.17: /etc/dovecot.conf # OS: Linux 2.6.18-238.5.1.el5xen x86_64 CentOS release 5.7 (Final) ssl_cert_file: /etc/dovecot/ssl/dovecot.crt ssl_key_file: /etc/dovecot/ssl/dovecot.key ssl_cipher_list: ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:-LOW:-SSLv2:-EXP login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login login_process_per_connection: no login_processes_count: 10 login_max_processes_count: 100 login_max_connections: 500 mail_max_userip_connections: 200 maildir_copy_preserve_filename: yes mail_plugins: quota imap_quota namespace: type: private prefix: INBOX. inbox: yes list: yes subscriptions: yes lda: postmaster_address: postmaster(a)example.com auth default: mechanisms: plain login cache_size: 2048 username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789!#$-=?^_{}~./@+% passdb: driver: checkpassword args: /usr/local/cpanel/bin/dovecot-auth userdb: driver: prefetch socket: type: listen client: path: /var/run/dovecot/auth-client mode: 438 plugin: quota: maildir quota_rule: Trash:ignore I started a test box with Debian running the same version of dovecot (1.2.x) and on that system I run into problems every time I make a virtual folder a root folder. I assume it is trying to look up a normal folder instead of the virtual ones and I am confusing it. So I came here because it would be really really neat if I could pull this off. Again, thank you in advance. -cornfeed

2 1

[Dovecot] Dovecot 2.1 with custom OpenSSL fails to build
by Andreas M. Kirchwitz 27 Feb '12

27 Feb '12

Hello Dovecot users! There seems to be a new dependency in some modules (eg, lib-storage, libdovecot-lda, libdovecot-ssl) on OpenSSL. In Dovecot 2.0, those modules didn't require OpenSSL, but 2.1 does. For the linking process the path to the OpenSSL library isn't specified properly (SSL_LIBS). Dovecot fails to build if OpenSSL is in a non-standard path. (Haven't checked if SSL_CFLAGS isn't properly used as well.) Example for lib-storage: env SSL_CFLAGS="-I/usr/local/ssl/include" SSL_LIBS="-L/usr/local/ssl/lib -Wl,-R/usr/local/ssl/lib -lcrypto -lssl" ./configure --prefix=/usr/local/${DOVECOTVER} --with-ssl=openssl --with-ssldir=/usr/local/${DOVECOTVER}/etc/dovecot/certs make gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-master -I../../src/lib-settings -I../../src/lib-mail -I../../src/lib-storage -DPKG_RUNDIR=\""/usr/local/Dovecot-2.1.1/var/run/dovecot"\" -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -I/usr/local/ssl/include -MT master-connection.o -MD -MP -MF .deps/master-connection.Tpo -c -o master-connection.o master-connection.c mv -f .deps/master-connection.Tpo .deps/master-connection.Po /bin/sh ../../libtool --tag=CC --mode=link gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -I/usr/local/ssl/include -no-undefined -Wl,--as-needed -o indexer-worker indexer-worker.o indexer-worker-settings.o master-connection.o ../../src/lib-storage/libdovecot-storage.la ../../src/lib-dovecot/libdovecot.la -export-dynamic -ldl -lrt libtool: link: gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -I/usr/local/ssl/include -Wl,--as-needed -o .libs/indexer-worker indexer-worker.o indexer-worker-settings.o master-connection.o -Wl,--export-dynamic ../../src/lib-storage/.libs/libdovecot-storage.so ../../src/lib-dovecot/.libs/libdovecot.so -ldl -lrt -Wl,-rpath -Wl,/usr/local/Dovecot-2.1.1/lib/dovecot /usr/bin/ld: warning: libcrypto.so.1.0.0, needed by ../../src/lib-storage/.libs/libdovecot-storage.so, not found (try using -rpath or -rpath-link) /usr/bin/ld: warning: libssl.so.1.0.0, needed by ../../src/lib-storage/.libs/libdovecot-storage.so, not found (try using -rpath or -rpath-link) ../../src/lib-storage/.libs/libdovecot-storage.so: undefined reference to `OBJ_txt2nid' ../../src/lib-storage/.libs/libdovecot-storage.so: undefined reference to `SSL_set_ex_data' [...] # ldd src/lib*/.libs/*.so src/lib-dovecot/.libs/libdovecot.so: linux-gate.so.1 => (0x00979000) libdl.so.2 => /lib/libdl.so.2 (0x00c31000) librt.so.1 => /lib/librt.so.1 (0x009ed000) libc.so.6 => /lib/libc.so.6 (0x0054d000) /lib/ld-linux.so.2 (0x00c12000) libpthread.so.0 => /lib/libpthread.so.0 (0x008f4000) src/lib-lda/.libs/libdovecot-lda.so: linux-gate.so.1 => (0x0096d000) libdovecot-storage.so.0 => /usr/local/src/dovecot-2.1.1/src/lib-storage/.libs/libdovecot-storage.so.0 (0x00ae4000) libdovecot.so.0 => /usr/local/src/dovecot-2.1.1/src/lib-dovecot/.libs/libdovecot.so.0 (0x00110000) librt.so.1 => /lib/librt.so.1 (0x00189000) libc.so.6 => /lib/libc.so.6 (0x00192000) libcrypto.so.1.0.0 => not found libssl.so.1.0.0 => not found libdl.so.2 => /lib/libdl.so.2 (0x0031c000) libpthread.so.0 => /lib/libpthread.so.0 (0x00ebc000) /lib/ld-linux.so.2 (0x003f8000) src/lib-sql/.libs/libdovecot-sql.so: linux-gate.so.1 => (0x00a95000) libdovecot.so.0 => /usr/local/src/dovecot-2.1.1/src/lib-dovecot/.libs/libdovecot.so.0 (0x002b6000) libdl.so.2 => /lib/libdl.so.2 (0x00ab8000) librt.so.1 => /lib/librt.so.1 (0x0072a000) libc.so.6 => /lib/libc.so.6 (0x008f7000) /lib/ld-linux.so.2 (0x00ebd000) libpthread.so.0 => /lib/libpthread.so.0 (0x00619000) src/lib-ssl-iostream/.libs/libdovecot-ssl.so: linux-gate.so.1 => (0x00da6000) libcrypto.so.1.0.0 => not found libssl.so.1.0.0 => not found libdl.so.2 => /lib/libdl.so.2 (0x00df0000) librt.so.1 => /lib/librt.so.1 (0x00112000) libc.so.6 => /lib/libc.so.6 (0x00b5e000) /lib/ld-linux.so.2 (0x00e76000) libpthread.so.0 => /lib/libpthread.so.0 (0x005a6000) src/lib-storage/.libs/libdovecot-storage.so: linux-gate.so.1 => (0x006ed000) libcrypto.so.1.0.0 => not found libssl.so.1.0.0 => not found libdovecot.so.0 => /usr/local/src/dovecot-2.1.1/src/lib-dovecot/.libs/libdovecot.so.0 (0x00c66000) libdl.so.2 => /lib/libdl.so.2 (0x00491000) librt.so.1 => /lib/librt.so.1 (0x00be2000) libc.so.6 => /lib/libc.so.6 (0x00110000) /lib/ld-linux.so.2 (0x0036b000) libpthread.so.0 => /lib/libpthread.so.0 (0x0029a000) Without SSL_CFLAGS and SSL_LIBS but just PKG_CONFIG_PATH, it also won't work. Help appreciated ... Andreas

2 1

[Dovecot] Error with 2.0.18
by Ralf Hildebrandt 27 Feb '12

27 Feb '12

Today I found this in my log: Feb 26 14:27:51 postamt dovecot: imap(tscxxxf): Error: mmap(/home/t/s/tscxxxf/Maildir/dovecot.index.search.uids) failed: Cannot allocate memory Feb 26 14:27:51 postamt dovecot: imap(tscxxxf): Error: Corrupted squat uidlist file /home/t/s/tscxxxf/Maildir/dovecot.index.search.uids: uidlist not found Feb 26 14:27:52 postamt dovecot: imap(tscxxxf): Panic: file squat-trie.c: line 289 (squat_trie_lock): assertion failed: (trie->fd != -1) Feb 26 14:27:52 postamt dovecot: imap(tscxxxf): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x3d44a) [0xb771644a] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x3d4bb) [0xb77164bb] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0xb7716d87] -> /usr/local/lib/dovecot/lib21_fts_squat_plugin.so(+0x3bfa) [0xb74e1bfa] -> /usr/local/lib/dovecot/lib21_fts_squat_plugin.so(squat_trie_build_deinit+0x9fc) [0xb74e4d3c] -> /usr/local/lib/dovecot/lib21_fts_squat_plugin.so(+0x2a95) [0xb74e0a95] -> /usr/local/lib/dovecot/lib20_fts_plugin.so(fts_backend_build_deinit+0x1b) [0xb752f6bb] -> /usr/local/lib/dovecot/lib20_fts_plugin.so(+0x3726) [0xb7530726] -> /usr/local/lib/dovecot/lib20_fts_plugin.so(+0x51d3) [0xb75321d3] -> /usr/local/lib/dovecot/lib20_fts_plugin.so(+0x5c34) [0xb7532c34] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_search_next_nonblock+0x3b) [0xb778b0cb] -> dovecot/imap [tscxxxf 141.42.206.38 SELECT UID SEARCH]() [0x805ce6e] -> dovecot/imap [tscxxxf 141.42.206.38 SELECT UID SEARC Feb 26 14:27:55 postamt dovecot: master: Error: service(imap): child 18468 killed with signal 6 (core dumped) -- 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] Dovecot altmove questions
by Maria Arrea 27 Feb '12

27 Feb '12

Hello We are using Dovecot 2.0.17 with mdbox+zlib and we are evaluating alternative storage. These are the relevant settings mdbox_rotate_interval = 1d mdbox_rotate_size=60m [...] zlib_save_level = 9 # 1..9 zlib_save = gz # or bz2 [...] zlib plugin enabled in dovecot-lda These are my questions: 1º General mdbox question. We are happy usings zlib_save, but we would like to try bzip2 compression. Can we change zlib to bzlib without problems? In other words, can we mix & match gzipped and bzipped messages in the same mdbox file ? 2º With doveadm altmove we can move messages matching a pattern to alternate storage. I have read an older post in this mailing list about passing specific mdbox options to doveadm altmove. Should be a good idea to have a "main" mdbox area with zlib 9 and mdbox_rotate=1d and mdox_rotate_size=60m and an "alternate area" with bzip9, mdbox_rotate=1 week and rotate_size > 60 MB? In the alternate area should only be "old" mail (1 year older). 3º We have separate raids for indexes (raid 1+0) and mdboxes (raid 5). We have almost 3 TB of gzipped mdboxes, and our backup (bacula) is taking almost 16 hours to make a full backup. Our main problem is that indexes are backupd hours before mdboxes, and that bring us some inconsistencies. What is the "right" way of backing up for separate indexes and mdboxes? Thank you for your support. Maria

3 2

[Dovecot] IMAP-proxy or not with sogo webmail and dovecot backend
by Jan-Frode Myklebust 27 Feb '12

27 Feb '12

We've been collecting some stats to see what kind of benefits UP/SquirrelMail's IMAP Proxy in for our SOGo webmail users. Dovecot is running in High-performance mode http://wiki2.dovecot.org/LoginProcess with authentication caching http://wiki2.dovecot.org/Authentication/Caching During the weekend two servers (webmail3 and webmail4) has been running with local imapproxy and two servers without (webmail1 and webmail2). Each server has served about 1 million http requests, over 3 days. server avg. response time # requests ---------------------------------------------------- webmail1.example.net 0.370411 1092386 webmail2.example.net 0.374227 1045141 webmail3.example.net 0.378097 1043919 imapproxy webmail4.example.net 0.378593 1028653 imapproxy ONLY requests that took more than 5 seconds to process: server avg. response time # requests ---------------------------------------------------- webmail1.example.net 26.048 1125 webmail2.example.net 26.2997 1080 webmail3.example.net 28.5596 808 imapproxy webmail4.example.net 27.1004 964 imapproxy ONLY requests that took more than 10 seconds to process: server avg. response time # requests ---------------------------------------------------- webmail1.example.net 49.1407 516 webmail2.example.net 53.0139 459 webmail3.example.net 59.7906 333 imapproxy webmail4.example.net 58.167 384 imapproxy The responstimes are not very fast, but they do seem to support the claim that an imapproxy isn't needed for dovecot. -jf

5 31

[Dovecot] FreeBSD maintainer ?
by Frank Bonnet 27 Feb '12

27 Feb '12

Hello Does the FreeBSD Dovecot's port maintainer read this mailing-list ? Thanks

4 4

[Dovecot] v2.0.13 problems after kernel patch for CVE-2011-1083 applied on Centos 5
by Doug Henderson 27 Feb '12

27 Feb '12

Greetings, This email is both a request for assistance/help and a heads-up. [8irgehuq] CVE-2011-1083: Algorithmic denial of service in epoll. After ksplice automatically installed the above patch on our mail servers, most/all IMAP/POP3 connections began experiencing time-outs trying to connect, or extreme timeouts in the auth procedure. dovecot: imap-login: Disconnected (no auth attempts): rip=a.a.a.a, lip=b.b.b.b, TLS handshaking: Disconnected dovecot: pop3-login: Disconnected (no auth attempts): rip=a.a.a.a, lip=b.b.b.b, TLS handshaking: Disconnected dovecot: pop3-login: Panic: epoll_ctl(add, 6) failed: Invalid argument dovecot: pop3-login: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0 [0x3cb543baa0] -> /usr/lib64/dovecot/libdovecot.so.0 [0x3cb543baf6] -> /usr/lib64/dovecot/libdovecot.so.0 [0x3cb543afb3] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handle_add+0x118) [0x3cb5447708] -> /usr/lib64/dovecot/libdovecot.so.0(io_add+0xa5) [0x3cb5446e15] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_init_finish+0x1c6) [0x3cb54355a6] -> /usr/lib64/dovecot/libdovecot-login.so.0(main+0x136) [0x37a000bdf6] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x3cb301d994] -> dovecot/pop3-login(main+0x49) [0x401b99] dovecot: master: Error: service(pop3-login): child 27603 killed with signal 6 (core not dumped - add -D parameter to service pop3-login { executable } dovecot: master: Error: service(pop3-login): command startup failed, throttling dovecot: imap-login: Panic: epoll_ctl(add, 6) failed: Invalid argument dovecot: imap-login: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0 [0x3cb543baa0] -> /usr/lib64/dovecot/libdovecot.so.0 [0x3cb543baf6] -> /usr/lib64/dovecot/libdovecot.so.0 [0x3cb543afb3] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handle_add+0x118) [0x3cb5447708] -> /usr/lib64/dovecot/libdovecot.so.0(io_add+0xa5) [0x3cb5446e15] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_init_finish+0x1c6) [0x3cb54355a6] -> /usr/lib64/dovecot/libdovecot-login.so.0(main+0x136) [0x37a000bdf6] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x3cb301d994] -> dovecot/imap-login(main+0x39) [0x402069] dovecot: master: Error: service(imap-login): child 27604 killed with signal 6 (core not dumped - add -D parameter to service imap-login { executable } Once this patch was removed, everything started working again. Is it possible that dovecot is trying to re-add already-added connections to the polling list - which this specific 'patch' prevents? We haven't dug deeper yet, but the error is being thrown from the method io_loop_handle_add in ioloop-epoll.c http://hg.dovecot.org/dovecot-2.0/file/aa8dfa085a99/src/lib/ioloop-epoll.c Thanks Doug

3 7

[Dovecot] upgrade to dovecot 2.1.1 any question
by ml 27 Feb '12

27 Feb '12

hi guys hi master of "Fu" hi Timo I am having problems to migrate to dovecot dovecot 2.0.18 to 2.1.1 I encounter fatal errors. I created it myself rpms available here http://ns.fakessh.eu/rpms/dovecot-2.1.1-1.centme.el5.src.rpm I can not run dovecot with this config file like this http://ns.fakessh.eu/rpms/dovecot-2.1.1-1.centme.el5.src.rpm i run this config ks37777 ~]# dovecot -n # 2.0.18: /etc/dovecot/dovecot.conf # OS: Linux 2.6.31.5-xxxx-rt14-ipv6-32 i686 CentOS release 5.7 (Final) auth_mechanisms = plain login base_dir = /var/run/dovecot/ lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes listen = [::] log_path = /var/log/maillog log_timestamp = %Y-%m-%d %H:%M:%S login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c mail_debug = yes mail_location = maildir:~/Maildir mail_max_userip_connections = 30 mail_plugins = " quota trash zlib" managesieve_notify_capability = mailto managesieve_sieve_capability = comparator-i;octet comparator-i;ascii-casemap fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date spamtest spamtestplus virustest namespace { inbox = yes location = prefix = separator = . } passdb { driver = pam } plugin { antispam_mail_notspam = --ham antispam_mail_sendmail = /usr/bin/sa-learn antispam_mail_sendmail_args = --username=%u antispam_mail_spam = --spam antispam_mail_tmpdir = /tmp antispam_signature = X-Spam-Flag antispam_signature_missing = move antispam_spam = SPAM;Spam;spam;Junk;junk antispam_trash = trash;Trash;Deleted Items;Deleted Messages autocreate = Trash autocreate2 = Junk autocreate3 = Sent autocreate4 = Drafts autosubscribe = Trash autosubscribe2 = Junk autosubscribe3 = Sent autosubscribe4 = Drafts deleted_to_trash_folder = Trash plugin = $mail_plugins autocreate managesieve sieve quota quota = maildir:User quota quota_exceeded_message = Quota exceeded, please go to http://www.fakessh.eu/over_quota_help.html for instructions on how to fix this. quota_rule = *:storage=10GB quota_rule2 = Trash:storage=+10% quota_rule3 = Spam:storage=+20% quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = ~/.dovecot.sieve sieve_before = /var/sieve-scripts/roundcube.sieve sieve_dir = ~/sieve sieve_global_path = whatever trash = /etc/dovecot/dovecot-trash.conf.ext zlib_save = bz2 zlib_save_level = 9 } protocols = sieve imap pop3 service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0600 user = postfix } unix_listener auth-master { mode = 0666 } unix_listener auth-userdb { mode = 0666 } vsz_limit = 64 M } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { address = * , [::] port = 993 } process_limit = 1 vsz_limit = 64 M } service imap { client_limit = 1024 service_count = 0 } service managesieve-login { inet_listener managesieve-login { address = * , [::] port = 2000 } process_limit = 1 vsz_limit = 64 M } service pop3-login { inet_listener pop3 { port = 0 } inet_listener pop3s { address = * , [::] port = 995 } process_limit = 1 vsz_limit = 64 M } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { user = mail } user = dovecot } ssl_ca = </etc/pki/tls/certs/class3.crt ssl_cert = </etc/pki/tls/certs/ks37777.kimsufi.com.cert ssl_key = </etc/pki/tls/private/ks37777.kimsufi.com.key ssl_verify_client_cert = yes userdb { driver = passwd } userdb { driver = passwd } version_ignore = yes protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep imap_max_line_length = 64 k mail_plugins = " quota trash zlib autocreate quota imap_quota zlib antispam imap_zlib" } protocol pop3 { mail_plugins = autocreate quota quota autocreate zlib deleted_to_trash pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s } protocol lda { hostname = r13151.ovh.net info_log_path = log_path = mail_plugins = autocreate sieve quota postmaster_address = postmaster(a)fakessh.eu sendmail_path = /usr/lib/sendmail } protocol sieve { managesieve_implementation_string = dovecot managesieve_logout_format = bytes ( in=%i : out=%o ) managesieve_max_line_length = 65536 } -- 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 7

[Dovecot] deliver(test@[***domain_name***]): Fatal: setgid(5000) failed with ... Operation not permitted
by fxCode 26 Feb '12

26 Feb '12

Hi, I am relatively new to linux, and have set up my first lamp server around a month ago. The server is housed in a data centre a few miles from my house, and is working as a web server (with apache, tomcat, mysql) just fine. I have now been trying for a week to get Postfix and Dovecot working with postfixadmin and mysql. (below I have replaced my test domain name with [***domain_name***]) The story so far; I can send 'welcome' emails from within postfix admin to an external email address... and they are received by the mail client on my computer at home no problem. I can set up alias email addresses within postfix admin, such as webmaster@[***domain_name***], and emails sent to this address are redirected to the proper address as expected. But - if I set up a standard mailbox within postfix admin - test@[***domain_name***] , and email it from my home system, nothing appear in postfixadmin (after a fetch request) or the mysql database. Here is the fail point in my mail.log file ; Feb 26 12:50:27 quantum dovecot: deliver(test@[***domain_name***]): Fatal: setgid(5000) failed with euid=8(mail), gid=8(mail), egid=8(mail): Operation not permitted I don't know what the setguid(5000) is, or where it is being set, or what it should be! I have been changing permissions with the 'socket listen' section of my /etc/dovecot/dovecot.conf file, and when I restart dovecot it creates the auth-master file with the permissions as expected; socket listen { master { path = /var/run/dovecot/auth-master mode = 0777 user = vmail group = mail } client { path = /var/spool/postfix/private/auth mode = 432 #user = postfix #group = postfix } } my mail folders should be located at /var/vmail, but the folder is empty. I have chmod the permissions to be as follows; me@myserver: ls -ld /var/vmail drwxrwxrwx 2 vmail mail 4096 2012-02-11 08:40 /var/vmail Can anyone spot where this is going wrong? Thanks in advance for any help, it is very very much appreciated!!! My hosts file is as follows; 127.0.0.1 localhost [**server_ip***] quantum.[***domain_name***] quantum # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ...and 'dovecot -n' replies as follows; me@myserver: dovecot -n # 1.2.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-38-server x86_64 Ubuntu 10.04.4 LTS ext4 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s 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_location: maildir:/var/vmail/%d/%n 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 lda: log_path: /var/log/dovecot-deliver.log auth_socket_path: /var/run/dovecot/auth-master postmaster_address: fxcode(a)me.com mail_plugins: sieve auth default: mechanisms: plain login 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 userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 master: path: /var/run/dovecot/auth-master mode: 511 user: vmail group: mail

1 1

[Dovecot] IMAP NOTIFY extension
by Timo Sirainen 26 Feb '12

26 Feb '12

http://hg.dovecot.org/dovecot-2.2-notify/ contains the initial implementation of IMAP NOTIFY extension. It's less than half-working, but the difficult part of it is done I think. If I give it a command like: x notify set (personal (messagenew messageexpunge flagchange)) and then in another session I copy a message to another mailbox, it sends: * STATUS "foobar" (MESSAGES 77 UIDNEXT 78 UIDVALIDITY 1329431281 UNSEEN 75) This requires mailbox_list_index=yes to work. It works by following the dovecot.list.index.log changes, so it's going to be pretty efficient. Some TODO that I've so far noticed: - NOTIFY is handled currently only for non-selected mailboxes. (handling the new features for selected mailbox should be simple) - initial STATUS sending isn't done with STATUS option - only MessageNew, MessageExpunge and FlagChange notifications are sent currently - MailboxName handling probably needs to be able to get "old" and "new" views, figure out what changed in them and send those changes (dsync has similar code) - mailbox list indexes seem to be adding too much stuff, which results in: - STATUS duplicates, but there should already be code to avoid these so I'm not sure what's going on - ACLs and shared mailboxes don't work right - add 0.5s delay before notifying IMAP code, so multiple changes can be bundled into one

1 0

[Dovecot] Solr not indexing
by Daniel L. Miller 26 Feb '12

26 Feb '12

What did I do wrong to make this happen? "doveadm(dmiller(a)amfes.com): Debug: fts: Indexes disabled for namespace 'shared/%n/'" doveadm -D fts rescan -u dmiller(a)amfes.com doveadm(root): Debug: Loading modules from directory: /usr/local/lib/dovecot doveadm(root): Debug: Module loaded: /usr/local/lib/dovecot/lib01_acl_plugin.so doveadm(root): Debug: Module loaded: /usr/local/lib/dovecot/lib20_fts_plugin.so doveadm(root): Debug: Module loaded: /usr/local/lib/dovecot/lib21_fts_solr_plugin.so doveadm(root): Debug: Loading modules from directory: /usr/local/lib/dovecot/doveadm doveadm(root): Debug: Module loaded: /usr/local/lib/dovecot/doveadm/lib10_doveadm_acl_plugin.so doveadm(root): Debug: Skipping module doveadm_expire_plugin, because dlopen() failed: /usr/local/lib/dovecot/doveadm/lib10_doveadm_expire_plugin.so: undefined symbol: expire_set_lookup (this is usually intentional, so just ignore this message) doveadm(root): Debug: Skipping module doveadm_quota_plugin, because dlopen() failed: /usr/local/lib/dovecot/doveadm/lib10_doveadm_quota_plugin.so: undefined symbol: quota_user_module (this is usually intentional, so just ignore this message) doveadm(root): Debug: Skipping module doveadm_zlib_plugin, because dlopen() failed: /usr/local/lib/dovecot/doveadm/lib10_doveadm_zlib_plugin.so: undefined symbol: i_stream_create_deflate (this is usually intentional, so just ignore this message) doveadm(root): Debug: Module loaded: /usr/local/lib/dovecot/doveadm/lib20_doveadm_fts_plugin.so doveadm(dmiller(a)amfes.com): Debug: Added userdb setting: mail=mdbox:/var/mail/amfes.com/dmiller/mdbox doveadm(dmiller(a)amfes.com): Debug: Added userdb setting: plugin/acl_groups='allshared' doveadm(dmiller(a)amfes.com): Debug: Effective uid=5000, gid=8, home=/var/mail/amfes.com/dmiller doveadm(dmiller(a)amfes.com): Debug: Namespace : type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=mdbox:/var/mail/amfes.com/dmiller/mdbox doveadm(dmiller(a)amfes.com): Debug: fs: root=/var/mail/amfes.com/dmiller/mdbox, index=, control=, inbox=, alt= doveadm(dmiller(a)amfes.com): Debug: Namespace : Using permissions from /var/mail/amfes.com/dmiller/mdbox: mode=0700 gid=-1 doveadm(dmiller(a)amfes.com): Debug: acl: initializing backend with data: vfile:/usr/local/etc/dovecot/global-acls:cache_secs=300 doveadm(dmiller(a)amfes.com): Debug: acl: acl username = dmiller(a)amfes.com doveadm(dmiller(a)amfes.com): Debug: acl: owner = 1 doveadm(dmiller(a)amfes.com): Debug: acl vfile: Global ACL directory: /usr/local/etc/dovecot/global-acls doveadm(dmiller(a)amfes.com): Debug: Namespace : type=shared, prefix=shared/%n/, sep=/, inbox=no, hidden=no, list=children, subscriptions=no location=mdbox:/var/mail/%d/%n/mdbox doveadm(dmiller(a)amfes.com): Debug: shared: root=/usr/local/var/run/dovecot, index=, control=, inbox=, alt= doveadm(dmiller(a)amfes.com): Debug: fts: Indexes disabled for namespace 'shared/%n/' doveadm(dmiller(a)amfes.com): Debug: acl: initializing backend with data: vfile:/usr/local/etc/dovecot/global-acls:cache_secs=300 doveadm(dmiller(a)amfes.com): Debug: acl: acl username = dmiller(a)amfes.com doveadm(dmiller(a)amfes.com): Debug: acl: owner = 0 doveadm(dmiller(a)amfes.com): Debug: acl vfile: Global ACL directory: /usr/local/etc/dovecot/global-acls -- Daniel

2 3

[Dovecot] Maildir migration: Courier-imap 4.4.3 to Dovecot 1.2.
by Rafał Radecki 25 Feb '12

25 Feb '12

Hi all. I am currently gathering information about migration of Maildir/ structures from Courier to Dovecot. What do you think about http://wiki.dovecot.org/Migration/Courier ? For each courier Maildir account I want to use http://www.dovecot.org/tools/courier-dovecot-migrate.pl to produce dovecot-uidlist file mv courierimapsubscribed subscriptions sed sed -i 's/INBOX\.//' subscriptions rm -r courierimaphieracl rm courierimapacl rm courierimapkeywords I want also to leave default pop3_uidl_format (%08Xu%08Xv) in dovecot.conf Should I look into something else? Have I missed something? Best regards, Rafal.

3 2

[Dovecot] Apple od/ad authentication problem
by Troy Shafer 25 Feb '12

25 Feb '12

Hello all. Im pretty new to dovecot and postfix world. I'm completely stumped. OS X 10.7.3, behind a Cisco asa NAT. When trying to authenticate (ssl or not) via the webmail interface I get this error... NAT IP is the public ip I assigned. It doesn't work for an AD account or an account local to the Mac server. However it DOES work on the internal LAN. Feb 22 18:15:36 mail dovecot[3501]: auth: Error: od (username,natIP): verify plain: lookup failed for user: username Feb 22 18:15:51 mail dovecot[3501]: auth: Error: od[getpwnam_ext](username,natIP): No record for user I figured I'm missing something in the dovecot config. I have followed apple's kb articles for AD webmail authentication and kerberos, and that works internally.

2 3

[Dovecot] How to limit max number of connections for ip address
by Wilberth Perez 25 Feb '12

25 Feb '12

Hi List: Does any one , knows if is possible configure dovecot for limit max number of connections for IP address? I would like to prevent future fork-bombing attacks for pop3 and imap login process in my email server. Our dovecot version is : 1.2.10 Thanks, Wilberth.

3 4

[Dovecot] How to achieve proper privilege separation?
by "Tóth Attila" 24 Feb '12

24 Feb '12

I'm using a simple mbox config with regular Unix users and pam authentication. I'm also using grsecurity. That's why I see what dovecot does in which users' name. As times goes by and new versions are coming I can frustratedly see, that more and more tasks are performed as root. Why? When I used 1.x series of Dovecot, imap process started in the name of the user whose mbox was accessed. Now I can see, that nearly every task is performed by root. Why? It even tampers with the mail directories of each user as root instead of the user as it was usual long before. Please let me know how should I change the config to make dovecot stop using root privileges and revert it back to the old behavior. Thanks for your help: Dw. Here's my current config: dovecot -n # 2.0.17 (684381041dc4+): /etc/dovecot/dovecot.conf # OS: Linux 3.2.6-hardened i686 Gentoo Base System release 2.0.3 auth_socket_path = /var/run/dovecot/auth-userdb auth_verbose = yes auth_worker_max_count = 16 base_dir = /var/run/dovecot/ disable_plaintext_auth = no first_valid_gid = 99 first_valid_uid = 1000 hostname = host.name last_valid_gid = 65533 last_valid_uid = 1003 listen = * mail_access_groups = mail mail_full_filesystem_access = yes mail_gid = mail mail_location = mbox:~/mail/:INBOX=/var/spool/mail/%u mail_max_keyword_length = 150 mail_privileged_group = mail mail_uid = mail passdb { args = * driver = pam } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } postmaster_address = postmaster(a)host.name protocols = imap service auth-worker { user = root } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } service_count = 1 vsz_limit = 16 M } service imap { process_limit = 4 vsz_limit = 64 M } ssl_cert = </etc/apache2/ssl/cert-file.pem ssl_key = </etc/apache2/ssl/key-file.pem userdb { driver = passwd } verbose_proctitle = yes protocol lda { mail_plugins = sieve } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags imap_max_line_length = 64 k -- dr Tóth Attila, Radiológus, 06-20-825-8057 Attila Toth MD, Radiologist, +36-20-825-8057

2 7

[Dovecot] From Maildir back to smtp
by Marc Perkel 24 Feb '12

24 Feb '12

Not sure how this can be done. Right now I'm running a free backup MX record service. People point their high MX records to my servers and if they go down we store the email. When they come back up it's delivered. What I want to do is have a premium service that would allow them to view through IMAP the stored email. In order to do that I would have to deliver the email locally to a dovecot server - to a single account perhaps - and they can view/forward/delete etc. But - when their server comes back online I'd like to gather up all the delivered email stored in Maildir format and run it back into smtp for delivery. Has anyone even done something like this? Or is there an easier way that I'm missing? Thanks in advance

4 4

[Dovecot] dsync 2.0.x versus 2.1.x field report
by Michael Grimm 24 Feb '12

24 Feb '12

Hi -- I used to run two mailservers with identical MX priorities (poor man's fail-over approach) with Maildir mail folders accessed by Dovecot. Synchronization has been achieved using unison, mirroring all files except dovecot index files. Once in a while some oddities could be observed, like reappearing of deleted mails, duplicates and such alike. But the all-over performance was quite good. Then I wanted to migrate to mdbox, and I became interested in dsync. I did start with 2.0.16 a couple of month ago, and recently upgraded to 2.0.18. My experience with the 2.0.x dsync version is as follows (synchronization time: every minute): -- As long as mail is not stored in corresponding mailboxes at both servers at the same time, all mailboxes become synchronized perfectly well, and no oddites like reappearing of deleted mails or generation of duplicates can be observed. -- If mail is stored into corresponding mailboxes at both servers simultaneously in between two synching runs, it gets worrying. -- If I do run dsync without '-f' those two mailboxes end up in becoming asynchronous. -- If I do run dsync with '-f' both mailboxes will become synchronized let's say in 95% of all synchronization runs. BUT in 5%, I do experience asynchronicity. Here a 'doveadm force-resync' sometimes works, but not always, what worries me a lot. -- I can see the missing mail in the mdbox storage file using UNIX' little helpers but not with the help of dovecot tools. (Or I was unable to use them properly.) -- Modifying MX priorities in a way, that I do now have a primary and backup mailserver scenario, very much reduced the risk of losing legitimate mail. -- But sometimes I do lose some syslog mail being produced at the same time. Therefore I modified runtimes in way to omit synchronicity. Ok, I could have lived with that, but I was anxious to learn, if 2.1.x dsync would perform better ;-) Here my observations sofar (synchronization time: every minute): -- No losses sofar using 'doveadm sync' with '-f' -- A *lot* of reappearing deleted mails or mails moved from one mailbox to the other. -- Quite often I am unable to delete those mails using client functionality (Mail.app, Roundcube). -- In those cases one needs to stop synchronization, run 'doveadm force-resync', delete all reappearing mail (quite a lot sometimes), empty 'Deleted' folders, and finally run 'doveadm purge'. -- Running of 'doveadm sync' without '-f' doesn't improve the situation. Still I do have to struggle with reappearing mails, and sometimes with appearing duplicates. -- I do have a test setup running for 24 hours now, where I do generate test mails in a 6 minutes interval at both servers. Mails become synchronized perfectly well, irrespectively if '-f' is set or not. This is a major improvement to 2.0x. dsync (sofar). -- But running the synchronization without '-f' still shows a *lot* of reappering mail, though. I do have the feeling that dsync became very much improved with regard to missing mail in synchronization, good. But those reappearing mails make me think about switching back to 2.0.x dsync and live with the drawback of preventing mail to arrive synchronously at both servers. Is someone out there experiencing a similar behaviour with dsync 2.1.x regarding reappearing, thus indelible mail? Regards, Michael

1 0

[Dovecot] Creating and interacting with array inside plugin
by Alex Baule 24 Feb '12

24 Feb '12

Hi Timo.... I Follow your instruction to look inside quota plugin to get the notification from dovecot that expunged a message, that's Ok. Follow the quota, it's use a array to keep all uids from a email expunged, to compare with uid that is got in notify_sync, that's OK too, but to me i need to keep uid and a char* with my body name, to erase it too. I made this: struct emexis_ids_x_uis{ uint32_t ids; char *uis_file; }; struct emexis_mailbox { union mailbox_module_context module_ctx; ARRAY_DEFINE(expunge_uids, struct emexis_ids_x_uis); }; ok, inside my expunged rewrite function i create the array like quota does, and append it to my array. struct emexis_ids_x_uis append_uis; append_uis.ids = _mail->uid; append_uis.uis_file = bodyFile; array_append(&ebox->expunge_uids, &append_uis, 1); But when i do a foreach in this Array, my ids is OK, but my uis_file has tha same value every time (the value is the lasted value inserted). Append to UID array (156) --> (/storage/gss/emexis/common/t/33/88/t33889eb1bccd28fd6643ebc3ecf548b12a1ad095) Append to UID array (157) --> (/storage/gss/emexis/common/t/e3/35/te335c20e978e12d37ad0a35ae009245cd34080c0) Append to UID array (158) --> (/storage/gss/emexis/common/t/0b/83/t0b83efc253c34db35843fc89b655586d628cccaf) Calling Sync Expunged --> (156) Sync Expunged (156 == 156) --> (/storage/gss/emexis/common/t/0b/83/t0b83efc253c34db35843fc89b655586d628cccaf) Sync Expunged Match (156 == 156) --> (/storage/gss/emexis/common/t/0b/83/t0b83efc253c34db35843fc89b655586d628cccaf) Sync Expunged (157 == 156) --> (/storage/gss/emexis/common/t/0b/83/t0b83efc253c34db35843fc89b655586d628cccaf) Sync Expunged (158 == 156) --> (/storage/gss/emexis/common/t/0b/83/t0b83efc253c34db35843fc89b655586d628cccaf) Finish Calling Sync Expunged --> (156) Can i use a struct as a array Item ?? something is wrong with my array creation, append and etc ? Tks Timo !!

2 2

Re: [Dovecot] Why is dovecot involved in my smtp process
by Joseph Tam 24 Feb '12

24 Feb '12

From: "Peter A. Giessel" <pgiessel(a)mac.com>: > Not totally true. Typical cyrus sasl2 implementation used with > sendmail uses an imap server for smtp authentication. I recall having > to tweak the sasl2 configuration on my own sendmail server to talk > correctly with dovecot. I don't recall the exact tweaks. Just to make it clear to the OP, I have a Dovecot/Sendmail/SASL working just fine (which is independent of dovecot). I suspect Peter hit the nail on the head here. Look at the contents of $SASL_INSTALL/lib/Sendmail.conf Mine is (only) pwcheck_method:saslauthd which I think looks up my name service backend via the login and plain plugins. I'm a little hazy on how this was set up, but if you are able to successfully login without dovecot, then it appears you have some sort of authentication stack that will try IMAP first, then fallback to your the other method. Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] Settings for authentication without an extra password file
by Keith Christian 24 Feb '12

24 Feb '12

Hello, I'm new to dovecot, and, due to having an older version of an OS installed on a test server, I'll be using an older version of dovecot (dovecot-1.0-1.2) to provide IMAP services. On this wiki page (http://wiki.dovecot.org/BasicConfiguration?highlight=%28passwd.dovecot%29) There are instructions for creating a separate dovecot password file: echo "$USER:{PLAIN}password" > passwd.dovecot sudo mv passwd.dovecot /etc So, it appears that two password files will be needed, one for dovecot and one for regular system logins. Is the statement above correct, or am I misreading something? Is there a setting in dovecot.conf which will authenticate IMAP using /etc/password and /etc/shadow, without a separate dovecot password file? ========Keith

2 1

[Dovecot] Why is dovecot involved in my smtp process
by Steve Campbell 23 Feb '12

23 Feb '12

I've been trying to get smtp auth set up for days. All my sendmail and sasl2 stuff seems to be proper, but the user can't use the system on port 587, which is where I require authorization. Now I see where messages are in my maillog of the type: auth: pam_unix(dovecot:auth) : authentication failure ........ Why is dovecot involved in my smtp processes and how do I fix this. I've got some very mad users. The 10-auth.conf file is pretty much stock except for allowing plain text logins. steve campbell

7 12

[Dovecot] Can't connect to my mail server (postfix + dovecot, IMAP) with Thunderbird
by GASPARD Kévin 23 Feb '12

23 Feb '12

I'm sorry, some one tell me my netstat (on IRC) is useless. Also my pastes will be destroyed in something like one day, that's stupid (that's originally for IRC), so this is the output of my : dovecot -n : http://pastebin.com/Tewcb7bm telnet : http://pastebin.com/6gY2puxF netstat -Nnap | grep "dovecot" : http://pastebin.com/yx2wxfWf Sorry for the error.

2 1

[Dovecot] Can't connect to my mail server (postfix + dovecot, IMAP) with Thunderbird
by GASPARD Kévin 23 Feb '12

23 Feb '12

Hi, I've a problem with Dovecot and Thunderbird. Actually I'm trying to setup a virtual host server mail with postfix + dovecot (2.0.9) on CentOS 6.2. This is my dovecot -n : http://pastebin.com/wZWAE5Cj (I guess the errors are not important, that's just saying there is some obsoletes values, I will fix that later until it's not inconvenient to setup correctly dovecot). I've a file to store password (/etc/dovecot/passwd) and when I'm trying to connect with telnet to my host on port 143 it works, after I can log myself with the command «a login user(a)domain.tld passwd» and it works, this is the entire output of the telnet connection : http://pastebin.com/h10cQVqf but actually when I'm trying to connect with thunderbird I've an error about the password and the login, this is a screenshoot : http://images.koshie.fr/TB_problem.png and to finish, there is nothing into the log... The password and the user are corrects ! Of course, dovecot and postfix are started, this is the netstat -a | grep "dovecot" : http://pastebin.com/bwfsS4Tf If you need more informations tell me. PS : Excuse me for my bad english, also I'm new with dovecot. Cordially, GASPARD Kévin

1 0

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

23 Feb '12

http://dovecot.org/releases/2.1/dovecot-2.1.1.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.1.tar.gz.sig v2.1.0 had a couple of bugs, but overall people have been pretty quiet about it. I'm hoping v2.1.2 won't need to be released for many more weeks. :) BTW. v2.2 branch has also been opened in hg. Not much stuff in there yet though. + dsync: If message with same GUID is saved multiple times in session, copy it instead of re-saving. - acl plugin + autocreated mailboxes crashed when listing mailboxes - doveadm force-resync: Don't skip autocreated mailboxes (especially INBOX). - If process runs out of fds, stop listening for new connections only temporarily, not permanently (avoids hangs with process_limit=1 services) - auth: passdb imap crashed for non-login authentication (e.g. smtp).

1 0

Re: [Dovecot] Problem with Postfix + Dovecot + MySQL + Squirrelmail
by Gustavo 22 Feb '12

22 Feb '12

Ok, I study the wikki and the dovecot works. But when I try to send a mail using squirrel, I get this error on logs: Feb 11 18:41:55 jubileu postfix/smtpd[19522]: connect from localhost.localdomain[127.0.0.1] Feb 11 18:41:55 jubileu postfix/smtpd[19522]: warning: xsasl_cyrus_server_get_mechanism_list: no applicable SASL mechanisms Feb 11 18:41:55 jubileu postfix/smtpd[19522]: fatal: no SASL authentication mechanisms Feb 11 18:41:56 jubileu postfix/master[18383]: warning: process /usr/lib/postfix/smtpd pid 19522 exit status 1 Feb 11 18:41:56 jubileu postfix/master[18383]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling How can I fix this? My conf files seems to be ok: ## Diretorio Base ## base_dir = /var/run/dovecot/ ## Protocolos que ele ira executar ## protocols = imap imaps pop3 pop3s log_timestamp = '%Y-%m-%d %H:%M:%S ' syslog_facility = mail ## Dados do SSL ## ssl_listen = localhost ssl_cert_file = /etc/postfix/mail-cert.pem ssl_key_file = /etc/postfix/mail-key.pem ssl_parameters_regenerate = 168 verbose_ssl = no mail_location = maildir:/var/vmail/%d/%u mail_access_groups = mail mail_debug = no first_valid_uid = 150 last_valid_uid = 150 maildir_copy_with_hardlinks = yes protocol imap { } protocol pop3 { # Login executable location. login_executable = /usr/lib/dovecot/pop3-login mail_executable = /usr/lib/dovecot/pop3 pop3_uidl_format = %08Xu%08Xv } protocol lda { sendmail_path = /usr/lib/sendmail auth_socket_path = /tmp/auth-master } auth_verbose = no auth_debug = no auth default { mechanisms = plain login passdb pam { } passdb sql { args = /etc/dovecot/dovecot-sql.conf } userdb passwd { } userdb sql { args = /etc/dovecot/dovecot-sql.conf } socket listen { master { path = /tmp/auth-master mode = 0600 user = vmail group = mail } client { path = /tmp/auth-client mode = 0660 user = vmail group = mail } } } dict { } plugin { } ######################################### And Postfix conf: # SASL Authentication smtpd_sasl_auth_enable = yes smtpd_sasl2_auth_enable = yes smtpd_sasl_exceptions_networks = $mynetworks smtpd_sasl_security_options = noanonymous broken_sasl_auth_clients = yes smtpd_sasl_path = private/auth smtpd_sasl_application_name = smtpd smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination permit_mynetworks = 127.0.0.0/8, 184.22.103.88/32, 184.22.103.87/32 Thanks!!! > -----Mensagem Original----- From: Timo Sirainen > Sent: Saturday, January 28, 2012 3:51 PM > To: Gustavo > Cc: dovecot(a)dovecot.org > Subject: Re: [Dovecot] Problem with Postfix + Dovecot + MySQL + > Squirrelmail > > On 27.1.2012, at 14.32, Gustavo wrote: > > #service dovecot start >> Starting IMAP/POP3 mail server: dovecotLast died with error (see error >> log for more information): Auth process died too early - shutting down >> > > No need to keep guessing the problem. "See error log for more information" > like it says. http://wiki.dovecot.org/**Logging<http://wiki.dovecot.org/Logging> > > -- Gustavo - clube03(a)gmail.com

2 2

[Dovecot] Where did the message end up?
by Dag Nygren 22 Feb '12

22 Feb '12

Hi all! Just migrated out UW-IMAP installation to Dovecot and so far so good. Had small teething problems though which left me with one question. The scenario was that I have a set of public folders that are only needed by the main company group (gid = company). Then there are some external users as well, not directly in the company group. I set up the public mailbox with permissions 660, owner me and group "company". That is the externals didn't have access to the mail folder. At this point all looked fine, but later there was an email to an external person and this was passed on to deliver by procmail. Procmail logs says all was OK, but there is an entry about the public folder not accessible in the Dovecot log. The email is nowhere to be found. My question: Where is the delivered email? Best Dag

2 5

Re: [Dovecot] Questions still about a uw-imap -> dovecot conversion
by Joseph Tam 22 Feb '12

22 Feb '12

Steve Campbell <campbell(a)cnpapers.com> writes: > > This was piped into a script that Email'd users about the changes > > that was going to happen, what they would expect to see, and a > > FAQ on how to set up a mail client correctly. > > Here, I'm not sure what should be done. The users with the secondary > folders that are not in ~/mail can't seem to get the client configured. "Great artists steal". Google around for a good set of instructions on how to set up IMAP prefix's for various mail clients, and refer your users to that. I also referred them to our webmail (with the correct mail prefix) as a reference to a list of mailboxes they ought to see. If they don't match, then that's a symptom of a bad prefix. > I've tried this and modified the .mailboxlist, but I'm thinking Dovecot > is ignoring this and I'm not sure what it's looking at to determine the > imap folders. > > > - .subscription files were moved into the mail folder > > (don't have to edit prefixes since the aliasing > > will take care of that). > > And when would these .subscription files be created? The first time the > folders would be accessed, or when? This seems to be part of my fix that > I'm getting lost on. Sorry, as Timo intimated, dovecot uses .subscription, which can be adjusted back to .mailboxlist, which uw-imapd uses. You shouldn't have to edit it if you set up namespace aliasing. Just move it from the top-level into your user's mail directory during cutover: (if you use dovecot's default subscription filename) mv $USER/.mailboxlist $USER/mail/.subscription If your IMAP client is still ignoring subscriptions, it usually means the client was configured that way. > > - your setup is fairly close to mine, so you may also run into > > the problem of user having mailboxes with group ownership that > > users are not part of (for example, group "mail" for INBOX set > > by your LDA or personal mailboxes with groups the user is no > > longer a member of) *and* with group permission not mode=0. > > Sendmail sort of requires the "mail" group, does it not? I'll take a > look and see if all users are part of this or not. A crazy solution > would be in order here? I think sendmail works fine if you set your mail spool mode=1777 (like /tmp), but have each inbox mode=0600. This setting will persist. It's sendmail LDA mail.local that's the problem: it autocreates new inboxes with permissions user:mail/660 and unless the user is in group "mail", chaos will ensue. You can maybe do a cron script or some other hack, or better yet, use dovecot LDA, which sets up the perms correctly (and keeps indexes updated). A one time "chmod go-rwx" during cutover is all that is required then. The log entry that points this problem out looks like dovecot: imap(smith): Error: chown(/dc-cache/smith/.imap/xx, group=6(mail)) failed: Operation not permitted (egid=5678(goodgroup), group based on /home/smith/mail/xx - see http://wiki2.dovecot.org/Errors/ChgrpNoPerm) dovecot: imap(smith): Error: mkdir(/dc-cache/smith/.imap/xx) failed: Not owner Joseph Tam <jtam.home(a)gmail.com>

2 1

[Dovecot] dsync, hard-links and refcounts
by Christoph Bußenius 21 Feb '12

21 Feb '12

Hi, when creating a copy of a mail, dovecot provides a feature that will store its contents only once. In maildir, this is done by means of hard links, while mdbox has some special refcounting mechanism. My question is, how can we convert mails from maildir to mdbox without duplicating these copies? It seems that dsync does not detect the hard links. Even if the hard-linked mails have the same GUID listed in dovecot-uidlist, dsync creates multiple instances of the text. - Is there some way to make dsync notice the hard links? (I used dovecot 2.0.17) - Alternatively, is there some tool to deduplicate the mdbox after it has been converted from maildir? - NB: I am not talking about single-instance storage for attachments. Thank you very much, Christoph -- 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 10

[Dovecot] Managesieve AUTHENTICATE with IDN using UTF-8 or encode into ACE?
by Christian Rohmann 21 Feb '12

21 Feb '12

Hey dovecot-users, clients that speak telnet based protocols like http, smtp usually encode IDN (International Domain Names) containing UTF-8 characters into ACE (ASCII Compatible Encoding) punycode. I am wondering what the case was with managesieve (RFC 5804). For example if I was using a username like "user(a)xn--4ca0br.example.com" with the AUTHENTICATE command. Would that need to be encoded into ACE or be left in UTF-8? Reading section "2.1. AUTHENTICATE Command" or "4. Formal Syntax" suggests that quoted or literal UTF-8 is correct. Thanks Christian

2 1

[Dovecot] Some trouble with dovecot 2.1 and SASL
by Alessio Cecchi 21 Feb '12

21 Feb '12

Hi, I'm testing dovecot 2.1.0, on Debian 6.0, with "passdb driver = imap" and SASL for postfix's SMTP-Auth, like explained ih this howto: http://wiki2.dovecot.org/HowTo/PostfixAndDovecotSASL Authentications over IMAP (local dovecot -> remote dovecot) works fine, and it's great. Also smtp-auth on postfix (over SASL) works fine. But in the dovecot log I found this error: Feb 19 11:11:42 demo-vpop dovecot: auth: Fatal: master: service(auth): child 30506 killed with signal 11 (core dumps disabled) even though all works fine. This is my dovecot configuration: # 2.1.0: dovecot.conf-imapc # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.4 auth_mechanisms = plain login default_login_user = nobody imapc_host = 10.0.0.1 mail_gid = imapproxy mail_home = /home/imapproxy/%u mail_location = imapc:~/imapc mail_uid = imapproxy passdb { args = host=10.0.0.1 default_fields = userdb_imapc_user=%u userdb_imapc_password=%w driver = imap } protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } ssl = no userdb { driver = prefetch } But if instead of "unix_listener /var/spool/postfix/private/auth" I use: service auth { unix_listener auth-userdb { } inet_listener { port = 12345 } } no errors appears in the log. In both cases all works fine. Is there any errors in my dovecot's configuration? -- Alessio Cecchi is: on LinkedIn -> http://www.linkedin.com/in/alessice Assistenza Sistemi Linux -> http://www.cecchi.biz/ Hosting Linux -> http://www.hosting-linux.it @ PLUG -> ex-Presidente, adesso senatore a vita, http://www.prato.linux.it

3 4

Re: [Dovecot] Questions still about a uw-imap -> dovecot conversion
by Steve Campbell 21 Feb '12

21 Feb '12

On 2/20/2012 4:58 PM, Jim Lawson wrote: > On 2/20/12 3:36 PM, Steve Campbell wrote: >> >> Thanks for that input. I still think I'm missing something since I >> too used the compatibility link that you pointed to. Only thing is >> that proceeding those namespaces, I used the first example of: >> >> namespace { >> type = private >> separator = / >> prefix = "#mbox/" >> location = mbox:~/mail:INBOX=/var/mail/%u >> inbox = yes >> hidden = yes >> list = no >> } >> namespace { >> type = private >> separator = / >> prefix = >> location = maildir:~/mail >> } >> >> This seemed to get the ball rolling so that users could access >> anything at all. I still have the problem of client imap folders >> being different from webmail imap folders. That's pretty much why I'm >> thinking of using mbox as the INBOX and all other imap folders in the >> ~/mail directory in maildir format. > You ought to be able to get webmail to see the same folders as the > imap clients. > >> >> Should I remove the first two namespaces, in your opinion? Right now, >> the whole thing is kind of fragile. >> > > From your added namespaces, it looks like you are trying to support > mbox and maildir and ~/mail at the same time. Do you already have > maildir folders to support? If not, I would try to get things working > well with mbox first before I started a conversion to maildir. I > would also ask why you're thinking of moving to maildir. Yes, there > are caching benefits, but when you add the Dovecot indexing on top of > mbox, it's pretty much a wash. If you are using file-level backup, > rather than some sort of snapshot technology, maildir will be much, > much slower to back up. Your system will spend all its time walking > directories, opening and closing files. If you don't have many users > to worry about it might be OK, but make sure it's worth it. A lot of > sites went to maildir in the 1998-2004 era and have regretted the > decision as their systems get overloaded with files and they can't > back them up. No, I've got all mbox formats. Previous posts probably suggested that I wanted to move to maildir, but all of the replies I've received have convinced me that I do not want to do that. The folders in ~ and ~/mail are mboxes, so I need to see what damage I've done with a maildir namespace. The maildir reference could be part of the problems I'm seeing. I'm still not sure whether I should be seeing .subscriptions or mail/subscriptions anywhere and whether Dovecot will use the .mailboxlist that exists. The wiki suggests that I need to recompile Dovecot to continue using .mailboxlist. This is something I don't want to do. > >> Horde/Imp updates are probably out of the question until I can get a >> server to install the upgrade on. > For Dovecot and IMP both, you should set up an alternate server to > test out your config changes on before you put them into production. > If you are running on a bare metal single server, set up another > Dovecot instance on a different set of ports (I commonly use 20143 > (imap), 20993 (imaps), 20110 (pop3)) which you can fiddle with > freely. Once you are satisfied with the result in your various > clients, put it into production. You can do the same with Horde/IMP > by putting an installation in a different location on your webserver. > > Jim I've got a second server that is totally independent of the one I'm messing with. I've done the horde/imp alternate port/config. It all went well. The downside is that I didn't realize those secondary folders in ~/mail were being hidden. Kinda late to switch back, but the secondary server supports another domain, so I have it to test with. Again, the damage I've caused to those secondary imap folders needs to be determined to get this fixed properly. Most users are seing the secondary folders and can use them. It's just those users who have folders in ~ that are seeing problems as far as I can tell. Thanks steve > >

2 1

Re: [Dovecot] Questions still about a uw-imap -> dovecot conversion
by Joseph Tam 21 Feb '12

21 Feb '12

Steve Campbell wrote: > The more I read about all of this, the more I'm thinking about moving to > maildir format. My switchover this weekend is full of holes due to the > way user's imap folders were laid out. Some had folders in their home > directory and others might have folders in their /home/mail directory. I had the same problem, and handled it more or less the same way as the later poster (Jim Lawson <jtl+dovecot(a)uvm.edu>) handled his site. I retained use of mbox format as well. I planned the migration like this - scan user home directories for mailboxes (especially "Trash", "Drafts", "Sent", etc.) looking for "From " as the first 5 bytes. This was piped into a script that Email'd users about the changes that was going to happen, what they would expect to see, and a FAQ on how to set up a mail client correctly. - during the cutover, - mailboxes left on the home directory were moved to ~/mail, or renamed (e.g. "Sent" -> "00Sent" to avoid name collision for users that had a mixture of correct and blank prefixes. (I think I deleted "Trash", "Junk", etc. anyways). - Namespace aliasing was used so that prefixes "", "mail", "~/mail", and whatever darn fool settings my users used, would map to the same directory. - .subscription files were moved into the mail folder (don't have to edit prefixes since the aliasing will take care of that). - depending on what POP3 client you used (I used qpopper), you may need to configure pop3_reuse_xuidl = yes to avoid a massive re-downloading from POP3 clients after cutover. - the mail clients I control centrally (e.g. webmail, public server mail clients, etc). shouldn't need updating since they ought to have been set up properly in the first place. - after cutover, a second notification was sent for users that didn't move their mailboxes the first time around, and was it done for them during migration. And of course, test like crazy and watch the logs like a hawk. Other gotcha's: - your setup is fairly close to mine, so you may also run into the problem of user having mailboxes with group ownership that users are not part of (for example, group "mail" for INBOX set by your LDA or personal mailboxes with groups the user is no longer a member of) *and* with group permission not mode=0. You'll have to treat these (set mode=0, or change the group to something the user is part of), or the dovecot index creation will fail and they won't be able to access their mailboxes. I think my migration went pretty smoothly. Less than a handful of wazzup' Email problem reports. Joseph Tam <jtam.home(a)gmail.com>

2 1

[Dovecot] Recalculate quota when quota=dict ?
by Jacek Osiecki 21 Feb '12

21 Feb '12

Hi, My current setting for quota is: plugin { #quota = dirsize:User quota #quota = maildir:User quota quota = dict:User quota::proxy::quota #quota = fs:User quota } I have used mb2md.pl and copied result files manually to a desired mail folder - but quota was not recalculated. And it seems, that no matter what I do - the quota usage remains the same. I tried uncommenting line with: quota = maildir:User quota but it did not help. Any other idea how to recalculate quota? Greetings, -- Jacek Osiecki joshua(a)ceti.pl GG:3828944 I don't want something I need. I want something I want.

4 6

[Dovecot] passwd-file - lower limit for username?
by Oon-Ee Ng 21 Feb '12

21 Feb '12

Hi, previously I could use the following in my passwd-file:- AB:{plain}password I'm not sure when it stopped working, its not an account I access with any regularity, but today it would not work (2.1.0, 64-bit Arch Linux), with an 'unknown user' error in the logs. Is there some new lower limit for username length?

2 3

Re: [Dovecot] dovecot freezes when trying to get mail from maildir with mail
by postmaster 21 Feb '12

21 Feb '12

From: Timo Sirainen <tss(a)iki.fi> > #9 0x0007ba2f in mail_index_update_day_headers () So Dovecot calls localtime() and the process hangs. Something's badly broken in your system related to timezone handling, nothing Dovecot can do about it.. OK - Thanks for your help :-) I'll take it up on the macports mailing lists then ! -- Bjarne D Mathiesen København N ; Danmark ; Europa ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ denne besked er skrevet i et totalt M$-frit miljø MacOS X 10.7.3 Lion ; 2.8GHz Intel Core i7 ; 16GB 1067MHz DDR3

1 0

Re: [Dovecot] [dovecot] dovecot freezes when trying to get mail from maildir with mail
by postmaster 21 Feb '12

21 Feb '12

[ I'm sorry I can't reply in thread, but at present I'm reading email as plain text files directly off the file system - which is a PITA ;-) ] Bjarne D Mathiesen København N ; Danmark ; Europa ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ denne besked er skrevet i et totalt M$-frit miljø MacOS X 10.7.3 Lion ; 2.8GHz Intel Core i7 ; 16GB 1067MHz DDR3 arrrrgh -- used pop3 instead of imap :-( 4604ds1-ynoe:~ root# gdb --args /macports/libexec/dovecot/imap -u postmaster(a)mathiesen.info GNU gdb 6.3.50-20050815 (Apple version gdb-1518) (Sat Feb 12 02:49:13 UTC 2011) Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-apple-darwin"...Reading symbols for shared libraries ..... done (gdb) run Starting program: /macports/libexec/dovecot/imap -u postmaster(a)mathiesen.info Reading symbols for shared libraries ++++. done Debug: auth input: postmaster(a)mathiesen.info uid=5000 gid=5000 home=/Volumes/BrugerData/PostFix/mail/mathiesen.info/postmaster(a)mathiesen.info/ Debug: Effective uid=5000, gid=5000, home=/Volumes/BrugerData/PostFix/mail/mathiesen.info/postmaster(a)mathiesen.info/ Debug: maildir++: root=/Volumes/BrugerData/PostFix/mail/mathiesen.info/postmaster(a)mathiesen.info/, index=, control=, inbox=/Volumes/BrugerData/PostFix/mail/mathiesen.info/postmaster(a)mathiesen.info/, alt= * PREAUTH [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] Logged in as postmaster(a)mathiesen.info a select inbox ^C Program received signal SIGINT, Interrupt. 0x90003afa in mach_msg_trap () (gdb) bt full #0 0x90003afa in mach_msg_trap () No symbol table info available. #1 0x90004267 in mach_msg () No symbol table info available. #2 0x9001b431 in vproc_mig_look_up2 () No symbol table info available. #3 0x9001b26a in bootstrap_look_up2 () No symbol table info available. #4 0x9001b0e4 in bootstrap_look_up () No symbol table info available. #5 0x9001af30 in notify_register_check () No symbol table info available. #6 0x9001ada7 in notify_register_tz () No symbol table info available. #7 0x9001a621 in tzsetwall_basic () No symbol table info available. #8 0x90041903 in localtime () No symbol table info available. #9 0x00092a2f in mail_index_update_day_headers () No symbol table info available. #10 0x0008ec95 in mail_index_transaction_finish () No symbol table info available. #11 0x0008d80a in mail_index_transaction_commit_v () No symbol table info available. #12 0x0008dacf in mail_index_transaction_commit_full () No symbol table info available. #13 0x0008db18 in mail_index_transaction_commit () No symbol table info available. #14 0x00096434 in mail_index_sync_commit () No symbol table info available. #15 0x00066f02 in maildir_sync_index_finish () No symbol table info available. #16 0x00068376 in maildir_sync_context () No symbol table info available. #17 0x000686f2 in maildir_storage_sync_init () No symbol table info available. #18 0x000295fd in mailbox_sync () No symbol table info available. #19 0x00007833 in cmd_select_full () No symbol table info available. #20 0x00007d49 in cmd_select () No symbol table info available. #21 0x00009f63 in client_command_input () No symbol table info available. #22 0x0000a0c2 in client_command_input () No symbol table info available. #23 0x0000a1d3 in client_handle_input () No symbol table info available. #24 0x000095bd in client_input () No symbol table info available. #25 0x001171a7 in io_loop_call_io () No symbol table info available. #26 0x00118492 in io_loop_handler_run () No symbol table info available. #27 0x00117148 in io_loop_run () No symbol table info available. #28 0x0010425a in master_service_run () No symbol table info available. #29 0x00013c5a in main () No symbol table info available. (gdb) quit The program is running. Exit anyway? (y or n) y 4604ds1-ynoe:~ root#

1 0

Re: [Dovecot] [dovecot] dovecot freezes when trying to get mail from maildir with mail
by postmaster 21 Feb '12

21 Feb '12

[ I'm sorry I can't reply in thread, but at present I'm reading email as plain text files directly off the file system - which is a PITA ;-) ] Bjarne D Mathiesen København N ; Danmark ; Europa ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ denne besked er skrevet i et totalt M$-frit miljø MacOS X 10.7.3 Lion ; 2.8GHz Intel Core i7 ; 16GB 1067MHz DDR3 On a note regarding my hardware : the computer has three ethernet-interfaces: but that doesn't really seem to be an issue as telnet from localhost also hangs indefinetely I'm seeing the issue no matter which interface I connect to, whether the two external WAN or the internal LAN IP-number . root# system_profiler SPEthernetDataType 2012-01-22 01:34:36.524 system_profiler[47377:903] Found bsdName (0x2603) for AppleUSBEthernet 2012-01-22 01:34:36.626 system_profiler[47377:903] Found bsdName (0x2c03) for AppleUSBEthernet Ethernet Cards: Apple USB Ethernet Adaptor: Type: USB BSD name: en4 Kext name: AppleUSBEthernet.kext Location: /System/Library/Extensions/IONetworkingFamily.kext/Contents/PlugIns/AppleUSBEthernet.kext Version: 2.1.39 MAC Address: 00:1f:f3:8a:f3:5a Product ID: 5122 Vendor ID: 1452 Apple USB Ethernet Adaptor: Type: USB BSD name: en3 Kext name: AppleUSBEthernet.kext Location: /System/Library/Extensions/IONetworkingFamily.kext/Contents/PlugIns/AppleUSBEthernet.kext Version: 2.1.39 MAC Address: 00:1f:f3:8b:26:c1 Product ID: 5122 Vendor ID: 1452 Marvell Yukon Gigabit Adapter 88E8053 Singleport Copper SA: Name: ethernet Type: Ethernet Controller Bus: PCI Vendor ID: 0x11ab Device ID: 0x4362 Subsystem Vendor ID: 0x11ab Subsystem ID: 0x5321 Revision ID: 0x0022 Link Width: x1 BSD name: en0 Kext name: AppleYukon2.kext Location: /System/Library/Extensions/IONetworkingFamily.kext/Contents/PlugIns/AppleYukon2.kext Version: 3.2.1b1 ethernet: Type: Ethernet Controller Bus: PCI Slot: AirPort Vendor ID: 0x168c Device ID: 0x001c Subsystem Vendor ID: 0x106b Subsystem ID: 0x0086 Revision ID: 0x0001 Link Width: x1 BSD name: en1 Kext name: AirPortAtheros21.kext Location: /System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortAtheros21.kext Version: 425.14.7 root# ifconfig lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 inet 127.0.0.1 netmask 0xff000000 gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280 stf0: flags=0<> mtu 1280 en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 ether 00:16:cb:a8:7d:01 inet6 fe80::216:cbff:fea8:7d01%en0 prefixlen 64 scopeid 0x4 inet 192.168.1.37 netmask 0xffffff00 broadcast 192.168.1.255 media: autoselect (1000baseT <full-duplex,flow-control>) status: active en4: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 ether 00:1f:f3:8a:f3:5a inet6 fe80::21f:f3ff:fe8a:f35a%en4 prefixlen 64 scopeid 0x5 inet 90.184.13.xxx netmask 0xfffffe00 broadcast 90.184.13.zzz media: autoselect (100baseTX <full-duplex,flow-control>) status: active en3: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 ether 00:1f:f3:8b:26:c1 inet6 fe80::21f:f3ff:fe8b:26c1%en3 prefixlen 64 scopeid 0x6 inet 90.184.12.yyy netmask 0xfffffe00 broadcast 90.184.13.zzz media: autoselect (100baseTX <full-duplex,flow-control>) status: active fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 2030 lladdr 00:17:f2:ff:fe:8e:e6:d2 media: autoselect <full-duplex> status: inactive en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 ether 00:17:f2:52:62:9e media: autoselect (<unknown type>) status: inactive root# system_profiler SPHardwareDataType Hardware: Hardware Overview: Model Name: Mac mini Model Identifier: Macmini1,1 Processor Name: Intel Core Duo Processor Speed: 1,83 GHz Number Of Processors: 1 Total Number Of Cores: 2 L2 Cache: 2 MB Memory: 2 GB Bus Speed: 667 MHz Boot ROM Version: MM11.0055.B08 SMC Version (system): 1.3f4 root# system_profiler SPSoftwareDataType Software: System Software Overview: System Version: Mac OS X 10.6.8 (10K549) Kernel Version: Darwin 10.8.0 Boot Volume: X Boot Mode: Normal Computer Name: MiniWeb User Name: System Administrator (root) Secure Virtual Memory: Enabled 64-bit Kernel and Extensions: No Time since boot: 5 days 1:31 >On 19.2.2012, at 14.53, postmaster wrote: > >> Feb 19 11:52:20 4604ds1-ynoe dovecot[443]: auth-worker: Debug: >sql(abuse(a)mathiesen.info,127.0.0.1): SELECT 5000 AS uid , 5000 AS gid , >concat ( '/Volumes/BrugerData/PostFix/mail/' , maildir ) AS home , >concat ( '/Volumes/BrugerData/PostFix/mail/' , maildir ) AS mail FROM >mailbox WHERE username =3D 'abuse(a)mathiesen.info' AND domain =3D >'mathiesen.info' AND active =3D 1 > >Probably won't help with your problem, but it's better if you don't >fetch "mail" field. Just fetch the home and set: > >mail_location = maildir:~/ > >This avoids maildir autodetection. That seemed to fix the autodetection :-) > >> # OS: Darwin 10.8.0 i386 hfs > >With HFS+ it's a good idea to set maildir_copy_with_hardlinks = no OK - set to no as advised > >> a list "" * >> * LIST (\HasNoChildren) "." "INBOX" >> a OK List completed. >> a select inbox >> Connection closed by foreign host. >> 4604ds1-ynoe:~ root# > >You mean the session hangs here until it's killed? Yes ... It does some of what it's supposed to do : the dovecot-uidlist.lock is set email is copied from new to cur, but then nothing more seems to happen :-( 4604ds1-ynoe:mail root# ls -l mathiesen.info/macintosh\(a)mathiesen.info/ total 40 drwx------ 2 5000 5000 4352 Feb 21 09:58 cur -rw------- 1 5000 5000 8119 Feb 21 10:28 dovecot-uidlist -rw------- 1 5000 5000 32 Feb 21 10:28 dovecot-uidlist.lock -rw------- 1 5000 5000 8 Feb 21 10:28 dovecot-uidvalidity -r--r--r-- 1 5000 5000 0 Feb 21 10:28 dovecot-uidvalidity.4f4363ac -rw------- 1 5000 5000 40 Feb 21 10:28 dovecot.index.log drwxr-xr-x 2 5000 5000 68 Feb 19 11:18 dovecot.rawlog drwx------ 2 5000 5000 68 Feb 21 09:58 new drwx------ 2 5000 5000 68 Feb 21 09:11 tmp 4604ds1-ynoe:mail root# >Try attaching gdb into it: > >gdb -p <pid of imap session> >bt full 4604ds1-ynoe:~ root# ps -axj | grep dovecot root 40655 1 40655 4d84750 0 Ss ?? 0:00.02 /macports/sbin/dovecot -c /macports/etc/dovecot/dovecot.conf _dovecot 40657 40655 40655 4d84750 0 S ?? 0:00.01 dovecot/anvil root 40658 40655 40655 4d84750 0 S ?? 0:00.03 dovecot/log root 40660 40655 40655 4d84750 0 S ?? 0:00.06 dovecot/config _dovecot 40662 40655 40655 4d84750 0 S ?? 0:00.02 dovecot/auth root 40663 40655 40655 4d84750 0 S ?? 0:00.03 dovecot/auth -w 5000 40677 40655 40655 4d84750 0 S ?? 0:00.01 dovecot/pop3 5000 40689 40655 40655 4d84750 0 S ?? 0:00.01 dovecot/pop3 5000 40803 40655 40655 4d84750 0 S ?? 0:00.01 dovecot/pop3 root 40618 362 40618 5680af8 1 S+ s001 0:00.01 tail -f dovecot.log root 40952 396 40951 4d85d40 2 R+ s003 0:00.00 grep dovecot 4604ds1-ynoe:~ root# gdb -p 40803 GNU gdb 6.3.50-20050815 (Apple version gdb-1518) (Sat Feb 12 02:49:13 UTC 2011) Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-apple-darwin". /private/var/root/40803: No such file or directory Attaching to process 40803. Reading symbols for shared libraries . done Reading symbols for shared libraries ...... done 0x90003afa in mach_msg_trap () (gdb) bt full #0 0x90003afa in mach_msg_trap () No symbol table info available. #1 0x90004267 in mach_msg () No symbol table info available. #2 0x9001b431 in vproc_mig_look_up2 () No symbol table info available. #3 0x9001b26a in bootstrap_look_up2 () No symbol table info available. #4 0x9001b0e4 in bootstrap_look_up () No symbol table info available. #5 0x9001af30 in notify_register_check () No symbol table info available. #6 0x9001ada7 in notify_register_tz () No symbol table info available. #7 0x9001a621 in tzsetwall_basic () No symbol table info available. #8 0x90041903 in localtime () No symbol table info available. #9 0x0007ba2f in mail_index_update_day_headers () No symbol table info available. #10 0x00077c95 in mail_index_transaction_finish () No symbol table info available. #11 0x0007680a in mail_index_transaction_commit_v () No symbol table info available. #12 0x00076acf in mail_index_transaction_commit_full () No symbol table info available. #13 0x00076b18 in mail_index_transaction_commit () No symbol table info available. #14 0x0007f434 in mail_index_sync_commit () No symbol table info available. #15 0x0004ff02 in maildir_sync_index_finish () No symbol table info available. #16 0x00051376 in maildir_sync_context () No symbol table info available. #17 0x000516f2 in maildir_storage_sync_init () No symbol table info available. #18 0x000125fd in mailbox_sync () No symbol table info available. #19 0x000024ba in client_create () No symbol table info available. #20 0x00001a2a in client_create_from_input () No symbol table info available. #21 0x00001f35 in login_client_connected () No symbol table info available. #22 0x000eb1a8 in master_login_auth_finish () No symbol table info available. #23 0x000eae80 in master_login_auth_callback () No symbol table info available. #24 0x000ebb3a in master_login_auth_input () No symbol table info available. #25 0x001001a7 in io_loop_call_io () No symbol table info available. #26 0x00101492 in io_loop_handler_run () No symbol table info available. #27 0x00100148 in io_loop_run () No symbol table info available. #28 0x000ed25a in master_service_run () No symbol table info available. #29 0x00001df8 in main () No symbol table info available. (gdb) quit The program is running. Quit anyway (and detach it)? (y or n) y Detaching from process 40803. 4604ds1-ynoe:~ root# > >or alternatively try: > >gdb --args /usr/local/libexec/dovecot/imap -u user@domain >run >a select inbox ><ctrl-c> >bt full 4604ds1-ynoe:~ root# gdb --args /macports/libexec/dovecot/pop3 -u postmaster(a)mathiesen.info GNU gdb 6.3.50-20050815 (Apple version gdb-1518) (Sat Feb 12 02:49:13 UTC 2011) Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-apple-darwin"...Reading symbols for shared libraries ..... done (gdb) run Starting program: /macports/libexec/dovecot/pop3 -u postmaster(a)mathiesen.info Reading symbols for shared libraries ++++. done Debug: auth input: postmaster(a)mathiesen.info uid=5000 gid=5000 home=/Volumes/BrugerData/PostFix/mail/mathiesen.info/postmaster(a)mathiesen.info/ Debug: Effective uid=5000, gid=5000, home=/Volumes/BrugerData/PostFix/mail/mathiesen.info/postmaster(a)mathiesen.info/ Debug: maildir++: root=/Volumes/BrugerData/PostFix/mail/mathiesen.info/postmaster(a)mathiesen.info/, index=, control=, inbox=/Volumes/BrugerData/PostFix/mail/mathiesen.info/postmaster(a)mathiesen.info/, alt= Debug: Namespace : Using permissions from /Volumes/BrugerData/PostFix/mail/mathiesen.info/postmaster(a)mathiesen.info/: mode=0700 gid=-1 a select inbox ^C Program received signal SIGINT, Interrupt. 0x90003afa in mach_msg_trap () (gdb) bt full #0 0x90003afa in mach_msg_trap () No symbol table info available. #1 0x90004267 in mach_msg () No symbol table info available. #2 0x9001b431 in vproc_mig_look_up2 () No symbol table info available. #3 0x9001b26a in bootstrap_look_up2 () No symbol table info available. #4 0x9001b0e4 in bootstrap_look_up () No symbol table info available. #5 0x9001af30 in notify_register_check () No symbol table info available. #6 0x9001ada7 in notify_register_tz () No symbol table info available. #7 0x9001a621 in tzsetwall_basic () No symbol table info available. #8 0x90041903 in localtime () No symbol table info available. #9 0x0007ba2f in mail_index_update_day_headers () No symbol table info available. #10 0x00077c95 in mail_index_transaction_finish () No symbol table info available. #11 0x0007680a in mail_index_transaction_commit_v () No symbol table info available. #12 0x00076acf in mail_index_transaction_commit_full () No symbol table info available. #13 0x00076b18 in mail_index_transaction_commit () No symbol table info available. #14 0x0007f434 in mail_index_sync_commit () No symbol table info available. #15 0x0004ff02 in maildir_sync_index_finish () No symbol table info available. #16 0x00051376 in maildir_sync_context () No symbol table info available. #17 0x000516f2 in maildir_storage_sync_init () No symbol table info available. #18 0x000125fd in mailbox_sync () No symbol table info available. #19 0x000024ba in client_create () No symbol table info available. #20 0x00001a2a in client_create_from_input () No symbol table info available. #21 0x00001d71 in main () No symbol table info available. (gdb) quit The program is running. Exit anyway? (y or n) y 4604ds1-ynoe:~ root#

2 1

[Dovecot] Folder name migration when moving from 2.0.x to 2.1.x?
by Ralf Hildebrandt 21 Feb '12

21 Feb '12

Today I encountered this after upgrading: Feb 18 18:15:40 postamt dovecot: imap(lehnertr): Panic: LIST: Mailbox name not UTF-8: INBOX.Entw�rfe Feb 18 18:15:40 postamt dovecot: imap(lehnertr): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x4104a) [0xb75cc04a] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x410bb) [0xb75cc0bb] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0xb75cc9b7] -> dovecot/imap [lehnertr 85.178.5.225 LSUB]() [0x8052bac] -> dovecot/imap [lehnertr 85.178.5.225 LSUB](cmd_list_full+0x4af) [0x80530df] -> dovecot/imap [lehnertr 85.178.5.225 LSUB](cmd_lsub+0x17) [0x8053537] -> dovecot/imap [lehnertr 85.178.5.225 LSUB](command_exec+0x32) [0x8057c92] -> dovecot/imap [lehnertr 85.178.5.225 LSUB]() [0x8056c7d] -> dovecot/imap [lehnertr 85.178.5.225 LSUB]() [0x8056d95] -> dovecot/imap [lehnertr 85.178.5.225 LSUB](client_handle_input+0x135) [0x8056fa5] -> dovecot/imap [lehnertr 85.178.5.225 LSUB](client_input+0x60) [0x80578a0] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x44) [0xb75dafb4] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xce) [0xb75dbe5e] -> /usr/local/lib/dovecot/libdovecot.so.0 a) It should not PANIC (I think) b) How can I globally "fix" the folder names (preferably in such a way that I am able to switch back and forth between 2.0 and 2.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

5 13

[Dovecot] 2.1 upgrade docs?
by Marc Perkel 21 Feb '12

21 Feb '12

Just wondering if there's any upgrade docs for 2.1 online?

7 7

[Dovecot] dovecot 2 doesn't start with managesieve
by nti＠w4w.net 21 Feb '12

21 Feb '12

Hi I build dovecot 2.0.16 and and dovecot-pigeonhole-0.2.5 on two machines with the same options. The config files are equivalent. On the first machine everything works fine - on the second dovecot with managesive won't start (without sieve protocol it does). Error: socket() failed: Protocol not supported Error: service(managesieve-login): listen(::, 4190) failed: Protocol not supported Fatal: Failed to start listeners I controlled the config, build pigeonhole a second time - nothing helps. Any idea ? Is there a possibility to debug the start? Nicola ... plugin { ... sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap pop3 sieve ... service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service managesieve { process_limit = 1024 } ... protocol sieve { managesieve_max_compile_errors = 10 }

2 1

[Dovecot] user_filter problem
by sanito＠progresas.lt 21 Feb '12

21 Feb '12

Hello, I have a little bit complex setup. I'm trying to use dovecot lmtp and pop3 with user information stored in the LDAP database. The main problem is that email address and pop3 username are different for every mailbox (I cannot change this behaviour, because thousands of people already configured their email client for such a setup). So in my situation, user_filter for lmtp should be: user_filter=(mail=%u), but for pop3 it should be: user_filter=(cn=%u). Please, see: E-mail address: john(a)example.com pop3 username: 0005a pop3 password: very_secure_password And ldap ldiff for this mailbox: dn: cn=0005a,dc=example.com,ou=localmail,ou=mail uid: 0005a mail: john(a)example.com mailbox: /data/mail/example.com/0005a/Maildir/ sn: 0005a description: testing homeDirectory: /data/mail/example.com/0005a cn: 0005a userPassword:: e0NSWVBUfWxpOXBVaEw5SWJkRWc= objectClass: inetOrgPerson objectClass: CourierMailAccount objectClass: top I think I need to use different user_filter for lmtp and pop3, but it's not possible or I cannot find how to do it. Please, help! -- Best regards, dammit

2 1

[Dovecot] Possible broken indexer(lucene/solr)?
by Ingo Thierack 21 Feb '12

21 Feb '12

Hello, try to use the new 2.1rc and don't get any data in the searchindex. Tried first lucene, and switched than back so solr. If I do an search in an mailfolder, i get in the dovecot-log 2012-02-06 22:17:11 | dovecot: | indexer-worker(xxxxxx): Indexed 0 messages in INBOX/dovecot Log from solr. Feb 6, 2012 10:17:11 PM org.apache.solr.core.SolrCore execute INFO: [] webapp=/solr path=/select params={fl=uid,score&sort=uid+asc&fq=%2Bbox:120ed10bbe9dcd4c8d2e0000f8146a47+%2Buser:"xxxxxxx"&q=body:"solr"&rows=9159} hits=0 status=0 QTime=1 Maybe I miss something. Upgraded from 2.0.15 to 2.1(head from repository yesterday) With 2.0 i see, if i start an search, solr had to work on the mail, now happens nothing. Upgrade the schema.xml, delete the old index. Regard Ingo Thierack

4 4

[Dovecot] Feature request for maillog plugin
by Aydın Demirel 21 Feb '12

21 Feb '12

Hi, Is it possible to add the modification time and file name of the mail file to maillog plugin? Thanks -- *Aydın Demirel Endersys Ltd. Sistem Destek Mühendisi/ System Support Engineer* * *<<Endersys is the first Advanced Business Partner of Red Hat in Turkey! http://www.europe.redhat.com/partners/endersys/>> Phone : +90 216 470 9423 | GSM : +90 530 401 8203 Fax : +90 216 470 9508 | Web : http://www.endersys.com <http://www.endersys.com/> Blog : http://blog.endersys.com <http://blog.endersys.com/> Twitter : http://www.twitter.com/endersys LPI : The #1 Linux Certification for IT Professionals LPI (Linux Professional Institute) Turkey http://www.lpi-turkey.com <http://www.lpi-turkey.com/>

2 1

[Dovecot] Homedir vs locations vs mail_location?
by Alexander Chekalin 21 Feb '12

21 Feb '12

Hello, I use Dovecot for rather long time, but I'm still in doubt for some small things. Here they are: 1. The homedir value points to the place where everything for the user stored at, while mail_location is something (some place) where mail stored at. if I deal with pure virtual users (all users are in sql tables and no system homes for them at all), should I ever care for returning meaningful value for 'homedir' (via password_query's userdb_home), or I can simple return empty or constant ('' or '123') for it and it won't mess anything? 2. If I use single (default) namespace, should I set namespace's location (to the same value as global mail_location), and should I expect anything strange if I skip it to set? Reversely, is it possible not to set global mail_location and set only namespace's location (which would be more logical as namespace definition is compact and easy to find in config)? I've reread my questions and see it is dummy ones, but I'd like to know that for sure. Thank you in advance, Alexander

3 2

[Dovecot] dovecot freezes when trying to get mail from maildir with mail
by postmaster 21 Feb '12

21 Feb '12

I'm completely stumped by this problem and I've tried everything at present - including installing dovecot from scratch. The problem is that when trying to get email from the server -AND- there's email in the account, the pop3 or imap process freezes and no email is fetched. The crazy thing is, that it has been working perfectly, but suddenly I'm getting these freezes both when using telnet from localhost, roundcubemail on the same server and Seamonkey from another computer. Logging seems to work perfectly. For an account without email, dovecot finds the maildir++ and acts correctly. For an account -with- email, dovecot seems to find the maildir++, but also seems to try Namespace of which I haven't defined any. I've tried to get rawlog to work also, but that didn't work - the telnet process froze on login even though I'm quite sure I did the right thing and ps showed an active rawlog process Postfix is delivering the email straight into the mailboxes. Here is the information 4604ds1-ynoe:~ root# port installed | grep dovecot dovecot2 @2.0.18_0+mysql5+postgresql91 (active) dovecot2-sieve @0.2.5_1 (active) postfix @2.9.0_0+dovecot_sasl+mysql5+pcre+postgresql91 (active) 4604ds1-ynoe:~ root# 4604ds1-ynoe:log root# cat dovecot.log.txt Feb 19 11:46:52 4604ds1-ynoe dovecot[441]: master: Dovecot v2.0.18 starting up (core dumps disabled) Feb 19 11:51:47 4604ds1-ynoe dovecot[443]: auth: Debug: Loading modules from directory: /macports/lib/dovecot/auth Feb 19 11:51:47 4604ds1-ynoe dovecot[443]: auth: Debug: auth client connected (pid=495) Feb 19 11:52:20 4604ds1-ynoe dovecot[443]: auth: Debug: client in: AUTH 1 PLAIN service=imap secured lip=127.0.0.1 rip=127.0.0.1 lport=143 rport=49180 resp=AGFidXNlQG1hdGhpZXNlbi5pbmZvAHRlc3R0ZXN0 Feb 19 11:52:20 4604ds1-ynoe dovecot[443]: auth-worker: Debug: Loading modules from directory: /macports/lib/dovecot/auth Feb 19 11:52:20 4604ds1-ynoe dovecot[443]: auth-worker: mysql(/macports/var/run/mysql5/mysqld.sock): Connected to database infomathiesenpostfixadmin Feb 19 11:52:20 4604ds1-ynoe dovecot[443]: auth-worker: Debug: sql(abuse(a)mathiesen.info,127.0.0.1): query: SELECT username AS user, domain, password FROM mailbox WHERE username = 'abuse(a)mathiesen.info' AND domain = 'mathiesen.info' AND active = 1 Feb 19 11:52:20 4604ds1-ynoe dovecot[443]: auth: Debug: client out: OK 1 user=abuse(a)mathiesen.info Feb 19 11:52:20 4604ds1-ynoe dovecot[443]: auth: Debug: master in: REQUEST 738852865 495 1 687658e957c0e4f473891548eecc49be Feb 19 11:52:20 4604ds1-ynoe dovecot[443]: auth-worker: Debug: sql(abuse(a)mathiesen.info,127.0.0.1): SELECT 5000 AS uid , 5000 AS gid , concat ( '/Volumes/BrugerData/PostFix/mail/' , maildir ) AS home , concat ( '/Volumes/BrugerData/PostFix/mail/' , maildir ) AS mail FROM mailbox WHERE username = 'abuse(a)mathiesen.info' AND domain = 'mathiesen.info' AND active = 1 Feb 19 11:52:20 4604ds1-ynoe dovecot[443]: auth: Debug: master out: USER 738852865 abuse(a)mathiesen.info uid=5000 gid=5000 home=/Volumes/BrugerData/PostFix/mail/mathiesen.info/abuse(a)mathiesen.info/ mail=/Volumes/BrugerData/PostFix/mail/mathiesen.info/abuse(a)mathiesen.info/ Feb 19 11:52:20 4604ds1-ynoe dovecot[443]: imap-login: Login: user=<abuse(a)mathiesen.info>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=503, secured Feb 19 11:52:20 4604ds1-ynoe dovecot[443]: imap: Debug: Added userdb setting: mail=/Volumes/BrugerData/PostFix/mail/mathiesen.info/abuse(a)mathiesen.info/ Feb 19 11:52:20 4604ds1-ynoe dovecot[443]: imap(abuse(a)mathiesen.info): Debug: Effective uid=5000, gid=5000, home=/Volumes/BrugerData/PostFix/mail/mathiesen.info/abuse(a)mathiesen.info/ Feb 19 11:52:20 4604ds1-ynoe dovecot[443]: imap(abuse(a)mathiesen.info): Debug: mdbox autodetect: stat(/Volumes/BrugerData/PostFix/mail/mathiesen.info/abuse(a)mathiesen.info/storage) failed: No such file or directory Feb 19 11:52:20 4604ds1-ynoe dovecot[443]: imap(abuse(a)mathiesen.info): Debug: sdbox autodetect: stat(/Volumes/BrugerData/PostFix/mail/mathiesen.info/abuse(a)mathiesen.info/mailboxes) failed: No such file or directory Feb 19 11:52:20 4604ds1-ynoe dovecot[443]: imap(abuse(a)mathiesen.info): Debug: maildir++: root=/Volumes/BrugerData/PostFix/mail/mathiesen.info/abuse(a)mathiesen.info, index=, control=, inbox=/Volumes/BrugerData/PostFix/mail/mathiesen.info/abuse(a)mathiesen.info, alt= Feb 19 11:53:01 4604ds1-ynoe dovecot[443]: imap(abuse(a)mathiesen.info): Disconnected: Logged out bytes=45/750 Feb 19 11:53:06 4604ds1-ynoe dovecot[443]: auth: Debug: auth client connected (pid=512) Feb 19 11:53:55 4604ds1-ynoe dovecot[443]: auth: Debug: client in: AUTH 1 PLAIN service=imap secured lip=127.0.0.1 rip=127.0.0.1 lport=143 rport=49182 resp=AG1hY2ludG9zaEBtYXRoaWVzZW4uaW5mbwB0ZXN0dGVzdA== Feb 19 11:53:55 4604ds1-ynoe dovecot[443]: auth-worker: Debug: sql(macintosh(a)mathiesen.info,127.0.0.1): query: SELECT username AS user, domain, password FROM mailbox WHERE username = 'macintosh(a)mathiesen.info' AND domain = 'mathiesen.info' AND active = 1 Feb 19 11:53:55 4604ds1-ynoe dovecot[443]: auth: Debug: client out: OK 1 user=macintosh(a)mathiesen.info Feb 19 11:53:55 4604ds1-ynoe dovecot[443]: auth: Debug: master in: REQUEST 1866334209 512 1 332714ca2a070d7adb342d4baba4a19a Feb 19 11:53:55 4604ds1-ynoe dovecot[443]: auth-worker: Debug: sql(macintosh(a)mathiesen.info,127.0.0.1): SELECT 5000 AS uid , 5000 AS gid , concat ( '/Volumes/BrugerData/PostFix/mail/' , maildir ) AS home , concat ( '/Volumes/BrugerData/PostFix/mail/' , maildir ) AS mail FROM mailbox WHERE username = 'macintosh(a)mathiesen.info' AND domain = 'mathiesen.info' AND active = 1 Feb 19 11:53:55 4604ds1-ynoe dovecot[443]: auth: Debug: master out: USER 1866334209 macintosh(a)mathiesen.info uid=5000 gid=5000 home=/Volumes/BrugerData/PostFix/mail/mathiesen.info/macintosh(a)mathiesen.info/ mail=/Volumes/BrugerData/PostFix/mail/mathiesen.info/macintosh(a)mathiesen.info/ Feb 19 11:53:55 4604ds1-ynoe dovecot[443]: imap-login: Login: user=<macintosh(a)mathiesen.info>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=522, secured Feb 19 11:53:55 4604ds1-ynoe dovecot[443]: imap: Debug: Added userdb setting: mail=/Volumes/BrugerData/PostFix/mail/mathiesen.info/macintosh(a)mathiesen.info/ Feb 19 11:53:55 4604ds1-ynoe dovecot[443]: imap(macintosh(a)mathiesen.info): Debug: Effective uid=5000, gid=5000, home=/Volumes/BrugerData/PostFix/mail/mathiesen.info/macintosh(a)mathiesen.info/ Feb 19 11:53:55 4604ds1-ynoe dovecot[443]: imap(macintosh(a)mathiesen.info): Debug: mdbox autodetect: stat(/Volumes/BrugerData/PostFix/mail/mathiesen.info/macintosh(a)mathiesen.info/storage) failed: No such file or directory Feb 19 11:53:55 4604ds1-ynoe dovecot[443]: imap(macintosh(a)mathiesen.info): Debug: sdbox autodetect: stat(/Volumes/BrugerData/PostFix/mail/mathiesen.info/macintosh(a)mathiesen.info/mailboxes) failed: No such file or directory Feb 19 11:53:55 4604ds1-ynoe dovecot[443]: imap(macintosh(a)mathiesen.info): Debug: maildir++: root=/Volumes/BrugerData/PostFix/mail/mathiesen.info/macintosh(a)mathiesen.info, index=, control=, inbox=/Volumes/BrugerData/PostFix/mail/mathiesen.info/macintosh(a)mathiesen.info, alt= Feb 19 11:54:13 4604ds1-ynoe dovecot[443]: imap(macintosh(a)mathiesen.info): Debug: Namespace : Using permissions from /Volumes/BrugerData/PostFix/mail/mathiesen.info/macintosh(a)mathiesen.info: mode=0700 gid=-1 Feb 19 12:12:16 4604ds1-ynoe dovecot[441]: master: Error: service(imap): child 522 killed with signal 3 Feb 19 12:15:48 4604ds1-ynoe dovecot[441]: master: Warning: Killed with signal 15 (by pid=1086 uid=0 code=unknown 0) 4604ds1-ynoe:log root# 4604ds1-ynoe:mail root# ps -axj | grep dovecot root 441 1 441 56804e0 0 Ss ?? 0:00.01 /macports/sbin/dovecot -c /macports/etc/dovecot/dovecot.conf _dovecot 442 441 441 56804e0 0 S ?? 0:00.01 dovecot/anvil root 443 441 441 56804e0 0 S ?? 0:00.01 dovecot/log 5000 522 441 441 56804e0 0 S ?? 0:00.01 dovecot/imap root 452 362 452 5680af8 1 S+ s001 0:00.00 tail -f dovecot.log root 543 380 542 4d84c30 2 R+ s002 0:00.00 grep dovecot 4604ds1-ynoe:mail root# kill -QUIT 522 4604ds1-ynoe:mail root# dovecot stop 4604ds1-ynoe:mail root# ps -axj | grep dovecot root 452 362 452 5680af8 1 S+ s001 0:00.00 tail -f dovecot.log root 1091 380 1090 4d84c30 2 R+ s002 0:00.00 grep dovecot 4604ds1-ynoe:mail root# 4604ds1-ynoe:~ root# telnet localhost 143 Trying 127.0.0.1... Connected to localhost (127.0.0.1). Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN] Dovecot ready. a login "abuse(a)mathiesen.info" "x" 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] Logged in a list "" * * LIST (\HasNoChildren) "." "INBOX" a OK List completed. a select inbox * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 0 EXISTS * 0 RECENT * OK [UIDVALIDITY 1326334461] UIDs valid * OK [UIDNEXT 4] Predicted next UID * OK [HIGHESTMODSEQ 1] Highest a OK [READ-WRITE] Select completed. a logout * BYE Logging out a OK Logout completed. Connection closed by foreign host. 4604ds1-ynoe:~ root# telnet localhost 143 Trying 127.0.0.1... Connected to localhost (127.0.0.1). Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN] Dovecot ready. a login "macintosh(a)mathiesen.info" "x" 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] Logged in a list "" * * LIST (\HasNoChildren) "." "INBOX" a OK List completed. a select inbox Connection closed by foreign host. 4604ds1-ynoe:~ root# 4604ds1-ynoe:~ root# dovecot -n # 2.0.18: /macports/etc/dovecot/dovecot.conf # OS: Darwin 10.8.0 i386 hfs auth_debug = yes auth_debug_passwords = yes auth_verbose = yes auth_verbose_passwords = plain base_dir = /macports/var/run/dovecot/ default_internal_user = _dovecot default_login_user = _dovenull disable_plaintext_auth = no first_valid_gid = 5000 first_valid_uid = 5000 mail_debug = yes mail_gid = 5000 mail_location = maildir:/Volumes/BrugerData/PostFix/mail/%d/%u mail_uid = 5000 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 mmap_disable = yes passdb { args = /macports/etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size } protocols = imap pop3 service postlogin { executable = script-login -d rawlog } ssl = no syslog_facility = local2 userdb { args = /macports/etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol pop3 { pop3_client_workarounds = oe-ns-eoh outlook-no-nuls } 4604ds1-ynoe:~ root#

2 1

[Dovecot] Something is strange - perhaps my AMD processors ?
by Finn B 21 Feb '12

21 Feb '12

Moi Timo / all. I've been using Dovecot on my Qmailtoaster production mailserver for some years - since 1.0.7 and current Version 2.0.10 - works perfectly. Now I am installing a backupsystem and a VM testsystem (2 boxes) - and no matter how and what Version I am installing on these 2 boxes I get below messages whenever I try to test connection with Telnet (localhost 110 / 995). I have tried to install all Dovecot versions from 2.010 to 2.018 as rpms, yums and as source and compiled it. It's on Centos5.7 (64) with Qmailtoaster (which I have installed as I have done many times before) I have tried to copy all my settings from my current production system (Centos 5.7, latest and greatest versions of qmailtoaster and Dovecot 2.0.10) - nothing helps. Now I come to think of it I realize that my production system is intel based and the 2 new ones are AMD based and wonder if this may be the case ? Dovecot.log master: Error: Service(auth): command startup failed, throttling log: Error: Service(auth): child 1859 returned error 89 (Fatal failure) pop3-login: Error: Timeout waiting for handshake from auth server. my pid=1858, input bytes=0 Regards, Finn B

7 8

[Dovecot] Questions still about a uw-imap -> dovecot conversion
by Steve Campbell 20 Feb '12

20 Feb '12

The more I read about all of this, the more I'm thinking about moving to maildir format. My switchover this weekend is full of holes due to the way user's imap folders were laid out. Some had folders in their home directory and others might have folders in their /home/mail directory. Some how, Horde/Imp seemed to keep track of it. Dovecot is not doing so well. I've been reading about the conversion technique to convert to maildir, but I'm wondering if I can do this based on the way our users are set up. Most are pop accounts. Our webmail is configured to read the inbox from /var/spool/mail and their imap folders from /home or /home/mail. Some have imap accounts on their desktop defined through their mail client. RH/Centos seems to want me to switch to postfix since most of the documentation I find doesn't mention Sendmail. My filesystem is laid out to handle Inboxes in /var/spool/mail and imap folders in /home(/mail) and these aren't logical volumes but true partitions, so I've got to consider this as I make any changes. I also run pop using dovecot, so I'll need to figure all this out. I've read the technique linked to on the dovecot site that points to "Replacing UW-IMAP with Dovecot on RHEL 3" written back in 2004, and that's about the only real pointers I'm finding. I don't want to have to go around to each machine and change their clients to IMAP.. Anyone care to comment on anything similar they've done and how many pitfalls they ran into and what they were? steve campbell

3 4

[Dovecot] A Postfix/Dovecot example with SQLite backend [crossposted]
by /dev/rob0 19 Feb '12

19 Feb '12

There are many mail howtos on the web ... can one more hurt? http://rob0.nodns4.us/howto/README http://rob0.nodns4.us/howto/ http://rob0.nodns4.us/howto/latest.tar.gz (all files) (Sorry, not HTML yet. That is on the agenda.) This is a multiple address class sample implementation of a Postfix MTA and Dovecot IMAP server using a SQLite3 data backend. Domain lookups, user maps, access and transport maps: all using a single, shared SQLite database file. What, other than the SQLite backend, distinguishes this from other mail system howtos? The Postfix high points include a complete implementation of all address classes and per-address transport(5) maps, virtual(8) UID/GID maps, and smtpd(8) recipient access(5) maps. (The latter is using smtpd_restriction_classes, which are not discussed in detail, but are implemented in an interesting way.) On the Dovecot side, it's mostly standard stuff. The SQL deny userdb implementation, and the seamless integration of system and SQL users, might be interesting. I think the database itself is the best part of this example. It's as close to "normalized" as I think it can reasonably be. A significant fact is that each revision of the system has tended to simplify the schema. That's a good sign, I think. One central Domain table lists all domains and hostnames to which the server makes reference. Likewise, a central Address table lists all addresses (with a pointer to the Domain table for each record.) The Alias table defines relationships between Address entries. (Both local(8) and virtual(5) alias maps exist in that table.) Comments and suggestions are welcome, on-list if it's topical to whichever list (please don't crosspost unless comments are relevant to both lists), or offlist to the address in the README file (or as detailed below.) Thanks for your interest. -- http://rob0.nodns4.us/ -- system administration and consulting Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:

1 0

[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 17 Feb '12

17 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 17 Feb '12

17 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 17 Feb '12

17 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