- dovecot - dovecot.org

[Dovecot] Update problem from 1.2 => 2.0.19 and recommended imap storage
by Gerhard Wiesinger 17 Mar '12

17 Mar '12

Hello, After fixing configuration and other issues I'm still having one problem with imap executable and pine: less .pinerc # Changed config: #rsh-command=/usr/sbin/dovecot --exec-mail imap rsh-command=/usr/local/bin/imap Calling imap still fails as non root: imap /usr/bin/ld: cannot open output file /usr/local/bin/.libs/2612-lt-imap: Permission denied collect2: ld returned 1 exit statusn Any ideas to fix it? BTW: What is the recommended dovecot storage for dovecot 2.x (upgradeable from mbox)? Thnx. Ciao, Gerhard

2 2

[Dovecot] Just in time AV scanning
by Kelsey Cummings 16 Mar '12

16 Mar '12

I'm curious if anyone has any plugins for AV integration directly into dovecot. Our old pop servers have been scanning messges as they're moved from new->cur in the inbox and, at least where user's aren't poping every few seconds, there is occasionally enough time between scanning through the MXs to message retreval to snag a few more virues with updated definitions before they reach customers. Anyone doing anything similar? -- Kelsey Cummings - kgc(a)corp.sonic.net sonic.net, inc. System Architect 2260 Apollo Way 707.522.1000 Santa Rosa, CA 95407

3 4

[Dovecot] Problem copying e-mails to IMAP - Dovecot 2.1.2
by Odhiambo Washington 16 Mar '12

16 Mar '12

I have a situation where I need to migrate e-mails from Outlook 2011 (Mac) to Apple Mail. Having looked at all options, I have resorted to the, perhaps, most difficult way: Create folders on the IMAP server, copy e-mails into them from Outlook, connect Apple Mail and do the reverse. However, I have hit a wall. I am running Dovecot 2.1.2 on FreeBSD, with mdbox storage. In my first attempt, I have 1792 messages in the "Sent Items" folder for Outlook. I have tried (3 times) to copy the messages to the IMAP/Sent Items folder, but the process dies at some point. When that happens, Outlook pops a screen saying "IMAP session state is inconsistent, please relogin". Dovecot says: Mar 16 13:30:26 jaribu dovecot: master: Warning: Killed with signal 15 (by pid=72242 uid=0 code=kill) Mar 16 13:30:29 master: Info: Dovecot v2.1.2 starting up Mar 16 13:31:15 auth-worker(72594): Info: mysql(localhost): Connected to database exim4u Mar 16 13:31:15 imap-login: Info: Login: user=<wash(a)kictanet.or.ke>, method=PLAIN, rip=192.168.40.194, lip=192.168.40.252, mpid=72595 Mar 16 13:31:15 imap: Debug: Loading modules from directory: /opt/dovecot2.1/lib/dovecot Mar 16 13:31:15 imap: Debug: Module loaded: /opt/dovecot2.1/lib/dovecot/lib10_quota_plugin.so Mar 16 13:31:15 imap(wash(a)kictanet.or.ke): Debug: Effective uid=26, gid=26, home=/var/spool/virtual/kictanet.or.ke/wash Mar 16 13:31:15 imap(wash(a)kictanet.or.ke): Debug: quota: No quota setting - plugin disabled Mar 16 13:31:15 imap(wash(a)kictanet.or.ke): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=mdbox:~/mdbox Mar 16 13:31:15 imap(wash(a)kictanet.or.ke): Debug: fs: root=/var/spool/virtual/kictanet.or.ke/wash/mdbox, index=, control=, inbox=, alt= Mar 16 13:31:15 imap(wash(a)kictanet.or.ke): Debug: Namespace : Using permissions from /var/spool/virtual/kictanet.or.ke/wash/mdbox: mode=0700 gid= -1 Mar 16 13:31:30 imap-login: Info: Login: user=<wash(a)kictanet.or.ke>, method=PLAIN, rip=192.168.40.194, lip=192.168.40.252, mpid=72646 Mar 16 13:31:30 imap: Debug: Loading modules from directory: /opt/dovecot2.1/lib/dovecot Mar 16 13:31:30 imap: Debug: Module loaded: /opt/dovecot2.1/lib/dovecot/lib10_quota_plugin.so Mar 16 13:31:30 imap(wash(a)kictanet.or.ke): Debug: Effective uid=26, gid=26, home=/var/spool/virtual/kictanet.or.ke/wash Mar 16 13:31:30 imap(wash(a)kictanet.or.ke): Debug: quota: No quota setting - plugin disabled Mar 16 13:31:30 imap(wash(a)kictanet.or.ke): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=mdbox:~/mdbox Mar 16 13:31:30 imap(wash(a)kictanet.or.ke): Debug: fs: root=/var/spool/virtual/kictanet.or.ke/wash/mdbox, index=, control=, inbox=, alt= Mar 16 13:31:30 imap(wash(a)kictanet.or.ke): Debug: Namespace : Using permissions from /var/spool/virtual/kictanet.or.ke/wash/mdbox: mode=0700 gid= -1 Mar 16 13:31:30 imap: Debug: Loading modules from directory: /opt/dovecot2.1/lib/dovecot Mar 16 13:31:30 imap: Debug: Module loaded: /opt/dovecot2.1/lib/dovecot/lib10_quota_plugin.so Mar 16 13:31:30 imap(wash(a)kictanet.or.ke): Debug: Effective uid=26, gid=26, home=/var/spool/virtual/kictanet.or.ke/wash Mar 16 13:31:30 imap(wash(a)kictanet.or.ke): Debug: quota: No quota setting - plugin disabled Mar 16 13:31:30 imap(wash(a)kictanet.or.ke): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=mdbox:~/mdbox Mar 16 13:31:30 imap(wash(a)kictanet.or.ke): Debug: fs: root=/var/spool/virtual/kictanet.or.ke/wash/mdbox, index=, control=, inbox=, alt= Mar 16 13:31:30 imap(wash(a)kictanet.or.ke): Debug: Namespace : Using permissions from /var/spool/virtual/kictanet.or.ke/wash/mdbox: mode=0700 gid=-1 Mar 16 13:31:30 imap-login: Info: Login: user=<wash(a)kictanet.or.ke>, method=PLAIN, rip=192.168.40.194, lip=192.168.40.252, mpid=72647 Mar 16 13:33:23 jaribu dovecot: imap(wash(a)kictanet.or.ke): Error: Corrupted dbox file /var/spool/virtual/kictanet.or.ke/wash/mdbox/storage/m.4 (around offset=894): msg header has bad magic value Mar 16 13:33:23 jaribu dovecot: imap(wash(a)kictanet.or.ke): Warning: mdbox /var/spool/virtual/kictanet.or.ke/wash/mdbox/storage: rebuilding indexes Mar 16 13:33:23 jaribu dovecot: imap(wash(a)kictanet.or.ke): Error: /var/spool/virtual/kictanet.or.ke/wash/mdbox/mailboxes/SentItems/dbox-Mails/dovecot.index reset, view is now inconsistent Mar 16 13:33:23 imap(wash(a)kictanet.or.ke): Info: Disconnected: IMAP session state is inconsistent, please relogin. bytes=13816863/907529 My doveconf output is here -> http://pastebin.com/6yNP5ygt -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ I can't hear you -- I'm using the scrambler. Please consider the environment before printing this email.

4 11

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

16 Mar '12

http://dovecot.org/releases/2.1/dovecot-2.1.3.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.3.tar.gz.sig Do not use v2.1.2 with multi-dbox format, it's broken. I didn't notice that a small optimization I did a few days ago broke mdbox in some situations (when mdbox first created a new m.X file, and later in same session saved another message to it). It's quite a high priority for me to run some automated testing before releasing new versions, for example a small imaptest run with mdbox would have caught this. Perhaps the next release will already have the automated testing.

1 0

[Dovecot] Another hint from the clue box 8-) imapc/imap proxy user mailbox server location
by Terry Carmen 16 Mar '12

16 Mar '12

I'm running imapproxy as shown at http://wiki2.dovecot.org/HowTo/ImapcProxy. In fact, that's my config in the wiki. 8-) It's been working, but has performance issues when the Exchange server that's hard-coded as imapc_host=xxx.xxx.xxx.xxx doesn't happen to be the user's home exchange server. I'd like to point dovecot at the correct Exchange server based on an LDAP query, and in fact, have an LDAP search that works: DC=example,DC=com (&(objectCategory=person)(objectClass=user)(!(userAccountcontrol:1.2.840.113556.1.4.803:=2))(sAMAccountName=username)) With the exchange server being returned in the msExchHomeServerName property as: /O=example/OU=INT/cn=Configuration/cn=Servers/cn=exchangeservername I believe this should somehow end up in the userdb section, which currently contains "driver = prefetch", but can't seem to figure out specifically what should be there. The only important part is "cn=exchangeservername", which is the machine name and would need to be prepended to example.com to get the fqdn. Can anybody toss me a clue? Once I get it working, I'll update the wiki. Thanks! Terry

4 14

[Dovecot] ldapi support
by Nikolaos Milas 16 Mar '12

16 Mar '12

Hi, Quick question: Does Dovecot support ldapi (i.e. via Unix Sockets) connections for LDAP lookups (user, password, auth etc.) or only ldap/ldaps (over TCP)? If yes, how do we specify ldapi://localhost in Dovecot configuration files? Thanks, Nick

2 1

[Dovecot] imaptest: performance testing
by Nick Urbanik 16 Mar '12

16 Mar '12

Dear Folks, Using head of imaptest with dovecot 2.1, I am attempting to put a heavy load on the server, with insufficient success. I made 15000 user accounts, put them in to a file, one per line. Then I ran imaptest with ./imaptest userfile=../../imap-test-userlist-15001.txt clients=15001 pass=SECRETPASSWORD But CPU load is only reaching 20. I put an mbox containing 67 messages into ~/mail/dovecot-crlf So what is the best way to put a really heavy load on an imap server? The documentation describes testing correctness of the server without really emphasising performance. I would like to do something like dnsperf, which adds a linearly increasing load until the server is unable to cope. This machine has 24G RAM and 8 cores. I'll be grateful for any constructive suggestions. -- Nick Urbanik http://nicku.org nicku(a)nicku.org GPG: 7FFA CDC7 5A77 0558 DC7A 790A 16DF EC5B BB9D 2C24 ID: BB9D2C24

3 2

[Dovecot] Upgrading from 2.0.x to 2.1.x
by Nikolaos Milas 16 Mar '12

16 Mar '12

Hi, A quick question: Are there any incompatibilities in config settings among versions 2.0.x and 2.1.x (and subsequently v2.2.x)? That is, upgrading Dovecot 2.0.x to 2.1.x software, will also require changes of any config settings (as upgrading from v1.x to 2.0.x did)? Thanks, Nick

2 2

[Dovecot] Lack of external documentation?
by Steve Campbell 16 Mar '12

16 Mar '12

Firstly, this isn't meant to be critical, and I realize the subject line probably suggest criticism, so... I was sort of forced into using dovecot as my imap/pop server due to upgrading 3 versions of OS on my mail servers. So far, that's not bad. What surprises me is that one of the first things I usually do whenever I start using different software is to purchase a book that seems to suit me. Searching all of the common places like amazon, ebay, etc for manuals turned up little to nothing on dovecot. I'm wondering why and is this so new that people just haven't written books about it yet? The one thing I'm a little critical of, though, is that trying to make heads or tails of dovecot by following the online documentation is a little problematic. I'm constantly jumping to another page and then back to the original page, and for the most part, I just don't know enough about it all yet to know what I'm looking for. Does anyone know of any manuals/books that have been written that might introduce me to most of the stuff in dovecot? So far, the list has been great, but once the "dsync" threads started popping up, I find there's even more I don't know about. Thanks for all the help I've received so far and I think I'm really going to like dovecot. Once I get the hang of it, I'll probably reduce the amount of noise on the list by half. steve campbell

8 8

[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