- dovecot - dovecot.org

Re: Released Pigeonhole v0.4.11 for Dovecot v2.2.21
by Juan C. Blanco 12 Jan '16

12 Jan '16

Hello Stephan. > 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… http://pigeonhole.dovecot.org/ seems to be down, right? Regards Juan C. > > 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 at rename-it.nl > > > -- +-------------------------------------------------------------------+ | Juan C. Blanco | | | | Centro de Calculo | | | E.T.S. Ingenieros Informáticos | E-mail: jcblanco(a)fi.upm.es | | Universidad Politécnica de Madrid | | | Campus de Montegancedo | | | Boadilla del Monte | Tel.: (+34) 91 336 7466 | | 28660 MADRID (Spain) | Fax : (+34) 91 336 6913 | +-------------------------------------------------------------------+

2 2

No SSL on some users
by Jonas Björklund 12 Jan '16

12 Jan '16

Hello, Is there a way to allow only certain users on IMAP/POP3 without SSL? Im running MySQL backend. /Jonas

2 1

TLS SNI Client Support
by absolutely_free＠libero.it 12 Jan '16

12 Jan '16

Hi,according to this page: http://wiki2.dovecot.org/SSL/SNIClientSupport (last change 2013) I would like to know if this limitation is still valid. # dovecot --version2.0.9 I am trying to configure Android default email client and I am not able at all to use TLS. With other clients I have no problem, so I think my server configuration is ok. Thank you

1 0

Missing Documentation
by Andre Helwig 12 Jan '16

12 Jan '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, could someone apply the folowing line to the wiki page at http://wiki2.dovecot.org/Tools/Doveadm/Sync Because it is write protected. - -R Reverse backup direction, so mails in location2 are backed up to default mail location. - -- Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-0 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJWlN6oAAoJEAoTNwRDnEhRfyAH/RZmdQO4jevf8d6Y/CjW/Lkc H7Ny1tB4W+dZnY/Lap+VY4RER/QWfgVgPDrWm0FG1r73FBpPqxafVlMeh2TM9Daf ARSlBQltDl4GvUu3w+ANByUm/eHe3+3+/HavgJApCpJwaxDfgGBpJoEkTsNQSs6d t2NZYY1k/MJV+5Vk7YWatUnHNdK3H6DPz03e+GLQkh+Np0HScy95ispU1c6rirH0 ROb/4X/HPL2Isut3KHcgJ+f5SkHDueNCgM9kq/O72wq8c1GxAIn/Mwk0wQhdVsw/ VoCrsw/IcJ3k6cTeys8rYmpmBMu4LaNfMHoRXTB0X98KmpLHS99WwJ1fXI2Oegw= =flsG -----END PGP SIGNATURE-----

1 0

autoexpunge problems
by Olaf Hopp 12 Jan '16

12 Jan '16

Hello, I tried to use the new autoexpunge for my Trash folders I had in 15-mailboxes.conf mailbox Trash { special_use = \Trash auto = subscribe } (dovecot -n of the original config is below) and added just the line autoexpunge = 1h Just a short period on my test system. But it failed. In the log I see Dec 18 10:54:07 irams2 dovecot: imap(ms2test): Error: Failed to autoexpunge mailbox 'Trash': Invalid mailbox name 'Trash': Missing namespace prefix 'INBOX.' But in 10-mail.conf I have namespace inbox { prefix = INBOX. separator = . inbox = yes } So I changed the line "mailbox Trash" to "mailbox INBOX.Trash". I now have mailbox INBOX.Trash { special_use = \Trash auto = subscribe autoexpunge = 1h } Now it seems to work (Trash is emptied, log file is fine) but in the mail client I see two Trash folders. Once the normal one below INBOX and another one also called Trash which is under a new created folder named INBOX below the original INBOX Thus I have INBOX INBOX.Trash INBOX.INBOX.Trash autoexpunge seems to work, but this is not what I like to offer to my users. Any glues ? Olaf # 2.2.21 (5345f22): /opt/dovecot/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.10 (d61ff8a5af9e+) doveconf: Warning: service auth { client_limit=2000 } is lower than required under max. load (23192) doveconf: Warning: service anvil { client_limit=2000 } is lower than required under max. load (17195) # OS: Linux 2.6.32-573.12.1.el6.x86_64 x86_64 CentOS release 6.7 (Final) auth_failure_delay = 3 secs auth_master_user_separator = * auth_mechanisms = plain login auth_username_format = %Ln auth_verbose = yes auth_worker_max_count = 60 default_client_limit = 2000 default_process_limit = 3000 mail_location = maildir:~/Maildir managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } mailbox spambox { auto = create special_use = \Junk } prefix = INBOX. separator = . } passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes } passdb { args = dovecot driver = pam } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = /etc/dovecot/sieve-master sieve_max_redirects = 20 } protocols = imap pop3 lmtp sieve sieve quota_full_tempfail = yes service imap-login { process_limit = 8192 process_min_avail = 16 service_count = 0 } service imap { process_limit = 8192 } service lmtp { executable = lmtp -L } service managesieve-login { inet_listener sieve { port = 4190 } } service pop3 { process_limit = 8192 } ssl = required ssl_ca = </etc/pki/tls/certs/chain.pem ssl_cert = </etc/pki/tls/certs/imap.pem ssl_key = </etc/pki/tls/private/imap.key ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv2 !SSLv3 syslog_facility = local3 userdb { driver = passwd } verbose_proctitle = yes protocol lmtp { mail_plugins = " sieve" } protocol imap { mail_max_userip_connections = 100 ssl_cert = </etc/pki/tls/certs/imap.pem ssl_key = </etc/pki/tls/private/imap.key } protocol pop3 { ssl_cert = </etc/pki/tls/certs/pop.pem ssl_key = </etc/pki/tls/private/pop.key } -- Karlsruher Institut für Technologie (KIT) ATIS - Abt. Technische Infrastruktur, Fakultät für Informatik Dipl.-Geophys. Olaf Hopp - Leitung IT-Dienste - Am Fasanengarten 5, Gebäude 50.34, Raum 009 76131 Karlsruhe Telefon: +49 721 608-43973 Fax: +49 721 608-46699 E-Mail: Olaf.Hopp(a)kit.edu atis.informatik.kit.edu www.kit.edu KIT – Die Forschungsuniversität in der Helmholtz-Gemeinschaft Das KIT ist seit 2010 als familiengerechte Hochschule zertifiziert.

2 2

Problems with doveadm backup in a dovecot director environment
by Tobi 12 Jan '16

12 Jan '16

Hi list I have configured my dovecot(s) in a frontend-backend setup using the director feature of dovecot. Works like charm, but I'm currently unable to use doveadm backup to "sync" the mailbox to a dovecot system which is not within director_mail_servers settings Before I added the director feature I could fire a simple doveadm backup -u myuser(a)mydomain.tld tcps:otherserver.mydomain.tld:2424 After activating the director the command above fails as the connection is always tried to be established to one of the servers specified in director_mail_servers. Is it possible to use doveadm backup towards a server which is not in director_mail_servers? I tried with the -o option of doveadm to override several settings like host or director_mail_servers but no success: the command still tries to connect to an ip from director_mail_servers and not to the destination given as parameter to the command. Is there anyway to achieve that? Thanks a lot for any help tobi

1 1

client setting "move to trash" in shared mailboxes
by Steffen Kaiser 12 Jan '16

12 Jan '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, does somebody run clients with "move to trash" on delete in conjunction with shared mailboxes successfully? When one tries to delete a mailbox in the shared namespace, Dovecot responds with "Can't rename mailboxes across specified storages" OK, the failure stems from the fact that the client (Thunderbird) tries to rename the mailbox into "Trash.mailbox" with the user's private namespace. Does somebody know of an AddOn to have Thunderbird move mailboxes into the shared user's Trash, for example? Does somebody uses "mark as deleted", but use a virtual folder as Trashbin? What option would I have, if the users expect a "trashbin" of some sort? - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBVpTAJHz1H7kL/d9rAQI3twgAsmZdUdYzwQ200j2ILE2XhG3Iy7oFSWd4 YrmOdw09Fr8JtrQIcsbu8BZyyBOse9CLNICQFkmfsSBEXSFX1v5IGfH98RcvhgaM pQwdY1SMctkI4nJHWkJFjC+SCQlDZmV6MVZD7pv+7VDjvvvh/jr0b/uQunYvPLle BEbz1hSssY8bFmWhZxddydzsYgQfFIHUR2VsINd/YHPZlUjJQUqkPwbmDZ4XVN+P WHXYaR4uhrn5arpibk0x5PG/9wlnQvMkStN/kZNBS4jfsKLz6RTQhKgeNmKXyoZD mjUK5r57GkU0MdrRNqQqbgOIrU9V0h1oBH7PFjVoaddw0pYECPlbuw== =hwNa -----END PGP SIGNATURE-----

1 0

password schemes when crypt() has no DES
by Stuart Henderson 12 Jan '16

12 Jan '16

https://github.com/dovecot/core/commit/54a1b3574acab5f778843f7f1e04d2d26d61… fixed a 'doveadm pw' crash "when trying to use CRYPT scheme when crypt() doesn't support DES" by testing to see if crypt would generate a DES password and, if not, disabling the scheme. I'm using Dovecot on OpenBSD with bcrypt passwords stored in LDAP as "{CRYPT}$2b$...". OpenLDAP is built with --enable-crypt which takes the same approach as Dovecot of just passing to crypt(), so before the above commit, both programs were able to authenticate. (Changing the scheme value stored in the ldap passdb to BLF-CRYPT would fix Dovecot but break things for other programs including OpenLDAP itself). For now I went with a dirty patch to get things working again, does anyone have an idea for a nicer fix? Thanks. --- src/auth/password-scheme-crypt.c.orig Fri Jan 8 01:04:13 2016 +++ src/auth/password-scheme-crypt.c Fri Jan 8 01:23:35 2016 @@ -111,7 +111,12 @@ static const struct { const char *salt; const char *expected; } sample[] = { +#ifdef __OpenBSD__ + { "08/15!test~4711", "$2a$04$0123456789abcdefABCDEF", + "$2a$04$0123456789abcdefABCDE.N.drYX5yIAL1LkTaaZotW3yI0hQhZru" }, +#else { "08/15!test~4711", "JB", "JBOZ0DgmtucwE" }, +#endif { "08/15!test~4711", "$2a$04$0123456789abcdefABCDEF", "$2a$04$0123456789abcdefABCDE.N.drYX5yIAL1LkTaaZotW3yI0hQhZru" }, { "08/15!test~4711", "$5$rounds=1000$0123456789abcdef", @@ -124,8 +129,13 @@ static const struct { /* keep in sync with the sample struct above */ static const struct password_scheme crypt_schemes[] = { +#ifdef __OpenBSD__ { "CRYPT", PW_ENCODING_NONE, 0, crypt_verify, + crypt_generate_blowfisch }, +#else + { "CRYPT", PW_ENCODING_NONE, 0, crypt_verify, crypt_generate_des }, +#endif { "BLF-CRYPT", PW_ENCODING_NONE, 0, crypt_verify, crypt_generate_blowfisch }, { "SHA256-CRYPT", PW_ENCODING_NONE, 0, crypt_verify,

1 0

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 09 Jan '16

09 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

doveadm expunge no longer works
by Fabian Groffen 31 Dec '15

31 Dec '15

Heya, Just upgraded from 2.2.19 to dovecot-2.2.21 and noticed expunging mail no longer works. # doveadm expunge -u theuser MAILBOX spam all Fatal: expunge: To avoid accidents, each branch in search query must contain something else besides MAILBOX (e.g. just add "all" if you want everything) Clearly, I've already got all in there, so I tried capitalising, etc. Looking at the code, I see expunge_search_args_is_msgset_or_ok apparently is failing. I'm wondering if this function [1] is actually doing what it is supposed to do, since it uses return, instead a var to figure out whether it is ok or not. In my case, just because it finds MAILBOX it returns without looking whether there is any further arguments. Or am I missing the point here (and how should I expunge a folder of mail?) Thanks, Fabian [1] https://github.com/dovecot/core/blob/6971937a6f3e93844dbd43bdbe903628e21a94… -- Fabian Groffen Gentoo on a different level

1 1

sieve-filter to script fails with SHUT_WR
by Mark Stover 31 Dec '15

31 Dec '15

Trying to make vnd.dovecot.filter to exchange an email with my script. (I have a vnd.dovecot.pipe script working, so I'm pretty sure it's not the configuration...) I'm passing the email using stdin/stdout and _not_ using sockets. My script receives the email and processes it, but the filter process fails: lda(<username>): Error: shutdown(/usr/local/lib/dovecot-sieve/sieve-filter/CleanAttachments.py, SHUT_WR) failed: Socket is not connected lda(<username>): Error: sieve: 20-filter-incoming: line 15: filter action: failed to execute to program `CleanAttachments.py' Not sure, what I'm doing wrong... Thanks, Mark $ doveconf -n # 2.2.21 (5345f22): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.9 (357ac0a0e68b+) # OS: Darwin 15.2.0 x86_64 lda_mailbox_autocreate = yes mail_location = maildir:~/Maildir maildir_broken_filename_sizes = yes maildir_very_dirty_syncs = yes plugin { sieve = file:~/.dovecot/sieve;active=~/.dovecot/sieve/user.sieve sieve_before = /usr/local/lib/dovecot-sieve/sieve.d/ sieve_execute_bin_dir = /usr/local/lib/dovecot-sieve/sieve-execute sieve_extensions = +vnd.dovecot.pipe +vnd.dovecot.execute +vnd.dovecot.filter +vnd.dovecot.debug sieve_filter_bin_dir = /usr/local/lib/dovecot-sieve/sieve-filter sieve_pipe_bin_dir = /usr/local/lib/dovecot-sieve/sieve-pipe sieve_plugins = sieve_extprograms sieve_user_log = ~/.dovecot/sieve/sieve.log } postmaster_address = mstover(a)cisco.com protocol lda { info_log_path = log_path = mail_plugins = " sieve" } Sieve Script: require [ "variables", "envelope", "vnd.dovecot.debug", "vnd.dovecot.filter" ]; if envelope :matches "to" "*" { set "to" "${1}"; } if envelope :matches "from" "*" { set "from" "${1}"; } debug_log "Received message TO=${to} FROM=${from}"; filter "CleanAttachments.py"; debug_log "Returned from CleanAttachments"; if envelope :matches "to" "*" { set "to" "${1}"; } if envelope :matches "from" "*" { set "from" "${1}"; } debug_log "Returned message TO=${to} FROM=${from}";

2 2

LMTP crashes on Debian with dovecot backports from rename-it.nl
by Christian Schmidt 30 Dec '15

30 Dec '15

Hello dovecot-users, we're running Debian 7.9 with dovecot from Stephan Bosch's repository: deb http://xi.rename-it.nl/debian/ oldstable-auto/dovecot-2.2 main Starting with dovecot 2.2.20-1 build 28, we suddenly discovered that some mails (to be locally delivered) "got stuck". dovecot's log revealed messages like the following one: Dec 29 09:56:50 mailhost dovecot: lmtp(MAILRECIPIENT(a)chemie.uni-hamburg.de): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x8360f) [0x7f58fce4f60f] -> /usr/lib/dovecot/libdovecot.so.0(+0x8366e) [0x7f58fce4f66e] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f58fcdf8a3e] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x3cc75) [0x7f58fd107c75] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xabeda) [0x7f58fd176eda] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_get_first_header+0xba) [0x7f58fd17723a] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_get_first_header+0x38) [0x7f58fd108cd8] -> /usr/lib/dovecot/modules/lib20_mail_log_plugin.so(+0x1b5c) [0x7f58fb16cb5c] -> /usr/lib/dovecot/modules/lib20_mail_log_plugin.so(+0x22e9) [0x7f58fb16d2e9] -> /usr/lib/dovecot/modules/lib15_notify_plugin.so(notify_contexts_mail_copy+0x46) [0x7f58fb371576] -> /usr/lib/dovecot/modules/lib15_notify_plugin.so(+0x2750) [0x7f58fb372750] -> /usr/lib/dovecot/modules/lib10_quota_plugin.so(+0xbc20) [0x7f58fb580c20] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_copy+0x7d) [0x7f58fd11305d] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver_save+0x171) [0x7f58fd4019c1]-> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0x11b) [0x7f58fd401dfb] -> dovecot/lmtp [DATA MAILRECIPIENT(a)chemie.uni-hamburg.de](+0x7263) [0x7f58fd831263] -> dovecot/lmtp [DATA MAILRECIPIENT(a)chemie.uni-hamburg.de](+0x79d9) [0x7f58fd8319d9] -> /usr/lib/dovecot /libdovecot.so.0(io_loop_call_io+0x5b) [0x7f58fce6282b] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd7) [0x7f58fce63c07] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7f58fce628d5] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f58fce62a78] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f58fcdfe443] -> dovecot/lmtp [DATA MAILRECIPIENT(a)chemie.uni-hamburg.de](main+0x19c) [0x7f58fd82f8dc] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7f58fca5fead] -> dovecot/lmtp [DATA MAILRECIPIENT(a)chemie.uni-hamburg.de](+0x59ad) [0x7f58fd82f9ad] Dec 29 09:56:50 mailhost dovecot: lmtp(MAILRECIPIENT(a)chemie.uni-hamburg.de): Fatal: master: service(lmtp): child 15897 killed with signal 6 (core dumps disabled) Dec 29 09:56:51 mailhost dovecot: lmtp(MAILRECIPIENT(a)chemie.uni-hamburg.de): Panic: file ../../../src/lib/array.h: line 219 (array_idx_i): assertion failed: (idx * array->element_size < array->buffer->used) All dovecot builds newer than 2.2.20-1~auto+26 show the same behaviour. Is there anything we can do? # doveconf -n # 2.2.20 (): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.10 # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.9 ext4 auth_default_realm = chemie.uni-hamburg.de auth_master_user_separator = * auth_mechanisms = plain login auth_verbose = yes login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k mail_gid = vmail mail_location = maildir:/mail/%d/%n/Maildir mail_plugins = acl mail_log notify quota zlib mail_uid = vmail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart imapflags notify namespace { list = children location = maildir:/mail/%%d/%%n/Maildir:INDEX=/mail/%d/%n/shared/%%u:CONTROL=/mail/%d/%n/shared/%%u prefix = SHARED/%%u/ separator = / type = shared } namespace inbox { hidden = no inbox = yes list = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = INBOX/ separator = / subscriptions = yes type = private } passdb { args = /etc/dovecot/deny-users deny = yes driver = passwd-file } passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile acl_shared_dict = file:/var/lib/dovecot/shared-mailboxes mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size quota = maildir:Mailbox-Quota quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = file:~/sieve;active=~/.dovecot.sieve sieve_extensions = +notify +imapflags zlib_save = gz zlib_save_level = 6 } pop3_client_workarounds = outlook-no-nuls oe-ns-eoh postmaster_address = postmaster(a)chemie.uni-hamburg.de protocols = " imap lmtp sieve pop3" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_min_avail = 8 service_count = 0 vsz_limit = 256 M } service imap { executable = imap postlogin process_limit = 1024 vsz_limit = 512 M } service lmtp { inet_listener lmtp { address = 127.0.0.1 port = 24 } unix_listener /var/spool/postfix/private/lmtp-dovecot { group = postfix mode = 0660 user = postfix } } service pop3-login { inet_listener pop3 { port = 0 } inet_listener pop3s { port = 995 ssl = yes } } service pop3 { executable = pop3 postlogin } service postlogin { executable = script-login -d rawlog } ssl = required ssl_ca = </ssl/CA.pem ssl_cert = </ssl/cert.pem ssl_key = </ssl/cert.key ssl_protocols = !SSLv2 !SSLv3 syslog_facility = daemon userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } verbose_proctitle = yes protocol lmtp { mail_plugins = acl mail_log notify quota zlib sieve } protocol lda { mail_plugins = acl mail_log notify quota zlib sieve } protocol imap { mail_max_userip_connections = 50 mail_plugins = acl mail_log notify quota zlib imap_acl imap_quota imap_zlib } protocol sieve { mail_max_userip_connections = 100 } protocol pop3 { mail_max_userip_connections = 50 } Thanks & kind regards, Christian Schmidt -- No signature available.

3 6

Re: sieve-filter crashes
by kjonca＠o2.pl 29 Dec '15

29 Dec '15

I tried to post earlier, but something goes wrong. KJ kjonca(a)o2.pl (Kamil Jońca) writes: > I want to refilter my mails in inbox so I tried to use: > > sieve-filter -e -W -D -C -v ~/.dovecot.sieve INBOX > > on three messages I got: > > info: filtering: [Fri, 28 Dec 2012 15:40:33 -0500; 14399 bytes] `[SPAM] Keep Defective by Design fight...'. > sieve-filter(kjonca): Panic: file str.c: line 22 (str_new_const): assertion failed: (str[len] == '\0') > sieve-filter(kjonca): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x82462) [0x7f2012002462] -> /usr/lib/dovecot/libdovecot.so.0(+0x824d9) [0x7f20120024d9] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f2011fa9a01] -> /usr/lib/dovecot/libdovecot.so.0(+0xa9098) [0x7f2012029098] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x5f1dc) [0x7f20128211dc] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_match+0xf1) [0x7f2012807721] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x5fa85) [0x7f2012821a85] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_interpreter_continue+0xe7) [0x7f20127fe657] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_interpreter_run+0x2b) [0x7f20127fe7db] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x4faca) [0x7f2012811aca] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_execute+0x47) [0x7f2012812637] -> /usr/bin/sieve-filter(main+0x754) [0x7f2012c96d24] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f20119f4b45] -> /usr/bin/sieve-filter(+0x43ca) [0x7f2012c973ca] > > > # 2.2.19 (a9c75e48cf8c): /etc/dovecot/dovecot.conf > # Pigeonhole version 0.4.9 > # OS: Linux 3.16.0-4-amd64 x86_64 Debian stretch/sid > > KJ -- http://stopstopnop.pl/stop_stopnop.pl_o_nas.html A stitch in time saves nine.

3 3

How to apply the patch for disable SSL3 on Dovecot 2.0.9
by Marco 29 Dec '15

29 Dec '15

Hi,I see on Dovecot 2.0.9 is no possibile disable SSL3 Until I wait the panel of my server will look into this issue and maybe put a more updated version, how I can fix this?I found on the Internet http://askubuntu.com/questions/537196/how-do-i-patch-workaround-sslv3-poodl… also link to the patch http://www.mail-archive.com/dovecot@dovecot.org/msg59945.html I don't know what to do for fix the SSL 3 Issue I AM On CentoOs 6.3Thanks.

2 1

Howto get information about quota used
by Макаров Денис 29 Dec '15

29 Dec '15

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

Query regarding migration from Maillenium to Dovecot mail server
by Sirisha R 29 Dec '15

29 Dec '15

Hi, We have few queries regarding dovecot mail server. Our application used to supported maillenium mail server, but soon this server is going to retire. So we are planning to migrate our application mail server to dovecot for which we seek your help. Previously, the mailboxes that our application used to support were under att domain, then the mailboxes were migrated to maillenium mail server, and aliases of the existing att mailboxes were created by maillenium support group, so that any mail sent to the att mailbox automatically gets redirected to maillenium alias mailbox. For instance, for the mailbox abc.att.com, an alias was created as abc(a)maillenium.att.com<mailto:abc@maillenium.att.com>. Maillenium support group provided us mailServerHost, mailServerUsername and mailServerPassword. We seek your help in migrating from Maillenium mail system to Dovecot. Thanks & Regards, R Sirisha This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp

1 0

Sieve: Invalid/unknown path to storage
by Kay-Michael Voit 25 Dec '15

25 Dec '15

Hi, I have just updated from Ubuntu 15.04 to 15.10. Unfortunately, sieve scripts are not recognized anymore. Here is my version: > dovecot --version > 2.2.18 > apt-cache policy dovecot-sieve > dovecot-sieve: > Installed: 1:2.2.18-2ubuntu2 > Candidate: 1:2.2.18-2ubuntu2 > Version table: > *** 1:2.2.18-2ubuntu2 0 > 500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages > 100 /var/lib/dpkg/status And this is the log entry: > Dec 25 09:24:12 home-le dovecot: lda(user1): Warning: sieve: file > storage: Active sieve script symlink /home/user1/.dovecot.sieve is > broken: Invalid/unknown path to storage (points to /home/user1/sieve). > Dec 25 09:24:12 home-le dovecot: lda(user1): > msgid=<567CFD2C.7070301(a)example.org>: saved mail to INBOX > Dec 25 09:24:12 home-le postfix/local[28536]: 70876BD035A: > to=<user1(a)example.org>, relay=local, delay=0.07, > delays=0.02/0.01/0/0.04, dsn=2.0.0, status=sent (delivered to command: > /usr/lib/dovecot/deliver -c /etc/dovecot/dovecot.conf -m "${EXTENSION}") It is not a permission issue (though there should even be one with more restrictive permissions) > otheruser@home-le:~$ cat /home/user1/.dovecot.sieve > require ["variables","date", "include"]; > > include :personal "00-delete"; > include :personal "01-spam"; > include :personal "50-bulk_filter"; It is apparently also not a path normalization issue (also according to the correct "points to" path in the log). I used an absolute path in the symlink: > user1@home-le:~$ ls -la .dovecot.sieve > lrwxrwxrwx 1 user1 user1 33 Dec 25 09:23 .dovecot.sieve -> > /home/kay/sieve/managesieve.sieve Any idea what could be wrong here? Here is my dovecot -n output: > namespace inbox { > inbox = yes > location = > mailbox Drafts { > special_use = \Drafts > } > mailbox Junk { > special_use = \Junk > } > mailbox Sent { > special_use = \Sent > } > mailbox "Sent Messages" { > special_use = \Sent > } > mailbox Trash { > special_use = \Trash > } > prefix = > separator = . > type = private > } > passdb { > driver = pam > } > plugin { > sieve = file:~/.dovecot.sieve > sieve_dir = ~/sieve > } > postmaster_address = postmaster(a)example.net > protocols = " imap sieve" > service managesieve-login { > inet_listener sieve { > port = 4190 > } > } > ssl_ca = </etc/ssl/certs/startssl.ca.pem > ssl_cert = </etc/ssl/certs/net.example.home-le.pem > ssl_key = </etc/ssl/private/net.example.home-le.key > submission_host = 192.168.153.1 > userdb { > driver = passwd > } > protocol lda { > mail_plugins = " sieve" > } > protocol imap { > mail_max_userip_connections = 50 > }

2 2

Debug Dovecot Plugin (shared library)
by David Becher 24 Dec '15

24 Dec '15

Hey! I was just wondering what would be the best way to debug a plugin I am currently writing for dovecot. The plugin basically registers a new IMAP capability and I want to set a breakpoint to the "cmd_handle_new_capability" function (thats just a function name for better explaining purposes). Right now I have opened a connection via openssl ('openssl s_client -connect example:143 -starttls imap') to be able to mess around with the my server. Then I am able to login into the server via 'a login "username" "password"' and feed the server with my self created IMAP capability command. I know that I can start gdb and attach to an already running process via its PID. But how do I know which process I have to attach to? Looking at the output of 'top' it seems to be an instance of the 'imap' command PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 13413 vmail 20 0 21004 1844 1524 S 0.0 0.0 0:00.00 Iman But its only started the exact moment I issue my IMAP command towards the server, so of course I am not fast enough to track down the PID before the function has returned, so the process handling the command seems to be up only for the short period of time to handle the command, there is no process before which I can attach to. My current workaround is that I put a tail onto /var/log/mail.log and from within my shared library function (cmd_handle_new_capability) I log the PID of the current process, then sleep(10) for 10 seconds, which gives me enough time to have a look at mail.log to get to know the PID which I then can attach to. But isn't there a better way to do this? Maybe attach to the process which originally creates the new process handling the IMAP command and then stepping into it? I hope someone can help me out :) All the best, David

2 2

Dovecot 2.2.20 autoexpunge
by Robert Blayzor 23 Dec '15

23 Dec '15

I have configured autoexpunge on some folders: namespace inbox { inbox = yes location = mailbox Junk { auto = subscribe autoexpunge = 30 days special_use = \Junk } mailbox Trash { auto = subscribe autoexpunge = 2 weeks special_use = \Trash } prefix = separator = / } After adding these and restarting, logging in and out several times, I still see messages days/weeks past the autoexpunge setting. I checked the logs but never see any autoexpunge messages logged. Is there something else that needs to be set to trigger this? -- Robert inoc.net!rblayzor XMPP: rblayzor.AT.inoc.net PGP Key: 78BEDCE1 @ pgp.mit.edu

4 6

dsync and namespaces
by Charlie Hothersall-Thomas 22 Dec '15

22 Dec '15

`doveconf -n' output: > # 2.2.10: /etc/dovecot/dovecot.conf > # OS: Linux 3.10.0-229.20.1.el7.x86_64 x86_64 CentOS Linux release 7.2.1511 (Core) > listen = * > mail_location = maildir:~/Maildir/ > namespace { > inbox = yes > location = > prefix = > separator = / > type = private > } > namespace { > location = maildir:/srv/mail/ > prefix = Public/ > separator = / > subscriptions = no > type = public > } > passdb { > driver = pam > } > ssl_cert = </etc/pki/dovecot/certs/dovecot.pem > ssl_key = </etc/pki/dovecot/private/dovecot.pem > userdb { > driver = passwd > } I have some public mailboxes in /srv/mail -- Public/Alpha and Public/Mike -- using configuration taken more or less verbatim from http://wiki2.dovecot.org/SharedMailboxes/Public. These are stored in Maildir format; here's a sample of how things look on disk at the moment: > /srv/mail/ > ├── .Alpha > │ ├── cur > │ │ └── 1450775948.M24820P23708.cht,S=8186,W=8360:2,S > │ ├── dovecot.index.cache > │ ├── dovecot.index.log > │ ├── dovecot-uidlist > │ ├── maildirfolder > │ ├── new > │ └── tmp > ├── cur > ├── dovecot.index.log > ├── dovecot-uidlist > ├── dovecot-uidvalidity > ├── dovecot-uidvalidity.5679158d > ├── maildirfolder > ├── .Mike > │ ├── cur > │ │ ├── 1450775948.M202327P23708.cht,S=8405,W=8576:2,S > │ │ ├── 1450775948.M257575P23708.cht,S=5590,W=5732:2,S > │ ├── dovecot.index.cache > │ ├── dovecot.index.log > │ ├── dovecot-uidlist > │ ├── maildirfolder > │ ├── new > │ └── tmp > ├── new > └── tmp I'm trying to convert these public mailboxes from Maildir to mdbox format. My end goal is a directory structure like the following. I obtained this example by emptying /srv/mail, changing `location = maildir:/srv/mail/' to use mdbox, and then delivering some messages into Public/Alpha and Public/Mike: > /srv/mail/ > ├── dovecot-uidvalidity > ├── dovecot-uidvalidity.567915fa > ├── mailboxes > │ ├── Alpha > │ │ └── dbox-Mails > │ │ ├── dovecot.index.cache > │ │ └── dovecot.index.log > │ ├── dbox-Mails > │ │ └── dovecot.index.log > │ └── Mike > │ └── dbox-Mails > │ ├── dovecot.index.cache > │ └── dovecot.index.log > └── storage > ├── dovecot.map.index.log > └── m.1 I know that dsync can be used to convert between mailbox formats, but is this possible in conjunction with namespaces? I can convert one of my mailboxes to an arbitrary mdbox location on disk using... > dsync -o mail_location=mdbox:/tmp/dbox/ mirror maildir:/srv/mail/.Mike/ ... although this puts the messages inside an INBOX mailbox: > /tmp/dbox/ > ├── mailboxes > │ └── INBOX > │ └── dbox-Mails > │ ├── dovecot.index.cache > │ └── dovecot.index.log > └── storage > ├── dovecot.map.index.log > └── m.1 I could run this once per public mailbox, writing each to a different mdbox location, but am unaware of a method to merge them such that they would work with my Public/ namespace. Is it possible to use dsync to convert my public Maildir mailboxes to mdbox, resulting in my desired directory structure above? I think I want to be able to tell dsync the location as a mailbox name, rather than a disk location, although this doesn't appear to be possible. If not, is there another solution? My best idea at the moment is to make the configuration change and then re-deliver all messages by mailbox name. Thanks in advance, and happy holidays, -- Charlie Hothersall-Thomas | w: https://charlie.ht | e: me(a)charlie.ht | pgp: 4096R/C3676E3E

1 0

[bug][Pigeonhole 0.4.10] Missing msgid
by Alexander Moisseev 22 Dec '15

22 Dec '15

Pigeonhole 0.4.10 doesn't log msgid for some messages. Dec 16 09:57:57 mx dovecot: lmtp(user1(a)example.com): EbLlL2gLcVYCBgEAPZa6/Q: sieve: msgid=<20151216065756.BE1DF1FFD8(a)cp.bitrix24.com>: forwarded to <user3(a)example.com> Dec 16 09:57:57 mx dovecot: lmtp(user1(a)example.com): EbLlL2gLcVYCBgEAPZa6/Q: sieve: stored mail into mailbox 'INBOX' Dec 16 09:57:57 mx dovecot: lmtp(user2(a)example.com): FrLlL2gLcVYCBgEAPZa6/Q: sieve: msgid=<20151216065756.C77BB1FFD8(a)cp.bitrix24.com>: forwarded to <user3(a)example.com> Dec 16 09:57:57 mx dovecot: lmtp(user2(a)example.com): FrLlL2gLcVYCBgEAPZa6/Q: sieve: msgid=<20151216065756.C77BB1FFD8(a)cp.bitrix24.com>: stored mail into mailbox 'bitrix'

2 6

Where exactly are these Junk]Trash etc folders stored?
by Robert Chalmers 22 Dec '15

22 Dec '15

These folders are stored somewhere .. but where? mailbox Trash { auto = no special_use = \Trash } mailbox Drafts { auto = no special_use = \Drafts } mailbox Sent { auto = subscribe # autocreate and autosubscribe the Sent mailbox special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Spam { auto = create # autocreate Spam, but don't autosubscribe special_use = \Junk } mailbox virtual/All { # if you have a virtual "All messages" mailbox auto = no special_use = \All }

2 1

Thanks again for Dovecot
by Steve Litt 21 Dec '15

21 Dec '15

Hi all, All email clients suck. IMHO Claws-Mail sucks less, but even on the Claws-Mail mailing list there are all sorts of problems discussed. Most of these problems are a moot point for me, because I use Claws-Mail only as a window into my locally hosted Dovecot IMAP server. Claws-Mail is like a little window into Dovecot. Meanwhile, all those "don't quite work right" functionalities normally done by an email client I do outside of Claws. For filtering, I use Procmail, which sorts messages into the correct (Dovecot) folders and sends trolls to /dev/null. If Claws-Mail ever becomes as lame as Kmail, I can just switch to another email client, because most of my setup is in Dovecot and the input to Dovecot. Email clients are interchangeable for me, and this REALLY makes my life less worrysome. And Dovecot does one thing and does it right. It never breaks. Thank you for this great tool! SteveT Steve Litt November 2015 featured book: Troubleshooting Techniques of the Successful Technologist http://www.troubleshooters.com/techniques

1 0

questions for a unusual master/slave like mail-server setup
by Christoph Anton Mitterer 21 Dec '15

21 Dec '15

Hey folks. I was planning since a long time for some more advanced mail server setup (described below), which basically has some weird ;) master/slave ideas behind. It's probably a bit more complicated (and maybe also a bit more insane) than the usual mail server setup, so I'd be happy about any advice and some questions answered: There are two mailservers (dovecot, as you may have guessed ;) ): - IMAP shall be used; using POP3 is not planned. - A format in which each mail is stored in a separate file shall be used. That leaves for either maildir or sdbox, where I'd prefer maildir, as I like to be able to loose the indexes. - Each (per user) mailbox shall have many subfolders and will receive loads of mail (including from several high traffic mailing lists). - Mail filtering shall take place *at least* on the "online" server, probably either with sieve or maildrop. - One of the mailservers is always "online", directly connected to the internet (and globally available). - The other mailserver is "offline", not directly connected to the internet (and only locally available). The "online" mailserver: - Is in a not fully trusted location (i.e. at some ISP). - Has somewhat limited storage. - Makes the mails on it available to MUAs connecting from anywhere. - Receives mail from various sources, e.g. via postfix/LDA or something like fetchmail. - Has only a parts of *all* mails, that means for example: - *All* mail from some personal contacts. - Only the last 1 year for low volume mailing lists. - Only the last 4 months for high volume mailing lists. The "offline" mailserver: - Is in a trusted location (beneath my pillow ;) ). - Has enough storage for the purposes of mail. - Makes all mails available to MUAs connecting from the LAN. - Receives mails from the "online" mailserver, when manually "moved" to it via some MUA over IMAP. - Has *all* mails. Client's MUAs, may connect to both, but the "offline" server will only be available at home. As you can imagine, the idea is basically the following: I get large amounts of mails, from all kind of mailing lists as well as personal mail. All that is filtered to a tree hierarchy of folders. There's a not fully secure mailserver, where mail arrives and which I can use when I'm on the way. It contains either just recent mails (the amount depending on the traffic of the list) or for selected senders/lists everything, and I control basically on a per folder basis how much should be retained (all, last 10 years, last week, etc.). There's another server, where *all* mail should eventually end up, for archival and security reasons. This implies obviously, that some of the mail is on both servers, some only on the "offline" server, and that this may vary from folder to folder. Further, on both servers, I may want to add filters, which basically split up a folder, e.g. of high traffic lists, so that mail of previous years or months is moved to subfolder structures, e.g.: linux-kernel +--2014 \--2013 and so on. So far, all that wouldn't be too difficult,... but as you can imagine, I'd like to have a bit more, which actually makes things quite tricky. How the two mailservers shall synchronise: I don't want to "simply" rsync - the whole system needs to be a bit smarter: 1) It's okay to assume, that synchronisation happens only at discrete times and not continuously (the "offline" server doesn't run always). 2) It would be ok, if the synchronisation requires a downtime of the "online" mailserver (i.e. the LDA). Since btrfs is used, I could also easily do snapshots. 3) One can also assume that, when synchronisation happens, the "offline" server contains at least all those folders, that the "online" server has as well (and possibly more). 4) Obviously, only maildir's cur/ directories should be synced (stuff in tmp&new may be still arriving). 5) As mentioned previously, not all mail may stay on the "online" server, depending on the folder, it will either stay permanently, or only for some period. 6) However, on the "offline" server, all mail stays, unless I manually delete it. 7) One must assume, that mails on *both* servers: - change their IMAP status (as in (S)een, (A)nswered, (F)lagged, etc.) - are moved to other mail folders - may be deleted via MUAs (not clear yet where this can happen) - "Fresh" mail, however, only appears on the "online" server. 8) Mails, once on the "offline" server, shouldn't be rewritten, in the sense that the mail is deleted and recreated (hopefully with the same content), which could happen either wenn the status of the mail changes or when it's moved to another folder (on the other server). The reason is simply, that I wouldn't fully trust the online server, so once the mail is local, it should be immutable (except for the status and folder location). The last, two points make things pretty difficult, or at least I wouldn't see a straightforward solution. (4) would be quite easy, e.g. when rsync would be used, then I'd just rsync all the cur/ directory. The rsync would happen not using --delete, so that mail which is no longer on the "online" server, doesn't get deleted from the "offline" server. (5) one could do, by "simply", on a per folder basis, remove mails older than X on the "online" server, after it has been copied to the "offline" server. An already existing tool for doing that would be nice, though. (7) and (8) is IMHO the most difficult: The only idea I have so far assumes that each mail file has an ID, which is unique for the *whole* mailbox (not just for each folder, as the mails may be moved between folders). The idea would be roughly, the following: * When I synchronise, I either shut down the LDA or make a snapshot of the "online" server's mailbox and work with that. * Then, I make a list (ID, status and pathname) of *all* mails on the online server and another one of *all* mails of the offline server. * Then, I probably scan for duplicate IDs in each list... just to be safe. * Then I process the mail lists as follows: a) If an ID is on *both* servers with the same status and pathname, than that mail had been previously synced already and neither moved nor changed its status since then. Nothing to do. b) If an ID is on *both* servers but with different pathnames or status, then the mail has either been moved or it's status has changed. Consequently, I would move/rename the mail to match the new location and/or IMAP-status. I would move/rename that with the older ctime to match the one with the newer (ctime gets set at move or rename and thus at status change). Even if an attacker would have fiddled with the "online" server's time or somehow else my system times were bogus, the worst that would happen was, that status changes are lost or mail ends up in the wrong folder. c) If an ID is on the "offline" server but not the "online" server, it could be either a mail that has already been garbage collected on the "online" server (so nothing would needed to be done),... or it could be mail hat was removed (via a MUA) on the "online" server and that should as well be removed on the "offline" server, either automatically, or manually after checking. How to find out which of that applies!? d) If an ID is on the "online" server but not the "offline" server, it could be either fresh mail that would needed to be synced,... or it could be mail that was removed on the "offline" server and should as well deleted on the "online" server, either automatically, or manually after checking. (a) and (b) are again rather simple, (c) and (d) not so much... Possible solutions that I could think of: - Either simply don't sync the removal of mails from the "online" server to the "offline" server and vice-versa. It will anyway happen rather rarely. - Remember a list of all IDs, that have been garbage collected on the "online" server. - Remebmer a list of all IDs, that have been removed via MUAs. => not sure if that's easily doable, probably not, is there any dierct way one could do this with dovecot. - Something to find out which mail has been gone on both, the each, the "offline" and the "online" server, since the last synchronisation, via tricks using the snapshot features of btrfs. - Somehow using the date of now and the last synchronisation and the mtimes (which are here basically like creation times, as the mail file contents never change). But I guess that would only work for (d) and not for (c),... and I'd rather not depend on times too much. * In any case, I could give the user a list of mails that would be deleted, for double checking. I actually think this would scale, as I don't expect many mails to be manually deleted through the MUA *once they had been synced*. After that, I think the two servers should be in sync - in the sense described in the beginning. Some further parts of the idea: As said, snapshots and the refcopy feature of btrfs could be quite helpful. So I could basically keep: - the "online" mailserver's mailbox - as of the last sync - as of now - the "offline" mailserver's mailbox - as of the last sync - as of now at the disk of the "offline" server without much additional cost. They'd all share reflinks and wouldn't use (much) additional space (except for fs meta-data) and I could use the snapshots to find out which files were deleted on either of the two servers since last time. Actually copying new mail from the "online" server to the offline server's disk (in the "as of now" area), could then happen via rsync'ing every cur/ from the "online" server to the "offline" server, with --delete and --ignore-existing (as I don't trust the "online" server and mail file contents should be immutable). So... questions... :D 1) Obviously, does anyone know a better solution, or has some improvements, other ideas? Or are there any problems with the above, which I haven't realised, or would you think it would work? 2) Does dovecot *ever* change the contents (i.e. the file contents) of a maildir mail file? 3) As ID I'd have thought that the maildir mail filename might work, e.g. 1234567890.M20046P2137.mailserver,S=4542,W=4642:2,Sb I mean especially the first part: 1234567890.M20046P2137.mailserver Is that unique across *all* folders of a mailbox? AFAIU, that name would be determined by whatever delivers the mail, right? So can I somehow configure that to make it unique? 4) Does dovecot ever change anything from the maildir mail filenames, except anything after the ":" above? I.e. would it ever change: 1234567890.M20046P2137.mailserver,S=4542,W=4642 ? 5) Would dovecot every copy, truncate+copy or somehow else rewrite files, instead of just moving them (i.e. thus possibly changing inodes, reflinks or that like)? 6) AFAIU, when using maildir, dovecots index files can get completely lost,... and one can fully "recover" all mails and their status. The only "bad" thing that might happen is that MUAs re-load all mail, right? 7) How graceful does dovceot handle the situation when mail is added or removed to/from cur/ by not using dovecot's IMAP,... especially with respect to index files. In the above solution I'd do a lot adding/moving/deleting files in maildirs, which would be done purely at the (file) system level, so the index would quite often get invalidated. How does it recognise that (if at all)? And is this generally stable, or should I rather remove any indexes after syncing and have them rebuilt by that? 8) All the above doesn't handle yet the thing of having yearly/monthly/etc. archive subfolders as described above, like: linux-kernel +--2014 \--2013 possibly on *both* "online" and "offline" server and possibly even in a different layout. I'm not yet sure whether this would be easily doable with the above solution,... my basic idea would be simply consider any such "archive" subfolders as the same than the "base" folder during syncing... and afterwards do re-order the mails on the "offline" and "online" server's folders as necessary. For example, if the "online" server has: linux-kernel +--01 +--02 +--03 ... \--12 in other words, one archive folder for the each of the last 12 months. While the "offline" server has: linux-kernel +--2014 \--2013 The script would then e.g. move the files to their new folders. => does anyone know, whether such thing exists already, i.e. a tool that sorts the mails into maildir subfolders, based on years, months, etc? 9) As said before, I'd like to be able to loose any indexes, but AFAICS, my solution wouldn't anyway work with sdbox. But if there's an sdbox based solution that makes everything much easier, do not hesitate to tell me :) 10) In the long-term I hope to be able to do something that makes server-side search (i.e. through the big fat mail archive) much faster (or is that already supported in dovecot?). I haven't really looked at all into that topic (just know about notmuch[0]). Anyway, if anyone sees problems in my above solution, when that would be used with something that gives me better server side search (i.e. some indexing solution),... I'd be happy to hear about that as well. Thanks a lot so far, Chris. [0] https://notmuchmail.org/

1 0

Possible bug about the SPECIAL-USE / CREATE-SPECIAL-USE extensions
by Jeff Stedfast 19 Dec '15

19 Dec '15

Hi all, I've locally got Dovecot 2.2.21 (5345f22) installed on my MacBook (via homebrew) that I've been using to test my IMAP library against. What is interesting is that even though Dovecot does not advertise CREATE-SPECIAL-USE, it supports creation of special-use folders via the "CREATE FolderName (USE (\Whatever))" syntax. According to rfc6154, a server is supposed to advertise the CREATE-SPECIAL-USE extension if it supports this: An IMAP server that supports this OPTIONAL feature will advertise the "CREATE-SPECIAL-USE" capability string. Clients MUST NOT use the "USE" parameter unless the server advertises the capability. Note that this capability string is different from the "SPECIAL-USE" string defined above, and a server that supports both functions MUST advertise both capability strings. Has this been fixed in a newer version, perhaps? Or could it be a misconfiguration on my part? Attached is my dovecot configuration (gotten via dovecot -n). Thanks, Jeff

2 2

Multiple IPs and hostname
by Thilo Engelbracht 18 Dec '15

18 Dec '15

Hi, I'm running postfix as SMTP-server and dovecot as IMAP-server. The server has multiple IPs, and postfix is configured that every domain is using a separate IPv4-address. Examle: foo1.com --> 11.22.33.44 foo2.com --> 22.33.44.55 foo3.com --> 33.44.55.66 bar.org --> 66.77.88.99 The hostname of the server is: mail.bar.org Now I have a request from one of my customers, who is using 3 different domains: - foo1.com - foo2.com - foo3.com If he receives a mail to "user(a)foo1.com", the header of the mail looks like this: Return-Path: <somebody(a)web.de> Delivered-To: <user(a)foo1.com> (II) Received: from mail.bar.org by mail.bar.org (Dovecot) with LMTP id V[...]wAAvP/pag for <user(a)foo1.com>; Sun, 29 Nov 2015 13:45:37 +0100 (I) Received: from mout.web.de (mout.web.de [212.227.17.11]) (using TLSv1.2 with cipher ECDHE-[...]-SHA384 (256/256 bits)) (No client certificate requested) by mail.foo1.com (Postfix) with ESMTPS id A[...]9 for <user(a)foo1.com>; Sun, 29 Nov 2015 13:45:36 +0100 (CET) As you can see in (I), postfix receives the mail and added a header with the correct hostname: mail.foo1.com But dovecot adds an additional header (see II). Here, the hostname of the system is visible. This is correct, because dovecot -n | grep -i hostname returns: hostname = mail.bar.org But my customer asks me if it's possible that only his domain is visible in the header: So, if somebody sends a mail to "user(a)foo1.com", only the hostname "mail.foo1.com" should be visible in the mail header. And if somebody sends a mail to "user(a)foo2.com", only the hostname "mail.foo2.com" should be visible in the mail header. Is there a way to do this? Thank you in advance. Kind regards Thilo

2 3

Merry Christmas
by IT Security Inc. 18 Dec '15

18 Dec '15

Merry Christmas from IT Security Inc. 12/18/2015 Visit us online Merry Christmas to you and your family from Hugh Haggerty, myself and everyone else at IT Security,Inc. Albert Whale Hugh Haggerty IT Security Inc. Merry Christmas! IT Security, Inc. 519 Nichols Road Pittsburgh, PA 15237 | in2contact.co/front/tracking.jsp?clientID=858&campaignID=188&userID=731&linkID=B710C911120204FA&emailID=689&sendID=307&triggerID= | in2contact.co/front/tracking.jsp?clientID=858&campaignID=188&userID=731&linkID=EB9D07803CDFE734&emailID=689&sendID=307&triggerID=

1 0

limiting autoexpunge to a service
by Burckhard Schmidt 18 Dec '15

18 Dec '15

Hello, like described at wiki "Mailbox settings": protocol imap { namespace inbox { mailbox Spam { autoexpunge = 10d } } } I tried to use autoexpunge inside lmtp: 20-lmtp.conf: protocol lmtp { mail_plugins = $mail_plugins sieve postmaster_address = ... info_log_path = /var/log/dovecot-lmtp.log sendmail_path = /opt/csw/sbin/sendmail namespace inbox { mailbox Junk { autoexpunge = 10d } } (line 23) } But I get an error during start of dovecot (same with service imap): doveconf: Fatal: Error in configuration file /usr/dovecot/etc/dovecot/conf.d/20-lmtp.conf line 23: Garbage after '{' /usr/dovecot/sbin/dovecot -n # 2.2.21 (): /usr/dovecot-2.2.21/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.10 Is it only a problem of doveconf? -- Regards --- Burckhard Schmidt Abteilung Systemsoftware und Kommunikation ZE Computer- und Medienservice der Humboldt-Universität zu Berlin Postanschrift: Unter den Linden 6, 10099 Berlin Standort: Rudower Chaussee 26; 12489 Berlin Tel.: +49-30-2093-70058 Fax: +49-30-2093-70199 Mail: bschmidt(a)cms.hu-berlin.de

1 0

Last chance to order the Dovecot book
by Peer Heinlein 17 Dec '15

17 Dec '15

Hi, as some people migth know I've written a book about Dovecot that has also been translated and published in English. Thanks for Timos great help and detailled background informations he provided to me. Unfortunately my book publisher has to shutdown his business at the end of 2015 -- right now. During the next few days you'll have the last chance to order the english version of the dovecot book at amazon, if you're interested in. Please don't wait too long. I think they'll stop offering the book before christmas and then it's gone. http://www.dovecot-book.com/online-shop/als-e-book-bestellen/ MAYBE we'll be able to re-publish it next year. Maybe. If not -- this will be the last chance to order it. Peer (The german version of the book will be still available at http://www.dovecot-buch.de) -- 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 1

Deleting Public Mailbox?
by Dag Nygren 17 Dec '15

17 Dec '15

Hi! What am I doing wrong here? Mission: Delete old empty sub mailboxes in our Public mailspace acl-file contents: MailingLists user=dag lrwstipekxa MailingLists/* user=dag lrwstipekxa Didn't work from my mail client so tried: Command tried: % doveadm mailbox delete -s MailingLists/Glibc -u dag doveadm(dag): Error: Can't delete mailbox MailingLists/Glibc: Permission denied % doveadm acl debug -u dag "MailingLists/Egcs" doveadm(dag): Info: Mailbox 'Egcs' is in namespace 'MailingLists/' doveadm(dag): Info: Mailbox path: /usr/local/var/mail/MailingLists/mailboxes/Egcs/dbox-Mails doveadm(dag): Info: All message flags are shared across users in mailbox doveadm(dag): Info: User dag has rights: lookup read write write-seen write-deleted insert post expunge create delete admin doveadm(dag): Error: Mailbox not found from dovecot-acl-list, rebuilding doveadm(dag): Info: Mailbox is in public namespace doveadm(dag): Info: Mailbox MailingLists/Egcs is visible in LIST Must be a config I have wrong. Would like to get rid of them... Best Dag

2 4

userdb username change ignored when using (My)SQL was: Re: userdb username changed
by Péter Márton 17 Dec '15

17 Dec '15

Hi! It works when using LDAP. I've duplicated the "username change" debug line, just to see that the variables are really updated: Apr 20 14:30:27 imap21 dovecot: auth-worker(27127): Debug: sql(ppp(a)example.net): username changed ppp(a)example.net -> uppp Apr 20 14:30:27 imap21 dovecot: auth-worker(27127): Debug: sql(uppp): username changed uppp -> uppp Apr 20 14:30:27 imap21 dovecot: auth: Debug: userdb out: USER#0111#011ppp@example.net#011home=/home/ppp#011uid=500#011gid=500#011quota_rule=*:storage=3100b:messages=1024 And the answer is of course yes. Just the userdb out string has the wrong value. The right value is lost somewhere. But where? Regards, Peter Log of the (for me unusable) LDAP query: Apr 20 14:28:07 imap21 dovecot: auth: Debug: master in: USER#0111#011m2500j6#011service=doveadm Apr 20 14:28:07 imap21 dovecot: auth: Debug: ldap(m2500j6): user search: base=ou=Users,ou=Mail,dc=bnet,dc=at scope=subtree filter=(uid=m2500j6) fields=mailHost Apr 20 14:28:07 imap21 dovecot: auth: Debug: ldap(m2500j6): result: mailHost=localhost; mailHost unused Apr 20 14:28:07 imap21 dovecot: auth: Debug: ldap(m2500j6): username changed m2500j6 -> localhost Apr 20 14:28:07 imap21 dovecot: auth: Debug: ldap(localhost): username changed localhost -> localhost Apr 20 14:28:07 imap21 dovecot: auth: Debug: ldap(localhost): result: mailHost=localhost Apr 20 14:28:07 imap21 dovecot: auth: Debug: userdb out: USER#0111#011localhost#011

2 4

doveadm-server does NOT know fts commands
by SATOH Fumiyasu 16 Dec '15

16 Dec '15

Hi, I'm using Dovecot 2.2.13 with Dovecot Director, Doveadm server and FTS. I want to run doveadm on Director hosts, but Dovecot server on backend hosts reject "fts *" commands. On Dovecot Director hosts: # doveadm fts optimize -u u0001(a)example.jp # echo $? 75 # doveadm fts rescan -u u0001(a)example.jp # echo $? 75 doveadm index -u u0001(a)example.jp INBOX # echo $? 0 On Dovecot backend hosts: # grep doveadm /var/log/maillog Jul 14 10:25:40 backend dovecot: doveadm: Error: doveadm: Client sent unknown command: fts optimize Jul 14 10:25:51 backend dovecot: doveadm: Error: doveadm: Client sent unknown command: fts rescan Is this doveadm-server restriction? On Dovecot backend hosts (2): # doveadm fts optimize -u u0001(a)example.jp -S /var/run/dovecot/doveadm-server # echo $? 75 # doveadm fts rescan -u u0001(a)example.jp -S /var/run/dovecot/doveadm-server # echo $? 75 # doveadm index -u u0001(a)example.jp -S /var/run/dovecot/doveadm-server INBOX # echo $? 0 # doveadm fts optimize -u u0001(a)example.jp # echo $? 0 # doveadm fts rescan -u u0001(a)example.jp # echo $? 0 # doveadm index -u u0001(a)example.jp INBOX # echo $? 0 -- -- 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

Assert failure in 2.2.20: imap-fetch.c:554 (ctx->client->output_cmd_lock || ctx->client->output_cmd_lock == cmd)
by Peter Eriksson 16 Dec '15

16 Dec '15

Just got another core-dump from Dovecot's imap process on our mail server. Dovecot 2.2.20 Solaris 10 / x86 Maildir Output from syslog: Dec 14 10:58:12 mail dovecot: [ID 583609 mail.crit] imap(oling): Panic: file imap-fetch.c: line 554: assertion failed: (ctx->client->output_cmd_lock == NULL || ctx->client->output_cmd_lock == cmd) Dec 14 10:58:15 mail dovecot: [ID 583609 mail.crit] imap(oling): Fatal: master: service(imap): child 2167 killed with signal 6 (core dumped) Checked the users' Maildir for files modified around this time and found: -rw------- 1 oling root 15743 Dec 14 10:54 .Deleted Messages/cur/1450099463.M318113P13582.mail,S=15743,W=16026:2,RSbcd Don't know if it's related though. Data from the core-dump / debugger: # /pkg/studio/default/bin/dbx /ifm/pkg/dovecot/default/libexec/dovecot/imap imap.2167.306 ... program terminated by signal ABRT (Abort) 0xfffffd7ffeb81eca: __lwp_kill+0x000a: jae __lwp_kill+0x18 [ 0xfffffd7ffeb81ed8, .+0xe ] Current function is default_fatal_finish 201 abort(); (dbx) where [1] __lwp_kill(0x1, 0x6, 0xfffffe88d2948e40, 0xfffffd7ffeb827be, 0x4552555443, 0x0), at 0xfffffd7ffeb81eca [2] _thr_kill(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7ffeb7a7d3 [3] raise(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7ffeb26fe9 [4] abort(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7ffeb05f60 =>[5] default_fatal_finish(type = LOG_TYPE_PANIC, status = 0), line 201 in "failures.c" [6] i_internal_fatal_handler(ctx = 0xfffffd7fffdff858, format = 0x492df0 "file %s: line %d: assertion failed: (%s)", args = 0xfffffd7fffdff840), line 670 in "failures.c" [7] i_panic(format = 0x492df0 "file %s: line %d: assertion failed: (%s)", ... = 0x467f4f, ...), line 275 in "failures.c" [8] imap_fetch_more(ctx = 0x736b00, cmd = 0x7369a8), line 554 in "imap-fetch.c" [9] cmd_fetch(cmd = 0x7369a8), line 297 in "cmd-fetch.c" [10] command_exec(cmd = 0x7369a8), line 172 in "imap-commands.c" [11] client_command_input(cmd = 0x7369a8), line 948 in "imap-client.c" [12] client_command_input(cmd = 0x7369a8), line 1008 in "imap-client.c" [13] client_handle_next_command(client = 0x4d16c0, remove_io_r = 0xfffffd7fffdffa7d), line 1022 in "imap-client.c" [14] client_handle_input(client = 0x4d16c0), line 1058 in "imap-client.c" [15] client_input(client = 0x4d16c0), line 1105 in "imap-client.c" [16] io_loop_call_io(io = 0x5bab00), line 559 in "ioloop.c" [17] io_loop_handler_run_internal(ioloop = 0x4b2580), line 211 in "ioloop-poll.c" [18] io_loop_handler_run(ioloop = 0x4b2580), line 607 in "ioloop.c" [19] io_loop_run(ioloop = 0x4b2580), line 583 in "ioloop.c" [20] master_service_run(service = 0x4b2450, callback = 0x482690 = &`imap`main.c`client_connected(struct master_service_connection *conn)), line 640 in "master-service.c" [21] main(argc = 1, argv = 0xfffffd7fffdffcb8), line 442 in "main.c" (dbx) print cmd cmd = 0x7369a8 (dbx) print ctx->client->output_cmd_lock ctx->client->output_cmd_lock = 0x72e0f8 (dbx) print *cmd *cmd = { prev = (nil) next = 0x72e0f8 client = 0x4d16c0 pool = 0x4d1eb0 tag = 0x736ac0 "150.11" name = 0x736ac8 "UID FETCH" args = 0x736ad8 "12663:12665 (BODY.PEEK[] BODYSTRUCTURE)" cmd_flags = COMMAND_FLAG_BREAKS_SEQS func = 0x437220 = &cmd_fetch(struct client_command_context *cmd) context = (nil) module_contexts = { arr = { buffer = 0x736a58 element_size = 8U } v = 0x736a58 v_modifiable = 0x736a58 } parser = 0x4d3d40 state = CLIENT_COMMAND_STATE_WAIT_INPUT start_time = { tv_sec = 1450087092 tv_usec = 924042 } start_ioloop_wait_usecs = 119688401U running_usecs = 0 bytes_in = 0 bytes_out = 0 sync = (nil) uid = 1U cancel = 0 param_error = 0 search_save_result = 0 search_save_result_used = 0 temp_executed = 0 tagline_sent = 0 } (dbx) print *(ctx->client->output_cmd_lock) *ctx->client->output_cmd_lock = { prev = 0x7369a8 next = 0x72d8c8 client = 0x4d16c0 pool = 0x4d1eb0 tag = 0x72e208 "149.11" name = 0x72e210 "UID FETCH" args = 0x72e220 "12666 (BODY.PEEK[] BODYSTRUCTURE)" cmd_flags = COMMAND_FLAG_BREAKS_SEQS func = 0x4371b0 = &`imap`cmd-fetch.c`cmd_fetch_continue(struct client_command_context *cmd) context = 0x72e248 module_contexts = { arr = { buffer = 0x72e1a8 element_size = 8U } v = 0x72e1a8 v_modifiable = 0x72e1a8 } parser = 0x5bb410 state = CLIENT_COMMAND_STATE_WAIT_OUTPUT start_time = { tv_sec = 1450087092 tv_usec = 923420 } start_ioloop_wait_usecs = 119688382U running_usecs = 538U bytes_in = 33U bytes_out = 32994U sync = (nil) uid = 1U cancel = 0 param_error = 0 search_save_result = 0 search_save_result_used = 0 temp_executed = 1U tagline_sent = 0 } -- [Ll.U] Peter Eriksson KITVS-IFM & ITI-NET IT.LiU.SE +46-70 518 2786

2 2

LIST command should not interpret wildcards in reference
by Robert Siemer 16 Dec '15

16 Dec '15

Hello everyone, I believe this is erroneously implemented in Dovecot: >>> for i in c.list_folders('deleteme.*.folder', '%'): ... print(i) ... ((b'\\HasNoChildren',), b'.', 'deleteme.*.folder') ((b'\\HasNoChildren',), b'.', 'deleteme.deleteme.deleteme.folder') We see here an interactive python session, which launches LIST "deleteme.*.folder" "%" over the wire and receives two mailboxes as answer. The response is already parsed, but that’s not important for my point: according to RFC3501 section 6.3.8 LIST Command, the arguments are “reference name” and “mailbox name with possible wildcards”. Both arguments are allowed to contain wildcard characters, but they have no special meaning in the reference. Dovecot 2.2.18 doesn’t do that right: the second mailbox should not be listed, because it is not a subfolder of reference. Is this a known issue? Regards, Robert

2 2

And one more core-dump in imap:str.c str_append(cstr = NULL)
by Peter Eriksson 16 Dec '15

16 Dec '15

Dovecot 2.2.20 Solaris 10 / x86 Maildir q (dbx) where [1] strlen(0x0, 0x0, 0x491baa, 0x0, 0x4d1ed0, 0x4d1ed0), at 0xfffffd7ffeaf6dd0 =>[2] str_append(str = 0x4a9120, cstr = (nil)), line 96 in "str.c" [3] client_get_commands_status(client = 0x4d16c0), line 282 in "imap-client.c" [4] client_log_disconnect(client = 0x4d16c0, reason = 0xfffffd7ffee24d80 "Connection closed"), line 322 in "imap-client.c" [5] client_default_destroy(client = 0x4d16c0, reason = (nil)), line 336 in "imap-client.c" [6] client_destroy(client = 0x4d16c0, reason = (nil)), line 263 in "imap-client.c" [7] client_input(client = 0x4d16c0), line 1099 in "imap-client.c" [8] io_loop_call_io(io = 0x5073b0), line 559 in "ioloop.c" [9] io_loop_handler_run_internal(ioloop = 0x4b2580), line 211 in "ioloop-poll.c" [10] io_loop_handler_run(ioloop = 0x4b2580), line 607 in "ioloop.c" [11] io_loop_run(ioloop = 0x4b2580), line 583 in "ioloop.c" [12] master_service_run(service = 0x4b2450, callback = 0x482690 = &`imap`main.c`client_connected(struct master_service_connection *conn)), line 640 in "master-service.c" [13] main(argc = 1, argv = 0xfffffd7fffdffcb8), line 442 in "main.c" (dbx) frame 3 Current function is client_get_commands_status 282 str_append(str, cmd->name); (dbx) print *cmd *cmd = { prev = (nil) next = (nil) client = 0x4d16c0 pool = 0x4d1eb0 tag = (nil) name = (nil) args = (nil) cmd_flags = <unknown enum member 0> func = (nil) context = (nil) module_contexts = { arr = { buffer = 0x4d1f80 element_size = 8U } v = 0x4d1f80 v_modifiable = 0x4d1f80 } parser = 0x4b8f90 state = CLIENT_COMMAND_STATE_WAIT_INPUT start_time = { tv_sec = 0 tv_usec = 0 } start_ioloop_wait_usecs = 0 running_usecs = 0 bytes_in = 0 bytes_out = 0 sync = (nil) uid = 0 cancel = 0 param_error = 0 search_save_result = 0 search_save_result_used = 0 temp_executed = 0 tagline_sent = 0 executing = 0 } (dbx) list 280 str_append(str, " ("); 281 for (cmd = client->command_queue; cmd != NULL; cmd = cmd->next) { 282 str_append(str, cmd->name); 283 if (cmd->next != NULL) 284 str_append_c(str, ','); 285 running_usecs += cmd->running_usecs; 286 bytes_in += cmd->bytes_in; 287 bytes_out += cmd->bytes_out; 288 last_cmd = cmd; 289 } Probably related to these entries in the syslog: Dec 11 16:18:47 mail dovecot: [ID 583609 mail.info] imap-login: Login: user=<perje>, method=PLAIN, rip=81.233.116.192, lip=130.236.160.9, mpid=9238, TLS, session=<CUwE16Am3fhR6X TA> Dec 11 16:18:50 mail dovecot: [ID 583609 mail.info] imap(perje): Connection closed in=196 out=995 Dec 11 16:18:50 mail dovecot: [ID 583609 mail.info] imap(perje): Connection closed in=168 out=5683 Dec 11 16:18:50 mail dovecot: [ID 583609 mail.info] imap(perje): Connection closed in=168 out=4713 Dec 11 16:18:50 mail dovecot: [ID 583609 mail.info] imap(perje): Connection closed in=194 out=1016 Dec 11 16:18:50 mail dovecot: [ID 583609 mail.info] imap(perje): Connection closed in=182 out=970 Dec 11 16:18:50 mail dovecot: [ID 583609 mail.info] imap(perje): Connection closed in=193 out=895 Dec 11 16:18:50 mail dovecot: [ID 583609 mail.info] imap(perje): Connection closed in=196 out=995 Dec 11 16:18:50 mail dovecot: [ID 583609 mail.info] imap(perje): Connection closed in=184 out=894 Dec 11 16:18:51 mail dovecot: [ID 583609 mail.info] imap-login: Login: user=<perje>, method=PLAIN, rip=81.233.116.192, lip=130.236.160.9, mpid=9273, TLS, session=<1uJB16AmtOhR6X TA> Dec 11 16:18:52 mail dovecot: [ID 583609 mail.info] imap-login: Login: user=<perje>, method=PLAIN, rip=81.233.116.192, lip=130.236.160.9, mpid=9278, TLS, session=<kR5Q16AmaOZR6X TA> Dec 11 16:18:52 mail dovecot: [ID 583609 mail.info] imap(perje): Connection closed in=150 out=491 Dec 11 16:23:08 mail dovecot: [ID 583609 mail.info] imap-login: Login: user=<perje>, method=PLAIN, rip=130.236.172.166, lip=130.236.160.9, mpid=10796, TLS, session=<GvSJ5qAms9CC 7Kym> Dec 11 16:23:08 mail dovecot: [ID 583609 mail.info] imap-login: Login: user=<perje>, method=PLAIN, rip=130.236.172.166, lip=130.236.160.9, mpid=10803, TLS, session=<nVqS5qAmttCC 7Kym> Dec 11 16:23:08 mail dovecot: [ID 583609 mail.info] imap(perje): Connection closed in=150 out=491 Dec 11 16:23:13 mail dovecot: [ID 583609 mail.info] imap(perje): Connection closed in=150 out=491 Dec 11 16:24:10 mail dovecot: [ID 583609 mail.crit] imap(perje): Fatal: master: service(imap): child 9006 killed with signal 11 (core dumped) (Would have been nice with a pid number in the syslog output :-) -- [Ll.U] Peter Eriksson KITVS-IFM & ITI-NET IT.LiU.SE +46-70 518 2786

2 1

Error: fcntl(write-lock) locking failed
by Marcin Janowski 16 Dec '15

16 Dec '15

Hello, one month ago I moved my smtp and imap server to other environment with /var/vmail on NFS. After this move i have warnings about too long "Locking transaction log", but today i have errors about "fcntl(write-lock) locking failed ". What this means? This is my dovecot config: # 2.2.9: /etc/dovecot/dovecot.conf doveconf: Warning: service auth { client_limit=1000 } is lower than required under max. load (2000) doveconf: Warning: service anvil { client_limit=1000 } is lower than required under max. load (1603) # OS: Linux 3.19.0-31-generic x86_64 Ubuntu 14.04.3 LTS nfs auth_mechanisms = plain login auth_worker_max_count = 300 default_process_limit = 400 mail_location = maildir:/var/vmail/%d/%n/Maildir mail_plugins = zlib managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = ~/.dovecot.sieve sieve_default = /var/vmail/globalsieverc sieve_dir = ~/sieve } postmaster_address = postmaster(a)smtp.DOMAIN protocols = " imap lmtp sieve pop3" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } } service imap { process_limit = 1024 } ssl_cert = </etc/ssl/private/DOMAIN.crt ssl_key = </etc/ssl/private/DOMAIN.key userdb { args = uid=vmail gid=vmail home=/var/vmail/%d/%n driver = static } protocol lda { mail_plugins = zlib sieve } protocol imap { mail_max_userip_connections = 100 } And this is errors from few day: 2015-12-14 15:33:35 1450103615 Dec 14 15:32:44 smtp-atena dovecot: imap(...): Error: fcntl(write-lock) locking failed for file /var/vmail/.../Maildir/dovecot.index.log: No locks available Dec 14 15:32:44 smtp-atena dovecot: imap(...): Error: mail_index_wait_lock_fd() failed with file /var/vmail/.../Maildir/dovecot.index.log: No locks available 2015-12-14 12:36:35 1450092995 Dec 14 12:36:06 smtp-atena dovecot: imap(...): Error: fcntl(write-lock) locking failed for file /var/vmail/.../Maildir/dovecot.index.log: No locks available Dec 14 12:36:06 smtp-atena dovecot: imap(...): Error: mail_index_wait_lock_fd() failed with file /var/vmail/.../Maildir/dovecot.index.log: No locks available 2015-12-14 12:18:35 1450091915 Dec 14 12:18:25 smtp-atena dovecot: imap(...): Error: fcntl(write-lock) locking failed for file /var/vmail/.../Maildir/dovecot.index.log: No locks available Dec 14 12:18:25 smtp-atena dovecot: imap(...): Error: mail_index_wait_lock_fd() failed with file /var/vmail//Maildir/dovecot.index.log: No locks available Dec 14 12:18:25 smtp-atena dovecot: imap(...): Error: fcntl(write-lock) locking failed for file /var/vmail/.../Maildir/dovecot.index.log: No locks available Dec 14 12:18:25 smtp-atena dovecot: imap(...): Error: mail_index_wait_lock_fd() failed with file /var/vmail/.../Maildir/dovecot.index.log: No locks available 2015-12-14 09:10:35 1450080635 Dec 14 09:10:19 smtp-atena dovecot: imap(...): Error: fcntl(write-lock) locking failed for file /var/vmail/.../Maildir/dovecot.index.cache: No locks available 2015-12-13 13:40:35 1450010435 Dec 13 13:40:06 smtp-atena dovecot: imap(...): Error: fcntl(write-lock) locking failed for file /var/vmail/.../Maildir/dovecot.index.log: No locks available Dec 13 13:40:06 smtp-atena dovecot: imap(...): Error: mail_index_wait_lock_fd() failed with file /var/vmail/.../Maildir/dovecot.index.log: No locks available 2015-12-13 10:48:35 1450000115 Dec 13 10:48:19 smtp-atena dovecot: imap(...): Error: fcntl(write-lock) locking failed for file /var/vmail/.../Maildir/dovecot.index.log: No locks available Dec 13 10:48:19 smtp-atena dovecot: imap(...): Error: mail_index_wait_lock_fd() failed with file /var/vmail/.../Maildir/dovecot.index.log: No locks available 2015-12-12 08:36:35 1449905795 Dec 12 08:36:30 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 60 seconds Dec 12 08:36:31 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 31 seconds 2015-12-12 08:35:35 1449905735 Dec 12 08:35:29 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 60 seconds 2015-12-12 08:34:36 1449905676 Dec 12 08:34:27 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 60 seconds 2015-12-11 11:48:36 1449830916 Dec 11 11:47:48 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 60 seconds 2015-12-11 08:55:35 1449820535 Dec 11 08:55:03 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 90 seconds Dec 11 08:55:33 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 120 seconds Dec 11 08:55:33 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 120 seconds 2015-12-11 08:54:35 1449820475 Dec 11 08:54:33 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 60 seconds 2015-12-11 08:53:35 1449820415 Dec 11 08:53:32 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 60 seconds 2015-12-11 08:52:35 1449820355 Dec 11 08:51:59 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 90 seconds Dec 11 08:51:59 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 90 seconds 2015-12-11 08:51:35 1449820295 Dec 11 08:51:29 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 60 seconds Dec 11 08:51:29 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 60 seconds

2 1

Dovecot SASL and GSSAPI (IPA)
by Ranbir 15 Dec '15

15 Dec '15

Hi Everyone, I'm currently using dovecot SASL in postfix and passwd-file in dovecot for authenticating my users. I want to switch to using IPA instead. I have both the postfix (mailman01) and dovecot (mailman02) servers joined to the IPA domain. I have GSSAPI working in dovecot for IMAP. But, the SASL GSSAPI authentication in postfix fails with this error: warning: unknown[10.200.5.100]: SASL GSSAPI authentication failed: This is what dovecot logs: Dec 12 22:31:54 mailman02 dovecot: auth: Debug: auth client connected (pid=0) Dec 12 22:31:54 mailman02 dovecot: auth: Debug: client in: AUTH 1 GSSAPI service=smtp nologin lip=10.200.9.14 rip=10.200.5.100 secured resp=<hidden> Dec 12 22:31:54 mailman02 dovecot: auth: Debug: gssapi(?,10.200.5.100): Obtaining credentials for smtp(a)mailman02.theinside.rnr Dec 12 22:31:54 mailman02 dovecot: auth: gssapi(?,10.200.5.100): While processing incoming data: Unspecified GSS failure. Minor code may provide more information Dec 12 22:31:54 mailman02 dovecot: auth: gssapi(?,10.200.5.100): While processing incoming data: Wrong principal in request Dec 12 22:31:56 mailman02 dovecot: auth: Debug: client passdb out: FAIL 1 I've tried changing the "smtpd_sasl_local_domain" in postfix's main.cf file to "mailman02.theinside.rnr", but I get the same errors in dovecot and postfix. Right now the config in postfix looks like this: import_environment="KRB5_KTNAME=/etc/postfix/smtp.keytab" smtpd_sasl_local_domain = mailman01.theoutside.rnr Does what I'm trying to do make sense? If so, how do I fix it? Do I have to stop using dovecot sasl in postfix and switch to cyrus sasl? -- Ranbir

2 3

Ideas needed for archiving
by Ben 15 Dec '15

15 Dec '15

I've been asked by a user whether it's possible to stop their IMAP client downloading messages older than a given date. Whilst I'm guessing it may well be possible to do this client-side using folders and subscriptions, it got me thinking .... is there a way to do this server side on dovecot ? i.e. is there a way to "hide" messages from a user without having to archive them off into a seperate account ? thanks

2 2

Released Pigeonhole v0.4.10 for Dovecot v2.2.21
by Stephan Bosch 14 Dec '15

14 Dec '15

Hello Dovecot users, I got a bit stalled by our recent switch to Git, but here is the final v0.4.10 release of Pigeonhole for Dovecot v2.2.21. Nothing of consequence changed since the last RC. Changelog v0.4.10: + Implemented the Sieve mime and foreverypart extensions (RFC 5703). These are fully implemented. The interaction with the editheader extension needs some work, but this should not influence most uses; i.e., changes by the editheader extension are not always visible using foreverypart/mime. + Sieve body extension: Properly implemented the `:text' body transform. It now extracts text for HTML message parts. + Sieve enotify extension: mailto method: Implemented the sieve_notify_mailto_envelope_from setting. This allows configuring the source of the notification sender address for e-mail notifications. This is similar to what already can be configured for redirect. + Added a sieve_enabled (defaults to 'yes') setting that allows explicitly disabling Sieve processing for particular users. This used to be possible by setting `sieve=', but ever since the sieve_before, sieve_after and sieve_default settings were added, this method was not reliable anymore. - variables extension: Fixed handling of empty string by the `:length' set modifier. An empty string yielded an empty string rather than "0". - Fixed memory leak in the Sieve script byte code dumping facility. Extension contexts were never actually freed. - Fixed handling of implicit keep when the last Sieve script is a global one. In that case the implicit keep action was executed in global context, which could mean that trivial (quota) errors ended up in the system log file, rather than the user log file. - doveadm sieve plugin: Fixed crashes caused by incorrect context allocation in the sieve command implementations. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/rc/dovecot-2.2-pigeonhole-0.4.10… http://pigeonhole.dovecot.org/releases/2.2/rc/dovecot-2.2-pigeonhole-0.4.10… 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

2 2

v2.2.21 released
by Timo Sirainen 13 Dec '15

13 Dec '15

http://dovecot.org/releases/2.2/dovecot-2.2.21.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.21.tar.gz.sig Due to a bit bad doveadm bugs in v2.2.20 here's a fixed v2.2.21. Also from this release forward we're finally using git with branches to make new releases. So new releases will have a bit more time to stabilize in the branch before they're being released (while still allowing new features to be developed in the master development branch). We already did something like this for the enterprise releases, but now it's done for community releases as well. - doveadm mailbox list (and some others) were broken in v2.2.20 - director: Fixed making backend changes when running with only a single director server. - virtual plugin: Fixed crash when trying to open nonexistent autocreated backend mailbox.

2 3

2.2.21: doveadm expunge is broken
by Alexander Moisseev 13 Dec '15

13 Dec '15

# doveadm expunge -u user(a)example.com MAILBOX Trash ALL Fatal: expunge: To avoid accidents, each branch in search query must contain something else besides MAILBOX (e.g. just add "all" if you want everything) -- Alexander

2 1

2.2.21: panic in stats-plugin.c: line 324 (stats_user_deinit): assertion failed: (stats_global_user == user)
by Jakub Jankowski 13 Dec '15

13 Dec '15

Hi, I've just upgraded dovecot to 2.2.21 (from 2.2.18), and I'm getting a crash when doing dsync backup: $ dsync -v -u user(a)domain.com backup maildir:/backup/maildirs/domain.com/user/Maildir dsync(user(a)domain.com): Panic: file stats-plugin.c: line 324 (stats_user_deinit): assertion failed: (stats_global_user == user) dsync(user(a)domain.com): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x7e4b4) [0x7f543d3c74b4] -> /usr/lib64/dovecot/libdovecot.so.0(+0x7e529) [0x7f543d3c7529] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f543d372300] -> /usr/lib64/dovecot/lib90_stats_plugin.so(+0x4116) [0x7f543c95a116] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_user_unref+0x35) [0x7f543d68efd5] -> /usr/bin/dsync [shasta(a)toxcorp.com done]() [0x420f90] -> /usr/bin/dsync [user(a)domain.com done](doveadm_mail_try_run+0x28c) [0x421edc] -> /usr/bin/dsync [user(a)domain.com done](main+0x2ff) [0x413a2f] -> /lib64/libc.so.6(__libc_start_main+0xf0) [0x7f543cd80870] -> /usr/bin/dsync [user(a)domain.com done](_start+0x29) [0x413bb9] Aborted This gets logged to syslog when it happens: Dec 13 02:12:33 host dovecot: imap-login: Login: user=<user(a)domain.com>, method=PLAIN, rip=A.B.C.D, lip=A.B.C.D, mpid=1576, TLS Dec 13 02:13:09 host dovecot: stats: Error: Mail server input error: CONNECT: Duplicate session ID 4rqRBSXGbFbDBgAAOpfmEQ for user user(a)domain.com service doveadm It definitely wasn't happening on 2.2.18 (I skipped .19 and .20). Here's my configuration (with some things sanitized): $ dovecot -n # 2.2.21 (5345f22): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.9 (357ac0a0e68b+) # OS: Linux 4.3.2 x86_64 Slackware 14.2 auth_cache_negative_ttl = 1 mins auth_cache_size = 4 k auth_mechanisms = plain login auth_socket_path = /var/run/dovecot/auth-userdb auth_verbose = yes auth_verbose_passwords = sha1 default_vsz_limit = 512 M deliver_log_format = msgid=%m psize=%p vsize=%w: %$ first_valid_gid = 500 first_valid_uid = 500 hostname = host.domain.com last_valid_gid = 500 last_valid_uid = 500 listen = * login_greeting = IMAP server ready. login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c mail_location = mdbox:~/mdbox:ALT=/var/vmail/altmdbox/%Ld/%Ln/altmdbox mail_plugins = " stats" mailbox_list_index = yes managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Spam { special_use = \Junk } mailbox Trash { special_use = \Trash } prefix = separator = / type = private } passdb { args = scheme=CRYPT username_format=%Lu /etc/dovecot/users driver = passwd-file } plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size recipient_delimiter = + sieve = ~/.dovecot.sieve sieve_default = /var/vmail/_sieve/default.sieve sieve_dir = ~/sieve stats_refresh = 30 secs stats_track_cmds = yes } pop3_client_workarounds = outlook-no-nuls postmaster_address = postmaster(a)domain.com protocols = imap pop3 lmtp sieve quota_full_tempfail = yes service auth-worker { user = $default_internal_user } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service dict { unix_listener dict { group = vmail mode = 0660 user = vmail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } service_count = 1 } service imap { process_limit = 128 } service lmtp { inet_listener lmtp { address = 127.0.0.1 port = 2424 } unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } unix_listener lmtp-vmail { group = vmail mode = 0660 user = vmail } } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 1 vsz_limit = 64 M } service managesieve { process_limit = 32 } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service pop3 { process_limit = 64 } service stats { fifo_listener stats-mail { mode = 0600 user = vmail } } ssl_cert = </etc/ssl/certs/cert.pem ssl_key = </etc/ssl/private/key.pem stats_command_min_time = 1 days stats_domain_min_time = 1 days stats_ip_min_time = 1 days stats_memory_limit = 32 M stats_session_min_time = 1 days stats_user_min_time = 1 days userdb { args = uid=vmail gid=vmail home=/var/vmail/mdbox/%Ld/%Ln driver = static } verbose_proctitle = yes protocol lda { mail_plugins = " stats sieve" } protocol imap { mail_max_userip_connections = 20 mail_plugins = " stats imap_stats" } protocol lmtp { mail_plugins = " stats sieve" } $ Let me know if there's anything else that I can provide to help narrowing it down. Cheers, shasta -- Jakub Jankowski|shasta@toxcorp.com|http://toxcorp.com/ GPG: FCBF F03D 9ADB B768 8B92 BB52 0341 9037 A875 942D

2 1

System-user-controllable custom passwords and mail locations
by Michal Petrucha 12 Dec '15

12 Dec '15

Hello everyone, I'd like to set up dovecot so that it uses the standard system accounts, but with different passwords specific to email. Seems like a fairly common setup, but the catch is, I want the users to be able to set their passwords themselves, without needing any assistance from a server administrator. I'm wondering what's the easiest way of implementing this. From what I've understood, this requirement would probably rule out a separate passwd-file (since the standard Linux passwd doesn't seem to support using a custom passwd file), SQL, flat-file dict, and Redis (since you can't give users access only to their row, or dict key; it's either the entire database (or flat file), or nothing). (Of course, I could work around that limitation by writing a C program that I would install as SUID root, which would only change the invoking user's password, but I'd prefer not to start dumping arbitrary SUID binaries all over the place.) So, that would probably only leave me with LDAP, checkpassword, and the FS dict backend. I can imagine how I could get LDAP to do this -- add some extra attribute for each user, and put together a simple script to change passwords, say, in Python, that would bind as the user and write the new password. However, this would require me to store the system user account database in LDAP, which is kind of overkill on at least one of the servers I want this setup on, where I know for certain that there won't ever be more than a handful of users. Checkpassword would probably work, too; perhaps by looking into some file in the user's $HOME or such. I'm not entirely certain about the security, or performance implications of that approach. With the FS dict backend, I could probably point it to a directory, in which every user would own a file containing their password, that no one else could write to. I haven't been able to find any more details about the structure of this directory hierarchy, though, or the contents of the individual files, so I don't know whether this is a viable approach, or not. My questions are, then: Is there some other way of implementing separate passwords that the users can set themselves that I'm overlooking? Is one of the three approaches described above a bad idea for some reason I don't see? Is there some kind of “standard solution” to this problem? The other thing I wanted to ask about is marginally related; I'd like to be able to allow users to customize the layout in which they store their mail. For instance, some users like to have their INBOX as an mbox in /var/mail, and other maildirs in ~/Maildirs/, others prefer having everything as a mix maildirs and mboxes in ~/mail, etc. Looking at the MailLocation wiki page, it seems like the only option, if I want to customize the location per user, is to set it in the userdb, but since we only have system users everywhere, it seems we have to use the passwd userdb, which doesn't support this kind of per-user customization (even on servers where PAM/NSS are configured to use LDAP). Again, am I overlooking something here? Is there nothing similar to ~/.imaprc, which is supported by certain versions of some other IMAP servers? Thanks in advance for any insights, Michal

1 0

Dovecot 1.2.15 and Convert Password Schemes
by Chuck Peters 11 Dec '15

11 Dec '15

Can I convert the password hashes with the older Dovecot? http://wiki2.dovecot.org/HowTo/ConvertPasswordSchemes shows how it can potentially be done with Dovecot 2.1, but when I try it with Dovecot 1.2.15, I'm not seeing a way to make it work. Any suggestions? This is an old Debian 6 system that's overdue for an upgrade. In the test environment upgrading OpenLDAP to Debian 8 I discovered most of our users passwords probably won't work. The hashes appear to be a old Unix DES based hash, ie base64 decoded ldif shows something like the following: userPassword:: {crypt}Aipcuzoh3eiVE Passwords stored in the SSHA hash seem to work fine. If given the password, a shell script could create the hashes with slappasswd and/or a SHA512 hash (using doveadm or mkpasswd) for use on Debian 8. # cat /usr/local/bin/dovecot-environment.sh #!/bin/sh set > /tmp/dovecot-environment exec /usr/lib/dovecot/imap "$@" I can show the /tmp/dovecot-environment if you like, but it's not showing the password as a variable... This system is using Debian's Dovecot package 1.2.15-7+deb6u1. Dovecot 2.1.7-7~bpo60+1 is available as a backport, but I would prefer not to upgrade Dovecot on the production system if I don't need to, or have some other reason such as some features for using IMAP for the migration. https://packages.debian.org/search?keywords=dovecot-common Thanks, Chuck # dovecot -n # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-686-bigmem i686 Debian 6.0.10 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s ssl_cert_file: /etc/lfrr/ca/thishost.crt ssl_key_file: /etc/lfrr/ca/thishost.key disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login verbose_proctitle: yes mail_privileged_group: mail mail_location: mbox:%h:INBOX=/var/mail/%Lu mbox_write_locks: fcntl dotlock mail_executable(default): /usr/local/bin/dovecot-environment.sh mail_executable(imap): /usr/local/bin/dovecot-environment.sh mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 pop3_reuse_xuidl(default): no pop3_reuse_xuidl(imap): no pop3_reuse_xuidl(pop3): yes auth default: mechanisms: plain login debug_passwords: yes passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf passdb: driver: pam args: session=yes dovecot userdb: driver: passwd args: /etc/passwd userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf plugin: quota: dirsize quota_rule: *:storage=204800 I should note, I think the default_pass_scheme = CRYPT doesn't do anything with auth_bind = yes. # grep -v '^ *$#.*$\?$' /etc/dovecot/dovecot-ldap.conf hosts = 127.0.0.1 sasl_bind = no auth_bind = yes auth_bind_userdn = uid=%u,ou=People,dc=ccil,dc=org ldap_version = 3 base = ou=People,dc=ccil,dc=org pass_attrs = uid=user,userPassword=password,homeDirectory=userdb_home,uidNumber=userdb_uid,gidNumber=userdb_gid pass_filter = (&(objectClass=posixAccount)(uid=%u)) default_pass_scheme = CRYPT

1 0

autoexpunge creates special_use folder
by Tom Sommer 11 Dec '15

11 Dec '15

namespace inbox { mailbox Spam { special_use = \Spam auto = create autoexpunge = 30d } } This creates the "Spam" folder in the filesystem on login/logout, even though it shouldn't. If I remove autoexpunge, the folder is not created. -- Tom Sommer

2 1

Have the Dovecot Enterprise Edition packages been discontinued?
by deoren 10 Dec '15

10 Dec '15

Hi, I've been using the Dovecot EE packages for Ubuntu for some time now and just recently started getting 404 errors. Have those packages been discontinued or is this just a temporary issue? Thanks.

3 3

Re: Autoexpunge and special user namespace
by Joseph Tam 09 Dec '15

09 Dec '15

On Wed, 9 Dec 2015, Timo Siraine wrote: >> I'm interested in replacing my cron script that expunges old >> deleted mail with the new feature announced in 2.2.20 >> >>> + Added mailbox { autoexpunge=<time> } setting. See >>> http://wiki2.dovecot.org/MailboxSettings for details. >> >> To use it, I need to specify which mailbox needs them using >> the namespace configuration. For example >> >> namespace inbox { >> mailbox Trash { >> auto = no >> special_use = \Trash >> autoexpunge = 7d >> mailbox_list_index = yes >> } >> ... > > mailbox_list_index=yes is a global setting. You can't have it here. Oh, yes. Thanks for pointing that out. By the way, what does it do? The wiki states mailbox_list_index=yes can help a lot by replying to IMAP STATUS (and similar) lookups from a single index without having to open each mailbox index separately. So it create an uber-index that combines information from individual indices? Are there any drawback to using this? > > 1) Do I need the special_user configuration at all? Will some > > clients start using different mailboxes to store deleted mail > > if I keep the special_use lines? > > special_use is independent of the autoexpunge. I guess it wouldn't > necessarily hurt.. but it's also somewhat better to have only a single > \Trash mailbox so clients don't become confused when more than one of > those mailboxes exist. Got it. Thanks, Timo. Joseph Tam <jtam.home(a)gmail.com>

2 1

Re: EVP_PKEY_get1_EC_KEY:expecting a ec key
by Oliver Riesen-Mallmann 09 Dec '15

09 Dec '15

Hi Teemu, > Could you post your doveconf -n output? # 2.2.20.rc1 (ed41702f14c2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.10.rc1 # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.9 auth_mechanisms = plain login log_timestamp = "%Y-%m-%d %H:%M:%S " login_greeting = Ready. login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k mail_location = maildir:%h/mails mail_plugins = zlib 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 index ihave duplicate mime foreverypart namespace inbox { inbox = yes list = yes location = maildir:%h/mails mailbox Archiv { auto = subscribe special_use = \Archive } mailbox Archives { auto = no special_use = \Archive } mailbox Drafts { auto = create special_use = \Drafts } mailbox "Gelöschte Elemente" { auto = no special_use = \Trash } mailbox Gesendete { auto = no special_use = \Sent } mailbox "Gesendete Elemente" { auto = no special_use = \Sent } mailbox Junk-E-Mail { auto = no special_use = \Junk } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Trash { auto = create special_use = \Trash } prefix = type = private } passdb { driver = shadow } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve zlib_save = gz zlib_save_level = 6 } postmaster_address = postmaster(a)langzeittest.de protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = root } ssl_cert = </etc/dovecot/ssl-cert-langzeittest-plus-cacert.crt ssl_cipher_list = ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_dh_parameters_length = 2048 ssl_key = </etc/dovecot/ssl-cert-langzeittest.key ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv2 !SSLv3 userdb { driver = passwd } protocol lda { mail_plugins = zlib sieve } protocol imap { mail_max_userip_connections = 20 mail_plugins = zlib imap_zlib } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } Regards Oliver

2 3

Sieve script replication glitches
by Apollon Oikonomopoulos 09 Dec '15

09 Dec '15

Hi, I'm running a replicated setup on Debian with Dovecot 2.2.18 and Pigeonhole 0.4.8 and run into some glitches with sieve script syncing. Replication is implemented via DSync/doveadm over SSL. While e-mail replication works as expected, sieve script replication is not always successful. In general I have observed the following behaviour re. sieve script replication: - Sometimes sieve scripts are replicated but have an mtime of 0 (Jan 1 1970) on the destination. - Subsequent updates to these "bad" scripts are not replicated at all. - Sometimes after creating *another* sieve script (which may or may not get the correct timestamp), the "bad" script's timestamp/contents are corrected on the receiving side. The following is a minimal real-world example of what happens (including transaction log entries): 1. On the master create a new sieve script: cat test.sieve | doveadm sieve put -u user(a)example.com test1 Sieve storage on the master: -rw------- 1 vmail vmail 2001 Dec 9 15:53 test1.sieve Transaction log on the master: record: offset=44756, type=attribute-update (ext), size=72, modseq=514 - add: private/vendor/vendor.dovecot/pvt/server/sieve/files/test1 : timestamp=2015-12-09 15:53:28 value_len=0 record: offset=44828, type=modseq-update (ext), size=20 - uid=0 modseq=723 Sieve storage on the slave: -rw------- 1 vmail vmail 2001 Jan 1 1970 test1.sieve Transaction log on the slave: record: offset=55356, type=attribute-update (ext), size=72, modseq=597 - add: private/vendor/vendor.dovecot/pvt/server/sieve/files/test1 : timestamp=2015-12-09 15:53:29 value_len=0 record: offset=55428, type=attribute-update (sync), size=72, modseq=598 - add: private/vendor/vendor.dovecot/pvt/server/sieve/files/test1 : timestamp=2015-12-09 15:53:29 value_len=0 2. Create a new script on the master: cat test.sieve | doveadm sieve put -u user(a)example.com test2 Sieve storage on the master: -rw------- 1 vmail vmail 2001 Dec 9 15:53 test1.sieve -rw------- 1 vmail vmail 2001 Dec 9 15:57 test2.sieve Transaction log on the master: record: offset=44848, type=attribute-update (ext), size=72, modseq=515 - add: private/vendor/vendor.dovecot/pvt/server/sieve/files/test2 : timestamp=2015-12-09 15:57:14 value_len=0 record: offset=44920, type=modseq-update (ext), size=20 - uid=0 modseq=725 record: offset=44940, type=modseq-update (ext), size=20 - uid=0 modseq=728 Sieve storage on the slave: -rw------- 1 vmail vmail 2001 Dec 9 15:53 test1.sieve -rw------- 1 vmail vmail 2001 Dec 9 15:57 test2.sieve Transaction log on the slave: record: offset=55500, type=attribute-update (ext), size=72, modseq=599 - add: private/vendor/vendor.dovecot/pvt/server/sieve/files/test2 : timestamp=2015-12-09 15:57:14 value_len=0 record: offset=55572, type=attribute-update (sync), size=72, modseq=600 - add: private/vendor/vendor.dovecot/pvt/server/sieve/files/test2 : timestamp=2015-12-09 15:57:14 value_len=0 record: offset=55644, type=attribute-update (ext), size=72, modseq=601 - add: private/vendor/vendor.dovecot/pvt/server/sieve/files/test1 : timestamp=2015-12-09 15:57:14 value_len=0 record: offset=55716, type=attribute-update (ext), size=72, modseq=602 - add: private/vendor/vendor.dovecot/pvt/server/sieve/files/test2 : timestamp=2015-12-09 15:57:14 value_len=0 record: offset=55788, type=attribute-update (sync), size=132, modseq=603 - add: private/vendor/vendor.dovecot/pvt/server/sieve/files/test1 : timestamp=2015-12-09 15:53:28 value_len=0 - add: private/vendor/vendor.dovecot/pvt/server/sieve/files/test2 : timestamp=2015-12-09 15:57:14 value_len=0 Apparently something gets messed up on the receiving side and strange things appear in the transaction log (e.g. test1 with a timestamp of 15:57:14 which it never had). The fact that it happens sometimes (around 30-40% of the time) likely indicates a race condition somewhere. Also I'm not at all sure sieve transactions should appear twice on the receiving side (ext and then sync); I see other entries (e.g. ext-intro) as a single "(ext) (sync)" record. Any ideas? Thanks, Apollon doveconf -n output follows: # 2.2.18: /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.8 (0c4ae064f307+) # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.2 auth_mechanisms = plain login default_vsz_limit = 320 M mail_location = mdbox:~/mdbox:ALT=/srv/mail/alt/%d/%n mail_plugins = " acl notify replication 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 index ihave duplicate namespace { location = maildir:/home/vmail/example.com/staging/Maildir:INDEX=/home/vmail/%d/%n/sta… prefix = Staging. subscriptions = no type = public } namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = . type = private } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { acl = vfile sieve = ~/.dovecot.sieve sieve_before = /home/vmail/global.sieve sieve_default = /home/vmail/global.sieve sieve_dir = ~/sieve } protocols = " imap sieve" service aggregator { fifo_listener replication-notify-fifo { user = vmail } unix_listener replication-notify { user = vmail } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0777 } } service doveadm { inet_listener { port = 12345 ssl = yes } vsz_limit = 1 G } service imap-login { process_limit = 500 process_min_avail = 5 } service imap-postlogin { executable = script-login /usr/local/sbin/ldap-postlogin user = $default_internal_user } service imap { executable = imap imap-postlogin process_limit = 1024 } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 user = vmail } } ssl_cert = </etc/ssl/certs/dovecot.crt ssl_client_ca_dir = /etc/ssl/certs ssl_key = </etc/ssl/private/dovecot.key userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol lda { log_path = /var/log/dovecot/deliver.log mail_plugins = sieve replication notify } protocol imap { mail_max_userip_connections = 500 }

1 0

v2.2.20 released
by Timo Sirainen 09 Dec '15

09 Dec '15

http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz.sig This could be (one of) the last v2.2.x release. We're starting v2.3 development soon. + Added mailbox { autoexpunge=<time> } setting. See http://wiki2.dovecot.org/MailboxSettings for details. + ssl_options: Added support for no_ticket + imap/pop3/managesieve-login: Added postlogin_socket=path passdb extra field. This allows replacing the default service imap/pop3/managesieve {} settings for specific users (e.g. running their imap process via valgrind or strace). + doveadm fetch: Added date.sent/received/saved.unixtime + fs-posix: Added mode=auto parameter to set the created files' and directories' mode based on the parent dir if it has setgid-bit. + director: Support backends having hostnames, which makes it possible to verify their SSL certificates. - director: Directors' state became desynchronized if doveadm director commands were used to modify the same backend in multiple directors at the same time with conflicting changes. This fix includes some extra checks, which makes sure that if such a conflict still happens it's automatically fixed. In some situations such an automatic fix may now be unnecessarily triggered and an error logged. - director: Backend tags weren't working correctly. - ldap: tls_* settings weren't used for ldaps URIs. - ldap, mysql: Fixed setting connect timeout. - auth: userdb lookups via auth-worker couldn't change username - dsync: Fixed handling deleted directories. Make sure we don't go to infinite mailbox renaming loop. - imap: Fixed crash in NOTIFY when there were watched namespaces that didn't support NOTIFY. - imap: After SETMETADATA was used, various commands (especially FETCH) could have started hanging when their output was large. - stats: Idle sessions weren't refreshed often enough, causing stats process to forget them and log errors about unknown sessions when they were updated later. - stats: Fixed "Duplicate session ID" errors when LMTP delivered to multiple recipients and fts_autoindex=yes. - zlib plugin: Fixed copying causing cache corruption when zlib_save wasn't set, but the source message was compressed. - fts-solr: Fixed escaping Solr query parameters. - lmtp: quota_full_tempfail=yes was ignored with lmtp_rcpt_check_quota=yes

9 12

core-dump in imap (Dovecot 2.2.19)
by Peter Eriksson 09 Dec '15

09 Dec '15

Just found a coredump from the imap process for one of our users on dovecot 2.2.19 on a Solaris 10/x86 system: > Dec 8 14:33:17 mail dovecot: [ID 583609 mail.crit] imap(leijo): Fatal: master: service(imap): child 14465 killed with signal 11 (core dumped) Please find attached dovecot -n output and some gdb backtrace. It seems that cmd->client was NULL when dereferencing it at line 178 in imap-commands.c (in the function command_exec): > 178 cmd->bytes_in += i_stream_get_absolute_offset(cmd->client->input) - > 179 cmd_start_bytes_in; Please let me know if you need more information. I don't know what the users was doing at that specific time. --- [Ll.U] Peter Eriksson KITVS-IFM & ITI-NET IT.LiU.SE +46-70 518 2786

2 1

Autoexpunge and special user namespace
by Joseph Tam 09 Dec '15

09 Dec '15

I'm interested in replacing my cron script that expunges old deleted mail with the new feature announced in 2.2.20 > + Added mailbox { autoexpunge=<time> } setting. See > http://wiki2.dovecot.org/MailboxSettings for details. To use it, I need to specify which mailbox needs them using the namespace configuration. For example namespace inbox { mailbox Trash { auto = no special_use = \Trash autoexpunge = 7d mailbox_list_index = yes } mailbox trash { auto = no special_use = \Trash autoexpunge = 7d mailbox_list_index = yes } mailbox "Deleted Messages" { auto = no special_use = \Trash autoexpunge = 7d mailbox_list_index = yes } mailbox "Deleted Items" { auto = no special_use = \Trash autoexpunge = 7d mailbox_list_index = yes } ... } Different readers use different mailboxes, so I include the common ones. Some questions: 1) Do I need the special_user configuration at all? Will some clients start using different mailboxes to store deleted mail if I keep the special_use lines? 2) I also expunge old mail in INBOX marked as deleted -- is there any way to handle this case? Create virtual mailbox? Joseph Tam <jtam.home(a)gmail.com>

2 1

v2.2.20 release candidate released
by Timo Sirainen 08 Dec '15

08 Dec '15

http://dovecot.org/releases/2.2/rc/dovecot-2.2.20.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.20.rc1.tar.gz.sig v2.2.20 probably will be released tomorrow or maybe during weekend. + Added mailbox { autoexpunge=<time> } setting. See http://wiki2.dovecot.org/MailboxSettings for details. + ssl_options: Added support for no_ticket + imap/pop3/managesieve-login: Added postlogin_socket=path passdb extra field. This allows replacing the default service imap/pop3/managesieve {} settings for specific users (e.g. running their imap process via valgrind or strace). + doveadm fetch: Added date.sent/received/saved.unixtime + fs-posix: Added mode=auto parameter to set the created files' and directories' mode based on the parent dir if it has setgid-bit. + director: Support backends having hostnames, which makes it possible to verify their SSL certificates. - director: Directors' state became desynchronized if doveadm director commands were used to modify the same backend in multiple directors at the same time with conflicting changes. This fix includes some extra checks, which makes sure that if such a conflict still happens it's automatically fixed. In some situations such an automatic fix may now be unnecessarily triggered and an error logged. - director: Backend tags weren't working correctly. - ldap: tls_* settings weren't used for ldaps URIs. - ldap, mysql: Fixed setting connect timeout. - auth: userdb lookups via auth-worker couldn't change username - dsync: Fixed handling deleted directories. Make sure we don't go to infinite mailbox renaming loop. - imap: Fixed crash in NOTIFY when there were watched namespaces that didn't support NOTIFY. - imap: After SETMETADATA was used, various commands (especially FETCH) could have started hanging when their output was large. - stats: Idle sessions weren't refreshed often enough, causing stats process to forget them and log errors about unknown sessions when they were updated later. - stats: Fixed "Duplicate session ID" errors when LMTP delivered to multiple recipients and fts_autoindex=yes. - zlib plugin: Fixed copying causing cache corruption when zlib_save wasn't set, but the source message was compressed. - fts-solr: Fixed escaping Solr query parameters.

6 11

Which mail does a certain attachment belong to?
by Ralf Hildebrandt 08 Dec '15

08 Dec '15

I'm seeing this: ./17/3c/173c81da2aab91f225f8eb5e8fcc87119be4eff0-b38d990442316a54a90c00008f4649af: SecuriteInfo.com.TR.Kryptik.180736.5155.16748.22498.UNOFFICIAL FOUND ./17/3c/173c81da2aab91f225f8eb5e8fcc87119be4eff0-bc70851b03216a54483f00008f4649af: SecuriteInfo.com.TR.Kryptik.180736.5155.16748.22498.UNOFFICIAL FOUND When scanning the "attachments" directory of my mdbox. How can I find out WHICH EMAIL these two attachments belong to? mail_location = mdbox:~/mdbox mail_plugins = zlib fts fts_lucene mdbox_rotate_size = 128M mdbox_rotate_interval = 0 mail_attachment_dir = /some/path/attachments mail_attachment_min_size = 128k mail_attachment_fs = sis posix mail_attachment_hash = %{sha1} -- [*] 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

3 2

Released Pigeonhole v0.4.10.rc2 for Dovecot v2.2.20
by Stephan Bosch 08 Dec '15

08 Dec '15

Hello Dovecot users, Here's the Pigeonhole RC that goes with Dovecot v2.2.20. Due to the earlier described conflict, RC1 will not compile with the new Dovecot release. I am not really in hurry to make a definitive release of Pigeonhole, since v0.4.9 still compiles fine with Dovecot v2.2.20. Still, if no big bugs emerge in the next few days, I will make a final release. So, please test this new RC and especially the new features. Changelog v0.4.10: + Implemented the Sieve mime and foreverypart extensions (RFC 5703). These are fully implemented. The interaction with the editheader extension needs some work, but this should not influence most uses; i.e., changes by the editheader extension are not always visible using foreverypart/mime. + Sieve body extension: Properly implemented the `:text' body transform. It now extracts text for HTML message parts. + Sieve enotify extension: mailto method: Implemented the sieve_notify_mailto_envelope_from setting. This allows configuring the source of the notification sender address for e-mail notifications. This is similar to what already can be configured for redirect. + Added a sieve_enabled (defaults to 'yes') setting that allows explicitly disabling Sieve processing for particular users. This used to be possible by setting `sieve=', but ever since the sieve_before, sieve_after and sieve_default settings were added, this method was not reliable anymore. - variables extension: Fixed handling of empty string by the `:length' set modifier. An empty string yielded an empty string rather than "0". - Fixed memory leak in the Sieve script byte code dumping facility. Extension contexts were never actually freed. - Fixed handling of implicit keep when the last Sieve script is a global one. In that case the implicit keep action was executed in global context, which could mean that trivial (quota) errors ended up in the system log file, rather than the user log file. - doveadm sieve plugin: Fixed crashes caused by incorrect context allocation in the sieve command implementations. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/rc/dovecot-2.2-pigeonhole-0.4.10… http://pigeonhole.dovecot.org/releases/2.2/rc/dovecot-2.2-pigeonhole-0.4.10… 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

EVP_PKEY_get1_EC_KEY:expecting a ec key
by Oliver Riesen-Mallmann 07 Dec '15

07 Dec '15

Hi, since my last update from the Dovecot Prebuilt Binary for Debian I get a lot of messages like this in mail.log: dovecot: imap-login: Error: SSL: Stacked error: error:0608308E:digital envelope routines:EVP_PKEY_get1_EC_KEY:expecting a ec key Nevertheless Dovecot seems to work normally. Email client doesn't mention any error. This was my last update: Start-Date: 2015-12-04 14:00:31 Commandline: apt-get upgrade Upgrade: dovecot-core:amd64 (2.2.19-1~auto+98, 2.2.20~rc1-1~auto+3), dovecot-managesieved:amd64 (2.2.19-1~auto+98, 2.2.20~rc1-1~auto+3), dovecot-sieve:amd64 (2.2.19-1~auto+98, 2.2.20~rc1-1~auto+3), dovecot-imapd:amd64 (2.2.19-1~auto+98, 2.2.20~rc1-1~auto+3), dovecot-pop3d:amd64 (2.2.19-1~auto+98, 2.2.20~rc1-1~auto+3), openssl:amd64 (1.0.1e-2+deb7u17, 1.0.1e-2+deb7u18), libssl1.0.0:amd64 (1.0.1e-2+deb7u17, 1.0.1e-2+deb7u18) End-Date: 2015-12-04 14:00:53 My current Dovecot version: 2.2.20.rc1 (0b81127e53da) on Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.68-1+deb7u1 x86_64 Is it a bug in Dovecot or in openssl/libssl? Regards Oliver

2 1

Dovecot cluster using GlusterFS
by Filip Pytloun 07 Dec '15

07 Dec '15

Hello, I have recently setup mailserver solution using 2-node master-master setup (mainly based on MySQL M-M replication and GlusterFS with 2 replica volume) on Ubuntu 14.04 (Dovecot 2.2.9). Unfortunately even with shared-storage-aware setting: mail_nfs_index = yes mail_nfs_storage = yes mail_fsync = always mmap_disable = yes ..I have hit strange issues pretty soon especially when user was manipulating same mailbox from multiple devices at the same time. Most issues was about corrupted indexes which was solved easily by just putting them on local storage of each node: mail_location = maildir:/srv/mail/%d/%u:INDEX=/var/lib/dovecot/index/%d/%u But I still hit issues like this one: dovecot: lmtp(6276, user(a)example.com) Error: Broken file /srv/mail/example.com/user(a)example.com/dovecot-uidlist line 8529: UIDs not ordered (8527 >= 8527) Which I am not sure how serious it is or if it's possible to solve or workaround? Anyway because of the above and high possibility of GlusterFS split-brains, I have decided to setup Dovecot Director according to the docs [1] but I have a couple of questions: - is custom monitoring still required? Poolmon [2] is 4 year old so I would suppose there's some progress since that? - it's not possible to have same backends and directors in Dovecot <2.2.17. I can backport newer Dovecot for Ubuntu Trusty, so this is not an issue, but.. - documentation states that it still doesn't work for LMTP [3]? Which is probably important for my setup, because both Postfix servers are using dovecot-lmtp for mail delivery so there can be still some issues (but probably less frequent?) when both servers will deliver new mails for one user at once. So do I really have to split directors from backends? Anyone has experience with clustered Dovecot setup? Why is Dovecot behaving so bad when it pretends to be shared storage friendly? Are these issues only specific for older Dovecot? Or is there something wrong in my architecture design? Thanks for any help, Filip --- [1] http://wiki2.dovecot.org/Director [2] https://github.com/brandond/poolmon/ [3] "LMTP however doesn't currently support mixing recipients to both being proxied and store locally." --- BTW if someone is interested in SaltStack, here are Salt formulas for Dovecot + Postfix + GlusterFS + Roundcube + Mailman setup which we are using: https://github.com/tcpcloud/salt-formula-dovecot https://github.com/tcpcloud/salt-formula-postfix https://github.com/tcpcloud/salt-formula-roundcube https://github.com/tcpcloud/salt-formula-glusterfs

6 7

mmap_disable=yes not honored always
by Peter Benko 06 Dec '15

06 Dec '15

<Sorry for the resend, it seems that the formatting of my original mail got garbled> Hi all, I'm experimenting with having the mail store on a 9p file system that lacks mmap() functionality. So I disabled it in dovecot: mmap_disable = yes However, I keep getting the following error messages in my log: Oct 15 16:55:00 computer-name dovecot: imap user(a)domain.com[192.168.1.3] Error: mmap() failed with file /mail/mailboxes/domain.com/user/indexpvt-accounts/other-user/mailboxes/INBOX/dovecot.index.pvt.log: Invalid argument I only get those messages for the shared folder's private indexes. This setup works perfectly on an ext2/3/4 fs. Any opinions, is this a bug? Is mmap_disable not mandatory for all operations? Best regards, Peter

2 1

[PATCH] [dovecot 2.2.9] Quota warnings ignored with FS quotas
by Grzegorz Nosek 06 Dec '15

06 Dec '15

Hi all, I noticed that in some circumstances quota warnings are ignored. The bug arises when both of the following are used: 1. percentage-based quota warnings, i.e.: quota_warning = storage=1%% quota-warning 1 %u 2. filesystem quota backend (and probably others, except for quotas configured directly in dovecot config) Percentage-based quota warnings have rule.bytes_limit recalculated based on root_set->default_rule.bytes_limit, however this value is zero when FS quotas are in use. Real quota values (from quotactl) are fetched very late, in quota_warnings_execute() but at that point no recalculation happens. As the warning rules have bytes_limit==0, they're effectively ignored. The patch below enables quota warnings to be sent when using filesystem (and possibly maildirsize-based) quotas. Based and tested on Ubuntu 14.04's dovecot 2.2.9. Best regards, Grzegorz Nosek diff --git a/src/plugins/quota/quota.c b/src/plugins/quota/quota.c index adbd70d..8e4d7e0 100644 --- a/src/plugins/quota/quota.c +++ b/src/plugins/quota/quota.c @@ -1163,6 +1163,8 @@ static void quota_warnings_execute(struct quota_transaction_context *ctx, &count_current, &count_limit) < 0) return; + quota_root_recalculate_relative_rules(root->set, bytes_limit, count_limit); + bytes_before = bytes_current - ctx->bytes_used; count_before = count_current - ctx->count_used; for (i = 0; i < count; i++) {

3 3

SIS attachments compressed
by Juan Carlos Sanchez 06 Dec '15

06 Dec '15

Hello: In case it is defined to use zlib compression, does SIS save attachments compressed? I have found this question replied in the past (2012) and the answer was NO. I ask again just to know if there have been changes or if it is in the roadmap to add compression. I have been testing to migrate from maildir+zlib to mdbox+zlib+sis and the results, in terms of space used, and worst than using just mdbox+zlib (without SIS), and suppose the reason in the lack of compression in attachments. Thanks in advance. -- ------------------------------------------------------ Juan Carlos Sanchez Hernandez Responsable de Seguridad y Correo Electronico Servicio de Planificacion Informatica y Comunicaciones Universidad Politecnica de Madrid Rectorado Avda. Ramiro de Maeztu 7 28040 Madrid ------------------------------------------------------

2 1

[Dovecot] lmtp_rcpt_check_quota not working
by Bernhard Schmidt 06 Dec '15

06 Dec '15

Hi, Dovecot 2.2.9 (Debian package from backports) does not seem to respect lmtp_rcpt_check_quota # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.4 deliver_log_format = from=<%e>, size=%p, message-id=<%m>, status=%$ disable_plaintext_auth = no lmtp_rcpt_check_quota = yes mail_debug = yes mail_gid = mstore mail_location = maildir:~/Maildir:INDEX=/var/cache/dovecot/index/%-1.1u/%u mail_plugins = quota mail_uid = mstore managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave mmap_disable = yes namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = INBOX. separator = . type = private } passdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } plugin { quota = maildir quota_rule = ?:storage=512M quota_rule2 = INBOX.Trash:ignore quota_status_nouser = DUNNO quota_status_overquota = 452 4.2.2 Mailbox is full quota_status_success = DUNNO quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=85%% quota-warning 85 %u sieve = ~/currently-active-script.sieve sieve_dir = ~/sieve } pop3_uidl_format = %08Xv%08Xu protocols = imap lmtp sieve pop3 quota_full_tempfail = yes service anvil { client_limit = 3000 unix_listener anvil { group = sudo mode = 0660 } } service auth { client_limit = 3000 unix_listener auth-userdb { group = mstore mode = 0660 user = mstore } } service imap-login { client_limit = 1024 inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_limit = 2500 process_min_avail = 4 service_count = 0 } service lmtp { inet_listener lmtp { address = xxx port = 24 } } service managesieve-login { inet_listener sieve { port = 2000 } service_count = 1 } service managesieve { process_limit = 1024 } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service quota-status { client_limit = 5 executable = quota-status -p postfix inet_listener { address = xxx port = 12340 } } service quota-warning { executable = script /etc/dovecot/quotawarnmsg.sh unix_listener quota-warning { user = mstore } user = mstore } ssl_cert = </etc/dovecot/dovecot.pem ssl_key = </etc/dovecot/private/dovecot.pem userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } verbose_proctitle = yes protocol imap { mail_plugins = quota imap_quota imap_zlib } protocol lda { mail_plugins = quota sieve } protocol lmtp { mail_plugins = quota sieve } so Dovecot should reject in RCPT TO phase, but according to the logs of the upstream Postfix it does so after END-OF-DATA (host xxx[2001:xxx] said: 452 4.2.2 <user(a)domain.de> Quota exceeded (mailbox for user is full) (in reply to end of DATA command)) I haven't seen any commits regarding to this in 2.2.10 or tip. Regards, Bernhard

3 6

Dovecot 2.2.18.2: Panic: file fs-api.c: line 756 (fs_copy): assertion failed: (src->fs == dest->fs)
by Frank Mehrtens 06 Dec '15

06 Dec '15

Hello, a colleague found some strange messages in the logs: Oct 27 13:08:43 mail postfix/qmgr[1618]: E83C8180F56: from=<user1(a)domain.de>, size=298937, nrcpt=2 (queue active) Oct 27 13:08:43 mail dovecot: lmtp(6740): Connect from local Oct 27 13:08:43 mail dovecot: lmtp(user2(a)domain.de): gYFbBEdpL1ZUGgAA0nA0dQ: message-id=<035901d110b0$3929bc20$ab7d3460$(a)domain.de>: saved mail to INBOX (from: user1(a)domain.de, subject: WG: Matthias, size: 295392) Oct 27 13:08:43 mail postfix/lmtp[6702]: E83C8180F56: to=<user2(a)domain.de>, relay=mail.domain.de[private/dovecot-lmtp], delay=0.41, delays=0.36/0/0/0.05, dsn=2.0.0, status=sent (250 2.0.0 <user2(a)domain.de> gYFbBEdpL1ZUGgAA0nA0dQ Saved) Oct 27 13:08:43 mail dovecot: lmtp(mailarchiv(a)domain.de): Panic: file fs-api.c: line 756 (fs_copy): assertion failed: (src->fs == dest->fs) Oct 27 13:08:43 mail dovecot: lmtp(mailarchiv(a)domain.de): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x7b53a) [0x7f10419e553a] -> /usr/lib64/dovecot/libdovecot.so.0(+0x7b5a6) [0x7f10419e55a6] -> /usr/lib64/dovecot/libdovecot.so.0(+0x281ea) [0x7f10419921ea] -> /usr/lib64/dovecot/libdovecot.so.0(+0x3163a) [0x7f104199b63a] -> /usr/lib64/dovecot/libdovecot-storage.so.0(sdbox_copy+0x4c4) [0x7f1041cbad94] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_copy+0x7a) [0x7f1041c9f37a] -> /usr/lib64/dovecot/libdovecot-lda.so.0(mail_deliver_save+0x1a7) [0x7f1041f891b7] -> /usr/lib64/dovecot/libdovecot-lda.so.0(mail_deliver+0x11b) [0x7f1041f8956b] -> dovecot/lmtp() [0x406922] -> dovecot/lmtp() [0x40730d] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x5b) [0x7f10419f7fbb] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xaf) [0x7f10419f918f] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x9) [0x7f10419f8049] -> /usr/lib64/dovecot/libdovec ot.so.0(io_loop_run+0x38) [0x7f10419f80c8] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f1041997043] -> dovecot/lmtp(main+0x18b) [0x404dbb] -> /lib64/libc.so.6(__libc_start_main+0xfd) [0x7f10415f4d5d] -> dovecot/lmtp() [0x404b49] Oct 27 13:08:43 mail dovecot: lmtp(mailarchiv(a)domain.de): Fatal: master: service(lmtp): child 6740 killed with signal 6 (core dumps disabled) Oct 27 13:08:43 mail postfix/lmtp[6702]: E83C8180F56: to=<mailarchiv(a)domain.de>, relay=mail.domain.de[private/dovecot-lmtp], delay=0.41, delays=0.36/0/0/0.05, dsn=4.4.2, status=deferred (lost connection with mail.domain.de[private/dovecot-lmtp] while sending end of data -- message may be sent more than once) Postfix always_bcc set to mailarchiv(a)domain.de. [root@mail ~]# rpm -qa | grep dove dovecot-ee-2.2.18.2-1.el6.x86_64 dovecot-ee-managesieve-0.4.8-1.el6.x86_64 dovecot-ee-pigeonhole-0.4.8-1.el6.x86_64 [root@mail ~]# doveconf -n # 2.2.18.2 (866bffbafde7): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.8 (73d4f6cd676a) # OS: Linux 2.6.32-573.7.1.el6.x86_64 x86_64 CentOS release 6.7 (Final) ext4 auth_cache_negative_ttl = 0 auth_mechanisms = plain login deliver_log_format = message-id=%m: %$ (from: %f, subject: %s, size: %p) dict { quota = pgsql:/etc/dovecot/dovecot-dict-sql.conf.ext } disable_plaintext_auth = no imap_client_workarounds = tb-extra-mailbox-sep mail_attachment_dir = /storage/mail/attachments mail_attachment_hash = %{sha512} mail_gid = vmail mail_location = sdbox:/storage/mail/%d/%n mail_plugins = acl quota mail_uid = vmail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate namespace { list = children location = sdbox:/storage/mail/%%d/%%n/ prefix = shared/%%u/ separator = / subscriptions = no type = shared } namespace { list = children location = maildir:/storage/mail/public:INDEX=/storage/mail/%d/%n/public prefix = public/ separator = / subscriptions = no type = public } namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox "Gelöschte Objekte" { special_use = \Trash } mailbox "Gesendete Objekte" { special_use = \Sent } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = subscriptions = yes type = private } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { acl = vfile acl_shared_dict = file:/storage/mail/shared-mailboxes sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } service dict { unix_listener dict { group = vmail mode = 0660 user = vmail } } service imap-login { inet_listener imaps { ssl = yes } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } service pop3-login { inet_listener pop3s { ssl = yes } } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = acl quota sieve } protocol imap { mail_plugins = acl quota imap_acl imap_quota } Best regards Frank -- DECOIT GmbH Fahrenheitstraße 9 D-28359 Bremen Tel.: +49-421-596064-0 Fax: +49-421-596064-09 E-Mail: info(a)decoit.de <mailto:info@decoit.de> Web: http://www.decoit.de <http://www.decoit.de/> Amtsgericht Bremen, HRB 21533 Geschäftsführer: Prof. Dr.-Ing. Kai-Oliver Detken

2 1

mailbox_list_index and maildir_very_dirty_syncs are in conflicts?
by Alessio Cecchi 06 Dec '15

06 Dec '15

Hi, I’m running Dovecot 2.2.19 with Maildir as storage and LDA for delivery. I noticed that if I set mailbox_list_index=yes and maildir_very_dirty_syncs=yes when I login via IMAP the STATUS command don’t “see” new messages in sub-folders (like Spam). Example, a new message as arrived in Spam folder (I can see in Maildir/new/) but IMAP STATUS don’t see it: . STATUS Spam (MESSAGES UNSEEN) * STATUS Spam (MESSAGES 139 UNSEEN 0) (in this case the date of “dovecot.list.index” files is not updated) If I comment out mailbox_list_index=yes or maildir_very_dirty_syncs=yes I can see the new message: . STATUS Spam (MESSAGES UNSEEN) * STATUS Spam (MESSAGES 140 UNSEEN 1) (in this case the date of “dovecot.list.index” files is updated after the STATUS command) Instead the SELECT command works fine always. An importante note, my dovecot LDA configuration (on MX servers) don’t update index files: protocol lda { mail_location = maildir:~/Maildir:INDEX=MEMORY mail_plugins = quota acl expire fts fts_solr zlib sieve } These because I need to filter incoming email via Sieve but since I cannot use LMTP (and Director) on MX (but I have Director for POP/IMAP access) the only way for not corrupting dovecot.index files is not update their on delivery emails. But reading http://wiki2.dovecot.org/MailLocation/Maildir this shouldn’t be a problem (Optimizations “maildir_very_dirty_syncs=yes” … It's still safe to deliver new mails to new/ …) since MX deliver new emails in new/. Is a Dovecot limit or is a problem of my configuration? Thanks my configuration: # 2.2.19 # Pigeonhole version 0.4.9 auth_cache_negative_ttl = 5 mins auth_cache_size = 10 M auth_cache_ttl = 20 mins auth_master_user_separator = * auth_worker_max_count = 50 deliver_log_format = msgid=%m, from=%f, subject="%s": %$ dict { acl = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext expire = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext sqlquota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } disable_plaintext_auth = no first_valid_gid = 89 first_valid_uid = 89 imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags imap_idle_notify_interval = 29 mins imap_logout_format = in=%i out=%o session=<%{session}> last_valid_gid = 89 last_valid_uid = 89 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes listen = 10.96.3.156 login_trusted_networks = 10.0.0.0/24 mail_fsync = always mail_location = maildir:~/Maildir mail_plugins = quota acl expire fts fts_solr zlib mailbox_list_index = yes maildir_very_dirty_syncs = yes managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate vnd.dovecot.duplicate mmap_disable = yes namespace { list = children location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u prefix = shared/%%n/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / } passdb { args = /etc/dovecot/dovecot-deny-sql.conf.ext deny = yes driver = sql } passdb { args = /etc/dovecot/extra/master-users driver = passwd-file master = yes pass = yes } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { acl = vfile acl_shared_dict = proxy::acl antispam_backend = mailtrain antispam_mail_notspam = --ham antispam_mail_sendmail = /usr/bin/sa-learn antispam_mail_spam = --spam antispam_spam = Spam antispam_trash = Trash expire = Trash expire2 = Spam expire_dict = proxy::expire fts = solr fts_solr = url=http://10.0.0.1:8983/solr/ quota = maildir:UserQuota quota2 = dict:Quota Usage::noenforcing:proxy::sqlquota quota_grace = 10M quota_rule2 = Trash:storage=+100M quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = ~/.dovecot.sieve sieve_before = /etc/dovecot/sieve/before.sieve sieve_dir = ~/sieve sieve_extensions = +vnd.dovecot.duplicate -vacation zlib_save = gz zlib_save_level = 6 } pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_fast_size_lookups = yes pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s, bytes=%i/%o, session=<%{session}> protocols = imap pop3 sieve sendmail_path = /var/qmail/bin/sendmail service auth { client_limit = 6524 unix_listener auth-userdb { group = vchkpw mode = 0660 user = vpopmail } } service dict { process_limit = 500 unix_listener dict { group = vchkpw mode = 0660 user = vpopmail } } service imap-login { process_min_avail = 4 service_count = 0 } service imap-postlogin { executable = script-login /etc/dovecot/scripts/imap-postlogin.sh unix_listener imap-postlogin { group = vchkpw mode = 0660 user = vpopmail } user = vpopmail } service imap { executable = imap imap-postlogin process_limit = 5000 service_count = 100 vsz_limit = 384 M } service managesieve-login { inet_listener sieve { port = 4190 } } service pop3-login { process_min_avail = 4 service_count = 0 } service pop3-postlogin { executable = script-login /etc/dovecot/scripts/pop3-postlogin.sh unix_listener pop3-postlogin { group = vchkpw mode = 0660 user = vpopmail } user = vpopmail } service pop3 { executable = pop3 pop3-postlogin process_limit = 1024 service_count = 100 } service quota-warning { executable = script /etc/dovecot/scripts/quota-warning.sh unix_listener quota-warning { user = vpopmail } user = vpopmail } ssl_cert = </etc/dovecot/ssl/wildcard.pem ssl_key = </etc/dovecot/ssl/wildcard.key ssl_protocols = !SSLv2 !SSLv3 submission_host = 127.0.0.1 userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } verbose_proctitle = yes protocol lda { mail_location = maildir:~/Maildir:INDEX=MEMORY mail_plugins = quota acl expire fts fts_solr zlib sieve } protocol imap { mail_max_userip_connections = 25 mail_plugins = quota acl expire fts fts_solr zlib imap_quota imap_acl imap_zlib } protocol sieve { mail_max_userip_connections = 2 } protocol pop3 { mail_max_userip_connections = 5 } -- Alessio Cecchi Postmaster AT http://www.qboxmail.it http://www.linkedin.com/in/alessice

2 1

ACL Troubles
by Bobber 06 Dec '15

06 Dec '15

Using dovecot version 2.2.19. In the config file I have the following to set up acls: > mail_plugins = $mail_plugins acl > protocol imap { > mail_plugins = $mail_plugins imap_acl > } > plugin { > acl = vfile:/usr/local/etc/dovecot/acls:cache_secs=300 > } And here's my acl file: > * anyone rl I am getting the following error in the dovecot log file: > Error: Global ACL file /usr/local/etc/dovecot/acls line 1: Unknown ID 'anyone rl' Also, my subfolders in the shared mailbox area are no longer visible or accessible. Any ideas what I am doing wrong? -- *Bob Wooldridge* Blog: http://kc0dxf.net/blog/

2 1

LIST MANAGEMENT BROKEN
by Edwardo Garcia 06 Dec '15

06 Dec '15

Timo I have for two days try to unsubscribe from this list using email mailman. The list server does not send me confirmation request. Please fix your server and remove me

2 1

Released Pigeonhole v0.4.10.rc1 for Dovecot v2.2.20.rc1
by Stephan Bosch 05 Dec '15

05 Dec '15

Hello Dovecot users, Here's the Pigeonhole RC that goes with the Dovecot RC. There is a conflict with the t_str_trim() function. To be able to quickly release Dovecot, Timo has reverted the involved change so that 0.4.9 will still compile with the final Dovecot v2.2.20 release. This Pigeonhole RC will therefore not compile against the final Dovecot release (only against v2.2.20.rc1), which I will mend quickly once Dovecot v2.2.20 is released. Changelog v0.4.10.rc1: + Implemented the Sieve mime and foreverypart extensions (RFC 5703). These are fully implemented. The interaction with the editheader extension needs some work, but this should not influence most uses; i.e., changes by the editheader extension are not always visible using foreverypart/mime. + Sieve body extension: Properly implemented the `:text' body transform. It now extracts text for HTML message parts. + Sieve enotify extension: mailto method: Implemented the sieve_notify_mailto_envelope_from setting. This allows configuring the source of the notification sender address for e-mail notifications. This is similar to what already can be configured for redirect. + Added a sieve_enabled (defaults to 'yes') setting that allows explicitly disabling Sieve processing for particular users. This used to be possible by setting `sieve=', but ever since the sieve_before, sieve_after and sieve_default settings were added, this method was not reliable anymore. - variables extension: Fixed handling of empty string by the `:length' set modifier. An empty string yielded an empty string rather than "0". - Fixed memory leak in the Sieve script byte code dumping facility. Extension contexts were never actually freed. - Fixed handling of implicit keep when the last Sieve script is a global one. In that case the implicit keep action was executed in global context, which could mean that trivial (quota) errors ended up in the system log file, rather than the user log file. - doveadm sieve plugin: Fixed crashes caused by incorrect context allocation in the sieve command implementations. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/rc/dovecot-2.2-pigeonhole-0.4.10… http://pigeonhole.dovecot.org/releases/2.2/rc/dovecot-2.2-pigeonhole-0.4.10… 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

Content-Enconding
by Leander Schäfer 05 Dec '15

05 Dec '15

Hi, With Apache one may use "mod_deflate" in order to reduce bandwidth by using e.g. gzip to compress the http traffic. I would like to use something similar for email traffic between mail clients to dovecote and postfix. My questions are: a) Is this established well enough in most mail clients? b) Can you recomment a good tutorial for this? Thank you very much

2 3

object storage
by Bradley Giesbrecht 04 Dec '15

04 Dec '15

Is the Dovecot Object Storage plugin still available for purchase? Clicking the store link [2] from this page [1] does not show any info about purchasing the plugin. [1] http://www.dovecot.fi/dovecot-object-storage-plugins-available-for-online-p… [2] http://shop.dovecot.fi/ Regards, Bradley Giesbrecht (pixilla)

7 7

FTS solr issue.
by Vijay Sarvepalli 04 Dec '15

04 Dec '15

Hello Dovecot admins, I seem to have a problem ever since recent upgrades to dovecot. The solr engine complains about some variable not being long. Although it does not say which variable. I havve updated the solr-schema.xml file from current dovecot install 2.2.15 ! Any ideas would be very helpful INFO: [] webapp=/solr path=/select params={fl=uid,score&sort=uid+asc&q=from:"modracon"+OR+to:"modracon"+OR+cc:"modracon"+OR+subject:"modracon"&fq=%2Bbox:1483350010e1de52e93800004bc94032+%2Buser:" user-psmail.net"&rows=106375} status=500 QTime=6 Dec 04, 2015 5:04:26 PM org.apache.solr.common.SolrException log SEVERE: java.lang.NumberFormatException: Invalid shift value in prefixCoded string (is encoded value really a LONG?) at org.apache.lucene.util.NumericUtils.prefixCodedToLong(NumericUtils.java:205)

1 0

Interpreting keywords
by Mark Foley 04 Dec '15

04 Dec '15

I've marked several messages in Thunderbird using tags. Tags used are: 0 Important 1 Work 2 To Do 3 Personal 4 Later The messages so tagged appear to have the flag fields set in the IMAP Maildir: cur/1449002162.8993_0.mail:2,Sb cur/1449001929.28087_0.mail:2,Sad I've looked in dovecot-keywords and find: $ more dovecot-keywords 0 $label1 1 $label2 2 $label3 3 $label4 I assume these "$label" values are macros that possibly refer to "Important", "Work", etc., but where are these $label's defined? Are they defined in the dovecot configs somewhere or does the mail client just "know" what these correspond to? --Mark

4 3

Trouble setting replication over TCP
by Борис Кукушкин 04 Dec '15

04 Dec '15

Good day, everyone. I'm playing around with replication to create a backup host. I have hosts backend3 (192.168.100.112) and backend3-replica (192.168.100.113). backend3 acts as a mail-receiving host, backend3-replica is a backup for the case of failure. Both versions are 2.2.13 (form Debian Jessie repository). backend3 receives mail via LMTP-proxy. So far I've managed to setup replication via ssh, but didn't have success with TCP replication. Any help would be much appreciated. Here is what I have in logs when processing a newly delivered e-mail. backend3: Dec 4 17:04:07 backend3 dovecot: lmtp(5451): Debug: none: root=, index=, indexpvt=, control=, inbox=, alt= Dec 4 17:04:07 backend3 dovecot: lmtp(5451): Connect from 192.168.100.101 Dec 4 17:04:07 backend3 dovecot: lmtp(5451): Debug: Loading modules from directory: /usr/lib/dovecot/modules Dec 4 17:04:07 backend3 dovecot: lmtp(5451): Debug: Module loaded: /usr/lib/dovecot/modules/lib15_notify_plugin.so Dec 4 17:04:07 backend3 dovecot: lmtp(5451): Debug: Module loaded: /usr/lib/dovecot/modules/lib20_replication_plugin.so Dec 4 17:04:07 backend3 dovecot: auth: Debug: master in: USER#0111#011postmaster(a)mailnet.local #011service=lmtp#011lip=192.168.100.112#011lport=24#011rip=127.0.0.1#011rport=33133 Dec 4 17:04:07 backend3 dovecot: auth-worker(5446): Debug: sql(postmaster(a)mailnet.local,127.0.0.1): SELECT pop AS home, uid, gid, CONCAT('*:bytes=', CAST(quota*1024*1024 AS CHAR)) AS quota_ rule FROM users WHERE username = 'postmaster(a)mailnet.local' Dec 4 17:04:07 backend3 dovecot: auth: Debug: userdb out: USER#0111#011postmaster(a)mailnet.local #011home=/usr/local/mail/mailnet.local/postmaster#011uid=8#011gid=8#011quota_rule=*:bytes=1048 57600 Dec 4 17:04:07 backend3 dovecot: lmtp(5451): Debug: auth input: postmaster(a)mailnet.local home=/usr/local/mail/mailnet.local/postmaster uid=8 gid=8 quota_rule=*:bytes=104857600 Dec 4 17:04:07 backend3 dovecot: lmtp(5451): Debug: Added userdb setting: plugin/quota_rule=*:bytes=104857600 Dec 4 17:04:07 backend3 dovecot: lmtp(5451): Debug: Effective uid=8, gid=8, home=/usr/local/mail/mailnet.local/postmaster Dec 4 17:04:07 backend3 dovecot: lmtp(5451): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/usr/local/mail/mailnet. local/postmaster/Maildir Dec 4 17:04:07 backend3 dovecot: lmtp(5451): Debug: maildir++: root=/usr/local/mail/mailnet.local/postmaster/Maildir, index=, indexpvt=, control=, inbox=/usr/local/mail/mailnet.local/postma ster/Maildir, alt= Dec 4 17:04:07 backend3 dovecot: lmtp(5451, postmaster(a)mailnet.local) Debug: Effective uid=8, gid=8, home=/usr/local/mail/mailnet.local/postmaster Dec 4 17:04:07 backend3 dovecot: lmtp(5451, postmaster(a)mailnet.local) Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildi r:/usr/local/mail/mailnet.local/postmaster/Maildir Dec 4 17:04:07 backend3 dovecot: lmtp(5451, postmaster(a)mailnet.local) Debug: maildir++: root=/usr/local/mail/mailnet.local/postmaster/Maildir, index=, indexpvt=, control=, inbox=/usr/local /mail/mailnet.local/postmaster/Maildir, alt= Dec 4 17:04:07 backend3 dovecot: lmtp(5451, postmaster(a)mailnet.local) F0skIVedYVZLFQAAamJeGw: msgid=unspecified: saved mail to INBOX Dec 4 17:04:07 backend3 dovecot: lmtp(5451): Disconnect from 127.0.0.1: Successful quit Dec 4 17:04:07 backend3 dovecot: auth: Debug: master in: PASS#0111#011postmaster(a)mailnet.local#011service=doveadm Dec 4 17:04:07 backend3 dovecot: auth-worker(5446): Debug: sql(postmaster(a)mailnet.local): query: SELECT username AS user, crypt AS password, proxy_maybe, host FROM users WHERE username = 'postmaster(a)mailnet.local' AND enabled = 1 Dec 4 17:04:07 backend3 dovecot: auth: Debug: passdb out: PASS#0111#011user=postmaster(a)mailnet.local#011host=192.168.100.112#011proxy Dec 4 17:04:07 backend3 dovecot: doveadm(postmaster(a)mailnet.local): Debug: auth input: user=postmaster(a)mailnet.local host=192.168.100.112 proxy Dec 4 17:04:07 backend3 dovecot: auth: Debug: master in: PASS#0111#011postmaster(a)mailnet.local #011service=doveadm#011lip=192.168.100.112#011lport=12345#011rip=192.168.100.112#011rport=58217 Dec 4 17:04:07 backend3 dovecot: auth-worker(5446): Debug: sql(postmaster(a)mailnet.local,192.168.100.112): query: SELECT username AS user, crypt AS password, proxy_maybe, host FROM users WHERE username = 'postmaster(a)mailnet.local' AND enabled = 1 Dec 4 17:04:07 backend3 dovecot: auth: Debug: passdb out: PASS#0111#011user=postmaster(a)mailnet.local Dec 4 17:04:07 backend3 dovecot: doveadm(192.168.100.112,postmaster(a)mailnet.local): Debug: auth input: user=postmaster(a)mailnet.local Dec 4 17:04:07 backend3 dovecot: auth: Debug: master in: USER#0112#011postmaster(a)mailnet.local #011service=doveadm#011lip=192.168.100.112#011lport=12345#011rip=192.168.100.112#011rport=58217 Dec 4 17:04:07 backend3 dovecot: auth-worker(5446): Debug: sql(postmaster(a)mailnet.local,192.168.100.112): SELECT pop AS home, uid, gid, CONCAT('*:bytes=', CAST(quota*1024*1024 AS CHAR)) AS quota_rule FROM users WHERE username = 'postmaster(a)mailnet.local' Dec 4 17:04:07 backend3 dovecot: auth: Debug: userdb out: USER#0112#011postmaster(a)mailnet.local #011home=/usr/local/mail/mailnet.local/postmaster#011uid=8#011gid=8#011quota_rule=*:bytes=1048 57600 Dec 4 17:04:07 backend3 dovecot: doveadm(192.168.100.112,postmaster(a)mailnet.local): Debug: auth input: postmaster(a)mailnet.local home=/usr/local/mail/mailnet.local/postmaster uid=8 gid=8 quo ta_rule=*:bytes=104857600 Dec 4 17:04:07 backend3 dovecot: doveadm(192.168.100.112,postmaster(a)mailnet.local): Debug: Added userdb setting: plugin/quota_rule=*:bytes=104857600 Dec 4 17:04:07 backend3 dovecot: auth: Debug: master in: PASS#0111#011postmaster(a)mailnet.local #011service=doveadm#011lip=192.168.100.112#011lport=12345#011rip=192.168.100.113#011rport=43001 Dec 4 17:04:07 backend3 dovecot: auth-worker(5446): Debug: sql(postmaster(a)mailnet.local,192.168.100.113): query: SELECT username AS user, crypt AS password, proxy_maybe, host FROM users WHE RE username = 'postmaster(a)mailnet.local' AND enabled = 1 Dec 4 17:04:07 backend3 dovecot: auth: Debug: passdb out: PASS#0111#011user=postmaster(a)mailnet.local Dec 4 17:04:07 backend3 dovecot: doveadm(192.168.100.113,postmaster(a)mailnet.local): Debug: auth input: user=postmaster(a)mailnet.local Dec 4 17:04:07 backend3 dovecot: auth: Debug: master in: USER#0112#011postmaster(a)mailnet.local #011service=doveadm#011lip=192.168.100.112#011lport=12345#011rip=192.168.100.113#011rport=43001 Dec 4 17:04:07 backend3 dovecot: auth-worker(5446): Debug: sql(postmaster(a)mailnet.local,192.168.100.113): SELECT pop AS home, uid, gid, CONCAT('*:bytes=', CAST(quota*1024*1024 AS CHAR)) AS quota_rule FROM users WHERE username = 'postmaster(a)mailnet.local' Dec 4 17:04:07 backend3 dovecot: auth: Debug: userdb out: USER#0112#011postmaster(a)mailnet.local #011home=/usr/local/mail/mailnet.local/postmaster#011uid=8#011gid=8#011quota_rule=*:bytes=1048 57600 Dec 4 17:04:07 backend3 dovecot: doveadm(192.168.100.113,postmaster(a)mailnet.local): Debug: auth input: postmaster(a)mailnet.local home=/usr/local/mail/mailnet.local/postmaster uid=8 gid=8 quo ta_rule=*:bytes=104857600 Dec 4 17:04:07 backend3 dovecot: doveadm(192.168.100.113,postmaster(a)mailnet.local): Debug: Added userdb setting: plugin/quota_rule=*:bytes=104857600 Dec 4 17:04:07 backend3 dovecot: doveadm(192.168.100.113,postmaster(a)mailnet.local): Debug: Effective uid=8, gid=8, home=/usr/local/mail/mailnet.local/postmaster Dec 4 17:04:07 backend3 dovecot: doveadm(192.168.100.113,postmaster(a)mailnet.local): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes lo cation=maildir:/usr/local/mail/mailnet.local/postmaster/Maildir Dec 4 17:04:07 backend3 dovecot: doveadm(192.168.100.113,postmaster(a)mailnet.local): Debug: maildir++: root=/usr/local/mail/mailnet.local/postmaster/Maildir, index=, indexpvt=, control=, inb ox=/usr/local/mail/mailnet.local/postmaster/Maildir, alt= Dec 4 17:04:07 backend3 dovecot: doveadm(192.168.100.112,postmaster(a)mailnet.local): Debug: Effective uid=8, gid=8, home=/usr/local/mail/mailnet.local/postmaster Dec 4 17:04:07 backend3 dovecot: doveadm(192.168.100.112,postmaster(a)mailnet.local): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes lo cation=maildir:/usr/local/mail/mailnet.local/postmaster/Maildir Dec 4 17:04:07 backend3 dovecot: doveadm(192.168.100.112,postmaster(a)mailnet.local): Debug: maildir++: root=/usr/local/mail/mailnet.local/postmaster/Maildir, index=, indexpvt=, control=, inb ox=/usr/local/mail/mailnet.local/postmaster/Maildir, alt= Dec 4 17:04:07 backend3 dovecot: doveadm(192.168.100.112,postmaster(a)mailnet.local): Debug: Namespace : Using permissions from /usr/local/mail/mailnet.local/postmaster/Maildir: mode=0700 gid =default Dec 4 17:04:07 backend3 dovecot: dsync-local(postmaster(a)mailnet.local): Error: read(backend3-replica.mailnet.local) failed: EOF (version not received) Dec 4 17:04:07 backend3 dovecot: dsync-server(postmaster(a)mailnet.local): Error: read(192.168.100.113) failed: EOF (version not received) Here is what goes to backend3-replica's log: Dec 4 17:04:07 backend3-replica dovecot: auth: Debug: master in: PASS#0111#011postmaster(a)mailnet.local #011service=doveadm#011lip=192.168.100.113#011lport=12345#011rip=192.168.100.112#011rport=46266 Dec 4 17:04:07 backend3-replica dovecot: auth-worker(4057): Debug: sql(postmaster(a)mailnet.local,192.168.100.112): query: SELECT username AS user, crypt AS password, proxy_maybe, host FROM users WHERE username = 'postmaster(a)mailnet.local' AND enabled = 1 Dec 4 17:04:07 backend3-replica dovecot: auth: Debug: passdb out: PASS#0111#011user=postmaster(a)mailnet.local#011host=192.168.100.112#011proxy Dec 4 17:04:07 backend3-replica dovecot: doveadm(192.168.100.112,postmaster(a)mailnet.local): Debug: auth input: user=postmaster(a)mailnet.local host=192.168.100.112 proxy Dec 4 17:04:07 backend3-replica dovecot: doveadm(192.168.100.112,postmaster(a)mailnet.local): Error: doveadm client: Unknown flag: V Dec 4 17:09:07 backend3-replica dovecot: auth: Debug: master in: PASS#0111#011postmaster(a)mailnet.local #011service=doveadm#011lip=192.168.100.113#011lport=12345#011rip=192.168.100.112#011rport=46269 Dec 4 17:09:07 backend3-replica dovecot: auth-worker(4062): Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Dec 4 17:09:07 backend3-replica dovecot: auth-worker(4062): Debug: Module loaded: /usr/lib/dovecot/modules/auth/libdriver_mysql.so Dec 4 17:09:07 backend3-replica dovecot: auth-worker(4062): Debug: sql(postmaster(a)mailnet.local,192.168.100.112): query: SELECT username AS user, crypt AS password, proxy_maybe, host FROM users WHERE username = 'postmaster(a)mailnet.local' AND enabled = 1 Dec 4 17:09:07 backend3-replica dovecot: auth: Debug: passdb out: PASS#0111#011user=postmaster(a)mailnet.local#011host=192.168.100.112#011proxy Dec 4 17:09:07 backend3-replica dovecot: doveadm(192.168.100.112,postmaster(a)mailnet.local): Debug: auth input: user=postmaster(a)mailnet.local host=192.168.100.112 proxy Dec 4 17:09:07 backend3-replica dovecot: doveadm(192.168.100.112,postmaster(a)mailnet.local): Error: doveadm client: Unknown flag: V Here is the output of dovecot -n for backend3: # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.2 ext4 auth_cache_negative_ttl = 0 auth_cache_size = 100 M auth_cache_ttl = 0 auth_debug = yes auth_mechanisms = plain login auth_verbose = yes disable_plaintext_auth = no doveadm_password = doveadmpass doveadm_port = 12345 first_valid_gid = 8 first_valid_uid = 8 last_valid_gid = 8 last_valid_uid = 8 lda_mailbox_autocreate = yes lmtp_rcpt_check_quota = yes login_trusted_networks = 192.168.100.100/32 192.168.100.101/32 mail_debug = yes mail_gid = 8 mail_location = maildir:/usr/local/mail/%d/%n/Maildir mail_plugins = " notify replication" mail_uid = 8 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } mailbox name { auto = subscribe } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { mail_replica = tcp:backend3-replica.mailnet.local sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } pop3_client_workarounds = oe-ns-eoh postmaster_address = postmaster@%d protocols = " imap lmtp sieve pop3" service aggregator { fifo_listener replication-notify-fifo { user = mail } unix_listener replication-notify { user = mail } } service doveadm { inet_listener { port = 12345 } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_min_avail = 10 } service lmtp { inet_listener lmtp { port = 24 } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 } } ssl = no userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } For backend3-replica: # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.2 ext4 auth_cache_negative_ttl = 0 auth_cache_size = 100 M auth_cache_ttl = 0 auth_debug = yes auth_mechanisms = plain login auth_verbose = yes disable_plaintext_auth = no doveadm_password = doveadmpass doveadm_port = 12345 first_valid_gid = 8 first_valid_uid = 8 last_valid_gid = 8 last_valid_uid = 8 lda_mailbox_autocreate = yes lmtp_rcpt_check_quota = yes login_trusted_networks = 192.168.100.100/32 192.168.100.101/32 mail_debug = yes mail_gid = 8 mail_location = maildir:/usr/local/mail/%d/%n/Maildir mail_plugins = " notify replication" mail_uid = 8 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } mailbox name { auto = subscribe } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql plugin { mail_replica = tcp:backend3.mailnet.local sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } pop3_client_workarounds = oe-ns-eoh postmaster_address = postmaster@%d protocols = " imap lmtp sieve pop3" service aggregator { fifo_listener replication-notify-fifo { user = mail } unix_listener replication-notify { user = mail } } service doveadm { inet_listener { port = 12345 } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_min_avail = 10 } service lmtp { inet_listener lmtp { port = 24 } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 } } ssl = no userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql }

1 0

Missing processes
by Ervin Hegedüs 04 Dec '15

04 Dec '15

Hi list, I'm new on dovecot mailing list, this is my second dovecot installation. I'm using Debian 8, dovecot packages cames from repository. I'm using it with Postfix - postfix uses dovecot as virtual transport. Looks like everything is fine: dovecot starts, and I see this line in syslog: Dec 4 00:57:04 myserver dovecot: master: Dovecot v2.2.13 starting up for imap, lmtp, pop3 (core dumps disabled) but there isn't any imap nor pop3 process: # ps ax | grep dovecot 23723 ? Ss 0:00 /usr/sbin/dovecot -F 23732 ? S 0:00 dovecot/anvil 23733 ? S 0:00 dovecot/log 23735 ? S 0:00 dovecot/config In logs, there isn't any relevant info. If I send a mail to Postfix, it uses dovecot/auth, ant it starts _only_when_ postfix used it: # ps ax | grep dovecot 23723 ? Ss 0:00 /usr/sbin/dovecot -F 23732 ? S 0:00 dovecot/anvil 23733 ? S 0:00 dovecot/log 23735 ? S 0:00 dovecot/config 25049 ? S 0:00 dovecot/lmtp 25050 ? S 0:00 dovecot/auth 25052 ? S 0:00 dovecot/auth -w But there still isn't the dovecot/imap... Why? Thanks, a. -- I � UTF-8

1 1

How do we disable LOGIN-REFERRALS?
by sb 03 Dec '15

03 Dec '15

> Network Working Group M. Gahrns > Request for Comments: 2221 Microsoft > Category: Standards Track October 1997 > > IMAP4 Login Referrals ... > 6. Security Considerations > > The IMAP4 login referral mechanism makes use of IMAP URLs, and as > such, have the same security considerations as general internet URLs > [RFC-1738], and in particular IMAP URLs [IMAP-URL]. > > A server MUST NOT give a login referral if authentication for that > user fails. This is to avoid revealing information about the user's > account to an unauthorized user. > > With the LOGIN-REFERRALS capability, it is potentially easier to > write a rogue 'password catching' server that collects login data and > then refers the client to their actual IMAP4 server. Although > referrals reduce the effort to write such a server, the referral > response makes detection of the intrusion easier.

2 7

[patch] Fix for bug in TLS/SSL for LMTP with chained certificates
by NederHost/Sebastiaan Hoogeveen 03 Dec '15

03 Dec '15

Hi, In case of tl;dr: I fixed a bug in TLS support for LMTP which caused chained certificates not to work, and another one which caused certificate read errors to be ignored; the patches are attached to this email. While testing LMTP with TLS and certificate verification by Postfix I discovered that certificate chains are not exchanged properly when using LMTP, even though everything works fine for POP3 and IMAP (both with or without STARTTLS). On LMTP only the server certificate is included in the TLS handshake, no intermediate certificates are provided by the server. The first problem I fixed is that in lib-ssl-iostream/iostream-openssl-context.c errors from the ssl_ctx_use_certificate_chain function are silently ignored because the function returns 0 for a failure but the caller checks for values smaller than 0. This problem is fixed in the tiny patch dovecot-2.2.19-ssl_ctx_certificate_chain_returnvalue.diff. After applying this patch the following error message appears in the logs for LMTP only (IMAP and POP3 still work fine): dovecot: lmtp(20683): Error: SSL context initialization failed, disabling SSL: Can't load SSL certificate: error:0608308E:digital envelope routines:EVP_PKEY_get1_EC_KEY:expecting a ec key It turns out this issue is not related to the reading of the certificate or its associated chain. Somewhere before ssl_ctx_use_certificate_chain is called an error is put in the OpenSSL error queue which is never retrieved. Only after loading the server certificate is the queue checked and because of the previously existing error the chain is not loaded. I think the error is related to setting specific protocol options in ssl_iostream_context_set (which may be different for LMTP than for IMAP or POP3) but I did not investigate this. I made the problem go away by making the following two changes: 1. The ssl_ctx_use_certificate_chain function now empties the OpenSSL error queue before doing its work by calling ERR_get_error() until the queue is empty. 2. The openssl_iostream_error function in a similar fashion empties the queue and returns only the error message for the most recent error (this prevent earlier errors from 'hiding' later/more relevant ones). After applying this second patch LMTP now works properly with certificate chains. Note that this patch makes previously unhandled errors simply 'disappear' from the queue, which may be a Very Bad Thing. I guess there is a more elegant way of handling this "queued error" issue but this works for me now and I'm actually not a C programmer. These two fixes are included in dovecot-2.2.19-lmtp_ssl_bug.diff. I suspect this is the same issue as the one reported by Piotr Rotter to this list on July the 27th. Kind regards, -- Sebastiaan Hoogeveen NederHost https://www.nederhost.nl/ KvK: 34099781

2 1

Dovecot doesn't sent rejection message user overquota
by Antonello Cioffi 03 Dec '15

03 Dec '15

Hi I'm using postfix+dovecot (2.2.18). The problem is that dovecot silently discard message when user has its own mailbox full without sending rejection message to the sender. Here a sample log: Dec 1 14:54:23 posta2 postfix/smtp[21478]: B315111C00B: to=<antonen(a)uniparthenope.it>, relay=192.168.241.110[192.168.241.110]:25, delay=0.4, delays=0.2/0/0/0.2, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as C27BF1244DD) Dec 1 14:54:23 posta2 dovecot: lda(antonen): Error: sieve: msgid=<565DA68E.8060308(a)uniparthenope.it>: failed to store into mailbox 'INBOX': Quota exceeded (mailbox for user is full) Dec 1 14:54:23 posta2 dovecot: lda(antonen): sieve: Execution of script /usr/local/etc/dovecot/sieve/default.sieve failed with unsuccessful implicit keep Dec 1 14:54:23 posta2 dovecot: lda(antonen): msgid=<565DA68E.8060308(a)uniparthenope.it>: rejected: Quota exceeded (mailbox for user is full) Dec 1 14:54:23 posta2 postfix/pipe[21020]: 111FB11C00B: to=<antonen(a)uniparthenope.it>, relay=dovecot, delay=0.14, delays=0.05/0.01/0/0.09, dsn=2.0.0, status=sent (delivered via dovecot service) This is dovecot configuration: posta2:/usr/local/etc/dovecot # doveconf -n # 2.2.18: /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.8 (0c4ae064f307+) # OS: Linux 3.0.101-0.46-default x86_64 SUSE Linux Enterprise Server 11 (x86_64) auth_mechanisms = plain login auth_username_format = %Ln auth_verbose = yes default_internal_user = vmail default_login_user = nobody disable_plaintext_auth = no first_valid_uid = 100 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_gid = 100 mail_location = maildir:%h mail_plugins = " quota" mail_uid = 1002 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 index ihave duplicate spamtest spamtestplus passdb { args = /usr/local/etc/dovecot/dovecot-people-ldap.conf.ext driver = ldap } plugin { last_login_dict = redis:host=127.0.0.1:port=6379 mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size quota = maildir:User quota quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = /usr/local/etc/dovecot/sieve/ sieve_dir = ~/.sieve sieve_extensions = +spamtest +spamtestplus +relational +comparator-i;ascii-numeric } postmaster_address = postmaster(a)uniparthenope.it protocols = imap pop3 sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } service_count = 0 vsz_limit = 256 M } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 1 vsz_limit = 64 M } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } service_count = 0 vsz_limit = 256 M } service quota-status { client_limit = 1 executable = quota-status -p postfix inet_listener { port = 12340 } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { user = vmail } user = vmail } ssl_ca = <file.pem ssl_cert = <file.pem ssl_key = <file.pem userdb { args = /usr/local/etc/dovecot/dovecot-people-ldap.conf.ext driver = ldap } protocol lda { mail_plugins = " quota quota sieve" } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags mail_max_userip_connections = 100 mail_plugins = " quota imap_quota last_login" } protocol pop3 { mail_max_userip_connections = 100 mail_plugins = " quota last_login" pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s, %u pop3_save_uidl = no pop3_uidl_format = %08Xu%08Xv } while in master.cf dovecot unix - n n - - pipe flags=DRhu user=vmail argv=/usr/local/libexec/dovecot/dovecot-lda -f ${sender} -d ${recipient} Is there someone who could help me? Regards -- Dott. Antonello Cioffi Ufficio Servizi Informatici Università degli Studi di Napoli Parthenope Tel. 081/5475292 - Fax. 081/5475180

3 4

CentOS rpm dovecot 2.2.10 auth/db-ldap.c TLS bug/patch
by Andrey Fesenko 03 Dec '15

03 Dec '15

Hello, CentOS rpm dovecot 2.2.10 сontains bug auth/db-ldap.c TLS (not connect LDAP+TLS server ldaps://), exist bug/patch https://bugs.centos.org/view.php?id=8267 As far as the correct patch in upstream dovecot quite a lot of changes at this point if there is a correct patch?

2 2

mail_log plugin and uid=error in log file
by Alessio Cecchi 02 Dec '15

02 Dec '15

Hi, I enabled notify and mail_log plugins to log the message uid for new emails delivered via LMTP. All works fine except that the uid is not always logged (see uid=error instead of uid=NUMBER) from dovecot.log: Dec 01 10:03:08 lmtp(alessio(a)domain.com): Info: copy from <lmtp DATA>: box=INBOX, uid=error, msgid=<14489594(a)domain.com>, from="WordPress" <wordpress(a)domain.com>, subject=Enquiry from Joy Dec 01 10:03:09 lmtp(alessio(a)domain.com): Info: copy from <lmtp DATA>: box=INBOX, uid=92, msgid=<03c4e16d(a)www.domain.com>, from="WordPress" <wordpress(a)domain.com>, subject=Enquiry from Joy When the uid number is missing the message have is uid in dovecot-uidlist file but is represented in different format: 92 G1448960589.M630964P41853.qb-dev :1448960589.M630964P41853.qb-dev,S=35341,W=35856 93 :1448960586.M423202P41802.qb-dev,S=35378,W=35890 It seems that the uid is determined after the log is written ... I'm running Dovecot 2.2.19, Maildir as storage format and LMTP for delivery. Is a bug or a "feature"? Can be fixed? Thanks this is my configuration: # dovecot -n # 2.2.19: /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.9 # OS: Linux 2.6.32-573.7.1.el6.x86_64 x86_64 CentOS release 6.7 (Final) auth_master_user_separator = * dict { expire = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext sqlquota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } first_valid_gid = 89 first_valid_uid = 89 last_valid_gid = 89 last_valid_uid = 89 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes log_path = /var/log/dovecot/dovecot.log mail_fsync = always mail_location = maildir:~/Maildir mail_plugins = quota zlib fts fts_lucene acl mail_log notify 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 index ihave duplicate namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = / } passdb { args = /etc/dovecot/dovecot-deny-sql.conf.ext deny = yes driver = sql } passdb { args = /etc/dovecot/extra/master-users driver = passwd-file master = yes pass = yes } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { acl = vfile:/etc/dovecot/global-acls:cache_secs=300 fts = lucene fts_lucene = whitespace_chars=@. mail_log_events = copy save mail_log_fields = uid box msgid from subject quota = dict:User quota::noenforcing:proxy::sqlquota sieve_default = /etc/dovecot/sieve/default.sieve zlib_save = gz zlib_save_level = 6 } protocols = imap sieve lmtp service auth { unix_listener auth-userdb { group = vchkpw mode = 0660 user = vmail } } service dict { unix_listener dict { group = vchkpw mode = 0660 user = vmail } } service imap-postlogin { executable = script-login /etc/dovecot/scripts/imap-postlogin.sh unix_listener imap-postlogin { group = vchkpw mode = 0660 user = vmail } user = vmail } service imap { executable = imap imap-postlogin } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } ssl_cert = </etc/dovecot/ssl/wildcard.pem ssl_key = </etc/dovecot/ssl/wildcard.key ssl_protocols = !SSLv2 !SSLv3 userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } verbose_proctitle = yes protocol lmtp { mail_plugins = quota zlib fts fts_lucene acl mail_log notify sieve } protocol imap { mail_plugins = quota zlib fts fts_lucene acl mail_log notify imap_quota imap_zlib imap_acl } -- Alessio Cecchi Postmaster @ http://www.qboxmail.it https://www.linkedin.com/in/alessice

4 5

doveadm backup -R
by Peer Heinlein 02 Dec '15

02 Dec '15

We're using doveadm -o imapc_user="$USER" -o imapc_password="$PASSWORD" -o imapc_host=$SERVER1 -o pop3c_user="$USER" -o pop3c_password="$PASSWORD" -o pop3c_host=$SERVER1 -D -v backup -R -u "$USER" imapc: to migrate Mails from Courier to Dovecot. We have some complaints on the old system that there are changes on the old system where delete mails are appearing again (IMAP) and/or mails are downloaded several times (POP3). AFAIK there can't be changes on the old system if "backup -R" is used. Or is there any situation where changes on the old system (where we connect with imapc) may happen? 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 1

Logstash pattern (GROK, KV, ...) to parse dovecot logs anyone?
by Christian Rohmann 02 Dec '15

02 Dec '15

Hello dovecot-users, I am currently playing with Elastics ELK stack and was kind of surprised to NOT yet find a good set of GROK or KV pattern to parse dovecots lush and information rich logs. The last post regarding this endeavor was in 2014 (http://www.dovecot.org/list/dovecot/2014-June/096589.html) which "only" extracts the key->value pairs but not other parts of the log lines. One finds the occasional attempt here and there on GitHub, like https://github.com/PCextreme/logstash-grok-patterns/blob/master/mail . But nothing in comparison to the simply amazingly good patterns there are for Postfix from whyscream (https://github.com/whyscream/postfix-grok-patterns) He even added some "I don't understand this yet" rule to learn where the parsing lags. I was wondering if anyone here is running logstash and does already have a set of GROK or KV configuration and is willing to share that with the world? A joint effort might get us to a complete extraction of key->values and all other interesting fields for dovecot quickly I hope. Regards Christian

1 0

mail_log & doveadm
by Larry Rosenman 01 Dec '15

01 Dec '15

Is there any way to have doveadm NOT log using mail_log, but have the daemons do it? (or have doveadm's log go to syslogd)? Thanks! ex: doveadm(ler): Info: copy from SA/FN: box=#ARCHIVE/2015/11/SA/FN, uid=1, msgid=<cm.021005.htukhul.cdhuutux.j(a)cmail2.com>, size=107835, vsize=110376, from="Alley Boost" <alleyboost1(a)gmail.com> , subject=Alley Boost: VIP Mixer TONIGHT, Startup Expo TOMORROW, & More! :), flags=(\Seen) -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larryrtx(a)gmail.com US Mail: 7011 W Parmer Ln, Apt 1115, Austin, TX 78729-6961

2 1

lmtp panic
by Sergey Schwartz 01 Dec '15

01 Dec '15

Gents, I've just upgraded to the latest build of dovecot , now lmtp delivery process panics for just one user Nov 10 15:36:49 mx10 dovecot: lmtp(oleg.vasilyev(a)bgoperator.com): Panic: file str.c: line 22 (str_new_const): assertion failed: (str[len] == '\0') Nov 10 15:36:49 mx10 dovecot: lmtp(oleg.vasilyev(a)bgoperator.com): Panic: file str.c: line 22 (str_new_const): assertion failed: (str[len] == '\0') Nov 10 15:36:49 mx10 dovecot: lmtp(oleg.vasilyev(a)bgoperator.com): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x820de) [0x7f50e596b0de] -> /usr/lib/dovecot/libdovecot.so.0(+0x821cc) [0x7f50e596b1cc] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f50e59128de] -> /usr/lib/dovecot/libdovecot.so.0(+0xa8bf8) [0x7f50e5991bf8] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x5ddbd) [0x7f50e380ddbd] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_match+0xf1) [0x7f50e37f43b1] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x5f555) [0x7f50e380f555] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_interpreter_continue+0xe7) [0x7f50e37eb2e7] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_interpreter_run+0x2b) [0x7f50e37eb46b] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x4e6ea) [0x7f50e37fe6ea] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_execute+0x47) [0x7f50e37ff277] -> /usr/lib/dovecot/modules/lib90_sieve_plugin.so(+0x3b81) [0x7f50e3a62b81] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0x49) [0x7f50e5f26899] -> dovecot/lmtp(+0x6a04) [0x7f50e6357a04] -> dovecot/lmtp(+0x72d7) [0x7f50e63582d7] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x4c) [0x7f50e597ebbc] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x101) [0x7f50e597ffb1] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7f50e597ec45] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f50e597ede8] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f50e59182e3] -> dovecot/lmtp(main+0x165) [0x7f50e6356135] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f50e5545ec5] -> dovecot/lmtp(+0x5223) [0x7f50e6356223] Nov 10 15:36:49 mx10 dovecot: lmtp(oleg.vasilyev(a)bgoperator.com): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x820de) [0x7f887f40e0de] -> /usr/lib/dovecot/libdovecot.so.0(+0x821cc) [0x7f887f40e1cc] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f887f3b58de] -> /usr/lib/dovecot/libdovecot.so.0(+0xa8bf8) [0x7f887f434bf8] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x5ddbd) [0x7f887d2b0dbd] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_match+0xf1) [0x7f887d2973b1] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x5f555) [0x7f887d2b2555] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_interpreter_continue+0xe7) [0x7f887d28e2e7] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_interpreter_run+0x2b) [0x7f887d28e46b] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x4e6ea) [0x7f887d2a16ea] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_execute+0x47) [0x7f887d2a2277] -> /usr/lib/dovecot/modules/lib90_sieve_plugin.so(+0x3b81) [0x7f887d505b81] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0x49) [0x7f887f9c9899] -> dovecot/lmtp(+0x6a04) [0x7f887fdfaa04] -> dovecot/lmtp(+0x72d7) [0x7f887fdfb2d7] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x4c) [0x7f887f421bbc] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x101) [0x7f887f422fb1] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7f887f421c45] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f887f421de8] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f887f3bb2e3] -> dovecot/lmtp(main+0x165) [0x7f887fdf9135] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f887efe8ec5] -> dovecot/lmtp(+0x5223) [0x7f887fdf9223] Nov 10 15:36:49 mx10 dovecot: lmtp(7502): Connect from local Nov 10 15:36:49 mx10 dovecot: lmtp(7509): Connect from local Nov 10 15:36:49 mx10 dovecot: lmtp(oleg.vasilyev(a)bgoperator.com): Panic: file str.c: line 22 (str_new_const): assertion failed: (str[len] == '\0') Nov 10 15:36:49 mx10 dovecot: lmtp(oleg.vasilyev(a)bgoperator.com): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x820de) [0x7fd26d0530de] -> /usr/lib/dovecot/libdovecot.so.0(+0x821cc) [0x7fd26d0531cc] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fd26cffa8de] -> /usr/lib/dovecot/libdovecot.so.0(+0xa8bf8) [0x7fd26d079bf8] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x5ddbd) [0x7fd26aef5dbd] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_match+0xf1) [0x7fd26aedc3b1] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x5f555) [0x7fd26aef7555] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_interpreter_continue+0xe7) [0x7fd26aed32e7] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_interpreter_run+0x2b) [0x7fd26aed346b] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x4e6ea) [0x7fd26aee66ea] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_execute+0x47) [0x7fd26aee7277] -> /usr/lib/dovecot/modules/lib90_sieve_plugin.so(+0x3b81) [0x7fd26b14ab81] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0x49) [0x7fd26d60e899] -> dovecot/lmtp(+0x6a04) [0x7fd26da3fa04] -> dovecot/lmtp(+0x72d7) [0x7fd26da402d7] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x4c) [0x7fd26d066bbc] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x101) [0x7fd26d067fb1] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7fd26d066c45] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fd26d066de8] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fd26d0002e3] -> dovecot/lmtp(main+0x165) [0x7fd26da3e135] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7fd26cc2dec5] -> dovecot/lmtp(+0x5223) [0x7fd26da3e223] Nov 10 15:36:49 mx10 dovecot: lmtp(oleg.vasilyev(a)bgoperator.com): Fatal: master: service(lmtp): child 7494 killed with signal 6 (core dumped) Nov 10 15:36:49 mx10 dovecot: lmtp(oleg.vasilyev(a)bgoperator.com): Fatal: master: service(lmtp): child 7497 killed with signal 6 (core dumped) Nov 10 15:36:49 mx10 dovecot: lmtp(oleg.vasilyev(a)bgoperator.com): Fatal: master: service(lmtp): child 7499 killed with signal 6 (core dumped) Nov 10 15:36:49 mx10 dovecot: lmtp(oleg.vasilyev(a)bgoperator.com): Fatal: master: service(lmtp): child 6719 killed with signal 6 (core dumped) Nov 10 15:36:49 mx10 dovecot: lmtp(oleg.vasilyev(a)bgoperator.com): Fatal: master: service(lmtp): child 7502 killed with signal 6 (core dumped) Nov 10 15:36:51 mx10 dovecot: lmtp(7509): Disconnect from local: Connection closed (in DATA finished) Oleg has lots and lots of small emails :) I'm running ubuntu server 14.04 x86_64 dovecot 2.2.19 (0b1c73b01a5a) build from http://xi.rename-it.nl/debian/ jessie-auto/dovecot-2.2 main -- Best regards, Sergey Schwartz Senior System Administrator Biblio Globus Tour Operator www.bgoperator.ru T: +7 495 5042500 ext 1532 E: sergey.schwartz(a)bgoperator.com

3 7

Let lmtp create target directories
by martin f krafft 01 Dec '15

01 Dec '15

Hello, we're using vmm¹ to manage our postfix+dovecot virtual mail setup, which allows us to give every virtual user a separate EUID and every domain a separate EGID for additional security (vs. handling all virtual mail with a single "vmail" user). As a consequence, however, vmm must itself create the user directories with the appropriate owners, and to do so, it requires root rights. I am trying to investigate getting rid of this need³. Since Dovecot quite happily creates ~/Maildir when necessary, couldn't it also create parents? The home directory should be trivial (same EUID/EGID), but grandparents etc. might need a different policy (e.g. 0/EGID for the grandparent, 0/0 for great-grandparents, etc.). Is this something that could fall within the realm of Dovecot's lmtp? Or is the lmtp invoked as the user and doesn't actually drop root? If so, might there be another way? ¹) http://vmm.localdomain.org/² ²) Hallo Pascal ³) http://bugs.debian.org/804382 Thanks, -- @martinkrafft | http://madduck.net/ | http://two.sentenc.es/ "perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away." -- antoine de saint-exupéry spamtraps: madduck.bogus(a)madduck.net

2 1

Looks like a bug to me: Dovecot ignores Maildir/new timestamp
by Fredrik Roubert 01 Dec '15

01 Dec '15

Hello! I run Debian jessie and have an issue with the interaction between Dovecot (2.2.13), Mutt (1.5.23) and the Android Gmail (5.8.105868218) IMAP client, when using Maildir: I use Dovecot LMTP for local delivery into Maildir and access these files both through Dovecot IMAP from the Android Gmail IMAP client and also directly through the filesystem by running Mutt locally on the mail server. When a new mail arrives, Dovecot LMTP will add a new file in Maildir/new and also update the Dovecot index cache. If I then open Mutt and just delete this new message, then Mutt will just delete this file from Maildir/new and the Dovecot index cache will be out-of-sync. (For testing, Mutt can be cut out of the equation entirely by instead just running "rm Maildir/new/*" from the command line to mimic what Mutt does when deleting a new message, but I mention the use of Mutt here to show why this is a real use-case for me.) If I after this open the Gmail app and pull down the message index to refresh from the Dovecot IMAP server, it'll get the cached version of the index, in which the new message is still present (but only the headers, no body will be loaded and the app will show no body snippet). Pulling down the message index again to force a second refresh will cause the new/deleted message to disappear again. This seems to be caused by Dovecot not looking at the Maildir/new timestamp to determine whether the index cache is up-to-date, but instead only looking at the Maildir/cur timestamp. If I instead repeat all these testing steps from the beginning, sending a new mail message, deleting it with "rm Maildir/new/*" but then also running "touch Maildir/cur" before opening the Gmail app and doing the refresh, then Dovecot does update the cache and does not send any ghost messages to the IMAP client. It does seem reasonable to me that Mutt doesn't touch Maildir/cur when just deleting new messages and I suspect that it might be a bug in Dovecot that it timestamp of Maildir/new isn't checked and the index cache updated if that timestamp is newer than the last index update done by the Dovecot LMTP service. Does this analysis seem sound? Did I miss anything? (Output of "doveconf -n" attached.) Cheers // Fredrik Roubert -- Forsterstrasse 64 | +41 78 8170377 CH-8044 Zürich | https://roubert.name/fredrik/

3 2

Sieve, shared folders, different daemons
by Frido Otten 01 Dec '15

01 Dec '15

Hi, In our dovecot setup we use 3 different config files. One for maildropping(sieve), one for dovecot/imap on standard ports with ssl config and one for dovecot/imap on standard ports+1 with a different ssl certificate. Currently the client using the standard port+1 config wants to make use of shared folders, but the thing is that the current namespace separator in all configs is '.'. This is conflicting with shared folders. Can we simply run one of the dovecot/imap daemons configured with a different separator and shared folders without having impact on sieve and the current connected users to the standard ports? Regards, Frido

2 2

How to delete "proxy" attribute in passdb lookup?
by Peer Heinlein 29 Nov '15

29 Nov '15

Hi, I have a complicated SQL backend with stored procedures to generate passdb/userdb queries. This result have the proxy-attribute set and it's very complicated to change that procedures. On one system I tried to override/delete the proxy attribute: passdb { driver = sql args = /etc/dovecot/dovecot-sql.conf.ext override_fields = proxy=n } Looks like that doesn't work. "proxy" is always set. doveadm auth lookup username passdb: username user : username host : mailserver proxy hostip : xx.xx.xx.xx Is there any way to override/delete an existing true/false attribute like "proxy"? 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 3

Connection between postfix and dovecot failing
by Sytse Kuijk 29 Nov '15

29 Nov '15

Hi all, Hope someone has been here and done that before. I am running a Mac mini with OSX server version 10.5, that is on El Capitan, but the problem I have started on Yosemite (the previous version) and did not change at all in the upgrade (I had hoped it would have solved itself). As you might know, OSX server uses postfix and dovecot as mailing engines, good choice. Since we suffered a short power outage a little over a week ago, the mail has failed in delivering messages to the local mailboxes. We can send mail out, check the mailboxes (they never change right now),etc. but incoming mail was first just not delivered and after a week warning are sent back to the senders, telling there is a temporary problem (hope that this message is right and I can solve the issue). What seems to go wrong is that postfix cannot connect to the local MTA. The error message that appears in several places is: recipient=ann.cools(a)surikata.be offset=769 dsn_orig_rcpt=rfc822;ann.cools(a)surikata.be status=4.4.1 action=delayed reason=delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused I find all sorts of explanations and cures, but none work up to now. I tried to find lock files that might be blocking, deleted some files ending in lck with zero size, with no result. I tried to switch off the spam/virus/junk features, no difference (some mail said that messages in the queue will not get through, but new ones would. Not so, not a single message up to now). I also get alerts in the Server application, warning that: An unassigned mail directory has been detected and is scheduled to be deleted. The unassigned mail directory located in: /Library/Server/Mail/Data/mail/702C16A8-6B2D-42D8-9362-659DD2949AFC is not associated with any user account and is scheduled to be deleted in 1 days. In the mean time no mail, and unfortunately, we need it badly. Any suggestions? Million thanks for your kind support. sytse -- ------------------------------------------ - Sytse Kuijk - ___ - R.S.R. n.v. - o|o - Gijzelaarsstraat 16 - \_____(.)_____/ - 2000 Antwerpen - - GSM: +32 468 20 00 00 - ___ - Phone: +32 3 216 4328 - o|o - E-mail: sytse(a)pobox.com <mailto:sytse@pobox.com> - \_____(.)_____/ ------------------------------------------ iThink therefore iMac

2 1

Re: Connection between postfix and dovecot failing
by Sytse Kuijk 28 Nov '15

28 Nov '15

Well, post fix tries, but cannot connect. Sounds to me like problem at the receiving side. In any case, one question would be: is amavis part of dovecot or of postfix? sytse -- ------------------------------------------ - Sytse Kuijk - ___ - R.S.R. n.v. - o|o - Gijzelaarsstraat 16 - \_____(.)_____/ - 2000 Antwerpen - - GSM: +32 468 20 00 00 - ___ - Phone: +32 3 216 4328 - o|o - E-mail: sytse(a)pobox.com - \_____(.)_____/ ------------------------------------------ iThink therefore iMac > On 28 nov. 2015, at 22:24, Edgar Pettifogging <edgar(a)pettijohn-web.com> wrote: > > This should probably move to postfix list. Doesn't look like dovecot gets a chance to deliver. > > Sent from my iPhone > >> On Nov 28, 2015, at 11:34 AM, Sytse Kuijk <sytse(a)pobox.com> wrote: >> >> Well, I tried that. I can connect a telnet session on that port and that does not refuse the connection, it sits there waiting, but I do not know the protocol so I cannot check if it does what it is supposed to. >> >> I also checked who is listening on that port, here is the dialog: >> >> sh-3.2# sudo lsof -i -n -P | grep 10024 >> perl5.18 75844 _amavisd 5u IPv4 0x866f6119e39f833d 0t0 TCP 127.0.0.1:10024 (LISTEN) >> perl5.18 75844 _amavisd 6u IPv6 0x866f6119e03f253d 0t0 TCP [::1]:10024 (LISTEN) >> >> looks sort of correct to me… >> >> sytse >> >> -- >> >> ------------------------------------------ >> - Sytse Kuijk - ___ >> - R.S.R. n.v. - o|o >> - Gijzelaarsstraat 16 - \_____(.)_____/ >> - 2000 Antwerpen - >> - GSM: +32 468 20 00 00 - ___ >> - Phone: +32 3 216 4328 - o|o >> - E-mail: sytse(a)pobox.com - \_____(.)_____/ >> ------------------------------------------ >> >> iThink therefore iMac >> >>> On 28 nov. 2015, at 18:31, Edgar Pettifogging <edgar(a)pettijohn-web.com> wrote: >>> >>> I would bet that whatever is listening at 127.0.0.1 port 10024 didn't get restarted when the power came back on. Amavis perhaps or another proxy server of some sort. >>> >>> Sent from my iPhone >>> >>>> On Nov 28, 2015, at 11:14 AM, Sytse Kuijk <sytse(a)pobox.com> wrote: >>>> >>>> Hi all, >>>> >>>> Hope someone has been here and done that before. >>>> I am running a Mac mini with OSX server version 10.5, that is on El Capitan, but the problem I have started on Yosemite (the previous version) and did not change at all in the upgrade (I had hoped it would have solved itself). >>>> >>>> As you might know, OSX server uses postfix and dovecot as mailing engines, good choice. >>>> Since we suffered a short power outage a little over a week ago, the mail has failed in delivering messages to the local mailboxes. >>>> We can send mail out, check the mailboxes (they never change right now),etc. but incoming mail was first just not delivered and after a week warning are sent back to the senders, telling there is a temporary problem (hope that this message is right and I can solve the issue). >>>> >>>> What seems to go wrong is that postfix cannot connect to the local MTA. The error message that appears in several places is: >>>> >>>> recipient=ann.cools(a)surikata.be >>>> offset=769 >>>> dsn_orig_rcpt=rfc822;ann.cools(a)surikata.be >>>> status=4.4.1 >>>> action=delayed >>>> reason=delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused >>>> >>>> I find all sorts of explanations and cures, but none work up to now. >>>> I tried to find lock files that might be blocking, deleted some files ending in lck with zero size, with no result. >>>> I tried to switch off the spam/virus/junk features, no difference (some mail said that messages in the queue will not get through, but new ones would. Not so, not a single message up to now). >>>> I also get alerts in the Server application, warning that: >>>> >>>> An unassigned mail directory has been detected and is scheduled to be deleted. >>>> >>>> The unassigned mail directory located in: >>>> /Library/Server/Mail/Data/mail/702C16A8-6B2D-42D8-9362-659DD2949AFC >>>> is not associated with any user account and is scheduled to be deleted in 1 days. >>>> >>>> In the mean time no mail, and unfortunately, we need it badly. >>>> >>>> Any suggestions? >>>> >>>> Million thanks for your kind support. >>>> >>>> sytse >>>> -- >>>> ------------------------------------------ >>>> - Sytse Kuijk - ___ >>>> - R.S.R. n.v. - o|o >>>> - Gijzelaarsstraat 16 - \_____(.)_____/ >>>> - 2000 Antwerpen - >>>> - GSM: +32 468 20 00 00 - ___ >>>> - Phone: +32 3 216 4328 - o|o >>>> - E-mail: sytse(a)pobox.com <mailto:sytse@pobox.com> - \_____(.)_____/ >>>> ------------------------------------------ >>>> >>>> iThink therefore iMac

2 1

Re: Connection between postfix and dovecot failing
by Sytse Kuijk 28 Nov '15

28 Nov '15

Well, I tried that. I can connect a telnet session on that port and that does not refuse the connection, it sits there waiting, but I do not know the protocol so I cannot check if it does what it is supposed to. I also checked who is listening on that port, here is the dialog: sh-3.2# sudo lsof -i -n -P | grep 10024 perl5.18 75844 _amavisd 5u IPv4 0x866f6119e39f833d 0t0 TCP 127.0.0.1:10024 (LISTEN) perl5.18 75844 _amavisd 6u IPv6 0x866f6119e03f253d 0t0 TCP [::1]:10024 (LISTEN) looks sort of correct to me… sytse -- ------------------------------------------ - Sytse Kuijk - ___ - R.S.R. n.v. - o|o - Gijzelaarsstraat 16 - \_____(.)_____/ - 2000 Antwerpen - - GSM: +32 468 20 00 00 - ___ - Phone: +32 3 216 4328 - o|o - E-mail: sytse(a)pobox.com - \_____(.)_____/ ------------------------------------------ iThink therefore iMac > On 28 nov. 2015, at 18:31, Edgar Pettifogging <edgar(a)pettijohn-web.com> wrote: > > I would bet that whatever is listening at 127.0.0.1 port 10024 didn't get restarted when the power came back on. Amavis perhaps or another proxy server of some sort. > > Sent from my iPhone > >> On Nov 28, 2015, at 11:14 AM, Sytse Kuijk <sytse(a)pobox.com> wrote: >> >> Hi all, >> >> Hope someone has been here and done that before. >> I am running a Mac mini with OSX server version 10.5, that is on El Capitan, but the problem I have started on Yosemite (the previous version) and did not change at all in the upgrade (I had hoped it would have solved itself). >> >> As you might know, OSX server uses postfix and dovecot as mailing engines, good choice. >> Since we suffered a short power outage a little over a week ago, the mail has failed in delivering messages to the local mailboxes. >> We can send mail out, check the mailboxes (they never change right now),etc. but incoming mail was first just not delivered and after a week warning are sent back to the senders, telling there is a temporary problem (hope that this message is right and I can solve the issue). >> >> What seems to go wrong is that postfix cannot connect to the local MTA. The error message that appears in several places is: >> >> recipient=ann.cools(a)surikata.be >> offset=769 >> dsn_orig_rcpt=rfc822;ann.cools(a)surikata.be >> status=4.4.1 >> action=delayed >> reason=delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused >> >> I find all sorts of explanations and cures, but none work up to now. >> I tried to find lock files that might be blocking, deleted some files ending in lck with zero size, with no result. >> I tried to switch off the spam/virus/junk features, no difference (some mail said that messages in the queue will not get through, but new ones would. Not so, not a single message up to now). >> I also get alerts in the Server application, warning that: >> >> An unassigned mail directory has been detected and is scheduled to be deleted. >> >> The unassigned mail directory located in: >> /Library/Server/Mail/Data/mail/702C16A8-6B2D-42D8-9362-659DD2949AFC >> is not associated with any user account and is scheduled to be deleted in 1 days. >> >> In the mean time no mail, and unfortunately, we need it badly. >> >> Any suggestions? >> >> Million thanks for your kind support. >> >> sytse >> -- >> ------------------------------------------ >> - Sytse Kuijk - ___ >> - R.S.R. n.v. - o|o >> - Gijzelaarsstraat 16 - \_____(.)_____/ >> - 2000 Antwerpen - >> - GSM: +32 468 20 00 00 - ___ >> - Phone: +32 3 216 4328 - o|o >> - E-mail: sytse(a)pobox.com <mailto:sytse@pobox.com> - \_____(.)_____/ >> ------------------------------------------ >> >> iThink therefore iMac

1 0

ldap paging
by Andre Helwig 27 Nov '15

27 Nov '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi List, in ldapsearch you are able to use paging in case of limited results on ldap server side with "-E pr=10000/noprompt" Is there any way to get the same effect for the iterate query? Thanks Andre -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJWWHvwAAoJEAoTNwRDnEhRVmMH/0+vGRx7urQ49bHbzc4asD7r XlbwS7whkDKrJpflK39PLPw5BJoptKhwLNOueotFv9Pq8EYQBkN/gX69BzxeoFk8 DZpiP/ogYQIG1lUijes4UkbttVpnviy9/mLBKjIfIkvGDu0q3zwuq5876q6t2Qxx kJkpLSizxAfnGLeD03txVPAc8wGzxhxkyEdosQ+ARriYI1Ce+dfK28z6hSAEXMA+ 4JZEvIsy6P+xepFCFYILFWeRO2YBzqHtgtjKu8KCiyBdUPG0Nii4z2YmN2AoCj7m rQ8l4CeTDw+lk0pMy26kCsmh+PK2/OXCUGjxgYJOR3mxn2HNSIfUXFVWs4ri464= =qWS+ -----END PGP SIGNATURE-----

1 0

Sieve Max Redirect
by Shakeel Shahzad 27 Nov '15

27 Nov '15

Hello, I have configured iRedMail ( 0.9.1) on Ubuntu (14.04 LTS). In my dovecot.conf file, I have set sieve_max_redirects as 500. In dovecot (2.2.9) configuration file, I see sieve_max_redirect as 100 but when I add email addresses more than 32, I see that redirect fails. Can you please help me to see this issue and fix it through? If you need anything from my side, please let me know. Regards... Shakeel

3 4

doveadm-backup verbosity?
by Andreas Fischer 27 Nov '15

27 Nov '15

Hi, according to the man page doveadm-backup, the verbosity switch "-v" should do the following: "Enables verbosity, including progress counter" However, i see no difference running the following command with or without the "-v" switch: >>doveadm -v backup -R -A remote:myhost The command itself works without problem, two mailboxes are correctly back-upped, but the output is only an empty line. Not sure if this is expected behavior. Regards # 2.2.19: /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.9 (357ac0a0e68b+) # OS: Linux 4.2.5-1-ARCH x86_64 dsync_remote_cmd = ssh -p 19022 -l root %{host} doveadm dsync-server -u%u first_valid_uid = 99 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 index ihave duplicate editheader passdb { args = nopassword=y driver = static } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve sieve_extensions = +editheader } protocols = service anvil { process_min_avail = 0 unix_listener anvil-auth-penalty { mode = 064 } } ssl = no userdb { args = /etc/dovecot/users default_fields = uid=nobody gid=nobody home=/backup/tmp/mail/%d/%n mail=sdbox:~/box driver = passwd-file }

1 0

fts_solr does not quote lucene's special characters
by Michael Stilkerich 27 Nov '15

27 Nov '15

Hello, I am using Dovecot 2.2.19 with the solr backend for full text search and experience the following issue. When I issue a search that includes characters that are part of lucene's query syntax (e.g. the double quote character), dovecot does not escape the special characters and issues a request with invalid syntax to the solr server. For example, I search for foo"bar, then my IMAP client (roundcube) sends the following to dovecot: A0003 UID THREAD REFS US-ASCII ALL UNDELETED BODY "foo\"bar" Dovecot in turn uses the following request URI to query SOLR: "GET /solr/select?fl=uid,score&rows=113739&sort=uid+asc&q=body:%22foo%22bar%22&fq=%2Bbox:4d86808c56d44282b35cea8700dda537+%2Buser:%22myuser%22 HTTP/1.1" 400 994 Solr responds with error 400 and the following body: type Status report message null description The request sent by the client was syntactically incorrect. This is because the " character in foo"bar is not quoted in the solr request. When I adapt the request to quote the " character solr succeeds with the expected result: "GET /solr/select?fl=uid,score&rows=113739&sort=uid+asc&q=body:%22foo%5C%22bar%22&fq=%2Bbox:4d86808c56d44282b35cea8700dda537+%2Buser:%22myuser%22 HTTP/1.1" 200 535 A fix for this would be highly appreciated. Cheers, Michael

2 1

auth_request_get_var_expand test fails on big endian arches.
by Rafael dos Santos 27 Nov '15

27 Nov '15

Hi, when running the tests in a big endian machine, I get the following error: 0 / 1 tests failed test-auth-request-var-expand.c:99: Assert failed: strcmp(str_c(str), test_output) == 0 test-auth-request-var-expand.c:104: Assert failed: strcmp(str_c(str), test_output) == 0 auth request var expand short and long ............................... : FAILED test: random seed #1 was 1446803094 auth request var expand flags ........................................ : ok test-auth-request-var-expand.c:158: Assert failed: strcmp(str_c(str), test_output) == 0 auth request var expand long-only .................................... : FAILED auth request var expand usernames .................................... : ok auth request var expand funcs ........................................ : ok 2 / 5 tests failed Makefile:1257: recipe for target 'check-test' failed Looking into it I found that auth_request_get_var_expand_table ends up calling the net_ip2addr function. This function, in turn, uses ntohl to convert from network byte order to host byte order. In big endian machines, that means that the string output will be ------------- big endian --------------- +user@+domain1@+domain2 +user +domain1@+domain2 +service 7.91.205.21 73.150.2.210 54321 +password +mech secured 21 210 valid instead of ---------- expected output --------- +user@+domain1@+domain2 +user +domain1@+domain2 +service 21.205.91.7 210.2.150.73 54321 +password +mech secured 21 210 valid Let me know in case you need help testing on big endian arches. Att. -- Rafael Fonseca

2 3

IMAP COPY creates invalid index data with zlib and mail_log plugins enabled but zlib_save off
by Robert L Mathews 27 Nov '15

27 Nov '15

I've noticed that maildir IMAP COPY commands can generate invalid dovecot.index entries when all seven of the following are true: - The zlib plugin is enabled; - The zlib_save/zlib_save_level options are NOT enabled; - The source message being copied is compressed; - The mail_log plugin is logging "copy" events; - The mail_log_fields setting includes at least one message header; - The destination mailbox folder has an index file that is recording the logged headers; - The source mailbox folder does NOT have an index file recording the logged headers. In this situation, copying a message results in an index entry in the destination that has all the headers blank, like this: RECORD: seq=5, uid=182415, flags=0x08 (Seen) - ext 1 modseq : 3 (0300000000000000) - ext 2 cache : 2352 (30090000) - cache offset=2352 size=120, prev_offset = 0 - hdr.FROM: - hdr.MESSAGE-ID: - hdr.SUBJECT: - hdr.DATE: - hdr.BCC: - hdr.CC: - hdr.CONTENT-TYPE: - hdr.IN-REPLY-TO: - hdr.NEWSGROUPS: - hdr.PRIORITY: - hdr.REFERENCES: - hdr.REPLY-TO: - hdr.TO: - hdr.X-PRIORITY: For these copies, the mail_log plugin records blank header data in the log, too, like this (despite the message having a valid message-ID, from, and subject): Oct 29 21:11:42 wheezy dovecot: imap[31763]: user=<1(a)example.com> ip=192.168.0.4 session=RV/MmUojyADAqAAE copy from INBOX.Saved: box=INBOX.Trash, uid=182412, msgid=, size=1357, vsize=1392, from=, subject=, flags=(\Seen) I've found this occurs in at least Dovecot 2.1.7, 2.2.13, and 2.2.18 (all packaged Debian versions). Changing any of the seven things I mentioned above fixes it. I've tried to find the code that causes this, but not yet been successful. My theory is that when the mail_log plugin calls mail_get_first_header(), and there's no index header record to read it from, it looks at the real message on disk. Perhaps it somehow operates on a compressed copy of the message although it expects uncompressed plaintext, so it doesn't find any of the headers. The "missing" headers then get cached to the destination index file as a side-effect. The copied maildir message itself is fine, by the way. It's an identical, still-compressed copy of the original message. And deleting the destination "dovecot.index*" files that contain the bad data causes Dovecot to rebuild the index with the correct header data. It's unusual to use the zlib plugin without the zlib_save/zlib_save_level options enabled, of course. That's probably why (as far as I can tell) there have been no reports of this before. I noticed it only because I was testing a small amount of manual mail compression before deploying it for all mail. Here's the "doveconf -n" of a system in the "has the problem" state: # 2.2.18: /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.8 (0c4ae064f307+) # OS: Linux 3.2.0-4-686-pae i686 Debian stretch/sid auth_mechanisms = plain login auth_username_format = auth_verbose = yes auth_verbose_passwords = sha1 default_vsz_limit = 1 G disable_plaintext_auth = no lda_mailbox_autosubscribe = yes listen = * log_timestamp = "%Y-%m-%d %H:%M:%S " login_log_format_elements = user=<%u> pid=[%{mail_pid}] method=%m rip=%r lip=%l %c mail_fsync = never mail_location = maildir:~/ mail_log_prefix = "%s[%{pid}]: user=<%u> ip=%{rip} session=%{session} " mail_max_userip_connections = 100 mail_plugins = mail_log notify zlib managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate spamtest spamtestplus namespace { inbox = yes location = prefix = INBOX. separator = . type = private } namespace { hidden = yes inbox = no list = no location = prefix = separator = . type = private } passdb { args = /etc/dovecot/dovecot.users driver = passwd-file } plugin { fts = lucene fts_lucene = whitespace_chars=@. mail_log_events = copy delete undelete expunge mailbox_delete mailbox_rename flag_change save mailbox_create mail_log_fields = vsize size flags box uid box msgid size flags vsize from subject sieve = %h/mailbox.sieve sieve_after = %h/../../domain-after.sieve sieve_before = %h/../../domain-before.sieve sieve_dir = %h/sieve sieve_extensions = -reject +spamtest +spamtestplus sieve_global_dir = %h/../../sieve-global-include-scripts sieve_spamtest_max_value = 7 sieve_spamtest_status_header = X-Spam-Level sieve_spamtest_status_type = strlen } protocols = pop3 imap lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { process_min_avail = 8 service_count = 0 } service imap { process_limit = 2000 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } service pop3-login { process_min_avail = 8 service_count = 0 } service pop3 { process_limit = 2000 } ssl = no userdb { args = /etc/dovecot/dovecot.users driver = passwd-file } verbose_proctitle = yes protocol imap { imap_client_workarounds = delay-newmail imap_logout_format = %i bytes in, %o bytes out } protocol pop3 { pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_logout_format = ; %i bytes in, %o bytes out, %t top (%p bytes), %r retr (%b bytes), %d of %m deleted, mailbox size %s bytes pop3_uidl_format = UID%u-%v } protocol lda { mail_fsync = optimized mail_plugins = mail_log notify zlib sieve } protocol lmtp { mail_fsync = optimized mail_plugins = mail_log notify zlib sieve } -- Robert L Mathews, Tiger Technologies, http://www.tigertech.net/

2 2

Problems Converting from Cyrus to Dovecot (cyrus2dovecot)
by Forrest 27 Nov '15

27 Nov '15

I have been attempting to use the cyrus2dovecot script, to no avail. I have many years of content that I want to convert from Cyrus to Dovecot; with the above not working, what are other options out there? Another idea I had is simply set up another IMAP server (using Dovecot) and drag-and-drop and just wait, which I may end up doing. In the above, I copied over my entire /var/imap and /var/spool/imap to another system; there is only one account (mine), so calling the script was fairly easy; it just doesn't work. inboxes=the "myaccount" that was copied over /home/myaccount/cyrus2dovecot --cyrus-inbox /home/myaccount/inboxes/%u \ --cyrus-seen /home/myaccount/varimap/user/%h/%u.seen \ --cyrus-sub /home/varimap/user/%h/%u.sub \ --dovecot-inbox /home/myaccount/dovecot/Maildir \ myaccount the log output complains of: cyrus2dovecot [myaccount]: (warning) Index record missing for: INBOX/62020. and correctly complains about squat indices, as that's not a file it would handle. There is no output into the Maildir, however. All directory paths are correct. Thanks.

6 9

logging imap searches ?
by mancyborg＠gmail.com 27 Nov '15

27 Nov '15

Hi thanks to this list support I'm using Dovecot's MailLog plugin http://wiki2.dovecot.org/Plugins/MailLog to log the following imap events: delete undelete expunge copy mailbox_delete mailbox_rename flag_change save mailbox_create and I'm very happy. Question: is it possible to also log imap searches https://tools.ietf.org/html/rfc3501#section-6.4.4 ? Thank you, Mike

1 0

imap logging ?
by mancyborg＠gmail.com 27 Nov '15

27 Nov '15

Hi I'm trying to log my users imap actions, like when creating a folder, moving an email or deleting an email. So I've enabled 'mail_debug' and I'm checking /var/log/dovecot/debug.log this is what happens when I delete an email: Nov 26 07:46:38 auth-worker(1555): Debug: sql(XXX,127.0.0.1): query: SELECT password FROM mailbox WHERE username = 'XXX' and active = 1 and restrictedAccess = 0 Nov 26 07:46:38 auth: Debug: client out: OK 1 user=XXX Nov 26 07:46:38 auth-worker(1555): Debug: sql(XXX,127.0.0.1): SELECT '/var/vmail/XXX/XXX' as home, 5000 AS uid, 5000 AS gid, concat('*:storage=', quota) AS quota_rule FROM mailbox WHERE username = 'XXX' Nov 26 07:46:38 auth: Debug: master out: USER 374472705 XXX home=/var/vmail/XXX/XXX uid=5000 gid=5000 quota_rule=*:storage=524288 Nov 26 07:46:38 imap(XXX): Debug: Effective uid=5000, gid=5000, home=/var/vmail/XXX/XXX Nov 26 07:46:38 imap(XXX): Debug: Quota root: name=User quota backend=maildir args= Nov 26 07:46:38 imap(XXX): Debug: Quota rule: root=User quota mailbox=* bytes=536870912 messages=0 Nov 26 07:46:38 imap(XXX): Debug: Quota rule: root=User quota mailbox=Trash bytes=+104857600 messages=0 Nov 26 07:46:38 imap(XXX): Debug: maildir++: root=/var/vmail/XXX/XXX/Maildir, index=/var/vmail/XXX/XXX/Maildir/indexes, control=, inbox=/var/vmail/XXX/XXX/Maildir, alt= and when creating a folder, access an email or moving an email, the output is basically the same: I'm unable to find the actual IMAP command. So, question: is there a way to log IMAP commands to a file ? Thank you, Mike

2 2

dsync imapc authentication mechanisms
by Randall Gellens 26 Nov '15

26 Nov '15

I'm trying to use dsync to mirror mail onto a remote IMAP server. The remote server is generating an error that authentication via plain text is not permitted. Does dsync imapc support any non-clear-text authentication mechanisms? The remote server supports: AUTH=CRAM-MD5 AUTH=DIGEST-MD5 AUTH=NTLM -- Randall Gellens Opinions are personal; facts are suspect; I speak for myself only -------------- Randomly selected tag: --------------- At a dinner party one should eat wisely but not too well, and talk well but not too wisely. --W. Somerset Maugham

2 1

Dsync problems
by Frank de Bot (lists) 26 Nov '15

26 Nov '15

Hi, I'm setting up a migration between 2 dovecot servers 2.1.12 to 2.2.19 . I've ran into some issues with dsync. I use the following command for syncing: doveadm -o mail_fsync=never -o imapc_host=%remote% -o imapc_master_user=master -o imapc_password=%masterpw% -o imapc_features="rfc822.size fetch-headers" -o mail_prefetch_count=20 -o imapc_user=%user% backup -1 -R -u %user% imapc: I execute a full sync first and when the mailserver are being migrated it only would have to do incremental. The first is run is without problems. But I find the following problem: - Flags on current mails aren't updated. If I set message to unread, the sync won't pick them up. - On the origin dovecot server I had removed some messages and purged the inbox. Those message are now in the Trash and are created again and again when I sync Is this normal behaviour? It renders it pretty much useless since data consistency isn't guaranteed. Regards, Frank de Bot

2 1

FTS, multiple virtualmailbox entries for single mailbox
by Frank de Bot (lists) 26 Nov '15

26 Nov '15

Hi, i have a dovecot setup with virtual users. Each user has 2 entries for his mailbox. One is with the username formatted as %username%@%default_realm% , the other %username%@%domain% I've done some tests with it, but I don't complete understand how it works - I've emptied all document in solr so it empty. Doveadm is instructed to do the same with 'doveadm -D -v fts rescan -A' - I reindex %username%@%default_realm% with 'doveadm -D index -u %username%@%default_realm% '*' - With fluke I can see 4 indexes documents. - I reindex %username%@%domain% - No documents are added to Solr, dovecot finds it's up-to-date - After 'doveadm -D -v fts rescan -A' the documents are added The part I don't understand is that a certain key used for indexing, but dovecot checks based on something else. If find this inconsistent. How can I manage to get virtualmailboxes where multiple logins are allowed on 1 mailbox and FTS is working? I think it won't work well this way if a user logs in with only a certain username with the default realm. Message received by dovecot will be indexed in Solr with %username%@%domain% , but there will be no indexed documents for %username%@%default_realm% A earlier threads suggested to be able to override the username for FTS, but it was tought to be not a good idea. Regards, Frank de Bot

2 1

Re: Questions about hardlinks, alternate storage and compression
by Gionatan Danti 26 Nov '15

26 Nov '15

Hi Javier, thanks for your reply. I already checked SIS and, while interesting, is not what I want, because: 1) it can be difficult to restore a single message/attachment from a backup 2) only the attachments, and not the entire messages, are deduped. Message-based hardlinks really exists for a reason. The good news is that I found _why_ they are not working: it depends from how dovecot and its sieve plugin (pigenhole) interact. Basically, if I define anything for the before_sieve and after_sieve variables, dovecot stops creating hardlinks for multiple copies of the same message. On the other hand, private (per-user) sieve file works without interfering with hardlinks. In a similar manner, disabling sieve also permits dovecot to create multiple hardlinks for a single message. Does someone know if newer dovecot versions change anything in this regard? Thank you all. On 13/07/15 11:10, Javier Miguel Rodríguez wrote: > Search about "single instance storage dovecot". This is what you need. > > Regards > > Javier > > On 27/06/2015 18:18, Gionatan Danti wrote: >> Hi all, >> I have some questions about hardlinks, alternate storage and >> compression. I already scanned the list for related information and I >> have an idea of how things works, but I would like to have a definite >> answer. >> >> System spec: >> - CentOS 6.6 x64 >> - dovecot-2.0.9-8.el6_6.4.x86_64 RPM package/version >> - sdbox mail store >> >> 1) About hardlinks: when sending the same message to two different >> recipients, I see that the two u.x files are created as two different >> files. Diffing them, I see that the only difference is a single char >> (see [1] for an example). My questions are: >> a) it is possible to tell dovecot to create a single file + a single >> hardlink (linkref=2)? As other IMAP servers support that features (eg: >> Cyrus, CommunigatePro, etc) I am wondering if I missed something in >> configuring dovecot... >> b) If it is not possible, can I run a script that compare the >> various files and substitute equal ones (minus the changing line) with >> hardlinks, or it will confuse dovecot? As a side note, why the >> changing line ever exists? >> >> 2) About alternate storage and compression: actually, I use a single >> mail_location without compression. I would like to have an alternate >> storage and to enable compression on it only, leaving the main >> location without compression. I if understand it correctly, it >> _should_ be done using a command similar to "doveadm -Dv -o >> "plugin/zlib_save=gz" altmove -uu testuser sentbefore 8d". I'm right >> thinking that it should work? I will really end with a primary >> uncompressed mail store and an alternate, zlib-compressed one? >> >> Thank you all and sorry if I did some naive questions. >> >> [1] >> 63c63 >> < G2fd0811c64be8e553d970000eaa8309f >> --- >>> G2ed0811c64be8e553d970000eaa8309f >> >> >> > -- Danti Gionatan Supporto Tecnico Assyoma S.r.l. - www.assyoma.it email: g.danti(a)assyoma.it - info(a)assyoma.it GPG public key ID: FF5F32A8

3 6

LZ4 mailbox corruption
by Renaud Allard 25 Nov '15

25 Nov '15

Hello, When I look at email files on my server (mdbox format), they contain random LZ4 stuff. I have now changed the compression to gzip and new mails look cleaner. But older ones have problems. A mail file looks like this: 2 M1e C5655b6a8 ^A^BN 00000000000006F4 Dovecot-LZ4^M*<9B><C5>^@^A^@^@^@^@^F<DD><FF><83>Return-path: <nobody(a)winnie.projecthoneypot.org> Envelope-to: nikademus(a)llorien.org Delivery-date: Mon, 22 Nov 2004 09:50:58 +0100 Received: from }^@^G<F7> [66.135.39.84] by mail.}^@<FF>< with esmtp (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) id=1CW9uQ-0002gj-El for<DE>^@^C^_;<D0>^@8<B1>(localhost. ^@<F1>^Ddomain [127.0.0.1])<E5>^@^O^S^A^H<82>(8.12.8/^G^@^R)<FF>^@<F2>^HESMTP id iAM9gl4l021209<D6>^@^_<<D7>^@^B^_><D8>^@^A<B9>3:42:47 -06<A8>^Ac(from -^B^A<BA>^@Ohost<AC>^@^\<86>/Submit)<A8>^@!cd<A8>^@N7; 4^B <8C>^@^_DZ^B^D &^@<F2>^KMessage-Id: <200411220942.^Y^A^Dq^@^O<F1>^B <FF>^BTo: Renaud AllardB^A^E<B2> Then, I randomly see errors like this in maillog: truncated lz4 chunk at 555395 Given I am still able to read the mails using imap, I think there might be a way to recover them to a proper format. However, using dsync to make a mirror throws a lot of errors like below. # dsync -v -u recover -o "mail_plugins=zlib" mirror dbox:~/ndbox dsync(recover): Error: lz4.read(//home/vmail/recover/mdbox/storage/m.2): corrupted lz4 chunk at 43551 dsync(recover): Error: write(/home/vmail/recover/ndbox/mailboxes/INBOX/dbox-Mails/.temp.1448464321.P24341Q6M965521.isildur.arnor.org) failed: Invalid argument dsync(recover): Error: copy: i_stream_read(zlib(//home/vmail/recover/mdbox/storage/m.2)) failed: read(//home/vmail/recover/mdbox/storage/m.2) failed: lz4.read(//home/vmail/recover/mdbox/storage/m.2): corrupted lz4 chunk at 43551 dsync(recover): Error: read(zlib(//home/vmail/recover/mdbox/storage/m.2)) failed: read(//home/vmail/recover/mdbox/storage/m.2) failed: lz4.read(//home/vmail/recover/mdbox/storage/m.2): corrupted lz4 chunk at 43551 (uid=42028, box=INBOX) dsync(recover): Error: Mailbox INBOX: read(msg input) failed: read(//home/vmail/recover/mdbox/storage/m.2) failed: lz4.read(//home/vmail/recover/mdbox/storage/m.2): corrupted lz4 chunk at 43551 dsync(recover): Error: read(zlib(//home/vmail/recover/mdbox/storage/m.2)) failed: read(//home/vmail/recover/mdbox/storage/m.2) failed: lz4.read(//home/vmail/recover/mdbox/storage/m.2): corrupted lz4 chunk at 43551 (uid=42028, box=INBOX) dsync(recover): Error: unlink(��) failed: No such file or directory dsync(recover): Error: unlink(��//home/vmail/recover/mdbox/mailboxes/Drafts/dbox-Mails/dovecot.index.log.2) failed: No such file or directory dsync(recover): Error: unlink(Internal error occurred. Refer to server log for more information. [2015-11-25 16:12:01]) failed: No such file or directory dsync(recover): Error: unlink(��) failed: No such file or directory dsync(recover): Error: unlink(��) failed: File name too long dsync(recover): Error: unlink(Internal error occurred. Refer to server log for more information. [2015-11-25 16:12:01]) failed: No such file or directory Any help welcome

1 0

sieve is working/forwarding mail - but not for all users
by Götz Reinicke - IT Koordinator 25 Nov '15

25 Nov '15

Hi, we have dovecot-ee-2.2.18.2 and pigeonhole/managesieve 0.4.8 running for some time. Today some users informed us that they did not get mails from one project account forwarded to there personal accounts any more. This worked till one week ago and I cant think of any changes we made... The project account keeps a copy of received mails. I tried two different accounts to configure forwarding to internal and external mail addresses which is working. Question: Any hint or idea? How may I debug sieve forwarding? Thanks and regards . Götz

3 3

Disabling auth fallback to PAM
by martin f krafft 21 Nov '15

21 Nov '15

Hi folks, According to the wiki,¹ it's considered a feature of Dovecot and its ability to support multiple authentication sources that "if the password doesn't match in the first database, it checks the next one". ¹) http://wiki.dovecot.org/Authentication/MultipleDatabases I think it's great that Dovecot allows auth sources to be stacked like this, but I am not sold on the idea that the next database ought to be tried when a *password* does not match. Let me elaborate: If the first database has knowledge of a user, then it can (should) be considered authoritative, and if the provided password does not match, it's an authentication error right away. Only if the first source does not posess any knowledge about a given user, then should Dovecot proceed to query/check with the next database. Can this be configured somehow? If not, would it make sense to make this behaviour configurable? Thanks, -- @martinkrafft | http://madduck.net/ | http://two.sentenc.es/ "the ships hung in the sky in much the same way that bricks don't." -- hitchhiker's guide to the galaxy spamtraps: madduck.bogus(a)madduck.net

2 2

doveadm import/sync with read-only source location
by Teodor Milkov 21 Nov '15

21 Nov '15

Hello, Currently doveadm tool can't be used with read-only source locations because it's trying to create lock files. I'd guess lock files shouldn't be necessary on a read-only media, because no one else is going to change anything while our doveadm instance is running anyway. Example: doveadm import -u test(a)example.com maildir:/backup.0/domains/example.com/postmaster/Maildir restored ALL doveadm(test(a)example.com): Error: open(/backup.0/domains/example.com/postmaster/Maildir/.Trash/dovecot-uidlis… failed: Read-only file system Perhaps this should be something like doveadm backup -R flag, but in the opposite direction – i.e. we have a [full] backup command, but no [partial] restore command right now. Or am I missing something? Best regards, Teodor

3 2

Shortcomings of Maildir++ layout
by Hadmut Danisch 21 Nov '15

21 Nov '15

Hi, I am trying to deal with the problem, that under regular mbox format a path can lead to either a file or a directory, but not both, while under IMAP, a path is usually both, a message folder containing subfolders. I found dovecot's approach to this problem, the Maildir++ layout described under http://wiki2.dovecot.org/MboxChildFolders , and was astonished to see, what problems come with Maildir++ and how complicated dovecot tries to deal with them. I wonder why dovecot is not using a much easier approach and just uses a configurable prefix and/or suffix like .dir or ____ for directory names, e.g. INBOX -> ~/mail/inbox abc -> ~/mail/abc abc/def -> ~/mail/abc.dir/def or ~/mail/___abc___/def which would make all that trouble with .subscriptions and .index much more easier. In my eyes the Maildir++ layout is overcomplicated because of the heap of workarounds to the self-created problems. regards Hadmut

4 5

bug in shared folders/lazy_expunge
by Infoo Matic 18 Nov '15

18 Nov '15

Hi list, I have a problem I was not able to resolve with my current setup (quite basic, the relevant part appended [1]). When userA shares a folder with userB then userB cannot access his mailbox. It's the same problem others have mentioned in *) http://www.dovecot.org/list/dovecot/2014-August/097449.html *) http://dovecot.org/pipermail/dovecot/2014-May/096355.html Could we please have a fix? TIA infoomatic [1] namespace { list = children location = mdbox:/var/lib/vmail/mail/%d/%%u prefix = shared/%%u/ separator = / subscriptions = no type = shared } namespace expunged { hidden = yes list = no location = mdbox:/var/lib/vmail/expunged/mail/%d/%u:INDEX=/var/lib/vmail/expunged/index/%d/%u:MAILBOXDIR=expunged prefix = .EXPUNGED/ subscriptions = no } namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = / type = private }

1 0

usage of recipient delimiters
by fsantiago＠garbage-juice.com 15 Nov '15

15 Nov '15

Hello, I have a forum system which can potentially have users send email to it for posting purposes that arrives addressed to a particular user account with a recipient delimiter: user+1a2b3c4d5e6f(a)domain.com The forum server is supposed to check the "user" account mailbox's inbox for the messages and post them to the site automatically. This doesn't work right now because when the messages arrive, they get placed into a newly and automatically created folder named after the alpha numeric string after the + in the address (eg... 1a2b3c4d5e6f). I feel dovecot is likely doing this. any ideas why and how i can shut this off and just allow them to arrive and stay in the inbox? My version is: 2.2.10 My config is: # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 4.1.5-x86_64-linode61 x86_64 CentOS Linux release 7.1.1503 (Core) auth_master_user_separator = * auth_mechanisms = PLAIN LOGIN dict { acl = mysql:/etc/dovecot/dovecot-share-folder.conf quotadict = mysql:/etc/dovecot/dovecot-used-quota.conf } first_valid_uid = 2000 last_valid_uid = 2000 listen = * [::] log_path = /var/log/dovecot.log mail_gid = 2000 mail_location = maildir:%Lh/Maildir/:INDEX=%Lh/Maildir/ mail_plugins = quota mailbox_alias acl mail_uid = 2000 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 = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Spam { auto = no special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / type = private } namespace { list = children location = maildir:%%Lh/Maildir/:INDEX=%%Lh/Maildir/Shared/%%u prefix = Shared/%%u/ separator = / subscriptions = yes type = shared } passdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } passdb { args = /etc/dovecot/dovecot-master-users driver = passwd-file master = yes } plugin { acl = vfile acl_shared_dict = proxy::acl auth_socket_path = /var/run/dovecot/auth-master mailbox_alias_new = Sent Messages mailbox_alias_new2 = Sent Items mailbox_alias_old = Sent mailbox_alias_old2 = Sent quota = dict:user::proxy::quotadict quota_rule = *:storage=1G quota_warning = storage=85%% quota-warning 85 %u quota_warning2 = storage=90%% quota-warning 90 %u quota_warning3 = storage=95%% quota-warning 95 %u sieve = %Lh/sieve/dovecot.sieve sieve_before = /var/vmail/sieve/dovecot.sieve sieve_dir = %Lh/sieve sieve_global_dir = /var/vmail/sieve } protocols = pop3 imap sieve lmtp service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0666 user = postfix } unix_listener auth-master { group = vmail mode = 0666 user = vmail } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } } service dict { unix_listener dict { group = vmail mode = 0660 user = vmail } } service imap-login { process_limit = 500 service_count = 1 } service lmtp { executable = lmtp -L inet_listener lmtp { address = 127.0.0.1 port = 24 } process_min_avail = 5 unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } user = vmail } service managesieve-login { inet_listener sieve { address = 127.0.0.1 port = 4190 } } service pop3-login { service_count = 1 } service quota-warning { executable = script /usr/local/bin/dovecot-quota-warning.sh unix_listener quota-warning { group = vmail mode = 0660 user = vmail } } ssl = required ssl_cert = </etc/pki/tls/certs/iRedMail.crt ssl_cipher_list = ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_dh_parameters_length = 2048 ssl_key = </etc/pki/tls/private/iRedMail.key ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv2 !SSLv3 userdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } protocol lda { auth_socket_path = /var/run/dovecot/auth-master lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes log_path = /var/log/dovecot-sieve.log mail_plugins = quota mailbox_alias acl sieve postmaster_address = root } protocol lmtp { info_log_path = /var/log/dovecot-lmtp.log lmtp_save_to_detail_mailbox = yes mail_plugins = quota sieve postmaster_address = postmaster recipient_delimiter = + } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_max_userip_connections = 20 mail_plugins = quota mailbox_alias acl imap_quota imap_acl } protocol pop3 { mail_max_userip_connections = 20 mail_plugins = quota mailbox_alias acl pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } Thank you. - Fabian S.

3 2

How to Restore emails
by Mark Foley 13 Nov '15

13 Nov '15

I have a user who accidentially deleted a large number of emails prior to a certain date. He wants them back. I do have a tarfile backup of these messages. Is there a good way to restore them? Can I simply restore them to the appropriate Maildir directory and dovecot will just "figure it out"? Thanks, --Mark

3 5

lmtp seg fault
by Robert Blayzor 13 Nov '15

13 Nov '15

dovecot -n # 2.2.19: /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.9 (357ac0a0e68b+) # OS: FreeBSD 10.2-RELEASE-p7 amd64 doveconf: Warning: Dovecot was last started using /etc/dovecot/dovecot.conf, but this config is /usr/local/etc/dovecot/dovecot.conf auth_cache_size = 10 M auth_cache_ttl = 5 mins auth_mechanisms = plain login auth_socket_path = /var/run/dovecot/auth-userdb auth_verbose = yes auth_worker_max_count = 10 base_dir = /var/run/dovecot/ default_client_limit = 2000 default_process_limit = 200 disable_plaintext_auth = no first_valid_uid = 25 imap_idle_notify_interval = 4 mins log_timestamp = "%Y-%m-%d %H:%M:%S " login_greeting = Ready to serve. mail_fsync = always mail_location = maildir:~/Maildir mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = zlib quota mail_temp_dir = /var/tmp mailbox_list_index = yes maildir_very_dirty_syncs = yes managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body environment mailbox date index ihave duplicate mbox_write_locks = fcntl mmap_disable = yes namespace inbox { inbox = yes location = mailbox Archive { auto = subscribe special_use = \Archive } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { quota = maildir:User quota quota_exceeded_message = Quota exceeded (Mailbox is full) quota_rule = *:storage=1G quota_rule2 = Trash:ignore sieve = ~/.dovecot.sieve sieve_default = /etc/dovecot/sieve/global/JunkFolder.sieve sieve_dir = ~/.sieve sieve_extensions = -enotify sieve_global_dir = /etc/dovecot/sieve/global/ zlib_save = xz zlib_save_level = 6 } pop3_fast_size_lookups = yes pop3_save_uidl = yes protocols = imap pop3 lmtp sieve rejection_reason = Your message to <%t> was rejected:%n%n %r%n rejection_subject = [BOUNCE] %s service imap-login { inet_listener imap { port = 143 } process_min_avail = 4 service_count = 100 } service imap { executable = imap last-login } service last-login { executable = script-login /etc/dovecot/post-login.sh user = mailnull } service lmtp { process_min_avail = 4 unix_listener lmtp { mode = 0666 } user = mailnull } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 1 } service managesieve { process_limit = 100 } service pop3-login { inet_listener pop3 { port = 110 } process_min_avail = 4 service_count = 100 } service pop3 { executable = pop3 last-login } ssl = no ssl_cipher_list = ALL:!SSLv2:!LOW:!ADH:!NULL:!DES:@STRENGTH ssl_protocols = !SSLv2 !SSLv3 submission_host = localhost:25 userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol lmtp { mail_plugins = zlib quota sieve } protocol lda { mail_plugins = zlib quota } protocol imap { mail_max_userip_connections = 8 mail_plugins = zlib quota imap_quota } protocol pop3 { mail_max_userip_connections = 2 mail_plugins = zlib quota } protocol sieve { mail_max_userip_connections = 3 managesieve_implementation_string = Dovecot managesieve_max_line_length = 65536 } GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"...(no debugging symbols found)... Core was generated by `lmtp'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/local/lib/dovecot/libdovecot-lda.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/dovecot/libdovecot-lda.so.0 Reading symbols from /usr/local/lib/dovecot/libdovecot-storage.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/dovecot/libdovecot-storage.so.0 Reading symbols from /usr/local/lib/dovecot/libdovecot.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/dovecot/libdovecot.so.0 Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /usr/local/lib/dovecot/lib10_quota_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/dovecot/lib10_quota_plugin.so Reading symbols from /usr/local/lib/dovecot/lib20_zlib_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/dovecot/lib20_zlib_plugin.so Reading symbols from /lib/libz.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/libz.so.6 Reading symbols from /usr/lib/libbz2.so.4...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libbz2.so.4 Reading symbols from /usr/lib/liblzma.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/lib/liblzma.so.5 Reading symbols from /usr/local/lib/dovecot/lib90_sieve_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/dovecot/lib90_sieve_plugin.so Reading symbols from /usr/local/lib/dovecot-2.2-pigeonhole/libdovecot-sieve.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/local/lib/dovecot-2.2-pigeonhole/libdovecot-sieve.so.0 Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x0000000010dd08c0 in buffer_free () from /usr/local/lib/dovecot/libdovecot.so.0 (gdb) bt #0 0x0000000010dd08c0 in buffer_free () from /usr/local/lib/dovecot/libdovecot.so.0 #1 0x0000000010b12908 in mail_transaction_log_file_open () from /usr/local/lib/dovecot/libdovecot-storage.so.0 #2 0x0000000010b165e0 in mail_transaction_log_find_file () from /usr/local/lib/dovecot/libdovecot-storage.so.0 #3 0x0000000010b149d7 in mail_transaction_log_view_set () from /usr/local/lib/dovecot/libdovecot-storage.so.0 #4 0x0000000010b03f4a in mail_index_sync_map () from /usr/local/lib/dovecot/libdovecot-storage.so.0 #5 0x0000000010afb288 in mail_index_map () from /usr/local/lib/dovecot/libdovecot-storage.so.0 #6 0x0000000010b11245 in mail_index_reset_error () from /usr/local/lib/dovecot/libdovecot-storage.so.0 #7 0x0000000010b109ad in mail_index_open () from /usr/local/lib/dovecot/libdovecot-storage.so.0 #8 0x0000000010b10853 in mail_index_open () from /usr/local/lib/dovecot/libdovecot-storage.so.0 #9 0x0000000010aebd0b in index_storage_mailbox_open () from /usr/local/lib/dovecot/libdovecot-storage.so.0 #10 0x0000000010aa3aec in maildir_is_backend_readonly () from /usr/local/lib/dovecot/libdovecot-storage.so.0 #11 0x0000000010aa30f1 in maildir_is_backend_readonly () from /usr/local/lib/dovecot/libdovecot-storage.so.0 #12 0x0000000011e15052 in zlib_plugin_deinit () from /usr/local/lib/dovecot/lib20_zlib_plugin.so #13 0x0000000010a7cfe2 in mailbox_open () from /usr/local/lib/dovecot/libdovecot-storage.so.0 #14 0x0000000010a7cee4 in mailbox_open () from /usr/local/lib/dovecot/libdovecot-storage.so.0 #15 0x0000000010832330 in mail_deliver_save_open () from /usr/local/lib/dovecot/libdovecot-lda.so.0 #16 0x00000000128b4e1f in sieve_action_opr_optional_read () from /usr/local/lib/dovecot-2.2-pigeonhole/libdovecot-sieve.so.0 #17 0x00000000128ac9b3 in sieve_result_execute () from /usr/local/lib/dovecot-2.2-pigeonhole/libdovecot-sieve.so.0 #18 0x00000000128bc5bc in sieve_execute () from /usr/local/lib/dovecot-2.2-pigeonhole/libdovecot-sieve.so.0 #19 0x000000001266b06e in sieve_plugin_init () from /usr/local/lib/dovecot/lib90_sieve_plugin.so #20 0x00000000108329aa in mail_deliver () from /usr/local/lib/dovecot/libdovecot-lda.so.0 #21 0x00000000004087f1 in cmd_xclient () #22 0x0000000000407fbf in cmd_data () #23 0x0000000010de7bd3 in io_loop_call_io () from /usr/local/lib/dovecot/libdovecot.so.0 #24 0x0000000010de96ef in io_loop_handler_run_internal () from /usr/local/lib/dovecot/libdovecot.so.0 #25 0x0000000010de80d4 in io_loop_handler_run () from /usr/local/lib/dovecot/libdovecot.so.0 #26 0x0000000010de7eb8 in io_loop_run () from /usr/local/lib/dovecot/libdovecot.so.0 #27 0x0000000010d841d8 in master_service_run () from /usr/local/lib/dovecot/libdovecot.so.0 #28 0x0000000000405531 in main ()

1 0

fail: doveadm backup -s "<state>" with a huuge number of mailboxes
by Heiko Schlittermann 12 Nov '15

12 Nov '15

Hello, I'm using 2.2.13. For syncing I'm using repetitions of about the following (simplified for readability): state_file=.s doveadm \ -o imapc_master_user=<master> \ -o imapc_password=<pw> \ -o imapc_host=<host> \ -o mail_fsync=never \ backup -s "$(<.s)" -u "<user>" -R imapc: >.s_new mv .s_new .s The user has about 4501 IMAP folders. This makes a huge state output of about 128 kB. This in turn leads to an overly long command line in the next iteration. (excuse: command line too long) Is there any chance to solve this? I think, the only possibility would be to have doveadm-backup -s read the state from a *file*, wouldn't it? (Apart from the fact that I do not see a manpage for this, except entries in the Wiki (but this may be due to poor packaging) of the Debian dovecot package.) Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de ---------------------------- internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - gnupg encrypted messages are welcome --------------- key ID: F69376CE - ! key id 7CBF764A and 972EAC9F are revoked since 2015-01 ------------ -

2 2

Problems after upgrade from 2.0 to 2.2
by Frank Rust 12 Nov '15

12 Nov '15

Hi all, after upgrade from some 2.0 version to 2.2.19 (debian) i face map login problems: # doveconf -n # 2.2.19 (ca91d540fd87): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.9 # OS: Linux 2.6.32-5-amd64 x86_64 Debian 8.2 ext4 auth_debug = yes auth_debug_passwords = yes auth_verbose = yes auth_verbose_passwords = plain debug_log_path = /var/log/dovecot-debug.log hostname = test.my.domain.de info_log_path = /var/log/dovecot.log mail_access_groups = smmta mail_debug = yes mail_location = mbox:/extra/mail/mbox.dir/%u/mailboxes:DIRNAME=mBoX-MeSsAgEs:INDEX=/extra/mail/mbox.dir/%u/index:CONTROL=/extra/mail/mbox.dir/%u/control:INBOX=/extra/mail/%u mail_plugins = quota mail_privileged_group = smmta 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 index ihave duplicate namespace inbox { location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename flag_change append quota = fs:User quota quota_rule = *:storage=1G quota_rule2 = Trash:storage=+100M quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = file:~/sieve;active=~/.dovecot.sieve } postmaster_address = postmaster(a)my.domain.de protocols = " imap sieve pop3" quota_full_tempfail = yes ssl = required ssl_cert = </etc/ssl/StartCom/test.my.domain.pem ssl_cipher_list = EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+SHA256:EECDH+aRSA+RC4:EDH+aRSA EECDH RC4:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS ssl_key = </etc/ssl/StartCom/test.my.domain.key ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv2 !SSLv3 userdb { driver = passwd } verbose_ssl = yes protocol lda { mail_plugins = } When I try to log in with openssl: $ openssl s_client -connect test.familie-rust.de:993 CONNECTED(00000003) depth=1 C = IL, O = StartCom Ltd., OU = Secure Digital Certificate Signing, CN = StartCom Class 1 Primary Intermediate Server CA verify error:num=20:unable to get local issuer certificate --- Certificate chain 0 s:/C=DE/CN=test.my.domain.de/emailAddress=postmaster@my.domain.de i:/C=IL/O=StartCom Ltd./OU=Secure Digital Certificate Signing/CN=StartCom Class 1 Primary Intermediate Server CA 1 s:/C=IL/O=StartCom Ltd./OU=Secure Digital Certificate Signing/CN=StartCom Class 1 Primary Intermediate Server CA i:/C=IL/O=StartCom Ltd./OU=Secure Digital Certificate Signing/CN=StartCom Certification Authority --- Server certificate -----BEGIN CERTIFICATE—— (…) -----END CERTIFICATE----- subject=/C=DE/CN=test.my.domain.de/emailAddress=postmaster(a)my.domain.de issuer=/C=IL/O=StartCom Ltd./OU=Secure Digital Certificate Signing/CN=StartCom Class 1 Primary Intermediate Server CA --- No client certificate CA names sent Peer signing digest: SHA512 Server Temp Key: ECDH, P-384, 384 bits --- SSL handshake has read 4328 bytes and written 506 bytes --- New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES256-GCM-SHA384 Server public key is 4096 bit Secure Renegotiation IS supported Compression: NONE Expansion: NONE No ALPN negotiated SSL-Session: Protocol : TLSv1.2 Cipher : ECDHE-RSA-AES256-GCM-SHA384 Session-ID: B0...5B Session-ID-ctx: Master-Key: 59D...EC0 Key-Arg : None PSK identity: None PSK identity hint: None SRP username: None TLS session ticket lifetime hint: 300 (seconds) TLS session ticket: 0000 - 35 47 73 57 22 45 21 7d-fe ea a4 36 f1 35 76 3a 5GsW"E!}…6.5v: (…) Start Time: 1447309592 Timeout : 300 (sec) Verify return code: 20 (unable to get local issuer certificate) --- * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN] Dovecot ready. 01 login frank myPassword * BYE Internal error occurred. Refer to server log for more information. closed And in the log files I find following information: dovecot.log Nov 12 07:47:27 imap-login: Info: Login: user=<frank>, method=PLAIN, rip=134.169.39.105, lip=134.169.39.22, mpid=9475, TLS, session=<...> dovecot-debug.log: Nov 12 07:47:27 imap-login: Debug: SSL: elliptic curve secp384r1 will be used for ECDH and ECDHE key exchanges Nov 12 07:47:27 auth: Debug: auth client connected (pid=11158) Nov 12 07:47:27 imap-login: Debug: SSL: where=0x10, ret=1: before/accept initialization [134.169.39.105] Nov 12 07:47:27 imap-login: Debug: SSL: where=0x2001, ret=1: before/accept initialization [134.169.39.105] Nov 12 07:47:27 imap-login: Debug: SSL: where=0x2001, ret=1: unknown state [134.169.39.105] Nov 12 07:47:27 imap-login: Debug: SSL: where=0x2001, ret=1: unknown state [134.169.39.105] Nov 12 07:47:27 imap-login: Debug: SSL: where=0x2001, ret=1: unknown state [134.169.39.105] Nov 12 07:47:27 imap-login: Debug: SSL: where=0x2001, ret=1: unknown state [134.169.39.105] Nov 12 07:47:27 imap-login: Debug: SSL: where=0x2001, ret=1: unknown state [134.169.39.105] Nov 12 07:47:27 imap-login: Debug: SSL: where=0x2001, ret=1: unknown state [134.169.39.105] Nov 12 07:47:27 imap-login: Debug: SSL: where=0x2002, ret=-1: unknown state [134.169.39.105] Nov 12 07:47:27 imap-login: Debug: SSL: where=0x2002, ret=-1: unknown state [134.169.39.105] Nov 12 07:47:27 imap-login: Debug: SSL: where=0x2001, ret=1: unknown state [134.169.39.105] Nov 12 07:47:27 imap-login: Debug: SSL: where=0x2002, ret=-1: unknown state [134.169.39.105] Nov 12 07:47:27 imap-login: Debug: SSL: where=0x2001, ret=1: unknown state [134.169.39.105] Nov 12 07:47:27 imap-login: Debug: SSL: where=0x2001, ret=1: unknown state [134.169.39.105] Nov 12 07:47:27 imap-login: Debug: SSL: where=0x2001, ret=1: unknown state [134.169.39.105] Nov 12 07:47:27 imap-login: Debug: SSL: where=0x2001, ret=1: unknown state [134.169.39.105] Nov 12 07:47:27 imap-login: Debug: SSL: where=0x20, ret=1: SSL negotiation finished successfully [134.169.39.105] Nov 12 07:47:27 imap-login: Debug: SSL: where=0x2002, ret=1: SSL negotiation finished successfully [134.169.39.105] Nov 12 07:47:27 auth: Debug: client in: AUTH 1 PLAIN service=imap secured session=QkLwUFIkXsCGqSdp lip=134.169.39.22 rip=134.169.39.105 lport=993 rport=49246 resp=xxxx (previous base64 data removed) Nov 12 07:47:27 auth-worker(11140): Debug: pam(frank,134.169.39.105): lookup service=dovecot Nov 12 07:47:27 auth-worker(11140): Debug: pam(frank,134.169.39.105): #1/1 style=1 msg=Password: Nov 12 07:47:27 auth: Debug: client passdb out: OK 1 user=frank Nov 12 07:47:27 auth: Debug: master in: REQUEST 3038248961 11158 1 4e2362c2872f9288b7c8c3ebd8469620 session_pid=11159 request_auth_token Nov 12 07:47:27 auth-worker(11140): Debug: pam(frank,134.169.39.105): lookup Nov 12 07:47:27 auth: Debug: master userdb out: USER 3038248961 frank system_groups_user=frank uid=1000 gid=100 home=/home/frank auth_token=1e04d2c61fb327ec14c1e54ff678d73a325d20bf Nov 12 07:47:27 imap(frank): Debug: Loading modules from directory: /usr/lib/dovecot/modules Nov 12 07:47:27 imap(frank): Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so Nov 12 07:47:27 imap(frank): Debug: Effective uid=1000, gid=100, home=/home/frank Nov 12 07:47:27 imap(frank): Debug: Quota root: name=User quota backend=fs args= Nov 12 07:47:27 imap(frank): Debug: Quota rule: root=User quota mailbox=* bytes=1073741824 messages=0 Nov 12 07:47:27 imap(frank): Debug: Quota rule: root=User quota mailbox=Trash bytes=+104857600 messages=0 Nov 12 07:47:27 imap(frank): Debug: Quota warning: bytes=1020054732 (95%) messages=0 reverse=no command=quota-warning 95 frank Nov 12 07:47:27 imap(frank): Debug: Quota warning: bytes=858993459 (80%) messages=0 reverse=no command=quota-warning 80 frank Nov 12 07:47:27 imap(frank): Debug: Quota grace: root=User quota bytes=107374182 (10%) Nov 12 07:47:27 imap(frank): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=no, hidden=no, list=yes, subscriptions=yes location=mbox:/extra/mail/mbox.dir/frank/mailboxes:DIRNAME=mBoX-MeSsAgEs:INDEX=/extra/mail/mbox.dir/frank/index:CONTROL=/extra/mail/mbox.dir/frank/control:INBOX=/extra/mail/frank Nov 12 07:47:27 imap(frank): Debug: fs: root=/extra/mail/mbox.dir/frank/mailboxes, index=/extra/mail/mbox.dir/frank/index, indexpvt=, control=/extra/mail/mbox.dir/frank/control, inbox=/extra/mail/frank, alt= Nov 12 07:47:27 imap(frank): Debug: fs quota add mailbox dir = /extra/mail/mbox.dir/frank/mailboxes Nov 12 07:47:27 imap(frank): Debug: fs quota block device = /dev/mapper/ownCloudVG-ownCloudData Nov 12 07:47:27 imap(frank): Debug: fs quota mount point = /extra Nov 12 07:47:27 imap(frank): Debug: fs quota mount type = ext4 Nov 12 07:47:27 imap-login: Debug: SSL alert: close notify [134.169.39.105] What could cause the problem? The problem is not quota related (I enhanced the allowed quota and got the same results) best regards, Frank

2 3

hunting the fatty
by mancyborg＠gmail.com 11 Nov '15

11 Nov '15

Hello dear list, I've recently discovered 'doveadm stats' and I'm trying to use "doveadm stats dump user" and "doveadm stats dump session" to understand the pop/imap users that put more stress on the hard disks. My problem is that some users refuse to delete their emails from the server, so they keep 20GB of maildir files on the server, the webmail (roundcube) takes forever to open the inbox, the imap searches takes forever and meanwhile all the users wait. (already tried roundcube + memcache(d) but didn't help) So my problem is not the storage usage itself: I don't care if the user gets tons of emails with big attachments; my problem is when the user opens / searches an imap folder with more than 10K mails and iostat util goes 100% for minutes. So I've enabled dovecot's stats and enjoying "doveadm stats top", "stats-top.pl" and "doveadm stats dump user/session", but talking about "doveadm stats dump user" and its output fields: user reset_timestamp last_update num_logins num_cmds user_cpu sys_cpu min_faults maj_faults vol_cs invol_cs disk_input disk_output read_count read_bytes write_count write_bytes mail_lookup_path mail_lookup_attr mail_read_count mail_read_bytes mail_cache_hits I'm not sure which of those fields can help me and I can't find any relevant documentation. So here are my questions: 1. is there a documentation for those 21 fields and for 'doveadm stats' in general ? 2. what's the difference between disk_output, read_bytes, read_count and mail_read_bytes ? 3. which field of those is, in your opinion, more representative for expressing the workload that gives me problems ? 4. which settings do I need to store 1 week worth of stats ? I'm currenty using the 'standard' values: stats_refresh = 30 secs stats_track_cmds = yes stats_memory_limit = 16 M stats_command_min_time = 1 mins stats_domain_min_time = 12 hours stats_ip_min_time = 12 hours stats_session_min_time = 15 mins stats_user_min_time = 1 hours Can you please tell me the correct parameters to store 1 week of stats ? Thank you, Mike

3 9

log client certificate
by Eugenio De Vena 11 Nov '15

11 Nov '15

Hello, I would like to log the client certificate ( don't want to authenticate using client certificate but just "log" the client certificate if present ( both Subject and Public key ) ). Is it possibile ? Eugenio

1 0

Active directory
by Станислав Черкасов 11 Nov '15

11 Nov '15

Hello. I have a iRedmail server integrated with AD. I make it following theese instructions http://www.iredmail.org/docs/active.directory.html In my AD i have a user attributes: sAMAccountName = user1 userPrincipalName = csi(a)int.mdom.com proxyAddresses = mail1(a)out.lor.com i need login with user user1 without domain and then have an address mail1(a)out.lor.com i user it in /⁠etc/⁠dovecot/⁠dovecot-⁠ldap.conf -⁠-⁠-⁠-⁠ hosts = dc1.int.mdom.com:389 ldap_version = 3 auth_bind = yes dn = userksa dnpass = sdjfuihJKHSAJKDHQUWjdskfh base = OU=Users,OU=QOL,DC=int,DC=mdom,DC=com scope = subtree deref = never user_filter = (&(objectClass=user)(sAMAccountName=%n) (memberof=CN=Mail_Users,OU=Groups,OU=SFP,DC=int,DC=mdom,DC=com)) pass_filter = (&(objectClass=user)(sAMAccountName=%n) (memberof=CN=Mail_Users,OU=Groups,OU=SFP,DC=int,DC=mdom,DC=com)) default_pass_scheme = CRYPT user_attrs = =home=/var/vmail/vmail1/%Ld/%Ln/Maildir/,=mail=maildir:/var/vmail/vmail1/%Ld/%Ln/Maildir/ -⁠-⁠-⁠-⁠ i have tried to do: #user_filter = (&(proxyAddresses=%u) (objectClass=person)(memberof=CN=Mail_Users,OU=Groups,OU=SFP,DC=int,DC=mdom,DC=com)) #pass_filter = (&(proxyAddresses=%u) (objectClass=person)(memberof=CN=Mail_Users,OU=Groups,OU=SFP,DC=int,DC=mdom,DC=com)) but nothing works.

1 0

Dovecot+AD
by Станислав Черкасов 11 Nov '15

11 Nov '15

Hello. I have a iRedmail server integrated with AD. I make it following theese instructions http://www.iredmail.org/docs/active.directory.html In my AD i have a user attributes: sAMAccountName = user1 userPrincipalName = csi(a)int.mdom.com proxyAddresses = mail1(a)out.lor.com i need login with user user1 without domain and then have an address mail1(a)out.lor.com i user it in /etc/dovecot/dovecot-ldap.conf ---- hosts = dc1.int.mdom.com:389 ldap_version = 3 auth_bind = yes dn = userksa dnpass = sdjfuihJKHSAJKDHQUWjdskfh base = OU=Users,OU=QOL,DC=int,DC=mdom,DC=com scope = subtree deref = never user_filter = (&(objectClass=user)(sAMAccountName=%n) (memberof=CN=Mail_Users,OU=Groups,OU=SFP,DC=int,DC=mdom,DC=com)) pass_filter = (&(objectClass=user)(sAMAccountName=%n) (memberof=CN=Mail_Users,OU=Groups,OU=SFP,DC=int,DC=mdom,DC=com)) default_pass_scheme = CRYPT user_attrs = =home=/var/vmail/vmail1/%Ld/%Ln/Maildir/,=mail=maildir:/var/vmail/vmail1/%Ld/%Ln/Maildir/ ---- i have tried to do: #user_filter = (&(proxyAddresses=%u) (objectClass=person)(memberof=CN=Mail_Users,OU=Groups,OU=SFP,DC=int,DC=mdom,DC=com)) #pass_filter = (&(proxyAddresses=%u) (objectClass=person)(memberof=CN=Mail_Users,OU=Groups,OU=SFP,DC=int,DC=mdom,DC=com)) but nothing works.

1 0

locked ldap users
by klemen＠arnes.si 11 Nov '15

11 Nov '15

Hello. I'm having a problem regarding locked users in ldap. We are using 389DS ldap server. We lock our users with nsAccountLock=true. If user successfully logs into dovecot, his credentials gets cached. When this user is locked its credentials still stay in cache. The problem I'm having is that our ldap server returns error code 53 ("Unwilling to perform - Account inactivated"). Dovecot takes this error code and decides that ldap doesnt work so it takes users credentials from cache (like stated in docs). User can still login untill his credentials are cleared from cache. Error message in logs: ldap(USERNAME,193.X.Y.Z,<aaaaaaaaaaaaaaaa>): ldap_bind() failed: Server is unwilling to perform Oct 20 14:39:31 SERVER dovecot: auth: ldap(USERNAME,193.X.Y.Z,<aaaaaaaaaaaaaaaa>): Falling back to expired data from cache Does dovecot reacts to error code 53 as it should? Maybe our ldap server should return different error code - like 49/533 (Account_disabled)? How would dovecot react to error code 49? Currenty we solve this problem by taking list of locked users and clear cache every minute. thank you and best regards, Klemen Andreuzzi Arnes

1 0

procmail as a content_filter with dovecot
by Vicki Brown 11 Nov '15

11 Nov '15

I am using Mac OS X Server. OS X Server uses postfix with dovecot set as mail_transport. I want to add procmail to the mix. I cannot use the (typical) mailbox_command = procmail -a "$EXTENSION" because mailbox_transport = dovecot overrides any mailbox_command parameter and it is NOT Possible to change, remove, or otherwise vary the mailbox_transport on OS X server. I'm thinking I should be able to set up a content_filter for procmail, but I've found nothing online to tell me if this is possible or how to declare it. Can anyone help? -- Vicki cfcl.com/vlb twitter.com/vlb

4 7

LDAP schema for dovecot proxy?
by Andrey Fesenko 10 Nov '15

10 Nov '15

Hello, I want to deploy dovecot proxy/director with the backend and authorization in LDAP. Dovecot wiki specifies only what is necessary to apply additional arguments that the scheme would have earned a proxy, but no solid LDAP schema. Is there such a scheme, such as the existing scheme http://www.zytrax.com/books/ldap/ape/courier.html http://pro-ldap.ru/sources/schema/qmail.schema http://open.rhx.it/phamm/schema/phamm.schema Unfortunately for the tasks they are not good because they just no dovecot-specific variables

1 0

Fw: new message
by dovecot 10 Nov '15

10 Nov '15

Hey! New message, please read <http://spectrumglobus.com/white.php?p> dovecot

1 0

Fw: new message
by dovecot 10 Nov '15

10 Nov '15

Hey! New message, please read <http://zoomincinema.in/rather.php?2> dovecot

1 0

Fw: new message
by fila＠pruda.com 10 Nov '15

10 Nov '15

Hey! New message, please read <http://prestigeimagegroup.com/few.php?hcpa> fila(a)pruda.com

1 0

Problem with permissions of the logfile
by Andreas Meyer 07 Nov '15

07 Nov '15

Hello! I want to have dovecot log into a separate file and set log_path = /var/log/dovecot instead of log_path = syslog Dovecot does not start if I do this. Tried to change permissions and overschip of the file, no luck, ha. Deleted it in the hope dovecot creates it but no. If I set log_path = syslog dovecot starts and I see it is running as # ps aux |grep dove root 2429 0.2 0.0 3416 2568 ? Ss 16:42 0:00 /usr/sbin/dovecot -F dovecot 2431 0.0 0.0 3100 2080 ? S 16:42 0:00 dovecot/anvil root 2432 0.0 0.0 3228 2316 ? S 16:42 0:00 dovecot/log root 2434 0.0 0.0 4220 3300 ? S 16:42 0:00 dovecot/config What must be done to have dovecot log into the specified file? Greetings Andreas

3 2

Questions on supporting Shared Mailboxes using imapc://
by Nathan Coulson 06 Nov '15

06 Nov '15

I was not able to get a shared mailbox setup working using imapc. Tested using mailboxes on the same server, as well as other servers. We are using dovecot 2.2.10 from Centos 7, following the guide at http://wiki2.dovecot.org/SharedMailboxes/ClusterSetup imapc_host=192.168.5.5 #(Local dovecot server) imapc_master_user= %u imapc_password=TempPass #imapc_user=test2(a)example.com # Added for testing. namespace { type = shared separator = / prefix = shared/%%u/ list = children location = imapc:~/shared/%%u/ } namespace { # used as a control to verify that shared mailboxes work type = shared separator = / prefix = shared2/%%u/ list = children location = sdbox:%%h:INDEXPVT=~/shared2/%%u } dict { acl = mysql:/etc/dovecot/dovecot-sql_aggelos_shares.conf.ext } plugin { acl = vfile acl_shared_dict = proxy::acl } mail_plugins = acl protocol imap { mail_plugins = acl imap_acl } passdb { driver = sql args = /etc/dovecot/dovecot-sql.conf.ext } passdb { # for master user logins driver = sql args = /etc/dovecot/dovecot-sql_aggelos_aclmaster.conf.ext master = yes pass = yes } userdb { driver = sql args = /etc/dovecot/dovecot-sql.conf.ext } I can login using test2@example.com*test@example.com (and see all of test2's email), and it looks like it authenticates ok via imap, but shared never shows up. No issues using shared2 which uses direct access to the mailbox doveadm acl debug -u test(a)example.com shared/test2(a)example.com (Fails, uses imapc) doveadm(test(a)example.com): Info: Mailbox 'INBOX' is in namespace 'shared/test2(a)example.com/' doveadm(test(a)example.com): Info: Mailbox path: /misc/1/2/mail/test@example.com-4/shared/test2@example.com/.INBOX doveadm(test(a)example.com): Info: All message flags are shared across users in mailbox doveadm(test(a)example.com): Info: User test(a)example.com has no rights for mailbox doveadm(test(a)example.com): Error: User test(a)example.com is missing 'lookup' right doveadm(test(a)example.com): Info: Mailbox shared/test2(a)example.com is NOT visible in LIST doveadm acl debug -u test(a)example.com shared/test2(a)example.com/Junk (Fails, contains a folder that exists) doveadm(test(a)example.com): Info: Mailbox 'Junk' is in namespace 'shared/test2(a)example.com/' doveadm(test(a)example.com): Info: Mailbox path: /misc/1/2/mail/test@example.com-4/shared/test2@example.com/.Junk doveadm(test(a)example.com): Info: All message flags are shared across users in mailbox doveadm(test(a)example.com): Info: User test(a)example.com has no rights for mailbox doveadm(test(a)example.com): Error: User test(a)example.com is missing 'lookup' right doveadm(test(a)example.com): Info: Mailbox shared/test2(a)example.com/Junk is NOT visible in LIST doveadm acl debug -u test(a)example.com shared/test2(a)example.com/z (Fails, contains a folder that does not exist. Expected result) doveadm(test(a)example.com): Error: Mailbox 'z' in namespace 'shared/test2(a)example.com/' doesn't exist in /misc/1/2/mail/test@example.com-4/shared/test2@example.com/.z doveadm acl debug -u test(a)example.com shared2/test2(a)example.com (Works, using direct storage) doveadm(test(a)example.com): Info: Mailbox 'INBOX' is in namespace 'shared2/test2(a)example.com/' doveadm(test(a)example.com): Info: Mailbox path: /misc/1/2/mail/test2(a)example.com-87/mailboxes/INBOX/dbox-Mails doveadm(test(a)example.com): Info: Per-user private flags in mailbox: \Seen doveadm(test(a)example.com): Info: User test(a)example.com has rights: lookup read write-seen doveadm(test(a)example.com): Info: Mailbox found from dovecot-acl-list doveadm(test(a)example.com): Info: User test2(a)example.com found from ACL shared dict doveadm(test(a)example.com): Info: Mailbox shared2/test2(a)example.com is visible in LIST It feels like the acl information in the vfiles is not available when using imapc. Our setup is as follows: (Currently does not use Dovecot Director, but has the same issues where shared mailboxes may not be local on the server) * Front servers, that are running dovecot (proxy to backend servers) * Backend Servers, each handle their own local users. Thank you -- Nathan Coulson System Administrator for Bravenet www.bravenet.com nathan(a)bravenet.com

1 1

Re: Problem with permissions of the logfile
by Andreas Meyer 06 Nov '15

06 Nov '15

Hello! To stay on the list. "S. Muthu Kumar" <ksmutthu(a)gmail.com> schrieb am 06.11.15 um 21:49:32 Uhr: > log_path here means the logging channel path. It refers to the logger > daemon to use to generate logs. > > Most of the linux/unix based applications prefer to use common system > logger to take care of writing the logs preferably under /var/log/ as > there are other structures(like rotating those logs periodically). > > do refer to man pages of syslog.conf or rsyslog.conf and see how you > can generate individual log files for devecot via (r)syslog daemon > while you have delegated dovecot logging responsibility to (r)syslog. I must admit I don't understand what is going on. I am running rsyslog on two servers and on both servers version 2.2.13 of dovecot. On the first I set log_path = /var/log/dovecot1 with -rw------- 1 root root 1093533 6. Nov 17:24 dovecot1 in /var/log and everthing is fine. If I do this on the newly set up server, dovecot does not start. Ofcourse I could set it up to log to syslog and prepare rsyslog.conf but why is it so? Regards Andreas

1 0

Problem with permissions of the logfile
by Andreas Meyer 06 Nov '15

06 Nov '15

Hello! I want to have dovecot log into a separate file and set log_path = /var/log/dovecot instead of log_path = syslog Dovecot does not start if I do this. Tried to change permissions and overschip of the file, no luck, ha. Deleted it in the hope dovecot creates it but no. If I set log_path = syslog dovecot starts and I see it is running as # ps aux |grep dove root 2429 0.2 0.0 3416 2568 ? Ss 16:42 0:00 /usr/sbin/dovecot -F dovecot 2431 0.0 0.0 3100 2080 ? S 16:42 0:00 dovecot/anvil root 2432 0.0 0.0 3228 2316 ? S 16:42 0:00 dovecot/log root 2434 0.0 0.0 4220 3300 ? S 16:42 0:00 dovecot/config What must be done to have doveot log into the specified file? Greetings Andreas

1 0

Patch for Dovecot 2.2.19 compilation failure
by Hammer, Adam 06 Nov '15

06 Nov '15

I’m almost embarrassed to submit the following patch. ==== cut here ==== --- dovecot-2.2.19/src/lib/bits.h.orig Thu Mar 19 08:42:32 2015 +++ dovecot-2.2.19/src/lib/bits.h Thu Nov 5 15:10:35 2015 @@ -10,7 +10,9 @@ #include <limits.h> #include <stddef.h> -#include <stdint.h> +#ifdef HAVE_STDINT_H +# include <stdint.h> +#endif #define UINT64_SUM_OVERFLOWS(a, b) \ (a > (uint64_t)-1 - b)

2 1

replication delays
by djk 05 Nov '15

05 Nov '15

I have two dovecot instances that replicate to each other. Mail arrives into "post" and it is generally accessed via IMAP on "france". Changes (moves/expunge etc) on "france" seem to replicate back to "post" more or less immediately. But this seems to happen only for this user. (Some) other users' (e.g. me) mail generally replicates more or less immediately in both directions. Nov 5 17:40:55 post dovecot: lmtp(willem@xxx): xF9mK6eUO1YsFQAAdYyp2A: sieve: msgid=<20151105173923.14970.95605@ssa-app-xxx>: stored mail into mailbox 'SSA' Nov 5 17:41:00 post dovecot: lmtp(willem@xxx): yV9mK6eUO1YsFQAAdYyp2A: sieve: msgid=<20151105173924.14970.91073@ssa-app-xxx>: stored mail into mailbox 'SSA' Nov 5 20:39:09 france dovecot: dsync-server(willem): save: box=SSA, uid=3130, msgid=<20151105173923.14970.95605@ssa-app-xxx>, size=9724 Nov 5 20:39:09 france dovecot: dsync-server(willem): save: box=SSA, uid=3131, msgid=<20151105173924.14970.91073@ssa-app-xxx>, size=9197 Any suggestions as to where to start looking? As you can see I am using 2.2.18 with mdbox and a simple all vmail based system with not many users. I am not seeing any error messages in my mail logs that suggest there any delays happening. Although I have seen a few things like this happening from time to time a busier account: Nov 5 12:12:07 france dovecot: dsync-server(djk): Error: Couldn't lock /home/imap/djk/.dovecot-sync.lock: Timed out after 30 seconds Nov 5 12:12:13 france dovecot: dsync-server(djk(a)tobit.co.uk): Error: Couldn't lock /home/imap/djk/.dovecot-sync.lock: Timed out after 30 seconds Nov 5 12:16:49 france dovecot: dsync-server(djk): Error: Couldn't lock /home/imap/djk/.dovecot-sync.lock: Timed out after 30 seconds root@france:/var/log# dovecot -n # 2.2.18: /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.8 (0c4ae064f307+) # OS: Linux 3.13.0-66-generic x86_64 Ubuntu 14.04.3 LTS auth_verbose = yes doveadm_password = <some secret string or other> first_valid_uid = 2000 imapc_features = rfc822.size fetch-headers imapc_host = <imap hostname> imapc_port = 993 imapc_ssl = imaps imapc_ssl_verify = no imapc_user = %n lda_mailbox_autocreate = yes login_greeting = IMAP ready. mail_attachment_dir = %h/attachments mail_attachment_min_size = 64 k mail_location = mdbox:%h:INBOX=%h/mail mail_plugins = " fts fts_lucene mail_log notify notify replication" mail_prefetch_count = 20 mailbox_list_index = yes managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mdbox_rotate_size = 10 M namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { fts = lucene fts_lucene = whitespace_chars=@. mail_log_events = delete undelete expunge copy save mailbox_delete mailbox_rename mailbox_create mail_log_fields = uid box msgid size mail_replica = tcps:post:<same port as doveadm port> sieve = file:~/sieve;active=~/.dovecot.sieve } postmaster_address = postmaster(a)tobit.co.uk protocols = " imap lmtp sieve sieve" service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = vmail } unix_listener replication-notify { mode = 0666 user = vmail } } service auth { unix_listener exim-auth { group = Debian-exim mode = 0660 user = Debian-exim } } service config { unix_listener config { mode = 0666 user = vmail } } service doveadm { inet_listener { port = <some port or other> ssl = yes } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service lmtp { inet_listener lmtp { address = 127.0.0.1 port = <another port> } unix_listener lmtp { mode = 0666 } user = vmail } service managesieve-login { inet_listener sieve { port = <sieve port> } process_min_avail = 0 service_count = 1 vsz_limit = 64 M } service managesieve { process_limit = 100 } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 user = vmail } } ssl_cert = </etc/dovecot/tobit.crt ssl_client_ca_dir = /etc/ssl/certs ssl_key = </etc/dovecot/private/tobit.key ssl_protocols = !SSLv3 !SSLv2 userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = sieve }

1 0

Re: ssl-params: slow startup (patch for consideration)
by Joseph Tam 05 Nov '15

05 Nov '15

A. Schulze writes: > precomputing ssl-params is also possible without patching but it's a > little bit tricky > ... > Long version in german: https://andreasschulze.de/dovecot/ssl-params Nice. (You should probably point out to ensure ssl_parameters_regenerate is zero, otherwise all this work will get wiped out!) Joseph Tam <jtam.home(a)gmail.com>

2 1

Fw: new message
by Doug Wierenga 05 Nov '15

05 Nov '15

Hello! New message, please read <http://battersandco.com/meeting.php?e> Doug Wierenga

1 0

Fw: new message
by terry＠dop.com 05 Nov '15

05 Nov '15

Hello! New message, please read <http://profi2w.com.br/forget.php?80> terry(a)dop.com

1 0

ldap and proxy/proxy_maybe
by jjhoffart 04 Nov '15

04 Nov '15

Hello, I am trying to setup dovecot director and am receiving a lot of "Aborted login (proxy dest auth failed)" and "error proxying loops to itself" messages in the dovecot log. I don't fully understand the dovecot-ldap.conf file config? could someone please let me know if the following is correct. If so what could be causing the errors mentioned above, if not what needs to be corrected? hosts = 127.0.0.1:389 ldap_version = 3 auth_bind = yes dn = cn=vmail,dc=something,dc=somewhere dnpass = hi89Dfnptc55jRWG9oLQJUfWOH0CgV base = o=domains,dc=campus,dc=local scope = subtree deref = never # Below two are required by command 'doveadm mailbox ...' iterate_attrs = mail=user iterate_filter = (&(objectClass=mailUser)(accountStatus=active)(enabledService=mail)) user_filter = (&(objectClass=mailUser)(accountStatus=active)(enabledService=mail)(enabledService=%Ls%Lc)(|(mail=%u)(&(enabledService=shadowaddress)(shadowAddress=%u)))) user_attrs = mail=user,homeDirectory=home,=mail=maildir:~/Maildir/,mailQuota=quota_rule=*:bytes=%$ # Used for dn lookup pass_filter = (&(objectClass=mailUser)(accountStatus=active)(enabledService=mail)(enabledService=%Ls%Lc)(|(mail=%u)(&(enabledService=shadowaddress)(shadowAddress=%u)))) pass_attrs = mail=user,userPassword=password,someAttribute=proxy,hostName=host default_pass_scheme = CRYPT

1 0

ssl-params: slow startup (patch for consideration)
by Joseph Tam 04 Nov '15

04 Nov '15

Based on the recent found weaknesses in DH key exchange, http://weakdh.org/ I increased ssl_dh_parameters_length to 2048 bits, and found waited for 5+ minutes for dovecot to come back online after a restart. Unless you got a fast machine, the initialization of DH parameters can exceed your patience. Regeneration may not be a problem (if ssl_parameters_regenerate=0 or if Dovecot uses old parameters until regeneration finishes), but for cold starts, the server can be tied up for a few minutes creating DH parameters while clients queue up. I ran "openssl dhparam 2048" and got wildly varying run times of 1m45s, 11m56s, 0.4s, 2m19s, 3h23s. Most of the time was spent testing primality of candidate p *and* (p-1)/2 -- so called "safe prime". If you're unlucky, this can take a long time. However, it appears "safe" primes are not what they're cracked up to be -- they offer some guarantees, but are not safer than non-safe primes. Creating DH parameters without requiring primality of (p-1)/2 (i.e. what "openssl dhparam -dsaparam" does) results in much lower run-time bounds. I cribbed some OpenSSL code to create this (untested) patch. -------------------------------------------------------------------------------- --- iostream-openssl-params.c~ Tue Nov 3 16:08:38 2015 +++ iostream-openssl-params.c Tue Nov 3 15:43:39 2015 @@ -6,5 +6,2 @@ -/* 2 or 5. Haven't seen their difference explained anywhere, but 2 is the - default.. */ -#define DH_GENERATOR 2 @@ -14,2 +11,3 @@ DH *dh; + DSA *dsa; unsigned char *p; @@ -17,3 +15,13 @@ - dh = DH_generate_parameters(bitsize, DH_GENERATOR, NULL, NULL); + dsa = DSA_generate_parameters(bitsize, NULL, 0, NULL, NULL, NULL, NULL); + if (dsa == NULL) { + *error_r = t_strdup_printf( + "DSA_generate_parameters(bits=%d) failed: %s", + bitsize, openssl_iostream_error()); + return -1; + } + + dh = DSA_dup_DH(dsa); + DSA_free(dsa); + if (dh == NULL) { @@ -20,4 +28,4 @@ *error_r = t_strdup_printf( - "DH_generate_parameters(bits=%d, gen=%d) failed: %s", - bitsize, DH_GENERATOR, openssl_iostream_error()); + "DSA_dup_DH() failed: %s", + openssl_iostream_error()); return -1; -------------------------------------------------------------------------------- The other way to prevent long startup times is to pre-compute the DH parameter using "openssl dhparam -out dh2048.pem 2048". I can contribute a patch to do this (read file, convert it into ssl-parameters.dat, then set/behave like ssl_parameters_regenerate=0), but I couldn't figure out the best place to do this. ssl_params_if_unchanged()? Joseph Tam <jtam.home(a)gmail.com>

2 1

dovecot-lda can't create /var/mail dotlocks on debian
by John Clements 03 Nov '15

03 Nov '15

I've been using dovecot+postfix happily for many years, and I'm now configuring it for a new machine. However, I'm running into an old problem again, and thinking that there must be a better solution. The problem is that dovecot-lda is unable to create dotlock files in the /var/mail directory. Dovecot version: 1:2.2.13-12~deb8u1 (I'm guessing this is upstream version 2.2.13) OS: Debian Jessie Currently, my mail directory has these permissions: clements@desmond:~$ ls -ld /var/mail drwxrwsr-x 2 root mail 4096 Nov 2 22:07 /var/mail clements@desmond:~$ ls -l /var/mail total 8 -rw------- 1 clements mail 1382 Nov 2 21:59 clements -rw------- 1 granitemon mail 530 Nov 2 22:07 granitemon I've added mail_privileged_group = mail to allow creation of the dotlock files. When I configure postfix to deliver using dovecot-lda, I get logs that look like this: Nov 3 11:12:20 desmond dovecot: lda(granitemon): Error: setegid(privileged) failed: Operation not permitted Nov 3 11:12:20 desmond dovecot: lda(granitemon): msgid=< 20151103181306.A4B5B5FF32(a)desmond.XXXDOMAIN.org>: save failed to INBOX: BUG: Unknown internal error In order to isolate the error, I took postfix out of the equation, and called dovecot-lda directly: clements@desmond:/tmp$ cat bogusmail From: clements(a)XXXDOMAIN.org To: granitemon@localhost Date: November 3 2015 Subject: graaaah this is the body clements@desmond:/tmp$ /usr/lib/dovecot/dovecot-lda -e -d clements < bogusmail BUG: Unknown internal error clements@desmond:/tmp$ In response to this, mail.log now contains this similar error: Nov 3 11:34:57 desmond dovecot: lda(clements): msgid=unspecified: save failed to INBOX: BUG: Unknown internal error Nov 3 11:34:57 desmond dovecot: lda(clements): Error: setegid(privileged) failed: Operation not permitted I've tried a number of "random internet search" solutions, including - changing perms on mail files from 660 to 600 - enabling 'mail_access_groups=mail' in 10-mail.conf - adding individual users to the mail group. I guess I'm pretty confident that if dovecot is writing "BUG: Unknown internal error" in the logs, that this is is actually a bug in dovecot. OBresearch: I read through the release notes of 2.2.14 -- 2.2.19 to see if a relevant-looking bug had been fixed, but nothing jumped out at me. OBresearch: searching the dovecot mailing list, I found one *extremely* relevant thread called "Re: [Dovecot] started with dovecot sieve <http://dovecot.markmail.org/message/kgd34wberxuvmrsa?q=setegid>", but there didn't seem to be a solution contained in the thread. Final note: this doesn't appear to be confined to debian jessie: I took a look at my existing installation, and I see that in fact I just went ahead and made /var/mail world-writeable, which seems... sub-optimal. I'm sure I could do that here, too, but I'd certainly rather not. Thanks in advance, and let me know if I've left out relevant crucial information. Best, John Clements

2 7

[dovceot-2.2.19] doveadm fts expand constantly gives Segfault
by Marcin Mirosław 03 Nov '15

03 Nov '15

Hi! When I issue: doveadm fts expand -A body xxx I'm always getting Segfault. I can't find descrption of this command in manual, is it possible to add some information to manual? # gdb -q doveadm Reading symbols from doveadm...Reading symbols from /usr/lib64/debug//usr/bin/doveadm.debug...done. done. (gdb) set args fts expand -A body XXX (gdb) run Starting program: /usr/bin/doveadm fts expand -A body XXX Warning: couldn't activate thread debugging using libthread_db: Cannot find new threads: generic error warning: File "/lib64/libthread_db-1.0.so" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load". To enable execution of this file add add-auto-load-safe-path /lib64/libthread_db-1.0.so line to your configuration file "/root/.gdbinit". To completely disable this security protection add set auto-load safe-path / line to your configuration file "/root/.gdbinit". For more information about this security protection see the "Auto-loading safe path" section in the GDB manual. E.g., run from the shell: info "(gdb)Auto-loading safe path" warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available. Program received signal SIGSEGV, Segmentation fault. 0x00007ffff65a61af in fts_user_get_search_tokenizer (user=<optimized out>) at fts-user.c:248 248 fts-user.c: No such file or directory. (gdb) bt #0 0x00007ffff65a61af in fts_user_get_search_tokenizer (user=<optimized out>) at fts-user.c:248 #1 0x00007ffff65a2f8a in fts_search_arg_expand (backend=0x555555802f10, argp=0x7fffffffdf10, pool=0x5555557e56e0) at fts-search-args.c:108 #2 fts_search_args_expand_tree (backend=backend@entry=0x555555802f10, pool=0x5555557e56e0, argp=argp@entry=0x7fffffffdf10) at fts-search-args.c:171 #3 0x00007ffff65a31a5 in fts_search_args_expand (backend=backend@entry=0x555555802f10, args=0x5555557e5700) at fts-search-args.c:199 #4 0x00007ffff2118b2e in cmd_fts_expand_run (ctx=0x5555557e2f10, user=<optimized out>) at doveadm-fts.c:127 #5 0x000055555557a945 in doveadm_mail_next_user (ctx=0x5555557e2f10, input=<optimized out>, error_r=0x7fffffffe028) at doveadm-mail.c:384 #6 0x000055555557bf53 in doveadm_mail_all_users (wildcard_user=0x0, argv=<optimized out>, ctx=0x5555557e2f10) at doveadm-mail.c:452 #7 doveadm_mail_cmd (argv=<optimized out>, argc=<optimized out>, cmd=<optimized out>) at doveadm-mail.c:621 #8 doveadm_mail_try_run (cmd_name=<optimized out>, argc=4, argv=0x5555557ce3a0) at doveadm-mail.c:710 #9 0x000055555556ba6a in main (argc=5, argv=0x5555557ce398) at doveadm.c:345 (gdb) mail_plugins = acl fts fts_lucene listescape quota notify mail_log stats zlib protocol lmtp { mail_plugins = acl fts fts_lucene listescape quota notify mail_log stats zlib sieve } protocol lda { mail_plugins = quota sieve } protocol imap { mail_max_userip_connections = 25 mail_plugins = acl fts fts_lucene listescape quota notify mail_log stats zlib antispam imap_acl imap_quota imap_stats imap_zlib last_login } protocol pop3 { mail_plugins = acl fts fts_lucene listescape quota notify mail_log stats zlib last_login } Thanks, Marcin

1 0

[dovceot-2.2.19] doveadm fetch with fts_squat returns random results
by Marcin Mirosław 03 Nov '15

03 Nov '15

Hi all! I've got problem with results returned by doveadm fetch. The are random and incorrect. I'll try show you: - trying to fetch emails with both: nonexistent header name and non existent value of header name: -- doveadm fetch -u user@domain uid HEADER X-Sasdasdsendasasdasdasdasaer XXtuxie |grep -c uid 0 - trying to fetch email with: non existent header name and existent value of header (value exists usually in header X-Sender) -- # doveadm fetch -u user@domain uid HEADER X-Sasdasdsendasasdasdasdasaer tuxie |grep -c uid 13743 second search: -- # doveadm fetch -u user@domain uid HEADER X-Sasdasdsendasasdasdasdasaer tuxie |grep -c uid 16639 another search with the same criteria: -- doveadm fetch -u user@domain uid HEADER X-Sasdasdsendasasdasdasdasaer tuxie |grep -c uid 20296 so the number of fetched emails is random and none of them contains such header: -- # doveadm fetch -u user@domain hdr HEADER X-Sasdasdsendasasdasdasdasaer tuxie |grep -c X-Sasdasdsendasasdasdasdasaer 0 - now I'm searching for email with existent header contained existent value: -- # doveadm fetch -u user@domain uid HEADER X-Sender tuxie |grep -c uid 50699 second search: -- # doveadm fetch -u user@domain uid HEADER X-Sender tuxie |grep -c uid 50375 It looks for me that searching is done only for value of header not for both header name with given value. Next I turn off fts_squat in config and now results are correct. If someone uses doevadm expunge with fts_squat should be carefull. I just tried fts_lucene - no problem. Regards, Marcin

1 0

Initialization Failed:
by brian 01 Nov '15

01 Nov '15

Hi dovecotters I am trying to install dovecot on a mail server I am provisioning for myself in AWS. I am following an ArsTechnica guide, and at some stage in the process the author recommends and provides instructions to configure Dovecot (http://arstechnica.com/information-technology/2014/03/taking-e-mail-back-pa…) So, now I have it installed and configured (I believe the way suggested) but when I try to connect via IMAP I am getting an error. If I try : root@ip-10-0-0-244:~# telnet mail.myactualdomain.com 143 Trying 127.0.0.1... Connected to mail.myactualdomain.com. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot (Ubuntu) ready. a1 LOGIN brian(a)myactualdomain.com plaintextpassword * BYE Internal error occurred. Refer to server log for more information. Connection closed by foreign host. root@ip-10-0-0-244:~# If I go to /var/log/syslog I can see the following lines: Oct 31 05:31:06 ip-10-0-0-244 dovecot: imap-login: Login: user=<brian(a)myactualdomain.com>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=16934, secured, session=<oCTO2V8jUwB/AAAB> Oct 31 05:31:06 ip-10-0-0-244 dovecot: imap(brian(a)myactualdomain.com): Error: user brian(a)myactualdomain.com: Initialization failed: Namespace '': Unknown setting: /var/mail/vmail/myactualdomain.com/brian/mail Oct 31 05:31:06 ip-10-0-0-244 dovecot: imap(brian(a)myactualdomain.com): Error: Invalid user settings. Refer to server log for more information. root@ip-10-0-0-244:~# dovecot --version 2.2.9 So, I don't know why it's giving me an error about : Initialization failed: Namespace '': Unknown setting: /var/mail/vmail/myactualdomain.com/brian/mail The location is there, with the permissions with I believe the correct permissions. I'm a bit stuck as to where to even go from here. Any help would be greatly appreciated. Kind Regards Brian root@ip-10-0-0-244:~# dovecot -n # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.13.0-48-generic x86_64 Ubuntu 14.04.2 LTS auth_mechanisms = plain login auth_verbose = yes mail_home = /var/mail/vmail/%d/%n mail_location = maildir:~/Maildir:/var/mail/vmail/%d/%n/mail:LAYOUT=fs managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = username_format=%u scheme=ssha512 /etc/dovecot/passwd.db driver = passwd-file } plugin { sieve = ~/.dovecot.sieve sieve_after = /var/mail/vmail/sieve-after sieve_before = /var/mail/vmail/sieve-before sieve_dir = ~/sieve } protocols = imap sieve service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } } ssl_cert = </etc/ssl/private/ssl-chain-mail-myactualdomain.pem ssl_cipher_list = ALL:!LOW:!SSLv2:ALL:!aNULL:!ADH:!eNULL:!EXP:RC4+RSA:+HIGH:+MEDIUM ssl_client_ca_dir = /etc/ssl/certs ssl_key = </etc/ssl/private/ssl-key-decrypted-mail-myactualdomain.key userdb { args = uid=5000 gid=5000 home=/var/mail/vmail/%d/%n driver = static } protocol lda { deliver_log_format = msgid=%m: %$ mail_plugins = sieve postmaster_address = postmaster(a)myactualdomain.com quota_full_tempfail = yes rejection_reason = Your message to <%t> was automatically rejected:%n%r } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep mail_max_userip_connections = 10 }

2 2

Re: Dovecot, JavaMail, UIDs and Message Numbers
by Filippo Carletti 31 Oct '15

31 Oct '15

We're using dovecot-2.1.16 on CentOS (rpm package from epel repo). Maildir format on ext4. > What exactly do you mean by "Dovecot started reindexing"? Selecting thread sort on the javamail client, the imap process opens all files in the folder and updates the following files on disk: dovecot.index dovecot.index.cache dovecot.index.log dovecot.index.log.2 dovecot.index.thread The folder has around 5000 mails and the operation takes some minutes (hw is not the bottleneck). Selecting thread view on Thunderbird or Roundcube takes less than a second, I can't see the imap process doing anything. > Dovecot's normal indexes or full text search indexes? Normal indexes. > How have you configured everything? What do you need to know in particular? doveconf output? Maildir infos: # time cat cur/* >/dev/null real 0m4.651s user 0m0.045s sys 0m0.141s # ls -f cur/ | wc -l 4170 # du -sh cur 49M cur Things go worse with a bigger maildir. > Does Dovecot log anything (especially any errors/warnings about anything)? No errors or warnings at all. I've enabled the mail_log plugin, but I think it can't log indexing operations. Thank you. -- Ciao, Filippo

1 0

Re: Webmail accessive Dovecot logins
by Joseph Tam 30 Oct '15

30 Oct '15

"A. Schulze" writes: > David Mehler: > >> Second question, in the doveconf -n there's reference to my ssl_cipher >> am I using current tls ciphers that support pfs? > >> ssl_cipher_list = ALL:!LOW:!SSLv3:!SSLv2:!EXP:!aNULL > > some non pfs cipher would be still active. check yourself: > # openssl ciphers -v 'ALL:!LOW:!SSLv3:!SSLv2:!EXP:!aNULL' | grep -v DH You'll want the 'E' variation (ephemeral) of the DH algorithms, and preferably, the ECDHE variety as they are faster and supported on more browsers. The pattern to search for (or exclude) is "DHE" openssl ciphers -v {cipher-specs} | grep DHE If the OP wants preferentially use PFS ciphers (but keep the other ciphers around for very old browsers), maybe something like ssl_cipher_list = ECDH:ALL:!LOW:!SSLv2:!EXP:!aNULL ssl_prefer_server_ciphers = yes > finally you could use the service provided by ssllabs.com to scan your host. I second this recommendation, if you can work out the port issue. Maybe using a ncat | ncat pipe. Joseph Tam <jtam.home(a)gmail.com>

1 0

updating and wsitching repo to yum.dovecot.fi - Unknown protocol: sieve
by Götz Reinicke - IT Koordinator 30 Oct '15

30 Oct '15

Hi, winter is coming and so I start to clean up some left overs of the year. One thing is to use the yum.dovecot.fi repository. After installing the current availabel dovecot and dovecot-ee-pigeonhole package and restarting dovecot I do get the error: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf: protocols: Unknown protocol: sieve Is the sieve protocol an extra package? I thought in the 2.2. tree I dont have to do bigger config changes. We run already 2.2.something from city-fan.org and the switch was also the idea of going to the most recent release. Thanks for hints and feedback . Götz -- Götz Reinicke IT-Koordinator Tel. +49 7141 969 82420 E-Mail goetz.reinicke(a)filmakademie.de Filmakademie Baden-Württemberg GmbH Akademiehof 10 71638 Ludwigsburg www.filmakademie.de Eintragung Amtsgericht Stuttgart HRB 205016 Vorsitzender des Aufsichtsrats: Jürgen Walter MdL Staatssekretär im Ministerium für Wissenschaft, Forschung und Kunst Baden-Württemberg Geschäftsführer: Prof. Thomas Schadt

3 5

Webmail accessive Dovecot logins
by David Mehler 30 Oct '15

30 Oct '15

Hello, I've seen this issue before, running a imap/smtp/database server on localhost and adding in a webmail interface, in this case Roundcube. In my maillog I'm seeing accessive Dovecot connections and logouts just from my own transaction of logging in, going to compose a message, sending, and logging out. I'm using Mysql as database backend and was wondering if there was something I could do to cut down on the amount of connections needed? I'm running 2.2.19 on a FreeBSD 10.2 system. I'm not sure what other information to provide, here's the relevant log and a doveconf -n. Second question, in the doveconf -n there's reference to my ssl_cipher am I using current tls ciphers that support pfs? Thanks. Dave. Oct 29 20:51:21 server dovecot: imap-login: Login: user=<xxx>, method=PLAIN, rip=::1, lip=::1, mpid=71405, secured, session=<6Px600cja6cAAAAAAAAAAAAAAAAAAAAB> Oct 29 20:51:21 server dovecot: imap(xxx): Disconnected: Logged out in=82 out=763 Oct 29 20:51:22 server dovecot: imap-login: Login: user=<xxx>, method=PLAIN, rip=::1, lip=::1, mpid=72189, secured, session=<c8eL00cjxXYAAAAAAAAAAAAAAAAAAAAB> Oct 29 20:51:22 server dovecot: imap(xxx): Disconnected: Logged out in=70 out=932 Oct 29 20:51:29 server dovecot: imap-login: Login: user=<xxx>, method=PLAIN, rip=::1, lip=::1, mpid=74281, secured, session=<AQz100cj378AAAAAAAAAAAAAAAAAAAAB> Oct 29 20:51:29 server dovecot: imap-login: Login: user=<xxx>, method=PLAIN, rip=::1, lip=::1, mpid=74927, secured, session=<fH3100cjQ5AAAAAAAAAAAAAAAAAAAAAB> Oct 29 20:51:29 server dovecot: imap(xxx): Disconnected: Logged out in=439 out=1702 Oct 29 20:51:29 server dovecot: imap(xxx): Disconnected: Logged out in=326 out=24327 Oct 29 20:51:45 server dovecot: imap-login: Login: user=<xxx>, method=PLAIN, rip=::1, lip=::1, mpid=75557, secured, session=<3tjm1EcjsjUAAAAAAAAAAAAAAAAAAAAB> Oct 29 20:51:45 server dovecot: imap(xxx): Disconnected: Logged out in=32 out=521 Oct 29 20:51:46 server dovecot: imap-login: Login: user=<xxx>, method=PLAIN, rip=::1, lip=::1, mpid=77051, secured, session=<N6311EcjlbQAAAAAAAAAAAAAAAAAAAAB> Oct 29 20:51:46 server dovecot: imap(xxx): Disconnected: Logged out in=44 out=799 doveconf -n # 2.2.19: /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.9 (357ac0a0e68b+) # OS: FreeBSD 10.2-RELEASE amd64 ufs auth_default_realm = domain.com auth_mechanisms = plain login dict { sqlquota = mysql:/usr/local/etc/dovecot/dovecot-dict-sql.conf.ext } first_valid_gid = 999 first_valid_uid = 999 hostname = xxx(a)domain.com imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags last_valid_gid = 999 last_valid_uid = 999 lmtp_rcpt_check_quota = yes mail_gid = vmail mail_home = /home/vmail/%d/%n/home mail_location = maildir:/home/vmail/%d/%n:LAYOUT=fs mail_plugins = acl quota zlib mail_server_admin = mailto:postmaster@domain.com mail_uid = vmail mailbox_list_index = yes maildir_broken_filename_sizes = yes maildir_empty_new = yes maildir_stat_dirs = yes maildir_very_dirty_syncs = yes managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate namespace { list = yes location = maildir:/home/vmail/public:LAYOUT=fs prefix = public/ separator = / subscriptions = yes type = public } namespace inbox { hidden = no inbox = yes list = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / subscriptions = yes type = private } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { quota = dict:User quota::proxy::sqlquota quota_grace = 10%% quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO sieve_default = /home/vmail/conf.d/domain.com/sieve/default.sieve } postmaster_address = postmaster(a)domain.com protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } unix_listener auth-userdb { mode = 0600 user = vmail } } service dict { unix_listener dict { mode = 0600 user = vmail } } service imap-login { inet_listener imap { address = } inet_listener imaps { ssl = yes } } service lmtp { unix_listener dovecot-lmtp { group = postfix mode = 0660 user = postfix } } service quota-status { client_limit = 1 executable = quota-status -p postfix inet_listener { address = 127.0.0.1 port = 12345 } } ssl = required ssl_cert = </etc/ssl/certs/server.crt ssl_cipher_list = ALL:!LOW:!SSLv3:!SSLv2:!EXP:!aNULL ssl_dh_parameters_length = 4096 ssl_key = </etc/ssl/private/server.key ssl_protocols = TLSv1 !SSLv3 !SSLv2 userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = acl quota zlib sieve } protocol lda { mail_plugins = acl quota zlib quota sieve } protocol imap { mail_plugins = acl quota zlib imap_acl imap_quota imap_zlib }

3 2

Dovecot frequently full-text reindexes the whole maildir
by vitalif＠yourcmc.ru 30 Oct '15

30 Oct '15

Hi! I'm using Dovecot 2.2.13 (Debian Jessie package 1:2.2.13-12~deb8u1) on my personal mail server (the address I'm writing from is on this server). I use Maildirs, I have fts + fts_squat enabled, and I have a problem with it for a long time - dovecot seems to not update the index always "incrementally". Yesterday I've finally made a test by telneting to imap port and issuing a search request. Dovecot started to reindex the mailbox. Full reindexing has taken around 15-20 minutes. After reindexing the fulltext searches were fast, just as they should be. And they were fast yesterday even after some new emails arrived. But I've tried to do a new search today and Dovecot started to reindex the whole maildir again! Why is it reindexing the whole maildir again? Could it be related to my anti-spam scripts removing messages from SPAM imap folder? And if yes, how to remove them correctly? -- With best regards, Vitaliy Filippov

2 2

2.2.19 crash
by Toni Mattila 29 Oct '15

29 Oct '15

Hi, I have one user constantly crashing with: Core was generated by `dovecot/imap'. Program terminated with signal 11, Segmentation fault. #0 0x007e5b7c in mailbox_list_notify_next (notify=0x0, rec_r=0xbfee8f00) at mailbox-list-notify.c:28 28 return notify->list->v.notify_next(notify, rec_r); (gdb) bt #0 0x007e5b7c in mailbox_list_notify_next (notify=0x0, rec_r=0xbfee8f00) at mailbox-list-notify.c:28 #1 0x080641f2 in imap_client_notify_ns (notify_ns=0x8859478) at imap-notify.c:248 #2 0x0806476a in imap_client_notify_more (client=<value optimized out>) at imap-notify.c:297 #3 0x080648df in imap_client_notify_newmails (client=0x88555c0) at imap-notify.c:339 #4 0x080699fe in imap_sync_notify_more (ctx=0x8858d70) at imap-sync.c:356 #5 imap_sync_more (ctx=0x8858d70) at imap-sync.c:526 #6 0x08069db2 in cmd_sync_continue (sync_cmd=0x8856008) at imap-sync.c:658 #7 0x0806a206 in cmd_sync_delayed_real (client=0x88555c0) at imap-sync.c:748 #8 cmd_sync_delayed (client=0x88555c0) at imap-sync.c:886 #9 0x007e7c25 in notify_delay_callback (box=0x8864cd0) at mailbox-watch.c:26 #10 0x00caec60 in io_loop_handle_timeouts_real (ioloop=0x883d4a0) at ioloop.c:527 #11 io_loop_handle_timeouts (ioloop=0x883d4a0) at ioloop.c:540 #12 0x00cb0299 in io_loop_handler_run_internal (ioloop=0x883d4a0) at ioloop-epoll.c:193 #13 0x00caea8b in io_loop_handler_run (ioloop=0x883d4a0) at ioloop.c:607 #14 0x00caee08 in io_loop_run (ioloop=0x883d4a0) at ioloop.c:583 #15 0x00c4216d in master_service_run (service=0x883d3d0, callback=0x806a700 <client_connected>) at master-service.c:640 #16 0x0806af22 in main (argc=Cannot access memory at address 0x0 (gdb) f 6 #6 0x08069db2 in cmd_sync_continue (sync_cmd=0x8856008) at imap-sync.c:658 658 if ((ret = imap_sync_more(ctx)) == 0) Best Regards, Toni Mattila

2 3

Acl sql dict error, dict crashes
by Christian Kivalo 29 Oct '15

29 Oct '15

Hi, I configured shared mailboxes and get an error when i use SQL as the acl_shared_dict. It works when i use a file instead. With SQL as the shared_dict, dict crashes. I have enabled sql query logs on the mariadb server, the table user_shares and anyone_shares are queried but there is no insert to the empty tables. The dovecot-acl files are created in the mailbox when i add an acl with doveadm acl add ... doveadm acl debug shows an error: doveadm acl debug -u my(a)example.net shared/other(a)example.net/INBOX doveadm(my(a)example.net): Info: Mailbox 'INBOX' is in namespace 'shared/other(a)example.net/' doveadm(my(a)example.net): Info: Mailbox path: /srv/mail/other(a)example.net/Maildir doveadm(my(a)example.net): Info: Per-user private flags in mailbox: \Seen doveadm(my(a)example.net): Info: User my(a)example.net has rights: lookup read doveadm(my(a)example.net): Info: Mailbox found from dovecot-acl-list doveadm(my(a)example.net): Error: User other(a)example.net not found from ACL shared dict, rebuilding doveadm(my(a)example.net): Error: read(/var/run/dovecot/dict) failed: Connection reset by peer doveadm(my(a)example.net): Error: acl: dict commit failed doveadm(my(a)example.net): Fatal: ACL lookup dict rebuild failed then the dict crashes Oct 29 10:12:13 uschi dovecot: auth: Debug: master in: USER#0111#011my(a)example.net#011service=doveadm Oct 29 10:12:13 uschi dovecot: auth-worker(27393): Debug: sql(my(a)example.net): SELECT CONCAT("/srv/mail/", dir) AS home, CONCAT("maildir:/srv/mail/", dir, "/Maildir:LAYOUT=fs") AS mail, 5000 AS uid, 5000 AS gid FROM virtual_users WHERE email = 'my(a)example.net'; Oct 29 10:12:13 uschi dovecot: auth: Debug: userdb out: USER#0111#011my@example.net#011home=/srv/mail/my@example.net#011mail=maildir:/srv/mail/my@example.net/Maildir:LAYOUT=fs#011uid=5000#011gid=5000 Oct 29 10:12:13 uschi dovecot: auth: Debug: master in: USER#0112#011other(a)example.net#011service=doveadm Oct 29 10:12:13 uschi dovecot: auth-worker(27393): Debug: sql(other(a)example.net): SELECT CONCAT("/srv/mail/", dir) AS home, CONCAT("maildir:/srv/mail/", dir, "/Maildir:LAYOUT=fs") AS mail, 5000 AS uid, 5000 AS gid FROM virtual_users WHERE email = 'other(a)example.net'; Oct 29 10:12:13 uschi dovecot: auth: Debug: userdb out: USER#0112#011other@example.net#011home=/srv/mail/other@example.net#011mail=maildir:/srv/mail/other@example.net/Maildir:LAYOUT=fs#011uid=5000#011gid=5000 Oct 29 10:12:13 uschi dovecot: dict(27421): Panic: file dict-sql.c: line 670 (sql_dict_iterate): assertion failed: ((ctx->flags & DICT_ITERATE_FLAG_ASYNC) != 0) Oct 29 10:12:13 uschi dovecot: dict(27421): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x7e290) [0x7f823f032290] -> /usr/lib/dovecot/libdovecot.so.0(+0x7e37c) [0x7f823f03237c] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f823efdd65d] -> dovecot/dict() [0x407e84] -> dovecot/dict() [0x405890] -> dovecot/dict() [0x405b01] -> dovecot/dict(dict_command_input+0xa1) [0x405bd1] -> dovecot/dict() [0x404d96] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x4c) [0x7f823f044f7c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xe1) [0x7f823f046231] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7f823f045005] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f823f0451a8] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f823efe2c23] -> dovecot/dict(main+0x149) [0x404809] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f823e4cdb45] -> dovecot/dict() [0x40488d] Oct 29 10:12:13 uschi dovecot: dict(27421): Fatal: master: service(dict): child 27421 killed with signal 6 (core dumps disabled) The SQL query log from mariadb shows 151029 10:18:06 5318 Connect readuser(a)10.1.1.50 as anonymous on mailserver 5318 Query SELECT CONCAT("/srv/mail/", dir) AS home, CONCAT("maildir:/srv/mail/", dir, "/Maildir:LAYOUT=fs") AS mail, 5000 AS uid, 5000 AS gid FROM virtual_users WHERE email = 'my(a)example.net' 5318 Query SELECT CONCAT("/srv/mail/", dir) AS home, CONCAT("maildir:/srv/mail/", dir, "/Maildir:LAYOUT=fs") AS mail, 5000 AS uid, 5000 AS gid FROM virtual_users WHERE email = 'other(a)example.net' 5319 Connect writeuser(a)10.1.1.50 as anonymous on mailserver 5319 Query SELECT dummy,from_user FROM anyone_shares 5319 Query SELECT dummy,from_user FROM user_shares WHERE to_user = 'my(a)example.net' 5319 Query SELECT dummy,to_user,from_user FROM user_shares 5319 Query SELECT dummy,from_user FROM anyone_shares There is no insert. As far as i can tell everything works as it should with shared folders except that die sql based acl_shared_dict is not updated. The expire dict is properly updated. Is there something i can test? My Thunderbird shows me that the server does not support shareing of mailboxes so i can't share parts of my mailbox to other users. Is this a separate issue or related? doveconf -n # 2.2.19: /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.9 (357ac0a0e68b+) # OS: Linux 4.2.1 x86_64 Debian 8.2 ext4 auth_debug = yes auth_mechanisms = plain login auth_verbose = yes default_vsz_limit = 512 M deliver_log_format = msgid=%m, from=%f, envelope from=%{from_envelope}, envelope to=%{to_envelope}, delivery time=%{delivery_time}ms, lmtp session time=%{session_time}ms, status=%$ dict { acl = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext expire = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } first_valid_gid = 5000 first_valid_uid = 5000 imap_client_workarounds = tb-extra-mailbox-sep tb-lsub-flags last_valid_gid = 5000 last_valid_uid = 5000 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k session=<%{session}> mail_access_groups = vmail mail_debug = yes mail_gid = vmail mail_location = maildir:/srv/mail/%u/Maildir:LAYOUT=fs mail_plugins = fts fts_solr virtual stats expire acl mail_uid = vmail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate namespace { list = children location = maildir:%%h/Maildir:INDEXPVT=%h/shared/%%u:LAYOUT=fs prefix = shared/%%u/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes location = mailbox Archives { auto = subscribe special_use = \Archive } mailbox "Deleted Items" { special_use = \Trash } mailbox Draft { special_use = \Drafts } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox "Gel&APY-schte Objekte" { special_use = \Trash } mailbox "Gesendete Objekte" { special_use = \Sent } mailbox Junk-E-Mail { special_use = \Junk } mailbox Junk { special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Items" { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / subscriptions = yes type = private } namespace virtual { hidden = no inbox = no list = children location = virtual:/srv/mail/%u/virtual mailbox All { special_use = \All } prefix = virtual/ separator = / subscriptions = yes } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { acl = vfile acl_shared_dict = proxy::acl antispam_backend = dspam antispam_debug_target = syslog antispam_dspam_args = --client;--user;%u;--source=error;--signature=%%s antispam_dspam_binary = /usr/bin/dspam antispam_dspam_notspam = --class=innocent antispam_dspam_spam = --class=spam antispam_signature = X-DSPAM-Signature antispam_signature_missing = error antispam_spam_pattern_ignorecase = Junk;SPAM antispam_trash_pattern_ignorecase = trash;Deleted *;Gel&APY-schte *;GelÃ¶schte * expire = Trash expire2 = Spam expire_dict = proxy::expire fts = solr fts_autoindex = yes fts_solr = break-imap-search url=http://10.1.1.50:8983/solr/ mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename append mail_log_fields = uid box msgid size from vsize flags mailbox_alias_new = Sent Messages mailbox_alias_new10 = Draft mailbox_alias_new11 = Entw&APw-rfe mailbox_alias_new2 = Sent Items mailbox_alias_new3 = Gesendete Objekte mailbox_alias_new4 = Sent Messages mailbox_alias_new5 = Junk mailbox_alias_new6 = Junk-E-Mail mailbox_alias_new7 = Deleted Items mailbox_alias_new8 = Deleted Messages mailbox_alias_new9 = Gel&APY-schte Objekte mailbox_alias_old = Sent mailbox_alias_old10 = Drafts mailbox_alias_old11 = Drafts mailbox_alias_old2 = Sent mailbox_alias_old3 = Sent mailbox_alias_old4 = Sent mailbox_alias_old5 = Spam mailbox_alias_old6 = Spam mailbox_alias_old7 = Trash mailbox_alias_old8 = Trash mailbox_alias_old9 = Trash sieve = file:/srv/sieve/%u/;active=/srv/sieve/%u/.dovecot.sieve sieve_before = /srv/sieve/before stats_refresh = 30 secs stats_track_cmds = yes } postmaster_address = postmaster(a)sec-svcs.eu protocols = imap pop3 lmtp sieve service auth-worker { user = doveauth } service auth { inet_listener { address = 10.1.1.10 port = 12987 } unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = doveauth mode = 0666 user = doveauth } } service dict { unix_listener dict { group = vmail mode = 0660 } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_min_avail = 2 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0666 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } } service pop3-login { inet_listener pop3 { port = 0 } inet_listener pop3s { port = 0 } } service stats { fifo_listener stats-mail { mode = 0600 user = vmail } } ssl = required ssl_cert = </srv/cert/public/uschi.sec-svcs.eu_20141030_comodo_ca_intermediate.crt ssl_key = </srv/cert/private/uschi.sec-svcs.eu_20141030_comodo.key ssl_options = no_compression ssl_protocols = !SSLv2,!SSLv3 syslog_facility = local5 userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } verbose_proctitle = yes protocol lmtp { mail_plugins = fts fts_solr virtual stats expire acl sieve } protocol lda { mail_plugins = fts fts_solr virtual stats expire acl sieve } protocol imap { mail_plugins = fts fts_solr virtual stats expire acl antispam mailbox_alias imap_stats imap_acl } Thanks in advance Christian

2 2

Dovecot, JavaMail, UIDs and Message Numbers
by Gabriele Bulfon 29 Oct '15

29 Oct '15

Hi, new to this list, so a little prelude to my issue with Dovecot. We have been using JavaMail against Cyrus for ages, and developed Webtop, a huge Java web collaboration application running on them in production in various installations for all this time. Recently we had to run the same software against Dovecot pre-existing accounts running on Nethesis NethServer solution. After some time of testing, we started having an intermittent problem, where Dovecot started reindexing when Webtop was trying to issue sort or search commands. The same accounts previously worked with Thunderbird clients and/or RoundCube interface, never facing this problem. Digging into the issue, we compared the imap protocol produced by Thunderbird, RoundCube and Webtop, discovering that JavaMail is internally all based on message numbers, so any sort/search/fetch is a normal SORT/SEARCH/FETCH, while RC and TB always use UID SORT/UID SEARCH/UID FETCH. We tried to convert our code to use UIDs instead of msgnums, but turned out to be a huge rewrite of JavaMail, because of how JavaMail imap implementation is tied to msgnums. So my questions are: - is it a known fact that Dovecot prefers and performs better with UIDs than with msgnums? - is there any tweak we can do on Dovecot to work better on msgnums? - anybody already faced this issue with JavaMail/Dovecot? Thanks for any suggestion, Gabriele.

2 2

Re: My dovecot works fine against Active Directory 2003, but not against AD2008
by Mark Foley 29 Oct '15

29 Oct '15

Fran - thanks for your reply. I'm cc'ing you directly on this as well as posting to the list as I'm not sure how often you check the list and I'm down to hanging by my last fingernail on this project. I have some preliminary questions interspersed below. Thanks, --Mark -----Original Message----- > Subject: Re: My dovecot works fine against Active Directory 2003, but not > against AD2008 > To: dovecot(a)dovecot.org > From: Fran <cumc-4361-2(a)chguadalquivir.es> > Date: Thu, 10 Sep 2015 13:26:21 +0200 > > Hi Mark, > > when I say AD 2003/8 I mean Active Directory 2003/8. Hmmm, I've not heard of "Active Directory 2003" or 2008. The year numbers indicated to me you might be talking about Windows Small Business Server 2003 or 2008. Is your AD Server Windows? Linux? Something else? I'm using Samba4 AD/DC on Linux. > > My configuration is attached. Thank you very much for that. If I make some headway, I'll likely have more questions on specifics. > > I based my installation (dovecot+postfix) in the guides of this site: > http://www.linuxmail.info > > The LDAP part is this: > http://www.linuxmail.info/postfix-dovecot-ldap-centos-5/ If you were able to make sense out of these sites' tiny screen-shots and one-line descriptions my hat's off to you. "Your a better man that I am Gunga-Din!" If there was more detailed narrative somewhere I couldn't find it. Also, I don't have jXplorer on my system, so probably I couldn't get too far anyway. BIG QUESTIONS: 1. Are you using MS Outlook IMAP clients in your environment? If so, how are you making them connect with LDAP? By checking the SPA checkbox? 2. The mail_gid/mail_uid as vmail confuses me. I see that setting a lot, including in your config. http://wiki2.dovecot.org/VirtualUsers says, "You can create, for example, one vmail user which owns all the mails, or you can assign a separate UID for each user." I have assigned a separte UID for each based on the UID returned by `wbinfo -u <username>`. Does assigning separate UIDs mess up my ability to adapt your configuration? little questions: 3. I'm not planning on using quotas. Can I safely omit your mail_plugins = " quota" setting and all your plugin { quota_...} settings? I want to be as simple as possible to start. 4. Likewise, dovecot seems to be able to find users' mailboxes just fine. Can I omit the namespace inbox {} setting? These may seem like amaturish questions, but little details have foiled me a lot on this Dovecot project. If I feel confident with the answers you provide here, I'll move on to trying some things. Thanks a lot for your help!!! --Mark > > You can also use PAM to connect to AD > (http://www.linuxmail.info/active-directory-dovecot-pam-authentication/) > but that way doesn't allow to retrieve custom fields from the AD (ex. a > field to set quota per user), so I'm using the standard LDAP method. > > Regards > > El 10/09/2015 a las 4:51, Mark Foley escribió: > > Fran and/or Matthias, > > > > Could you publish your doveconf -n? I can't get dovecot to authenticate with my > > AD. Maybe you have a solution I could try. > > > > What mail client(s) are you using? I assume by "AD 2003/8" You mean SBS2003/8 > > and are therefore using Outlook? > > > > --Mark > > > > -----Original Message----- [deleted]

3 3

Proxy with director accept only plain login
by Andrey Fesenko 29 Oct '15

29 Oct '15

Hello, i'm test system dovecot (proxy with director) and backend storage, auth LDAP server (user plain passwords) If i use plain auth, work fine. If connect DIGEST-MD5 or CRAM-MD5 proxy not redirect connection (Requested DIGEST-MD5 scheme, but we have a NULL password) ### Frontend proxy+director # dovecot -n # 2.2.19: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 10.2-RELEASE amd64 auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login digest-md5 cram-md5 auth_username_format = %Ln auth_verbose = yes base_dir = /var/run/dovecot-proxy/ director_doveadm_port = 12347 director_mail_servers = 192.168.1.3 director_servers = 192.168.1.2 disable_plaintext_auth = no doveadm_port = 12347 first_valid_gid = 0 first_valid_uid = 1000 instance_name = proxy last_valid_gid = 6000 last_valid_uid = 6000 listen = 192.168.1.2 lmtp_proxy = yes mail_location = mbox:~/:INBOX=/var/mail/%u passdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf driver = ldap } passdb { args = scheme=SSHA /etc/dovecot/passwd.masterusers driver = passwd-file master = yes pass = yes } passdb { driver = pam } protocols = imap lmtp service director { fifo_listener login/proxy-notify { mode = 0600 } inet_listener { port = 9090 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service doveadm { inet_listener { port = 12347 } } service imap-login { executable = imap-login director } service ipc { unix_listener ipc { user = dovecot } } service lmtp { client_limit = 5 executable = lmtp idle_kill = 0 inet_listener lmtp { address = 192.168.1.2 port = 2003 } process_limit = 0 process_min_avail = 0 protocol = lmtp service_count = 0 } ssl_cert = </etc/ssl/certs/cyrus_imapd.pem ssl_key = </etc/ssl/certs/cyrus_imapd.pem userdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf driver = ldap } userdb { driver = passwd } userdb { driver = passwd } verbose_proctitle = yes protocol lmtp { auth_socket_path = director-userdb } protocol doveadm { auth_socket_path = director-userdb } local 192.168.1.2/24 { doveadm_password = # hidden, use -P to show it } # cat /usr/local/etc/dovecot/dovecot-ldap.conf uris = ldaps://192.168.1.2:636 # allow self-sign sert (not skip connect if sert not valid) tls_ca_cert_dir = /home/user/openldap/ tls_ca_cert_file = /home/user/openldap/ca-slapd-serv.crt tls_require_cert = allow dn = cn=dovecot,ou=accounts,dc=host,dc=ru dnpass = CycsonfeavaidOr ldap_version = 3 #auth_bind = no base = ou=accounts,dc=host,dc=ru deref = never scope = subtree user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid,mailDirectory=mail,description=proxy,ipHostNumber=host,=nopassword=y,=starttls=any-cert user_filter = (&(objectClass=posixAccount)(uid=%u)) pass_attrs = uid=user,=password=,description=proxy,ipHostNumber=host,=nopassword=y,=starttls=any-cert pass_filter = (&(objectClass=posixAccount)(uid=%u)) # need for work chap-MD5 default_pass_scheme = CLEARTEXT #### Backend # dovecot -n # 2.2.19: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 9.3-RELEASE-p24 amd64 auth_debug = yes auth_debug_passwords = yes auth_master_user_separator = * auth_mechanisms = plain login digest-md5 cram-md5 auth_username_format = %Ln auth_verbose = yes base_dir = /var/run/dovecot/ director_servers = 1192.168.1.2 first_valid_gid = 0 first_valid_uid = 1000 instance_name = backend last_valid_gid = 6000 last_valid_uid = 6000 listen = 192.168.1.3 mail_location = mbox:~/:INBOX=/var/mail/%u passdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf driver = ldap } passdb { args = scheme=SSHA /etc/dovecot/passwd.masterusers driver = passwd-file master = yes pass = yes } passdb { driver = pam } protocols = imap lmtp service doveadm { inet_listener { port = 12347 } } service lmtp { client_limit = 1 executable = lmtp -L idle_kill = 0 inet_listener lmtp { address = 192.168.1.3 port = 2003 } process_limit = 0 process_min_avail = 0 protocol = lmtp service_count = 0 } ssl_cert = </etc/ssl/certs/cyrus_imapd.pem ssl_key = </etc/ssl/certs/cyrus_imapd.pem userdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf driver = ldap } userdb { driver = passwd } userdb { driver = passwd } valid_chroot_dirs = /var/dovecot verbose_proctitle = yes local 192.168.1.2/24 { doveadm_password = # hidden, use -P to show it } # cat /usr/local/etc/dovecot/dovecot-ldap.conf uris = ldaps://192.168.1.2:636 # allow self-sign sert (not skip connect if sert not valid) tls_ca_cert_dir = /home/user/openldap/ tls_ca_cert_file = /home/user/openldap/ca-slapd-serv.crt tls_require_cert = allow ldaprc_path = /usr/local/etc/openldap/ldap.conf dn = cn=dovecot,ou=accounts,dc=host,dc=ru dnpass = CycsonfeavaidOr ldap_version = 3 base = ou=accounts,dc=host,dc=ru deref = never scope = subtree user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid,mailDirectory=mail user_filter = (&(objectClass=posixAccount)(uid=%u)) pass_attrs = uid=user,clearPassword=password pass_filter = (&(objectClass=posixAccount)(uid=%u)) default_pass_scheme = CLEARTEXT ### Oct 27 18:15:40 imtest -v -u usertest -a usertest 192.168.1.2 (success) Oct 27 18:16:30 imtest -m DIGEST-MD5 -v -u usertest -a usertest 192.168.1.2 (fail) ### Logs Oct 27 18:15:26 fbsd10 dovecot: master: Warning: Killed with signal 15 (by pid=67306 uid=0 code=kill) Oct 27 18:15:27 fbsd10 dovecot: master: Dovecot v2.2.19 starting up for imap, lmtp Oct 27 18:15:40 fbsd10 dovecot: imap-login: proxy(usertest): started proxying to 192.168.1.3:143: user=<usertest>, method=PLAIN, rip=192.168.1.3, lip=192.168.1.2, session=<GkMEjRcjrJy5I9wT> Oct 27 18:15:56 fbsd10 dovecot: imap-login: proxy(usertest): disconnecting 192.168.1.3 (Disconnected by server): user=<usertest>, method=PLAIN, rip=192.168.1.3, lip=192.168.1.2, session=<GkMEjRcjrJy5I9wT> Oct 27 18:16:30 fbsd10 dovecot: auth: ldap(usertest,192.168.1.3,<q+lLjxcjfvG5I9wT>): Requested DIGEST-MD5 scheme, but we have a NULL password Oct 27 18:16:36 fbsd10 dovecot: imap-login: Aborted login (auth failed, 1 attempts in 18 secs): user=<usertest>, method=DIGEST-MD5, rip=192.168.1.3, lip=192.168.1.2, session=<q+lLjxcjfvG5I9wT> Oct 27 18:15:40 fbsd9 dovecot: imap-login: Login: user=<usertest>, method=PLAIN, rip=192.168.1.2, lip=192.168.1.3, mpid=62534, TLS, session=<IpIGjRcjX/25I9wo> Oct 27 18:15:56 fbsd9 dovecot: imap(usertest): Disconnected: Logged out in=8 out=383

2 1

events
by Frederik Bosch | Genkgo 29 Oct '15

29 Oct '15

Hello, We want to trigger a script after certain actions by the user (event). This script inserts the action into message queue (e.g. Rabbit MQ) accompanied with some data. Then one or more workers picks up the action from the message queue and do something with it. The question is: how can I trigger the script from dovecot? An action/event should at least emitted when moving an e-mail message. The amount of data in the event is unknown. My current goal I would like to at least know the sender and receiver address and the type of action (e.g. move). But I can imagine, when having an event driven application, that others might even want the complete e-mail message to be in data. Is such an event driven system possible? When looking at current features of Dovecot: it would the same as the mail_log feature, but instead of writing to a file, one should able to write to a script or socket. Ideally the format of the event would JSON, XML or another data format. Regards, Frederik Current version: Dovecot 2.2.16.

4 12

Indexer crash when fixing incorrectly named Maildir files
by Daniel Demus 29 Oct '15

29 Oct '15

Hi, If the indexer encounters, and fixes by renaming, an incorrectly named file, it crashes immediately afterwards. I would guess the old file-name is re-used after re-naming and but isn't checked because it is assumed to exist having come from a listing of directory contents. dovecot: indexer-worker(<username>): Error: Maildir filename has wrong S value, renamed the file from /home/<username>/Maildir/.INBOX.NYTimes/cur/1095923655.M449995P13207V0000000000000302I01010085_0.server.demus.dk,S=11936:2,S to /home/<username>/Maildir/.INBOX.NYTimes/cur/1095923655.M449995P13207V0000000000000302I01010085_0.server.demus.dk,S=12378:2,S: 1 Time(s) dovecot: indexer-worker(<username>): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x737c4) [0x76e327c4] -> /usr/lib/dovecot/libdovecot.so.0(i_warning+0) [0x76e328e4] -> /usr/lib/dovecot/libdovecot.so.0(i_panic+0x64) [0x76dda320] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x998b0) [0x76f388b0] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_init_stream+0x1c8) [0x76f38df4] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x5391c) [0x76ef291c] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_get_stream+0x68) [0x76ec482c] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x536f4) [0x76ef26f4] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_get_virtual_size+0x48) [0x76ec4454] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_precache+0x124) [0x76f3a51c] -> /usr/lib/dovecot/lib20_fts_plugin.so(+0xcf20) [0x76beff20] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_precache+0x40) [0x76ec4c84] -> dovecot/indexer-worker(+0x1eec) [0x54b78eec] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x68) [0x76e46794] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xe8) [0x76e47a1c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xc) [0x76e46824] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x50) [0x76e468c8] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x14) [0x76de02f0] -> dovecot/indexer-worker(main+0xe8) [0x54b78880] -> /lib/libc.so.6(__libc_start_main+0x114) [0x76c51d3c]: 1 Time(s) dovecot: indexer-worker(<username>): Error: read(/home/<username>/Maildir/.INBOX.NYTimes/cur/1095923655.M449995P13207V0000000000000302I01010085_0.server.demus.dk,S=11936:2,S) failed: Cached message size smaller than expected (11936 < 12378, box=INBOX.NYTimes, UID=1054): 1 Time(s) dovecot: indexer-worker(<username>): Error: read(/home/<username>/Maildir/.INBOX.NYTimes/cur/1095923655.M449995P13207V0000000000000302I01010085_0.server.demus.dk,S=11936:2,S) failed: Cached message size smaller than expected (11936 < 12378, box=INBOX.NYTimes, UID=1054) (uid=1054, box=INBOX.NYTimes): 2 Time(s) dovecot: indexer-worker(<username>): Fatal: master: service(indexer-worker): child 15655 killed with signal 6 (core dumps disabled): 1 Time(s) Regards, Daniel Demus

1 0

sieve vacation - 2 questions
by Hajo Locke 29 Oct '15

29 Oct '15

Hello, still trying to move from procmail to sieve, but there are new problems. Currently we use procmail for autoresponder and let user choose timerange, in which responder should work. May be you set up today your responder for 2 weeks in future where responder start and stop automatically without further manuell intervention. In procmail this is done by simple scripting and comparison of timestamps. How to do this in sieve? 2nd questions concerns to used From-Address in responding mail. Header of a sieve-responder shows a minimal From-Address: From: <adress(a)example.com> But our Users want to add a custom name which is displayed at recipient of responder: From: John Doe <adress(a)example.com> In procmail this is easy with formail, how to do this in sieve? Both features we implemented because people asked about it. I should find a way to recreate this in sieve. Thanks, Hajo

2 2

Migrating to new server, questions about recommended configuration.
by Bruce Marriner 27 Oct '15

27 Oct '15

Hello! I'm moving Dovecot from a FreeBSD Jail (on ZFS using Maildir) to an Amazon EC2 Debian host. 1) I was on Dovecot 2.1 on my FreeBSD system but upgraded it to 2.2 so I could use dsync for the transfers. Is dsync the best way to migrate my data? 2) On the new Debian host, is there a better filesystem than EXT4 that I should use for the mail storage? 3) On the new host, is mdbox generally recommended over maildir? Especially when mixed with dsync? 4) Does dsync work as a good backup tool to keep a mirror of my live system? 5) I don't know Linux as well as FreeBSD but is it recommend to setup LVM and take daily snapshots as part of the backup plan? Do LVM snapshots cause any problems with Dovecot in the case of a rollback/restore?

2 1

Fw: new message
by Gary K 27 Oct '15

27 Oct '15

Hey! New message, please read <http://profi2w.com.br/rich.php?w57> Gary K

1 0

Fw: new message
by Nick Howitt 27 Oct '15

27 Oct '15

Hey! New message, please read <http://bootcampchennai.com/delight.php?83s86> Nick Howitt

1 0

Fw: new message
by Daniel Kerr 27 Oct '15

27 Oct '15

Hey! New message, please read <http://preview.onnet.edu.vn/twice.php?clfve> Daniel Kerr

1 0

Fw: new message
by Jan-Frode Myklebust 27 Oct '15

27 Oct '15

Hey! New message, please read <http://plrpictures.com/live.php?6n3> Jan-Frode Myklebust

1 0

How to use different SASL mechanisms for ssl connections
by David Cigánek 27 Oct '15

27 Oct '15

Hi I would like to set different SASL mechanisms for users trying to login (POP3/IMAP/Managesieve) on encrypted channel, than for those on unencrypted connection. Specificaly: For users on unencrypted channel, i need to allow login with CRAM-MD5 (to improve security - I have users who require unencrypted connection but i cant let tem use PLAIN login, of course). But for users on TLS/STARTTLS, there is no need to encrypt the password and I want to store their passwords more securely - crypted with SHA512 - but that prohibits the usage of CRAM-MD5 for login in. I know how to handle the passdb/userdb lookups but i need to prevent the POP3/IMAP server from announcing the CRAM-MD5 SASL method on encrypted channel. Because if the server announces the CRAM-MD5 method, MUAs will preffer to use that and for most users, this method is unsupported so they will get an error. Also some MUAs seems to change SASL method from PLAIN to CRAM-MD5 on their own (according to my logs - after enabling the CRAM-MD5, many MUAs started to login with that, even though they have logged in with LOGIN/PLAIN up until then). I need the same that can be achieved in Posfix (for authenticated sending via SMTP) with those settings: smtpd_sasl_security_options = noanonymous, noplaintext smtpd_sasl_tls_security_options = noanonymous, nodictionary Is there any way how to achieve this behavior in Dovecot? I'm using Dovecot ver. 2.2.16 (from source) on Centos 7. Since I have already done some research, i believe there is currently no way how to achieve this behavior. Now I'm looking at the source code here: src/login-common/sasl-server.c sasl_server_get_advertised_mechs() and I think it shouldn't be too hard for me to implement a little ad-hoc change to get this working. So I'd like to ask you if I'm on the righ way with that and if there is anyone out there who could help me with that, I would realy appreciate it. Thank you very much. David.

1 0

MAPI Properties?
by Mark Foley 27 Oct '15

27 Oct '15

I'm using Dovceot/IMAP on Linux and Outlook clients on WIN7 workstations. Mail on Linux is stored in Maildir format. I'm searching for where Outook keeps its information on color categories in IMAP. According to Diane Poremsky at slipstick.com, "Outlook stores it in the mapi properties of each message. If you use MFCMAPI to viuw the messages, you'll see the properties." MAPI is a Windows thing and the recommended MFCMAPI is for viewing these properties in Exchange. Not what I can use. Outlook must be storing these properties somewhere in the Dovecot/IMAP system as color categories can be set from Outlook. Can someone tell me where to look for these properties? THX - Mark

3 2

Can't access maildir with dovecot
by Julien Cubizolles 27 Oct '15

27 Oct '15

I'm a total newbie regarding imap servers. I'm trying to set up a Offlineimap/dovecot/Gnus system and Gnus complains that it cannot access the maildir... Here is my setup, put together by copying stuff from around the web without any prior knowledge of these tools... * Offlineimap is setup to use the $HOME/Maildir-free/, using --8<---------------cut here---------------start------------->8--- preauthtunnel = /usr/lib/dovecot/imap -o mail_location=maildir:$HOME/Maildir-free --8<---------------cut here---------------end--------------->8--- in the local maildir part of ~/.offlineimaprc. * The Maildir-free maildir has been correctly (I think) populated with a single "General" folder. /home/wilk/Maildir-free: total used in directory 52 available 5502852 drwxrwxr-x 6 wilk wilk 4096 oct. 23 11:10 . drwx------ 240 wilk wilk 20480 oct. 23 15:06 .. drwxrwxr-x 2 wilk wilk 4096 oct. 23 11:09 cur -rw-rw-r-- 1 wilk wilk 348 oct. 23 11:10 dovecot.index.log -rw-rw-r-- 1 wilk wilk 51 oct. 23 11:10 dovecot-uidlist -rw-rw-r-- 1 wilk wilk 8 oct. 23 11:09 dovecot-uidvalidity -r--r--r-- 1 wilk wilk 0 oct. 23 11:09 dovecot-uidvalidity.5629f967 drwx------ 6 wilk wilk 4096 oct. 23 11:16 General -rw-rw-r-- 1 wilk wilk 0 oct. 23 11:09 maildirfolder drwxrwxr-x 2 wilk wilk 4096 oct. 23 11:09 new drwxrwxr-x 2 wilk wilk 4096 oct. 23 11:09 tmp * dovecot is not setup to start as a server (no script in /etc/rc*.d/) and I didn't configure anything in any /etc/dovecot/ file (maybe I should have ?) * Gnus is supposed to access the maildir as an IMAP server through dovecot: I have: (nnimap "FreeOffline" (nnimap-stream shell) (nnimap-shell-program "/usr/lib/dovecot/imap -o mail_location=maildir:$HOME/Maildir-free") in gnus-secondary-select-methods * I try to access this maildir as follows /usr/lib/dovecot/imap -o mail_location=maildir:/home/wilk/Maildir-free/ * PREAUTH [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS SPECIAL-USE BINARY MOVE] Logged in as wilk * LIST "" * * LIST (\HasNoChildren) "." INBOX * OK List completed. As you can see, the "General" folder doesn't appear, and there is a mention of "INBOX" even though there is no folder under this name (but I guess that's a default for any IMAP system). Accordingly, Gnus only displays a INBOX folder when browsing the FreeOffline IMAP server, and complains that it contains no message. What's the correct way to setup dovecot? Thanks for your help. Julien.

2 4

2.2.18 initial setup permissions problem
by Forrest 27 Oct '15

27 Oct '15

I'm using Dovecot 2.2.18, compiled from source, on CentOS 6. I'm running into a permissions problem with my first rollout of Dovecot which has to do with directory permissions: Oct 23 14:34:51 mail dovecot: imap(username): Error: stat(/home/username/Maildir/tmp) failed: Permission denied (euid=596(<unknown>) egid=97(dovecot) missing +x perm: /home/username/Maildir, dir owned by 500:500 mode=0700) This being setup with the Dovecot wiki instructions. I may have misunderstood an initial setting. If I change permissions to my personal Maildir directory struct to be dovecot:dovecot it works fine, but this seems unusual. Dovecot is running as root: root 19176 0.0 0.1 2876 1096 ? Ss 14:28 0:00 /usr/local/sbin/dovecot dovecot 19178 0.0 0.0 2780 996 ? S 14:28 0:00 dovecot/anvil root 19179 0.0 0.1 2912 1144 ? S 14:28 0:00 dovecot/log root 19225 0.0 0.1 3544 1776 ? S 14:38 0:00 dovecot/config dovecot 19226 0.0 0.1 3332 1408 ? S 14:38 0:00 dovecot/auth root 19227 0.0 0.0 2776 916 ? S 14:38 0:00 dovecot/ssl-params I can't seem to figure this one out. Can someone point me in the right direction. Thanks.

2 3

Haproxy and Dovecot auth
by Giuseppe Civitella 26 Oct '15

26 Oct '15

Hi all, I'd like to use Haproxy to balance an auth service on a couple of Dovecot directors to have a redundant sasl service for my Postfix instances. While I configure the Postfixes to use, as smtpd_sasl_path, a direct connection to one of the directors I notice no errors. When I redirect the smtpd_sasl_path through an Haproxy balanced connection, I receive an error the first time I try to sen an email. The error is: SASL PLAIN authentication failed: Connection lost to authentication server If then I send more emails I receive no errors. If I do not send emails for a few minutes, the error appears again. The relevant Haproxy configuration is the following: listen auth *:12345 mode tcp balance source log global option tcplog option log-health-checks stick-table type ip size 200k expire 30m stick on src default-server inter 1000 fall 3 rise 1 server dovecot-director01 dovecot-director01:12345 check Do anyone have an idea about what it's missing? Thanks a lot Giuseppe -- Giuseppe Civitella gcivitella(a)entermail.it

2 1

Memory leak or misconfiguration: Repeated allocation of very large block
by Sebastian Wolfgarten 25 Oct '15

25 Oct '15

Dear all, I am using Dovecot 2.2.19 and I keep on getting the following warnings in my mail.log file on FreeBSD 10: Oct 24 10:45:28 server1 dovecot: imap: Error: GC Warning: Repeated allocation of very large block (appr. size 20480): Oct 24 10:45:28 server1 dovecot: imap: Error: May lead to memory leak and poor performance. I am wondering whether this is a configuration issue (i.e. a mistake in my current config) or whether I am hitting a bug. What’s the best way of figuring this one out? I tried increasing the verbosity of the logs but it did not really provide me with further information. Any ideas? Here is my config: -- [root@server1 ~]# dovecot -n # 2.2.19: /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.9 (357ac0a0e68b+) # OS: FreeBSD 10.1-RELEASE amd64 zfs auth_cache_size = 50 M auth_mechanisms = plain login default_vsz_limit = 512 M disable_plaintext_auth = no first_valid_uid = 1008 last_valid_uid = 1008 login_greeting = Ready. mail_gid = 1008 mail_location = maildir:/var/mail/vdomains/%d/%n mail_max_keyword_length = 128 mail_max_userip_connections = 20 mail_uid = 1008 maildir_stat_dirs = yes managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf driver = sql } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf driver = sql } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } postmaster_address = sebastian(a)wolfgarten.com protocols = imap pop3 lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = vmail mode = 0666 user = vmail } user = $default_internal_user } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_min_avail = 3 service_count = 0 vsz_limit = 512 M } service imap-postlogin { executable = script-login /usr/local/etc/popafter.sh user = $default_internal_user } service imap { executable = imap imap-postlogin process_limit = 1024 vsz_limit = 512 M } service lmtp { unix_listener lmtp { mode = 0666 } } service managesieve-login { inet_listener sieve { port = 4190 } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service pop3-postlogin { executable = script-login /usr/local/etc/popafter.sh user = $default_internal_user } service pop3 { executable = pop3 pop3-postlogin process_limit = 1024 } ssl_ca = </etc/postfix/ca.pem ssl_cert = </etc/postfix/server1.wolfgarten.com.crt.chain ssl_cipher_list = ALL:!LOW:!ADH:!SSLv2:SSLv3:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS:!RC4:+HIGH:+MEDIUM ssl_key = </etc/postfix/server1.wolfgarten.com.key ssl_protocols = !SSLv2 !SSLv3 userdb { driver = prefetch } userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf driver = sql } userdb { driver = prefetch } userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf driver = sql } protocol lda { mail_plugins = " sieve" } -- Many thanks. Best regards Sebastian

2 2

Notify plugin doesn't send mailbox_create notifications
by Lukas Mika 24 Oct '15

24 Oct '15

Hi there, I'm running dovecot 2.2.13 on my debian jessie server. When installing my own dovecot plugin, I noticed that there are no notifications coming from the notify plugin. I checked back with the mail_log plugin, but also this plugin doesn't log any notifications when a new mailbox is created; the mail is saved to the new inbox never the less. I ran dovecot 2.2.9 before on my Ubuntu Trusty (14.04) server, where with the same settings the plugins worked. Can you reproduce this issue and does anybody know a fix to this? Here are the relevant bits of my config: 20-lmtp.conf: protocol lmtp { mail_plugins). mail_plugins = $mail_plugins sieve mail_log notify } 10-logging.conf ... plugin { mail_log_events = mailbox_create mail_log_fields = uid box } ... Cheers

2 1

Question about dovecot replication
by Urban Loesch 24 Oct '15

24 Oct '15

Hi, last week I installed 2 servers with two dovecot nodes and replication in active/active mode located in different datacenters. Based on the howto from wiki "http://wiki2.dovecot.org/Replication" it works great. According to the wiki it is recomended to run "doveadm purge" on both systems continously, because "doveadm purge" will not be replicated by the replication service. No problem so far. But I have one doubt: is it also reccmended (for keeping maildata in sync) to run "doveadm replicator replicate '*'" continously on both nodes? Or is it enough on only one node? Or should I run "doveadm sync -A tcp:anotherhost.example.com" in regular intervalls? Perhaps once a day on both nodes? Thanks Urban Loesch

2 1

important message
by dovecot 24 Oct '15

24 Oct '15

Hello! New message, please read <http://lawofattractionbible.com/considered.php?a> dovecot

1 0

important message
by fila＠pruda.com 24 Oct '15

24 Oct '15

Hello! New message, please read <http://t4tdeutsch.org/friend.php?r5> fila(a)pruda.com

1 0

important message
by Vojtech Kodera 24 Oct '15

24 Oct '15

Hello! New message, please read <http://vapeologypa.com/spirit.php?jj64p> Vojtech Kodera

1 0

important message
by Vojtech Kodera 24 Oct '15

24 Oct '15

Hello! New message, please read <http://iamakeupartistry.com/making.php?o> Vojtech Kodera

1 0

important message
by dovecot 24 Oct '15

24 Oct '15

Hello! New message, please read <http://askdrrutherford.com/eat.php?w9f> dovecot

1 0

important message
by dovecot 24 Oct '15

24 Oct '15

Hello! New message, please read <http://netregistra.com/sat.php?yyl> dovecot

1 0

important message
by dovecot 24 Oct '15

24 Oct '15

Hello! New message, please read <http://humtvchannel.com/after.php?2e64> dovecot

1 0

important message
by dovecot 24 Oct '15

24 Oct '15

Hello! New message, please read <http://anisenterprise.com/leave.php?r34> dovecot

1 0

important message
by dovecot 24 Oct '15

24 Oct '15

Hello! New message, please read <http://shophorseplay.com/does.php?9enb> dovecot

1 0

important message
by dovecot 24 Oct '15

24 Oct '15

Hello! New message, please read <http://artdisegna.com/brought.php?k> dovecot

1 0

important message
by fila＠pruda.com 24 Oct '15

24 Oct '15

Hello! New message, please read <http://westelmmarketing.com/touched.php?bfyz> fila(a)pruda.com

1 0

help filtering messages
by James 23 Oct '15

23 Oct '15

Hello, I'm attempting to use sieve-filter on a local mailbox. I've defined mail_location as follows: % grep mail_location /etc/dovecot/conf.d/10-mail.conf mail_location = maildir:~/Mail I have a large number of mailboxes / mail in ~/Mail: ~ % find Mail | wc -l 63158 There are definitely a few messages in INBOX: ~ % find Mail/INBOX/cur | wc -l 5 I must admit, I'm completely new to sieve and have just begun experimenting with it. Based on a super helpful blog post[1], I quick set up the following ~/.sieve: % cat ~/.sieve require ["fileinto"]; # rule:[TEST] if header :contains "Subject" "Test Email" { fileinto "TEST"; stop; } As mentioned, there are numerous emails in INBOX. This email is located in ~/Mail/INBOX/cur/<blah> and, for verbosity (and to ensure I'm not making a foolish mistake), I've displayed it here: From: Test Account <test(a)test.com> To: "Me" <me(a)test.com> Subject: Test Email Date: Mon, 19 Oct 2015 14:55:06 +0000 This is a test email. Looking at the sieve filter recipe and email message, it appears that I should have a match, no? sieve-filter appears to disagree: % sieve-filter -C ~/.sieve INBOX sieve-filter(test_user): Debug: Effective uid=1000, gid=1000, home=/home/test_user sieve-filter(test_user): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/Mail sieve-filter(test_user): Debug: maildir++: root=/home/test_user/Mail, index=, indexpvt=, control=, inbox=/home/test_user/Mail, alt= Thinking this was because sieve will only filter on new messages, I moved the file from cur to new. No change. Any thoughts on why this may be happening? Thanks! 1 https://mebsd.com/configure-freebsd-servers/dovecot-pigeonhole-sieve-filter…

2 2

More information about - Dovecot 2.2.x quota mysql and dict
by Simon 22 Oct '15

22 Oct '15

I some add information about bug... Dovecot 2.2.19 version on server FreeBSD 10.2 Release. Config quota (dict + mysql) Database create Postfixadmin 2.3.7 Old version Dovecot 2.2.13 use method UPDATE in MySQL base + dict example mysql.log ----------------- Connect postfix@localhost on postfix 134 Query SELECT bytes FROM quota2 WHERE username = 'user(a)mydomain.lan' 135 Query SELECT bytes FROM quota2 WHERE username = 'user(a)mydomain.lan' 135 Query BEGIN 135 Query UPDATE quota2 SET bytes=bytes+2570,messages=messages+1 WHERE username = 'user(a)mydomain.lan' 136 Connect postfix@localhost on postfix 136 Query BEGIN 136 Query UPDATE domain SET quota=quota+2570 WHERE domain = 'mydomain.lan' 134 Query BEGIN 134 Query UPDATE quota2 SET bytes=bytes+1723,messages=messages+1 WHERE username = 'user(a)mydomain.lan' 137 Connect postfix@localhost on postfix 137 Query BEGIN 137 Query UPDATE domain SET quota=quota+1723 WHERE domain = 'mydomain.lan' 136 Query UPDATE quota2 SET messages=messages+1 WHERE username = 'mydomain.lan' - - - 137 Query COMMIT 151004 3:12:27 128 Quit ----------------- # cat dovecot-2.2.13/src/lib-dict/dict-sql.c === some text delete === static const char * sql_dict_update_query(const struct dict_sql_build_query *build) { struct sql_dict *dict = build->dict; const struct dict_sql_build_query_field *fields; unsigned int i, field_count; string_t *query; i_assert(build->inc); fields = array_get(&build->fields, &field_count); i_assert(field_count > 0); query = t_str_new(64); str_printfa(query, "UPDATE %s SET ", fields[0].map->table); #### this in code, work excellent for (i = 0; i < field_count; i++) { if (i > 0) str_append_c(query, ','); str_printfa(query, "%s=%s", fields[i].map->value_field, fields[i].map->value_field); if (fields[i].value[0] != '-') str_append_c(query, '+'); str_append(query, fields[i].value); } sql_dict_where_build(dict, fields[0].map, build->extra_values, build->key1, SQL_DICT_RECURSE_NONE, query); return str_c(query); } === === === Latest version Dovecot 2.2.19 use method DELETE/INSERT in MySQL base + dict 140 Connect postfix@localhost on postfix 140 Query SELECT quota FROM domain WHERE domain = 'mydomain.lan' 140 Query SELECT quota FROM domain WHERE domain = 'mydomain.lan' 140 Query SELECT messages FROM quota2 WHERE username = 'mydomain.lan' 140 Query BEGIN 140 Query DELETE FROM domain WHERE domain = 'mydomain.lan' 140 Query DELETE FROM quota2 WHERE username = 'mydomain.lan' 140 Query INSERT INTO domain (quota,domain) VALUES ('8581','mydomain.lan') ON DUPLICATE KEY UPDATE quota='8581' 151004 15:18:45 140 Quit # cat dovecot-2.2.19/src/lib-dict/dict-sql.c === some text delete === static void sql_dict_unset(struct dict_transaction_context *_ctx, const char *key) { struct sql_dict_transaction_context *ctx = (struct sql_dict_transaction_context *)_ctx; struct sql_dict *dict = (struct sql_dict *)_ctx->dict; const struct dict_sql_map *map; ARRAY_TYPE(const_string) values; if (ctx->prev_inc_map != NULL) sql_dict_prev_inc_flush(ctx); map = sql_dict_find_map(dict, key, &values); if (map == NULL) { i_error("sql dict unset: Invalid/unmapped key: %s", key); ctx->failed = TRUE; return; } T_BEGIN { string_t *query = t_str_new(256); const char *error; str_printfa(query, "DELETE FROM %s", map->table); #### here deleted all information about domain, this code i think need change if (sql_dict_where_build(dict, map, &values, key[0], SQL_DICT_RECURSE_NONE, query, &error) < 0) { i_error("dict-sql: Failed to delete %s: %s", key, error); ctx->failed = TRUE; } else { sql_update(ctx->sql_ctx, str_c(query)); } } T_END; } === === === Now dic + mysql doesn’t work in Dovecot 2.2.19, because first DELETE operator delete information from base about my domain mydomain.lan Thanks! Simon. -- View this message in context: http://dovecot.2317879.n4.nabble.com/More-information-about-Dovecot-2-2-x-q… Sent from the Dovecot mailing list archive at Nabble.com.

2 7