- dovecot - dovecot.org

Dovecot code repository moved to Github
by Timo Sirainen 11 Jan '16

11 Jan '16

http://hg.dovecot.org/ is no longer being updated. The public repository exists now in https://github.com/dovecot/core instead. I'm not sure yet if we should continue pushing commit emails to dovecot-cvs list or if Github's internal notifications are enough. In any case dovecot-cvs list isn't working right now.

5 9

sieve - content checks with special chars
by Hajo Locke 11 Jan '16

11 Jan '16

Hello, currently i try subject tests with special chars and german umlauts öäü etc. if header :contains "subject" ["öööö äää"] { fileinto "umlauts"; } iam surprised, this is working out of the box. great! in procmail i had to add a second step by manual coding the needle with perl. is sieve reliable at this kind of tests or are there some special cases? iam worried about this, because it was to easy. confusing... ;) Thanks, Hajo

3 2

Enterprise Repository Access?
by Ben Johnson 10 Jan '16

10 Jan '16

Hello! I apologize if this has been asked already. (I did search before posting...) Is it still possible to obtain access to Dovecot's Enterprise Repository, for Ubuntu and Debian, at no cost? When last I registered for such access, I recall there being a "mock product" in the Dovecot Store that provided no-cost access to this repository. Any information in this regard is very much appreciated. Thank you in advance! -Ben

4 3

Directory delivery discombobulation
by mdb＠primelogic.com 10 Jan '16

10 Jan '16

Greetings, On a server running FreeBSD 8.2, I'm configuring Postfix 2.8.0 and Dovecot 1.2.16, using Dovecot for SASL and LDA. For reasons I won't go into, I don't want to upgrade anything on the server to current versions. I'm configuring for maildir with virtuals. Here's the directory structure I want to use: /usr/vmail/domain/username/cur,new,tmp And here's where Dovecot is delivering mail: /usr/vmail/domain/user/Maildir/cur,new,tmp Oddly, the first time I connected with Thunderbird (configured for IMAP), the following directories were created in /usr/vmail/domain/user/, i.e., below Maildir: .INBOX.Drafts .INBOX.Sent .Junk .Trash Thunderbird can see sent mail in .INBOX.Sent, but it can't see any mail in Maildir. Obviously, something is amiss in my configuration. Here's the dovecot -n output: # 1.2.16: /usr/local/etc/dovecot.conf # OS: FreeBSD 8.2-RELEASE i386 ufs protocols: imap pop3 ssl: no disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login verbose_proctitle: yes first_valid_uid: 1000 first_valid_gid: 1000 mail_privileged_group: mail mail_location: maildir:/home/vmail/%d/%n maildir_very_dirty_syncs: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh lda: sendmail_path: /usr/sbin/sendmail auth default: mechanisms: plain login username_format: %Lu passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: static args: uid=1000 gid=1000 home=/home/vmail/%d/%n socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: postfix group: postfix Note that I haven't defined mail_location as "maildir:~/Maildir," yet Dovecot is delivering to the Maildir directory (a directory I don't want). I'm not sure about the path in args: userdb: driver: static args: uid=1000 gid=1000 home=/home/vmail/%d/%n Here's the LDA config for virtuals in Postfix's master.conf: dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/local/libexec/dovecot/dovecot-lda -f ${sender} -d ${recipient} I'm also unsure about the home_mailbox value in Postfix's main.cf. The docs say this: " Specify "Maildir/" for qmail-style delivery (the / is required)." And there was no alternative listed, so that's what I used: home_mailbox = Maildir/ However, does it designate a directory named Maildir? Not sure if they're relevant, but here are some additional config lines from Postfix's main.cf virtual_mailbox_domains = /etc/postfix/vhosts virtual_mailbox_base = /home/vmail/ virtual_mailbox_maps = hash:/etc/postfix/vmaps virtual_minimum_uid = 1000 virtual_uid_maps = static:1000 virtual_gid_maps = static:1000 smtpd_sasl_type = dovecot # Can be an absolute path, or relative to $queue_directory smtpd_sasl_path = /var/spool/postfix/private/auth # and the common settings to enable SASL: smtpd_sasl_auth_enable = yes smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated,reject_unauth_destination Finally, "postconf -a" returns "dovecot," so SASL is copacetic. That's all I can think of that might be relevant. It sure would be nice if Dovecot would forget about the Maildir directory and deliver directly to the username/ directory so Thunderbird could access it, but other than setting the mail_location var to "maildir:/home/vmail/%d/%n," I'm at a loss. Thanks for your help. Doc

1 0

Pigeonhole code repository moved to Github
by Stephan Bosch 09 Jan '16

09 Jan '16

The public repository for Pigeonhole is now located at https://github.com/dovecot/pigeonhole . The repositories at http://hg.rename-it.nl are no longer updated.

1 0

2.2.13 fts-squat corrupt uidlist - wrong indexid
by dilieto＠lineone.net 09 Jan '16

09 Jan '16

I have the same problem described in this old thread: http://dovecot.org/list/dovecot/2012-April/135162.html I have done some debugging, by adding log messages to squat_uidlist_map_header and squat_trie_refresh. I have found that the "wrong indexid" warning is always triggered under the following conditions - uidlist->hdr.indexid != 0 - uidlist->trie->hdr.indexid == 0 - squat_trie_is_file_stale(trie) == 0 In other words it looks like the squat_uidlist_map_header function is called with an uninitialized trie, an initialized header, and a current (not stale) file. Because of the latter, squat_trie_refresh never calls squat_trie_open, the trie stays uninitialized and later triggers the warning. In addition the search results will only include mails added to the mailbox after the warning. By replacing the call to squat_trie_refresh with squat_trie_open in squat_uidlist_map_header, the warning no longer happens. Patch is attached. I am not sure this is the correct way of fixing the problem, but it works reliably.

1 0

Released Pigeonhole v0.4.11 for Dovecot v2.2.21
by Stephan Bosch 08 Jan '16

08 Jan '16

Hello Dovecot users, Here is the final v0.4.11 release of Pigeonhole for Dovecot v2.2.21. Nothing of consequence changed since the RC. Changelog v0.4.11: - Sieve mime extension: Fixed the header :mime :anychild test to work properly outside a foreverypart loop. - Several fixes in message body part handling: - Fixed assert failure occurring when text extraction is attempted on an empty or broken text part. - Fixed assert failure in handling of body parts that are converted to text. - Fixed header unfolding for (mime) headers parsed from any mime part. - Fixed trimming for (mime) headers parsed from any mime part. - Fixed erroneous changes to the message part tree structure performed when re-parsing the message. - LDA Sieve plugin: Fixed logging of actions; sometimes the configured log format was not followed. - LDA Sieve plugin: Fixed bug in error handling of script storage initialization. - Sieve Extprograms plugin: Ignored ENOTCONN error in shutdown(fd, SHUT_WR) call. - Fixed duplication of discard actions in the script result. Each discard was counted as a separate action, which means that action limit would be crossed too early. - Made sure that quota errors never get logged as errors in syslog. - Fixed handling of implicit keep for a partially executed transaction that yielded a temporary failure. - Fixed handling of global errors. If master and user error handler were identical, in some cases the log message could be lost. - Fixed AIX compile issue in message body parser. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.11.ta… http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.11.ta… Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

doveadm search -A tries to create mailboxes
by Bill Shirley 08 Jan '16

08 Jan '16

[0:root@elmo ~]$ rpm -q dovecot dovecot-2.2.18-2.fc22.x86_64 I got a surprise today when I tried the doveadm search function from: http://wiki2.dovecot.org/Plugins/Expire [0:root@elmo ~]$ doveadm search -A mailbox Trash savedbefore 30d doveadm(clamscan): Error: User initialization failed: Namespace '': mkdir(//Maildir) failed: Permission denied (euid=982(clamscan) egid=289(clamscan) missing +w perm: /, dir owned by 0:0 mode=0555) doveadm(clamscan): Error: User init failed doveadm(nm-openconnect): Error: User initialization failed: Namespace '': mkdir(//Maildir) failed: Permission denied (euid=986(nm-openconnect) egid=293(nm-openconnect) missing +w perm: /, dir owned by 0:0 mode=0555) doveadm(nm-openconnect): Error: User init failed doveadm(openvpn): Error: User initialization failed: Namespace '': mkdir(/etc/openvpn/Maildir) failed: Permission denied (euid=987(openvpn) egid=296(openvpn) missing +w perm: /etc/openvpn, dir owned by 0:0 mode=0755) doveadm(openvpn): Error: User init failed .. plus several more I wouldn't think the search function (or any operation) would try to create mailboxes. These are system user ids that don't have or need mailboxes. Is this correct? Bill

3 5

doveadm import - strange warning
by Ralf Hildebrandt 08 Jan '16

08 Jan '16

I'm using the doveadm import command to extract mails from my backup: % doveadm import -u restore(a)backup.invalid mdbox:/home/copymail/mdbox "" \ mailbox INBOX header Delivered-To backup+$SEARCHPATTERN(a)backup.invalid This works like a charm, I'm getting all the mails, and I can access the newly generated mailbox. But when executing the command I'm getting an annoying warning: doveadm(restore(a)backup.invalid): Error: chdir(/root/) failed: Permission denied (euid=1001(copymail) egid=1001(copymail) missing +x perm: /root, dir owned by 0:0 mode=0700) doveadm(restore(a)backup.invalid): Error: chdir(/root) failed: Permission denied I'm using a file based authentication: # cat passwd restore@backup.invalid:{SHA}+/...the.hash...:1001:1001:(gecos):/home/restore:: So why is "restore(a)backup.invalid" being associated with /root? I'm using 2:2.2.18-1~auto+91, but the warning has been around for ages :) -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein

5 7

strange interaction with MacOSX calendar server
by Jim Reid 08 Jan '16

08 Jan '16

I’ve installed and configured Apple’s calendar server. It seems to be working just fine. However it keeps trying to speak to my IMAP server — don’t know why — and the authentication attempts fail every 30 seconds or so. Here’s what’s in the calendar server logs: 2016-01-07 22:42:38+0000 [-] [caldav-1] [IMAP4DownloadProtocol (TLSMemoryBIOProtocol),client] [txdav.caldav.datastore.scheduling.imip.inbound.IMAP4DownloadProtocol#error] IMAP login failed for com.apple.calendarserver 2016-01-07 22:43:08+0000 [-] [caldav-1] [IMAP4DownloadProtocol (TLSMemoryBIOProtocol),client] [txdav.caldav.datastore.scheduling.imip.inbound.IMAP4DownloadProtocol#error] IMAP login failed for com.apple.calendarserver 2016-01-07 22:43:39+0000 [-] [caldav-1] [IMAP4DownloadProtocol (TLSMemoryBIOProtocol),client] [txdav.caldav.datastore.scheduling.imip.inbound.IMAP4DownloadProtocol#error] IMAP login failed for com.apple.calendarserver And in dovecot’s logs I see: Jan 7 22:47:43 hutch dovecot[63067]: imap-login: Disconnected (auth failed, 2 attempts in 4 secs): user=<com.apple.calendarserver>, method=PLAIN, rip=195.54.233.70, lip=195.54.233.70, TLS, session=<wkMAQsYoVADDNulG> Jan 7 22:48:10 hutch dovecot[63067]: auth-worker(65378): Error: pam(com.apple.calendarserver,195.54.233.70): pam_acct_mgmt() failed: permission denied Jan 7 22:48:14 --- last message repeated 1 time --- Jan 7 22:48:14 hutch dovecot[63067]: imap-login: Disconnected (auth failed, 2 attempts in 4 secs): user=<com.apple.calendarserver>, method=PLAIN, rip=195.54.233.70, lip=195.54.233.70, TLS, session=<dSvTQ8YoXQDDNulG> Jan 7 22:48:40 hutch dovecot[63067]: auth-worker(65378): Error: pam(com.apple.calendarserver,195.54.233.70): pam_acct_mgmt() failed: permission denied Jan 7 22:48:44 --- last message repeated 1 time — I tweaked dovecot to use AUTH PLAIN as well as CRAM-MD5. [The MD5 stuff has always worked fine for SMTP and IMAP over TLS.] I think /etc/pam.d/dovecot is OK too: % cat /etc/pam.d/dovecot # # as documented on Dovecot wiki auth required pam_opendirectory.so try_first_pass account required pam_nologin.so account required pam_opendirectory.so password required pam_opendirectory.so Here’s my dovecot.conf: # 2.2.5: dovecot.conf # OS: Darwin 12.5.0 x86_64 auth_mechanisms = plain login cram-md5 base_dir = /var/run/dovecot/ listen = *, [::] mail_debug = yes mail_privileged_group = mail mbox_write_locks = fcntl namespace inbox { hidden = yes inbox = yes list = no location = mbox:~/mail:INBOX=/var/mail/%u prefix = "#mbox/" separator = / type = private } namespace { inbox = no list = yes location = maildir:/var/imap/%u:LAYOUT=fs prefix = separator = / type = private } passdb { driver = pam args = failure_show_msg=yes } passdb { args = /usr/local/etc/dovecot-md5 driver = passwd-file } protocols = imap service auth { executable = /usr/local/libexec/dovecot/auth unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = root } service imap-login { client_limit = 32 executable = /usr/local/libexec/dovecot/imap-login inet_listener imap { port = 0 } process_limit = 128 process_min_avail = 3 service_count = 1 vsz_limit = 64 M } service imap { executable = /usr/local/libexec/dovecot/imap process_limit = 32 } service pop3-login { client_limit = 32 process_limit = 128 process_min_avail = 3 service_count = 1 vsz_limit = 64 M } service pop3 { process_limit = 32 } ssl_cert = </usr/local/etc/ssl/certs/dovecot.pem ssl_cipher_list = ALL:!LOW:!SSLv2 ssl_key = </usr/local/etc/ssl/private/dovecot.pem syslog_facility = local4 userdb { driver = passwd } protocol imap { mail_max_userip_connections = 10 mail_plugin_dir = /usr/local/lib/dovecot/imap } protocol lda { postmaster_address = postmaster(a)example.com } Can someone please explain what’s going on and how to fix/troubleshoot it? Thanks. The endless error messages in the log don’t seem to be causing any problems to either the mail setup or the calendaer server. Famous last words… However they are a bit annoying and probably point to an underlying problem or misconfiguration that really should be fixed. By the way, the password used by the calendar server is for my MacOSX login (which should be getting picked up via PAM, right?) while a different one is used for the SMTP/IMAP MD5 challenge-response. I hope someone can clear up my confusion.

1 0

Mapping of INBOX.INBOX breaks imapc_list_prefix=INBOX?
by Peer Heinlein 07 Jan '16

07 Jan '16

We're running a huge imapc-Migration from an old Courier-IMAP to Dovecot. Courier always uses "INBOX."-prefix for his folders, so we set namespace inbox { [...] separator = . prefix = INBOX. [...] } on our new Dovecot 2.2.20 system. And also we added: imapc_list_prefix=INBOX to avoid the dublication of the INBOX prefix. At the end, doveadm/dsync/imapc see "INBOX.Virus", adds his Prefix, has "INBOX.INBOX.Virus", deletes his imapc_list_prefix and the end we have "INBOX.Virus" again which is identical to the source folder from Courier. Works perfect BUT: It looks like there is a "hidden feature" in Dovecot that always maps "INBOX.INBOX" back to "INBOX". For me that looks like a workaround for broken mailclients to fix some of the common problems after changing the namespace prefix. I never heard about that "hidden feature", but even if I don't (!) have INBOX.INBOX: root@imap01:~/MIGRATION # doveadm mailbox list -u test INBOX INBOX.Virus INBOX.Spam INBOX.Trash I'm always able to access INBOX.INBOX which is identical to INBOX: root@imap01:~/MIGRATION # doveadm fetch -u test uid mailbox INBOX.INBOX uid: 1 Looks like there is such a magic-mapping and looks like this "hard coded mapping" (?) breaks the imapc_list_prefix-magic. If the user has on the SOURCE-server (Courier): Source-Server: INBOX (5 messages) INBOX.Inbox (3 messages) and I do migrate that user using doveadm/dsync/imapc, this user has on the DESTINATION-server (Dovecot) Destination-server: INBOX (5 messages) INBOX.Inbox (5 messages from "real INBOX") and his 3 messages from INBOX.Inbox are lost. I can NOT find any errors in the debug/error-output of doveadm/dsync/imapc. From the view of doveadm everything worked perfect as you can see in the attached logfile. Or am I completly wrong?! Peer -- Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-42 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

2 4

doveadm proxy kick shows always "0 connections kicked"?!
by Peer Heinlein 06 Jan '16

06 Jan '16

On Dovecot 2.2.20: There *IS* a user connected: root@mailproxy02:~ # doveadm proxy list | grep testuser username proto src ip dest ip port testuser imap xx.xx.xx.xx yy.yy.yy.yy 143 But if I kick him there are always "0 connections kicked": root@mailproxy02:~ # doveadm proxy kick testuser 0 connections kicked ...even if the user's gone after I kicked him. Peer -- Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-42 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

1 0

allow_nets=local in passdb gets "auth: Panic"
by SATOH Fumiyasu 05 Jan '16

05 Jan '16

Hi, I have the following configuration in my dovecot.conf for Dovecot 2.2.21: passdb { driver = ldap args = /etc/dovecot/dovecot-ldap.conf.ext default_fields = allow_nets=local,127.0.0.1,10.255.1.0/24 } This triggers "auth: Panic" on POP3/IMAP logins as the below: Dec 22 14:57:39 localhost dovecot: auth: ldap(u0000,::1,<oiF8SHYngqsAAAAAAAAAAAAAAAAAAAAB>): allow_nets: Invalid network 'local' Dec 22 14:57:39 localhost dovecot: auth: Panic: file net.c: line 1137 (net_is_in_network): assertion failed: (IPADDR_IS_V6(ip) == IPADDR_IS_V6(net_ip)) `doveadm auth test <username> <password>` is no problem as expected. What's wrong? Regards, -- -- Name: SATOH Fumiyasu @ OSS Technology Corp. (fumiyas @ osstech co jp) -- Business Home: http://www.OSSTech.co.jp/ -- GitHub Home: https://GitHub.com/fumiyas/ -- PGP Fingerprint: BBE1 A1C9 525A 292E 6729 CDEC ADC2 9DCA 5E1C CBCA

2 3

Replication - user permissions
by Petter Gunnerud 05 Jan '16

05 Jan '16

When setting up dsync for replication, what should the user permissions be for sync over ssh? I'm running virtual users only. Postfix and Dovecot services run as mail:mail. All the maildir folders are owned by mail:mail and permissions are 700. User mail is not allowed login. So whats the best practice in respect to security to allow for dsync over ssh? So of the options I consider: 1) change postfix/dovecot settings so that maildirs are created with 770 permissions, then create a user dsync:mail that is allowed for ssh login. 2) permit user mail to login using ssh 3)go with tcp sync rather than ssh Other suggestions? PG

1 0

Replication - hostname issue
by Petter Gunnerud 05 Jan '16

05 Jan '16

I have postfix/dovecot setup on a virtual gentoo server. It's been in service for almost two years without any issues. Now I want to set up a spare server to replicate mails from the one running. I copied the vm files to the second host server, changed the ip, hostname and hosts file for the copy and followed the dovecot replication doc. The last point in the doc tells to rundovecot --hostdomainto make sure the hostnames differ... To my surprise the command returned "localhost" on both servers. How do I set the hostname for dovecot service?(The hostname command returns the servers hostnames.)Will a change in dovecot hostname make all clients redownload all their mail? A second question. When configuring dovecot replication. Should the settings be done on the master server or the stand by server, or both? (Doc doesn't say anything regarding this) PG

2 2

2.2.21 imap core dump after enabling autoexpunge
by Tomi Vainio 04 Jan '16

04 Jan '16

Hi, I've enabled autoexpunge for Trash and Junk. Now imap process core dumps occasionally. Tomppa > program terminated by signal SEGV (no mapping at the fault address) > 0xff0dc2e0: o_stream_get_buffer_used_size : ld [%o0 + 20], %o0 > Current function is notify_ok (optimized) > 13 if (o_stream_get_buffer_used_size(client->output) != 0) > (dbx) where > [1] o_stream_get_buffer_used_size(0x0, 0x83ee8, 0x83ee8, 0x5f520, 0xfffe681c, 0xff13a978), at 0xff0dc2e0 > =>[2] notify_ok(mailbox = 0x90188, text = 0x83ee8 "Stale mailbox lock file detected, will override in 0 seconds", context = 0xa3588) (optimized), at 0x5f524 (line ~13) in "mail-storage-callbacks.c" > [3] dotlock_callback(0x0, 0x1, 0x90188, 0x567a61fe, 0xff1352a0, 0x2), at 0xff1ff478 > [4] dotlock_create(0xcc3d8, 0x2dc6c0, 0x1, 0x0, 0x0, 0x567a61fe), at 0xff0b0e68 > [5] file_dotlock_create_real(0xcc3d8, 0x1, 0x541c, 0x4, 0xff1352a0, 0xff13a6bc), at 0xff0b1104 > [6] file_dotlock_create(0xbf674, 0x8f990, 0x1, 0xbf690, 0x5, 0xcc3d8), at 0xff0b126c > [7] maildir_uidlist_lock_timeout(0xbf648, 0x1, 0x1, 0x1, 0x3f, 0x26c00), at 0xff1ff0ec > [8] maildir_uidlist_sync_lock(0xbf648, 0x8, 0xffbff59f, 0x1, 0x1, 0xf19c8), at 0xff2035bc > [9] maildir_uidlist_sync_init(0xbf648, 0x8, 0x83d20, 0x1, 0x44, 0xff2f502c), at 0xff203680 > [10] maildir_sync_context(0x83d08, 0x1, 0x0, 0xffbff707, 0x83d20, 0x83d08), at 0xff1fe290 > [11] maildir_sync_run(0x90188, 0x44, 0x0, 0x0, 0x0, 0x90420), at 0xff1fe74c > [12] maildir_storage_sync_init(0x90188, 0x44, 0x541c, 0x0, 0x80, 0xff2f502c), at 0xff1feaa0 > [13] mailbox_sync(0x90188, 0x44, 0x0, 0x4, 0x44, 0x90388), at 0xff1b91cc > [14] index_mailbox_get_metadata(0x90188, 0x40, 0xffbff910, 0x0, 0xff2f502c, 0x0), at 0xff273858 > [15] maildir_mailbox_get_metadata(0x90188, 0x40, 0xffbff910, 0xfffffff8, 0x0, 0xff2f502c), at 0xff1f9e4c > [16] mailbox_get_metadata(0x90188, 0x40, 0xffbff910, 0x0, 0xff2f502c, 0x2), at 0xff1b8ecc > [17] mailbox_autoexpunge(0x90188, 0x5651837e, 0xa1e28, 0xa2630, 0x0, 0x0), at 0xff1a6fcc > [18] mail_user_autoexpunge(0x9eaf4, 0x8, 0x5651837e, 0xff2f502c, 0x9c290, 0xffbff9ac), at 0xff1a72e8 > [19] mail_user_unref(0x9de20, 0xfffd135c, 0xff2f502c, 0x1, 0xff2c6388, 0xa35d4), at 0xff1c328c > [20] client_default_destroy(client = 0xa3588, reason = <value unavailable>) (optimized), at 0x41c8c (line ~390) in "imap-client.c" > [21] io_loop_call_io(0x9ca18, 0xfffdbba8, 0x0, 0xff1352a0, 0x8c6b8, 0x24400), at 0xff0c8fd4 > [22] io_loop_handler_run_internal(0x8c6b8, 0x1, 0x0, 0x8d1b8, 0x1, 0x9ca18), at 0xff0cadd8 > [23] io_loop_run(0x8c6b8, 0x1, 0xc0, 0xff13b26c, 0xff1352a0, 0x8d1b8), at 0xff0c90fc > [24] master_service_run(0x8c608, 0x60fe0, 0x1, 0x80, 0x27c00, 0x2), at 0xff0236c8 > [25] main(argc = <value unavailable>, argv = 0x1) (optimized), at 0x619c4 (line ~442) in "main.c" > (dbx) > # 2.2.21 (5345f22): /usr/local/etc/dovecot/dovecot.conf > # OS: SunOS 5.10 sun4u > base_dir = /var/run/dovecot/ > dsync_remote_cmd = ssh -l%{login} %{host} /usr/local/bin/doveadm dsync-server -u%u -U > first_valid_uid = 100 > last_valid_uid = 199 > mail_location = maildir:~/Maildir > mail_plugins = fts fts_solr > namespace inbox { > inbox = yes > location = > mailbox "Deleted Messages" { > special_use = \Trash > } > mailbox Drafts { > special_use = \Drafts > } > mailbox Junk { > auto = create > autoexpunge = 31 days > special_use = \Junk > } > mailbox Sent { > auto = subscribe > special_use = \Sent > } > mailbox "Sent Messages" { > special_use = \Sent > } > mailbox Spam { > special_use = \Junk > } > mailbox Trash { > autoexpunge = 31 days > special_use = \Trash > } > prefix = > } > passdb { > driver = pam > } > plugin { > fts = solr > fts_autoindex = yes > fts_solr = url=http://127.0.0.1:8983/solr/ break-imap-search > } > protocols = imap > service auth { > user = root > } > service imap-login { > inet_listener imap { > address = localhost > port = 143 > } > inet_listener imaps { > address = * > port = 993 > } > } > ssl_cert = </etc/mail/certs/server-all.crt > ssl_cipher_list = AES128+EECDH:AES128+EDH > ssl_dh_parameters_length = 2048 > ssl_key = </etc/mail/certs/server.key > ssl_prefer_server_ciphers = yes > ssl_protocols = !SSLv2 !SSLv3 > userdb { > driver = passwd > }

2 2

Re: segfault in dict_transaction_rollback() on doveadm quota recalc -u
by Lazy 04 Jan '16

04 Jan '16

Bump > Hi, > > We have a dovecot cluster with nfs storage, 2 directors and 3 > imap/pop3/lmtp backends. > > Redis is used as a dict backend with a dict proxy. > > dict { > quota = redis:host=127.0.0.1:prefix=user/ > } > > plugin { > > quota = dict:User quota::proxy::quota > > } > > Redis server is behind haproxy working in tcp mode. > > doveadm quota recalc -u user always couses dict process segfault (called > from imap backend or director host), otherwise quota is working correctly. > > > #0 dict_transaction_rollback (_ctx=_ctx@entry=0xea5fd0) at dict.c:194 > 194 ctx->dict->v.transaction_rollback(ctx); > (gdb) bt > #0 dict_transaction_rollback (_ctx=_ctx@entry=0xea5fd0) at dict.c:194 > #1 0x0000000000404d4d in dict_connection_destroy (conn=conn@entry=0xea5af0) > at dict-connection.c:166 > #2 0x0000000000405098 in dict_connection_input (conn=<optimized out>) at > dict-connection.c:127 > #3 dict_connection_input (conn=0xea5af0) at dict-connection.c:96 > #4 0x00007fbf886fe4fb in io_loop_call_io (io=0xeab550) at ioloop.c:501 > #5 0x00007fbf886ff54b in io_loop_handler_run_internal (ioloop=ioloop@entry=0xe9f730) > at ioloop-epoll.c:220 > #6 0x00007fbf886fe589 in io_loop_handler_run (ioloop=ioloop@entry=0xe9f730) > at ioloop.c:548 > #7 0x00007fbf886fe608 in io_loop_run (ioloop=0xe9f730) at ioloop.c:525 > #8 0x00007fbf8869fbc3 in master_service_run (service=0xe9f5c0, > callback=callback@entry=0x4059c0 <client_connected>) at > master-service.c:581 > #9 0x0000000000404ad8 in main (argc=1, argv=0xe9f390) at main.c:105 > (gdb) p ctx > $1 = (struct dict_transaction_context *) 0x0 > > > dovecot 2.2.18, redis server 2.8 > > > > Regards Michal >

2 2

[BUG] 2.2.21 Panic: file imap-client.c: line 841 (client_check_command_hangs): assertion failed: (!have_wait_unfinished || unfinished_count > 0)
by Florian Pritz 04 Jan '16

04 Jan '16

Hi, I'm seeing the following in my logs. Twice so far, no idea what caused it. I do however have the core dump if that is of any use. > Jan 4 11:14:11 karif dovecot[20876]: imap(username): Panic: file imap-client.c: line 841 (client_check_command_hangs): assertion failed: (!have_wait_unfinished || unfinished_count > 0) > Jan 4 11:14:11 karif dovecot[20876]: imap(username): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xa64ea) [0x7f6f99fa64ea] -> /usr/lib/dovecot/libdovecot.so.0(+0xa7a18) [0x7f6f99fa7a18] -> /usr/lib/dovecot/libdovecot.so.0(i_ > fatal+0) [0x7f6f99fa686d] -> dovecot/imap() [0x41dde6] -> dovecot/imap(client_continue_pending_input+0xd6) [0x41df50] -> dovecot/imap() [0x4122a9] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0xcd) [0x7f6f99fc3b01] -> /usr/lib/dovec > ot/libdovecot.so.0(io_loop_handler_run_internal+0x209) [0x7f6f99fc606e] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x24) [0x7f6f99fc3caa] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0xaf) [0x7f6f99fc3bf6] -> /usr/lib/dovec > ot/libdovecot.so.0(master_service_run+0x2e) [0x7f6f99f317af] -> dovecot/imap(main+0x2da) [0x430da2] -> /usr/lib/libc.so.6(__libc_start_main+0xf0) [0x7f6f99b7c610] -> dovecot/imap(_start+0x29) [0x40c639] > Jan 4 11:14:11 karif dovecot[20876]: imap(username): Fatal: master: service(imap): child 19463 killed with signal 6 (core dumped) In case it is easier to read, here's a gdb backtrace: > #0 0x00007f6f99b8f5f8 in raise () from /usr/lib/libc.so.6 > #1 0x00007f6f99b90a7a in abort () from /usr/lib/libc.so.6 > #2 0x00007f6f99fa6539 in default_fatal_finish (type=LOG_TYPE_PANIC, status=0) at failures.c:201 > #3 0x00007f6f99fa7a18 in i_internal_fatal_handler (ctx=0x7ffe660d4700, format=0x438a60 "file %s: line %d (%s): assertion failed: (%s)", args=0x7ffe660d4720) at failures.c:670 > #4 0x00007f6f99fa686d in i_panic (format=0x438a60 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:275 > #5 0x000000000041dde6 in client_check_command_hangs (client=0x2363450) at imap-client.c:841 > #6 0x000000000041df50 in client_continue_pending_input (client=0x2363450) at imap-client.c:884 > #7 0x00000000004122a9 in idle_client_input (ctx=0x23642a8) at cmd-idle.c:111 > #8 0x00007f6f99fc3b01 in io_loop_call_io (io=0x2374600) at ioloop.c:559 > #9 0x00007f6f99fc606e in io_loop_handler_run_internal (ioloop=0x232c740) at ioloop-epoll.c:220 > #10 0x00007f6f99fc3caa in io_loop_handler_run (ioloop=0x232c740) at ioloop.c:607 > #11 0x00007f6f99fc3bf6 in io_loop_run (ioloop=0x232c740) at ioloop.c:583 > #12 0x00007f6f99f317af in master_service_run (service=0x232c5e0, callback=0x430a35 <client_connected>) at master-service.c:640 > #13 0x0000000000430da2 in main (argc=1, argv=0x232c390) at main.c:442 Florian

3 3

postmaster domain
by Timothy Murphy 04 Jan '16

04 Jan '16

I recently upgraded a remote server to CentOS-7.2, after which email stopped coming through. I suspect that this was probably due to the fact that I had started a version of dovecot installed some time ago. I found messages in /var/log/maillog like Jan 4 12:56:56 alfred postfix/lmtp[7612]: 20A662202B4: to=<root(a)gayleard.eu>, relay=alfred.gayleard.eu[private/dovecot-lmtp], delay=34272, delays=34272/0.16/0.01/0.05, dsn=4.3.0, status=deferred (host alfred.gayleard.eu[private/dovecot-lmtp] said: 451 4.3.0 <root(a)gayleard.eu> Invalid user settings. Refer to server log for more information. (in reply to RCPT TO command)) Googling for this, I found the suggestion that one should insert the following postmaster_address line in /etc/dovecot/conf.d/20-lmtp protocol lmtp { postmaster_address = postmaster(a)alfred.eu # Space separated list of plugins to load (default is global ail_plugins). mail_plugins = $mail_plugins sieve } (alfred.eu being the server's domain). This seems to have solved the problem, after re-starting dovecot. I'm wondering if this was an issue that arose some time ago, and if so whether my solution was the recommended one? -- Timothy Murphy gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin

1 0

Re: Howto get information about quota used
by Макаров Денис 04 Jan '16

04 Jan '16

I tried this for correct user: sudo doveadm quota get -u user Quota name Type Value Limit % User STORAGE 0 614400 0 User MESSAGE 0 - 0 Ok, limit is correct. But why value and % = 0? Via Thunderbird I see 52%. >> Hello guys! >> >> I have Dovecot server (version: 2.2.9) with quota and imap_quota plugins. >> >> I wanna know how to get information about quota used of current email. >> >> I can do this with IMAP client like Thunderbird, but how I can do it >> on server? > Try this: > > # doveadm quota get -A > ... > > p@rick > -- Best regards, *Makarov Denis* *email*: makarovdenis11(a)gmail.com <mailto:makarovdenis11@gmail.com>

1 1

How to debug lmtpd?
by kjonca＠o2.pl 04 Jan '16

04 Jan '16

1. I have dovecot installation with lmtp 2. there are some sieve filter which call mailpost to put mails in my news server. 3. SOME mails are not mailposted :( I do not know why. Moreover these mails filtered by dovecot-lda ARE mailposted whit the same sieve filter. 4. How can I debug lmtp and it's descendant processes? strace -ff only? KJ -- http://wolnelektury.pl/wesprzyj/teraz/ Boys, you have ALL been selected to LEAVE th' PLANET in 15 minutes!!

2 1

Double folders?
by Frank W 04 Jan '16

04 Jan '16

Hi, I upgraded my dovecot install from 2.0.19 to 2.2.19. I haved update the configuration, accordingly, but I when I open roundcube, I see multiple folders like sent, trash, facebook, etc... I not sure if am missing something or not. Here is my configure: [root@mgmt ~]# cat dovecot_config.txt # 2.2.19: /etc/dovecot/dovecot.conf # OS: Linux 3.4.4 armv5tel Gentoo Base System release 2.1 ext3 auth_mechanisms = plain login disable_plaintext_auth = no first_valid_gid = 207 first_valid_uid = 207 last_valid_gid = 207 last_valid_uid = 207 listen = *, [::] mail_gid = 207 mail_location = maildir:/var/vmail/%u/Maildir/:INDEX=/var/vmail/%u/indexes mail_plugins = quota mail_uid = 207 namespace { inbox = yes location = prefix = INBOX. separator = . name = } namespace { location = mailbox { special_use = \Drafts name = Drafts } mailbox { special_use = \Junk name = Junk } mailbox { special_use = \Sent name = Sent } mailbox { special_use = \Trash name = Trash } prefix = name = inbox } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocols = imap pop3 service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { user = $default_internal_user name = auth-worker } service { unix_listener { group = postfix mode = 0666 user = postfix path = /var/spool/postfix/private/auth } unix_listener { group = mail mode = 0666 user = mail path = auth-userdb } name = auth } service config { name = config } service dict-async { name = dict-async } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap-hibernate { name = imap-hibernate } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service imap-master { 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 replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } ssl_cert = </etc/postfix/ssl/mail.xxxxxx.net.crt ssl_cipher_list = ALL:!LOW:!SSLv2 ssl_key = </etc/postfix/ssl/mail.xxxxxxx.net.key userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict-async { name = dict-async } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap-hibernate { name = imap-hibernate } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service imap-master { 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 replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } protocol lda { service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict-async { name = dict-async } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap-hibernate { name = imap-hibernate } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service imap-master { 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 replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } protocol imap { mail_plugins = quota imap_quota service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict-async { name = dict-async } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap-hibernate { name = imap-hibernate } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service imap-master { 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 replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } protocol pop3 { service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict-async { name = dict-async } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap-hibernate { name = imap-hibernate } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service imap-master { 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 replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } }

2 1

Released Pigeonhole v0.4.11.rc1 for Dovecot v2.2.21
by Stephan Bosch 04 Jan '16

04 Jan '16

Hello Dovecot users, First, a happy new year to you all! :) In the last few weeks I got quite a few bug reports. I also found a few things myself. Some of the bugs are quite annoying, so a new release is necessary. First, I release RC1. If all is well, I'll release the definitive Pigeonhole v0.4.11 within the next few days. Changelog v0.4.11: - Sieve mime extension: Fixed the header :mime :anychild test to work properly outside a foreverypart loop. - Several fixes in message body part handling: - Fixed assert failure occurring when text extraction is attempted on an empty or broken text part. - Fixed assert failure in handling of body parts that are converted to text. - Fixed header unfolding for (mime) headers parsed from any mime part. - Fixed trimming for (mime) headers parsed from any mime part. - Fixed erroneous changes to the message part tree structure performed when re-parsing the message. - LDA Sieve plugin: Fixed logging of actions; sometimes the configured log format was not followed. - LDA Sieve plugin: Fixed bug in error handling of script storage initialization. - Sieve Extprograms plugin: Ignored ENOTCONN error in shutdown(fd, SHUT_WR) call. - Fixed duplication of discard actions in the script result. Each discard was counted as a separate action, which means that action limit would be crossed too early. - Made sure that quota errors never get logged as errors in syslog. - Fixed handling of implicit keep for a partially executed transaction that yielded a temporary failure. - Fixed handling of global errors. If master and user error handler were identical, in some cases the log message could be lost. - Fixed AIX compile issue in message body parser. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/rc/dovecot-2.2-pigeonhole-0.4.11… http://pigeonhole.dovecot.org/releases/2.2/rc/dovecot-2.2-pigeonhole-0.4.11… Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this release candidate and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

Howto get information about quota used
by Макаров Денис 03 Jan '16

03 Jan '16

Hello guys! I have Dovecot server (version: 2.2.9) with quota and imap_quota plugins. I wanna know how to get information about quota used of current email. I can do this with IMAP client like Thunderbird, but how I can do it on server? doveconf -n | grep quota mail_plugins = quota, antispam quota = maildir:User quota_exceeded_message = Message quota_rule = *:storage=100M quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u quota_warning3 = -storage=100%% quota-warning below %u service quota-warning { executable = /usr/local/bin/quota-warning.sh mail_plugins = quota imap_quota mail_plugins = quota sieve For each mailboxes I use quota limits from MySQL. -- С уважением, *Макаров Денис* *почта*: makarovdenis11(a)gmail.com <mailto:makarovdenis11@gmail.com> Best regards, *Makarov Denis* *email*: makarovdenis11(a)gmail.com <mailto:makarovdenis11@gmail.com>

2 1

SASL binds
by Brendan Kearney 01 Jan '16

01 Jan '16

i am looking to get SASL binds working in Dovecot for userdb lookups, and i am not sure what i might be doing wrong. Dovecot version - 2.2.19 running on Fedora 22. MIT Kerberos and OpenLDAP are being used. my LDAP configs: uris = ldap://server1.bpk2.com ldap://server2.bpk2.com sasl_bind = yes sasl_mech = gssapi sasl_realm = BPK2.COM sasl_authz_id = imap/imap.bpk2.com(a)BPK2.COM base = dc=bpk2,dc=com the above results in the below error logs: Jan 01 13:56:58 mail auth[16747]: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (No Kerberos credentials available) Jan 01 13:56:58 mail dovecot[16722]: auth-worker(16747): Error: LDAP: binding failed (dn (none)): Local error, SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (No Kerberos credentials available) i am assuming the keytab, /etc/dovecot/dovecot.keytab would be used to bind to the directory, but i am not sure. the auth_krb5_keytab directive is set with the absolute path and keytab name. is there something i am missing, such as a /etc/sasl2/dovecot.conf file? in the directory, i am mapping the Kerberos ID to LDAP user object as such: uid=imap\/(.*).bpk2.com,cn=bpk2.com,cn=gssapi,cn=auth uid=mda,ou=processUsers,ou=Users,dc=bpk2,dc=com if i change the sasl_authz_id to uid=mda,ou=processUsers,ou=Users,dc=bpk2,dc=com, and restart dovecot, i still get the same error. can anyone shed light on where i am going wrong? thanks in advance, brendan

1 0