- dovecot - dovecot.org

[Dovecot] Odd ownership of the dovecot-uidlist file
by dclist.hook＠hook.net.nz 27 May '14

27 May '14

Hi, We have just recently switched from Courier to Dovecot for both IMAAP and POP access for our shared hosting platform, and while the issues we have been seeing with Courier have gone away a new one has popped up. Unfortunately googling for an answer is difficult as it falls into the ownership and permissions category which people seem to have all the time. But in those cases it always happens, whereas what we are seeing is a random ownership change on the dovecot-uidlist file. Basically what we see is the user is able to login fine for days and then all of a sudden the file has changed ownership to a user under a different domain, what's worse is the other user has not even logged in during that time. Here's a snippet from a case from a month ago which was escalated to us, there are plenty of other examples but its so random we only know its happened when the customer complains or we happen to watch the logs, the current help desk procedure when the customer calls is to just fix the ownership of the file. -- 8<-- Mar 25 11:18:05 brio dovecot: pop3-login: Login: user=<accounts@DOMAIN1>, method=PLAIN, rip=IP, lip=IP, mpid=21739, TLS, session=<mwQLnGH1ZAB2XalI> Mar 25 11:18:08 brio dovecot: pop3(accounts@DOMAIN1): Disconnected: Logged out top=0 (0 b), retr=4 (274142 b), messages=27 (10797760 b), del=0 Mar 25 11:19:24 brio dovecot: pop3(accounts@DOMAIN1): Error: open(/mnt/spool/keepers/t/DOMAIN1/accounts/Maildir/dovecot-uidlist) failed: Permission denied Mar 25 11:19:24 brio dovecot: pop3(accounts@DOAMIN1): Error: open(/mnt/spool/keepers/t/DOMAIN1/accounts/Maildir/dovecot-uidlist) failed: Permission denied -- 8<-- In this case the ownership of the file was: -rw------- 1 jacqui-30747 DOMAIN2 48839 Mar 25 10:31 dovecot-uidlist when it should be: -rw------- 1 accounts-25105 DOMAIN1 48839 Mar 25 10:32 dovecot-uidlist As you can see both the user and the group have changed to a different user as if that user had recreated the file. Its worth noting that the parent directory does not change: drwx------ 8 accounts-25105 DOMAIN1 4096 Mar 25 10:31 . so this user should not even be able to access this file. It would be great if someone can give us some hints where the problem maybe as this has us stumped. Some more detail if it helps: root@brio:~# dovecot -n # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.2 auth_mechanisms = plain login cram-md5 apop auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@& default_process_limit = 3000 disable_plaintext_auth = no lock_method = dotlock mail_fsync = always mail_location = maildir:~/Maildir:INDEX=/home/indexes/%1d/%n@%d mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = " quota" maildir_stat_dirs = yes mmap_disable = yes namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = INBOX. separator = . subscriptions = yes } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } passdb { args = /etc/dovecot/dovecot-sql-cram.conf.ext driver = sql } plugin { quota = maildir:User quota } protocols = " imap pop3" service imap-login { inet_listener imap25 { port = 25143 } } service imap-postlogin { executable = script-login -d /usr/local/bin/postlogin.sh } service imap { executable = imap imap-postlogin } service pop3-login { inet_listener pop325 { port = 25110 } } service pop3 { executable = pop3 imap-postlogin } ssl_cert = </var/www/mailadmin/ssl/cert.pem ssl_crypto_device = dynamic ssl_key = </var/www/mailadmin/ssl/mailx.hosts.net.nz.key userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } userdb { args = /etc/dovecot/dovecot-sql-cram.conf.ext driver = sql } verbose_proctitle = yes protocol imap { imap_capability = +XHOST_brio imap_logout_format = bytes=%i/%o mail_max_userip_connections = 50 mail_plugins = " quota imap_quota" } protocol pop3 { mail_max_userip_connections = 10 pop3_lock_session = no pop3_logout_format = top=%t (%p b), retr=%r (%b b), messages=%m (%s b), del=%d pop3_save_uidl = yes pop3_uidl_format = %f } root@brio:~# dpkg -l|grep dovecot ii dovecot-core 1:2.1.7-7 amd64 secure mail server that supports mbox, maildir, dbox and mdbox mailboxes ii dovecot-imapd 1:2.1.7-7 amd64 secure IMAP server that supports mbox, maildir, dbox and mdbox mailboxes ii dovecot-mysql 1:2.1.7-7 amd64 MySQL support for Dovecot ii dovecot-pop3d 1:2.1.7-7 amd64 secure POP3 server that supports mbox, maildir, dbox and mdbox mailboxes Mailbox storage is done over various NFS stores, however each user has a specific NFS store Connections are load balanced using LVS and keepalived over approx 10 real servers, persistant connections are setup so that a single user should only hit a single dovecot server (this is different from our courier setup due to the known NFS limitations with dovecot) We also have IMAP indexes stored on the dovecot servers ext3 file system itself rather than NFS. Each server is setup and maintained by puppet, and any one of the servers may see the issue. All servers are x86 with at least 2Gb of RAM User information comes from a MySQL database, and testing the SQL statements only ever return the correct record. Exim is writing to the Maildir with the correct permissions, and after fixing the ownership of the file dovecot can read and change the mailboxes. We do have a postlogin.sh script which runs after authentication to convert the old courier files over to the dovecot ones, this only happens however when the process has not run before (it appears dovecot deletes the files and recreates them, so we use a state file). Adding debugging to the script shows its running as the correct user at the last successful login. It does not run at all after the ownership has changed. There are some users who this is happening regularly, and other users who it has happened to only once. It is also not just limited to POP3, although this is where we commonly see it as dovecot accepts the IMAP connection if the ownership on a sub folders uidlist is different. If you need any further detail, I can provide it. Debugging could be much more difficult because of how random it is, while it can happen daily there have been periods of up to one week before its seen. Any help in finding this would be greatly appreciated, Cheers, Bruce

2 1

[Dovecot] Incorrect IMAP search results when FTS/Squat indexes are present with 2.1.7
by Robert L Mathews 27 May '14

27 May '14

We recently upgraded from Dovecot 1.2.15 (on Debian squeeze) to Dovecot 2.1.7 (on Debian wheezy/stable). For now, we continue to use FTS with Squat indexes. We'd like to eventually switch to Lucene but it's not yet supported in Debian stable. Since upgrading to 2.1.7, we've seen some problems with IMAP search results when an FTS Squat index is present (i.e., when the "dovecot.index.search" and "dovecot.index.search.uids" files are present). If it's present, even header searches sometimes give incorrect results (such as searches on FROM or SUBJECT headers). I'm wondering if this is a known issue with 2.1.7 and whether upgrading to a later version of Dovecot with Squat is likely to fix this (due to, say, <http://www.dovecot.org/list/dovecot-cvs/2012-June/020881.html>), or if Squat in all versions is a lost cause and I need to switch to Lucene. I can demonstrate the problem by showing the results of three searches on my mailbox. First, here are the correct results for header FTS searches when no "dovecot.index.search[.uids]" file is present: ---- . UID SEARCH FROM "Nick" * SEARCH 9 66 100 116 179 212 274 338 347 386 494 519 579 603 643 766 781 788 827 1107 1280 1626 1641 1667 1688 1702 1703 2184 2187 3202 3519 3716 3798 3885 3886 4024 4166 4345 4400 4401 4436 4491 4561 4595 4618 4676 4711 4712 4746 4788 4883 5217 5253 5577 5602 5722 . OK Search completed (0.059 secs). . UID SEARCH ALL FROM "Nick" * SEARCH 9 66 100 116 179 212 274 338 347 386 494 519 579 603 643 766 781 788 827 1107 1280 1626 1641 1667 1688 1702 1703 2184 2187 3202 3519 3716 3798 3885 3886 4024 4166 4345 4400 4401 4436 4491 4561 4595 4618 4676 4711 4712 4746 4788 4883 5217 5253 5577 5602 5722 . OK Search completed (0.058 secs). . UID SEARCH SUBJECT "Nick" * SEARCH 3466 3467 3507 . OK Search completed (0.054 secs). ---- These results are consistent (and correct) whether "mail_plugins = fts fts_squat" is enabled or not, as long as no "dovecot.index.search[.uids]" file is present. Now I generate an FTS index: ---- . UID SEARCH TEXT "Nick" * OK Indexed 98% of the mailbox, ETA 0:00 * OK Mailbox indexing finished * SEARCH 9 32 66 100 111 112 113 116 179 199 212 228 229 240 274 303 338 347 386 393 448 478 491 494 519 579 591 603 614 618 624 643 649 742 766 781 788 827 837 839 841 1095 1106 1107 1174 1188 1225 1227 1228 1240 1254 1261 1278 1280 1452 1482 1519 1520 1595 1626 1641 1656 1667 1688 1702 1703 1724 1758 2184 2187 2798 2883 2932 3034 3198 3202 3206 3230 3371 3432 3454 3457 3466 3467 3507 3519 3631 3637 3685 3702 3703 3716 3765 3798 3799 3803 3853 3854 3855 3857 3873 3885 3886 3962 3969 4024 4033 4050 4051 4058 4161 4166 4173 4176 4224 4273 4345 4400 4401 4436 4461 4490 4491 4498 4561 4595 4618 4651 4676 4711 4712 4713 4729 4731 4736 4737 4738 4739 4746 4786 4787 4788 4813 4816 4822 4847 4883 4885 4933 4941 4942 4957 4958 5029 5052 5097 5135 5136 5182 5217 5253 5271 5357 5543 5551 5565 5577 5589 5602 5612 5643 5692 5722 . OK Search completed (11.078 secs). ---- Now I run the same original three searches, but they return completely different results(!): ---- . UID SEARCH FROM "Nick" * SEARCH 9 66 100 116 179 212 228 240 274 338 347 386 448 494 519 579 603 643 766 781 788 827 1095 1107 1174 1240 1254 1261 1280 1595 1626 1641 1667 1688 1702 1703 1724 2184 2187 2883 2932 3202 3371 3432 3457 3466 3467 3507 3519 3631 3637 3685 3716 3765 3798 3803 3853 3854 3855 3885 3886 3969 4024 4050 4166 4176 4224 4345 4400 4401 4436 4461 4490 4491 4498 4561 4595 4618 4676 4711 4712 4729 4731 4746 4788 4883 5029 5135 5136 5182 5217 5253 5577 5602 5722 . OK Search completed (0.001 secs). . UID SEARCH ALL FROM "Nick" * SEARCH . OK Search completed (0.001 secs). . UID SEARCH SUBJECT "Nick" * SEARCH 9 66 100 116 179 212 228 240 274 338 347 386 448 494 519 579 603 643 766 781 788 827 1095 1107 1174 1240 1254 1261 1280 1595 1626 1641 1667 1688 1702 1703 1724 2184 2187 2883 2932 3202 3371 3432 3457 3466 3467 3507 3519 3631 3637 3685 3716 3765 3798 3803 3853 3854 3855 3885 3886 3969 4024 4050 4166 4176 4224 4345 4400 4401 4436 4461 4490 4491 4498 4561 4595 4618 4676 4711 4712 4729 4731 4746 4788 4883 5029 5135 5136 5182 5217 5253 5577 5602 5722 . OK Search completed (0.001 secs). ---- The "ALL" one returns nothing at all, even though an "AND" search on "ALL" should make no difference, and the "FROM" and "SUBJECT" ones now return identical incorrect results, many of which do not actually match the header requested when examined -- it's returning messages with "Nick" in *any* header. For example, message 9 does not contain "Nick" in the subject, despite the results shown above: ---- . FETCH 9 UID * 9 FETCH (UID 9) . OK Fetch completed. FETCH 9 BODY.PEEK[HEADER.FIELDS (SUBJECT)] * 9 FETCH (BODY[HEADER.FIELDS (SUBJECT)] {47} Subject: Re: Finishing Gallery support page ) . OK Fetch completed. ---- If I delete the "dovecot.index.search" and "dovecot.index.search.uids" files, or if I disable fts in the configuration entirely, the results immediately become correct again. As I mentioned above, I'm wondering if anyone knows the cause of (and fix for) this. Here's my doveconf -n: # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.4 auth_master_user_separator = * auth_mechanisms = plain login auth_username_format = 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 = pid=[%p] user=<%u> method=%m rip=%r lip=%l %c mail_fsync = never mail_location = maildir:~/ mail_max_userip_connections = 100 mail_plugins = fts fts_squat mail_log notify 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 ihave 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 } passdb { args = /etc/dovecot/master-passwords driver = passwd-file master = yes pass = yes } plugin { fts = squat mail_log_events = copy expunge mail_log_fields = box msgid size from 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 = sieve postmaster_address = postmaster(a)tigertech.net sendmail_path = /usr/local/bin/dovecot-sendmail-wrapper } protocol lmtp { mail_fsync = optimized mail_plugins = sieve postmaster_address = postmaster(a)tigertech.net sendmail_path = /usr/local/bin/dovecot-sendmail-wrapper } -- Robert L Mathews, Tiger Technologies, http://www.tigertech.net/

1 0

[Dovecot] LDAP: allow pop3, restrict imap
by Andreas Schulze 26 May '14

26 May '14

Hello, I have all userdata in a ldapserver. Every user has the right to use pop3. There is no explicit attribute allowing that. It's simply possible. Now I like to add imap. For a starting period I like to restrict, who may use imap. http://wiki2.dovecot.org/Authentication/RestrictAccess mention a solution where I could modify ldap pass_filter. But that require an attribute "service=pop3" to be present in the ldap servers. In my case I have to add it for every existing user :-/ No way... Are there other options? Thanks, Andreas

3 3

[Dovecot] socket /var/spool/postfix/private/auth not created
by lister171254 26 May '14

26 May '14

I'm on Ubuntu 13.10 and followed these instructions http://wiki2.dovecot.org/HowTo/PostfixAndDovecotSASL to configure Dovecot for Postfix. No matter what I try, the listener is not created. <http://dovecot.2317879.n4.nabble.com/file/n48182/32.png> dovecot -n does not show the listener (I guess that's why its not created) This is the extract from the /etc/dovecot/conf.d/10-master.conf --------------- service auth { # auth_socket_path points to this userdb socket by default. It's typically # used by dovecot-lda, doveadm, possibly imap process, etc. Users that have # full permissions to this socket are able to get a list of all usernames and # get the results of everyone's userdb lookups. # # The default 0666 mode allows anyone to connect to the socket, but the # userdb lookups will succeed only if the userdb returns an "uid" field that # matches the caller process's UID. Also if caller's uid or gid matches the # socket's uid or gid the lookup succeeds. Anything else causes a failure. # # To give the caller full permissions to lookup all users, set the mode to # something else than 0666 and Dovecot lets the kernel enforce the # permissions (e.g. 0777 allows everyone full permissions). unix_listener auth-userdb { #mode = 0666 #user = #group = } # Postfix smtp-auth unix_listener /var/spool/postfix/private/auth { mode = 0600 user = postfix group = postfix } # Auth process is run as this user. #user = $default_internal_user } ---------------- Postfix is not involved in this right now as I expect the socket to be created when I restart dovecot. Can't find any meaningfull errors in the logs either. I hope I'm missing something obvious Thanks, Leo -- View this message in context: http://dovecot.2317879.n4.nabble.com/socket-var-spool-postfix-private-auth-… Sent from the Dovecot mailing list archive at Nabble.com.

6 14

[Dovecot] Copies of outgoing emails in the Sent folder
by Dmitry Podkovyrkin 26 May '14

26 May '14

Hi! My mail server works in tandem: Dovecot (IMAP) + Postfix. How can I configure in Gmail: Outgoing email copied to the Sent folder using postfix without mail client? This question is for the mailing list for Postfix? Mail client itself copies outgoing messages in the folder Sent, but the messages are large, and the server is far away. And to transmit email twice for sending and copying is not effective. Sorry for my English ). -- Regards Dmitry Podkovyrkin mobile: +7 922 20 56 756 email: dmirty(a)rutelecom.company skype: dmitryrw

6 15

[Dovecot] Multilayer mail handling
by Jimmy Thrasibule 26 May '14

26 May '14

Hi, I'm wondering what is the correct architecture and configuration to setup a multilayer mail handling? What I have in mind is something more like what we can found in Web platform architectures. 1. First layer does first checks: user authentication and SSL offloading. If all checks are OK request is proxied to layer 2. 2. Second layer, will actually handle the IMAP/POP3 connection proxied by layer 1, no major checks should be done as already made by layer 1. 3. Finally, layer 3 to do some virus checks on the emails and maybe some other things I can't think about. Do you have some pointers on how to set up such a mail stack where each layer can be on multiple other hosts? Best regards, Jimmy

1 0

[Dovecot] Index cache errors worse with 2.2.x
by Alexander 'Leo' Bergolth 25 May '14

25 May '14

Hi! I am getting "Cached message size smaller than expected" errors since dovecot-2.1.x. Until now, I thought that those errors don't do any harm, I assumed that the cache will just be rebuilt after the error had been detected. However, since dovecot 2.2.x (I tried 2.2.7 and 2.2.10), the errors sometimes seem to actually cause mail access to fail. With dovecot-2.1.1, only the first two messages were logged, since using 2.2.7 and 2.2.10, the "read ... failed: Invalid argument" sometimes appear: -------------------- 8< -------------------- May 7 17:03:52 samba dovecot: imap(xyz): Error: Cached message size smaller than expected (2246 < 2247) May 7 17:03:52 samba dovecot: imap(xyz): Error: Corrupted index cache file /home/xyz/mail/.imap/INBOX/dovecot.index.cache: Broken physical size for mail UID 11277 May 7 17:03:52 samba dovecot: imap(xyz): Error: read(/var/mail/xyz) failed: Invalid argument May 7 17:03:52 samba dovecot: imap(xyz): Error: read(/var/mail/xyz) failed: Invalid argument (uid=11277) -------------------- 8< -------------------- I am using dovecot on RHEL6 with mbox mailboxes. Message size differences are always 1 byte. Any hints would be appreciated! Cheers, --leo P.S.: Those errors occur some times a day and affect different users.. (Upgrade 2.1.1 -> 2.2.7 was on 2013-11-22, 2.2.10 was installed on 2014-01-20.) # for f in maillog* ; do echo -n "$f: "; grep "dovecot:.*Error: read.*failed.*Invalid arg" $f | wc -l; done maillog: 31 maillog-20130801: 0 maillog-20130901: 1 maillog-20131001: 0 maillog-20131101: 0 maillog-20131201: 30 maillog-20140101: 92 maillog-20140201: 110 maillog-20140301: 99 maillog-20140401: 133 maillog-20140501: 100 # for f in maillog* ; do echo -n "$f: "; grep "dovecot:.*Error: Cached message size smaller than expected" $f | wc -l; done maillog: 99 maillog-20130801: 465 maillog-20130901: 484 maillog-20131001: 512 maillog-20131101: 460 maillog-20131201: 520 maillog-20140101: 402 maillog-20140201: 400 maillog-20140301: 355 maillog-20140401: 481 maillog-20140501: 434 -- e-mail ::: Leo.Bergolth (at) wu.ac.at fax ::: +43-1-31336-906050 location ::: IT-Services | Vienna University of Economics | Austria

4 13

[Dovecot] Conditional jump or move depends on uninitialised value
by Daminto Lie 23 May '14

23 May '14

Hi, My Server runs on Ubuntu Server 12.04 LTS 32 bits. I'm getting the following error messages when I run "make check" during the compilation of dovecot-2.2.13. <snip> ==2058== Conditional jump or move depends on uninitialised value(s) ==2058== at 0x4049DD8: inflateReset2 (in /lib/i386-linux-gnu/libz.so.1.2.3.4) ==2058== by 0x4049EC7: inflateInit2_ (in /lib/i386-linux-gnu/libz.so.1.2.3.4) ==2058== by 0x804AFEF: i_stream_zlib_init (istream-zlib.c:320) ==2058== by 0x804B122: i_stream_create_zlib (istream-zlib.c:475) ==2058== by 0x804AA18: test_compression_handler (test-compression.c:72) ==2058== by 0xEFCDAB88: ??? ==2058== make[2]: *** [check-test] Error 1 make[2]: Leaving directory `/usr/src/dovecot-2.2.13/src/lib-compression' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/usr/src/dovecot-2.2.13/src' make: *** [check-recursive] Error 1 Any help would be greatly appreciated. Thank you

2 1

[Dovecot] dsync incredibly slow
by Alan McGinlay 23 May '14

23 May '14

Hi! While performing a dsync from cyrus imap to dovecot 2.2.12, dsync seems to stop for perhaps a minute without disk / cpu / memory activity (that I can see). This happens several times per sync per user so it takes an enormous amount of time to sync just a couple of gigs of mail. dsync -D -v -o mail_fsync=never mirror -f -R -u user(a)example.com imapc: What could possibly be the cause of this slowness? Is it protocol dependent or just dsync it's self? Thanks!

2 1

[Dovecot] Mail logger plugin, improvement request
by Gilles Chauvin 23 May '14

23 May '14

Hi Timo, Would it be possible for the mail logger plugin to also log the imap MOVE events (RFC6851) ? Thanks. Regards, Gilles.

1 0

[Dovecot] Dovecot ontop of glusterfs issue.
by Eliezer Croitoru 23 May '14

23 May '14

Hey, I am testing Glusterfs as a storage backend for dovecot as a LDA and imap server. I have seen similar lines in the logs to these: May 21 10:46:01 mailgw dovecot: imap(eliezer(a)ngtech.co.il): Warning: Created dotlock file's timestamp is different than current time (1400658105 vs 1400658361): /home/vmail/ngtech.co.il/eliezer/Maildir/.Mailing_lists.ceph_users/dovecot-uidlist May 21 10:46:01 mailgw dovecot: imap(eliezer(a)ngtech.co.il): Error: Transaction log /home/vmail/ngtech.co.il/eliezer/Maildir/dovecot.index.log: duplicate transaction log sequence (2713) The volume is mounted only by one server with ubutntu 14.04. I have seen threads and posts about similar issue with nfs. I want to try to debug the issue but note that with the same settings of the server nfs worked fine but slower. dovecot -n output: http://pastebin.centos.org/9626/ The glusterfs is a replicated volume constructed of two bricks which is mounted only on one dovecot server. All three servers are using the same ntp pool and are synced. Any direction is better then the state I am now. Thanks, Eliezer

4 6

[Dovecot] director with same director / backend servers
by Will Yardley 23 May '14

23 May '14

I know this has been covered somewhat, but I'm still not totally clear. I'm trying to setup a 3 node cluster with 3 directors and 3 backend systems. This post (from 2012) suggests that proxy_maybe should work with director: http://www.dovecot.org/list/dovecot/2012-December/069806.html However, these two posts (from 2013) seem to say that it will not: http://dovecot.org/pipermail/dovecot/2013-November/093776.html http://dovecot.org/pipermail/dovecot/2013-November/093809.html When I try to just set =proxy_maybe=y in my LDAP config's pass_attrs, and not have an explicit 'director' listener for pop3-login / imap-login, it complains about lack of a host. May 22 14:28:08 XXXX dovecot: pop3-login: Error: proxy: host not given: user=<XXXXXXX>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Guessing the answer is "no", but is there any way (with v 2.x) to have one regular "listener" for imap / pop3, and one "director" listener for each as well, using the same instance of Dovecot? Has anyone gotten this to work successfully? I'm using LDAP, and do not want to explicitly specify a host for each username, I just want director to balance users across the 3 hosts. Obviously, I can just create two instances, but not only does this make the config more convoluted (especially following the convention of having the config files broken out into a bunch of files), but means I have to modify the default init script to really do it cleanly (something we were doing on the older iteration of this system that I had really been hoping to avoid). I'm assuming it's not possible to simply have the listeners for 'foo-login' execute something different depending on the port? I tried a couple different ways of configuring this, but it didn't seem to work. Dovecot is version 2.0.9 from RHEL 6. w

1 0

[Dovecot] Dovecot pam
by Tommy Berglund 22 May '14

22 May '14

Hello! How can I disable passdb { driver = pam } in /etc/dovecot/conf.d/auth-system.conf.ext from file /etc/dovecot/local.conf. I have postfix and dovecot set up to only use virtual users. I'd rather do all the configuration in local.conf if possible. My doveconf-n # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.13.0-24-generic x86_64 Ubuntu 14.04 LTS auth_failure_delay = 5 secs auth_mechanisms = plain login cram-md5 listen = * log_timestamp = "%Y-%m-%d %H:%M:%S " mail_home = /var/vmail/%d/%n mail_location = mdbox:~/ 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 "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = scheme=cram-md5 /etc/dovecot/passwd driver = passwd-file } plugin { sieve = /vmail/%d/%n/.dovecot.sieve sieve_dir = /vmail/%d/%n/sieve sieve_global_path = /vmail/dovecot/sieve/default.sieve } protocols = imap lmtp sieve service auth { executable = /usr/lib/dovecot/auth unix_listener /var/spool/postfix/private/auth-client { group = postfix mode = 0660 user = postfix } user = root } service imap-login { inet_listener imaps { port = 993 ssl = yes } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } user = vmail } ssl_cert = </etc/dovecot/dovecot.pem ssl_key = </etc/dovecot/private/dovecot.pem userdb { driver = passwd } userdb { args = /etc/dovecot/users driver = passwd-file } protocol lmtp { mail_plugins = sieve postmaster_address = postmaster@localhost } Best regards

2 2

[Dovecot] When the subject portion of an e-mail contains a control character, dovecot.sieve terminates unexpectatedly.
by Atsuko Tanaka 22 May '14

22 May '14

Hello. We have currently set dovecot.sieve to insert the text "[SPAM]" at the beginning of an e-mail's subject when it's X-Spam-Score is above 80%. After we set our system as stated the following errors occur: 1) When an e-mail's subject contains control characters like [Ctrl+V|^V], dovecot.sieve terminates with an error and an e-mail is not able to be sent. When a MIME encoded Subject like [ＴＥＳＴ^VＭＡＩＬ] is sent we're not able to edit the subject and dovecot ends with an error. This is a sample of the data that was used in testing. Subject: =?ISO-2022-JP?B?GyRCI1QjRSNTI1QbKEIWGyRCI00jQSNJI0wbKEI=?= X-Spam-Score: 100.00% ↓ Subject: =?ISO-2022-JP?B?GyRCI1QjRSNTI1QbKEIWGyRCI00jQSNJI0wbKEI=?= X-Spam-Score: 100.00% This is the log generated by the data above. ---------------------------------------------------------------------- sieve: info: started log at May 02 10:46:22. main script: line 14: error: addheader action: specified value `[SPAM] ＴＥＳＴ?・・' is invalid. ---------------------------------------------------------------------- Aside from [Ctrl + V] the following control charcters also cause errors: backspace Ctrl + A Ctrl + C Ctrl + [ Ctrl + X Ctrl + Y 2) When an e-mail's subject line contains a "\0" character, everything following the null character is deleted. When a MIME encoded Subject is sent, for example "ＴＥＳＴ\0ＭＡＩＬ", the subject becomes "[SPAM]ＴＥＳＴ", the characters after the NULL character are deleted and dovecot.sieve ends normally. This is a sample of the data that we collected. Subject: =?ISO-2022-JP?B?GyRCI1QjRSNTI1QbKEIAGyRCI00jQSNJI0wbKEI=?= X-Spam-Score: 100.00% ↓ Subject: [SPAM] =?utf-8?b?77y077yl77yz77y0?= X-Spam-Score: 100.00% -Environment ・OS CentOS release 6.5 (Final) x86_64 ・Software Version dovecot-2.2.12 dovecot-2.2-pigeonhole-0.4.2 ・Results from the "dovecot -n" command. ---------------------------------------------------------------------- # 2.2.12: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-431.5.1.el6.x86_64 x86_64 CentOS release 6.5 (Final) disable_plaintext_auth = no lock_method = dotlock mail_fsync = always mail_gid = vmail mail_location = maildir:~/Maildir mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = quota mail_temp_dir = /var/tmp 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 ihave spamtest spamtestplus editheader mbox_write_locks = dotlock mmap_disable = yes passdb { driver = passwd } plugin { quota = maildir:User quota sieve = ~/Maildir/dovecot.sieve sieve_dir = ~/Maildir/sieve sieve_editheader_max_header_size = 1k sieve_editheader_protected = X-Verified sieve_extensions = +editheader +spamtest +spamtestplus sieve_max_actions = 250 sieve_max_redirects = 100 sieve_spamtest_max_value = 100.00 sieve_spamtest_status_header = X-Spam-Score: ([[:digit:]]+\.[[:digit:]]+)% sieve_spamtest_status_type = score sieve_user_log = /var/log/dovecot.sieve/%d/%u.log } postmaster_address = postmaster(a)example.jp protocols = pop3 imap service auth { unix_listener auth-userdb { group = vmail mode = 0600 user = vmail } } ssl_ca = </etc/pki/tls/certs/CA.crt ssl_cert = </etc/pki/tls/certs/example.jp.crt ssl_key = </etc/pki/tls/private/example.jp.key submission_host = 127.0.0.1:20025 userdb { args = /etc/dovecot/ldap/userdb.conf.ext driver = ldap } protocol lda { mail_plugins = quota sieve } protocol imap { mail_plugins = quota imap_quota passdb { args = /etc/dovecot/ldap/passdb.conf.ext driver = ldap } } protocol pop3 { passdb { args = /etc/dovecot/ldap/passdb.conf.ext driver = ldap } } ---------------------------------------------------------------------- -Contents of the "dovecot.sieve" file user/Maildir/dovecot.sieve ---------------------------------------------------------------------- require "fileinto"; require "mailbox"; require "envelope"; require "variables"; require "editheader"; require "spamtestplus"; require "relational"; require "enotify"; require "comparator-i;ascii-numeric"; if spamtest :percent :value "ge" :comparator "i;ascii-numeric" "80" { if exists "subject" { deleteheader :matches "subject" "*"; addheader "Subject" "[SPAM] ${1}"; } else { addheader "Subject" "[SPAM]"; } } ---------------------------------------------------------------------- Please reply. Thank you. -- ---------------------------------------- Atsuko Tanaka DesigNET Inc. e-mail：tanaka(a)designet.co.jp ----------------------------------------

4 5

[Dovecot] Sieve fileinto extension and redirect action
by FUSTE Emmanuel 21 May '14

21 May '14

Hello, Is there any way to limit the use of the "redirect" action (local user only or silent ignore) as provisioned by the RFC in the Pigeonhole implementation ? The only way I found for the moment is to completely disable the fileinto extension which hardly beat the users experience. "redirect" is forbidden by my organization policy. Regards, Emmanuel.

3 3

[Dovecot] LMTP hostname ignoring ENV variables
by G H 21 May '14

21 May '14

I am having an issue with LMTP appending the local hostname to received mail from Postfix. I either want to append localhost, a custom string, or nothing at all. Looking through the source code, I believe I should be able to set "export DOVECOT_HOSTNAME" and "export DOVECOT_HOSTDOMAIN" in my initscript to override the hostname set in lmtp/commands.c, client_get_added_headers() I'm using Centos 5; my hostname is mailtest1.atest.qq -- it is not defined in /etc/hosts. The added header is below: Received: from mail.mailorxyz.de by mailtest1.atest.qq (Dovecot) with LMTP id sreUK1+sfFOseQAAPYI4hw for <admin(a)mailorxyz.de>; Wed, 21 May 2014 13:39:03 +0000 Received: by mail.mailorxyz.de (Postfix, from userid 97) id CC743116AB5; Wed, 21 May 2014 13:39:03 +0000 (UTC) I have the following defined in /etc/init.d/dovecot: export DOVECOT_HOSTDOMAIN=dovecot.mailorxyz.de export DOVECOT_HOSTNAME=dovecot.mailorxyz.de Am I missing something or did I misunderstand the source code? Thanks.

2 1

Re: [Dovecot] Per-user Sieve script location question
by Selcuk Yazar 21 May '14

21 May '14

Hi Again, we have one domain, i suppose we don't have any problem with %n parameter. our mail server has mapped LUN Storage disk , we have some empty space problems, so i think it's better keep user things in storage for backup etc. we have totally 40K users(most of students) but i think at most 50 of them use this filter, autorespond etc. :) thank you for your reply. Selçuk On Wed, May 21, 2014 at 3:15 PM, Steffen Kaiser < skdovecot(a)smail.inf.fh-brs.de> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Wed, 21 May 2014, Selcuk Yazar wrote: > > Hi Selcuk, > > > i changed my 90-sieve.conf >> >> to >> >> sieve = /var/sieve-scripts/%u.sieve >> sieve_dir = /home/vmail/domains/sieve/%n/.sieve >> > > Yeah, looks good. However, do you host multiple domains? In your config > you differ domains: > > mail_location = mbox:/home/vmail/domains/%d/%u > > with sieve = /var/sieve-scripts/%u.sieve , too, but > with sieve_dir = /home/vmail/domains/sieve/%n/.sieve you do not. > > http://wiki2.dovecot.org/Variables > %u user full username (e.g. user@domain) > %n username user part in user@domain, same as %u if there's no domain > %d domain domain part in user@domain, empty if user with no domain > > I suppose, you should use: > > sieve_dir = /home/vmail/domains/sieve/%u/.sieve > > otherwise info(a)example.org and info@localhost share the same Sieve dir. > > BTW: Because you have an unique directory per user now anyway, why not use > is that as home directory? I'm not sure, what other things use the home > for. E.g. use > > mail_home = /home/vmail/domains/home/%d/%u > > and keep the home-relative paths for Sieve: ~/... > > > On Wed, May 21, 2014 at 12:10 PM, Steffen Kaiser < >> skdovecot(a)smail.inf.fh-brs.de> wrote: >> >> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> On Wed, 21 May 2014, Selcuk Yazar wrote: >>> >>> my dovecot conf is >>> >>>> >>>> doveconf -n >>>> # 2.0.9: /etc/dovecot/dovecot.conf >>>> >>>> [...] >>> >>> mail_location = mbox:/home/vmail/domains/%d/%u >>>> >>>> [...] >>> >>> userdb { >>>> args = /etc/dovecot/conf.d/dovecot-ldap.conf.ext >>>> driver = ldap >>>> } >>>> >>>> you're right we have mail_location , >>>> >>>> should i add mail_home value >>>> >>>> >>> That depends on if your LDAP configuration contains a (for the mailserver >>> usable) home for the individual user. >>> >>> mail_home = /home/vmail/domains/%d/%u >>> >>>> >>>> >>> The value shows that you did not followed my advice from the last >>> response: "Read the link above about why not store Sieve files below an >>> user's mail location." maybe because you missed it because you toppost. >>> >>> to 10-mail.conf file ? >>> >>>> >>>> >>> never use the same dir for mail location and user's home. >>> >>> >>> On Wed, May 21, 2014 at 11:43 AM, Steffen Kaiser < >>> >>>> skdovecot(a)smail.inf.fh-brs.de> wrote: >>>> >>>> -----BEGIN PGP SIGNED MESSAGE----- >>>> >>>>> >>>>> >>>> On Wed, 21 May 2014, Selcuk Yazar wrote: >>> >>>> >>>>> our users stored OpenLdap and users home folder like below: >>>>> >>>>> >>>>>> >>>>>> without seeing your current doveconf -n output and the ldap >>>>> configuration >>>>> file, I would guess that your users have no home directory: >>>>> http://wiki2.dovecot.org/VirtualUsers/Home >>>>> >>>>> >>>>> >>>>> /home/vmail/domains/domainname.edu.tr/username/... >>>>> >>>>>> >>>>>> now when i used default settings for dovecot sieve >>>>>> >>>>>> sieve = ~/.dovecot.sieve >>>>>> sieve_dir = ~/sieve >>>>>> >>>>>> sieve script write and work globaly and stored, >>>>>> /home/vmail/domains/sieve >>>>>> >>>>>> i looked up Dovecot docs for per user but i don't understand clearly >>>>>> >>>>>> can i replace sieve parameters like >>>>>> >>>>>> sieve = /home/vmail/domains/..................edu.tr/%n/.dovecot. >>>>>> sieve >>>>>> sieve_dir = /home/vmail/domains/.........................edu.tr/%n/. >>>>>> sieve >>>>>> >>>>>> for per user scirpt. >>>>>> >>>>>> >>>>>> Read the link above about why not store Sieve files below an user's >>>>> mail >>>>> location. >>>>> >>>>> >>>> - -- Steffen Kaiser >>> -----BEGIN PGP SIGNATURE----- >>> Version: GnuPG v1.4.11 (GNU/Linux) >>> >>> iQEVAwUBU3xtn3z1H7kL/d9rAQIu1wf/XMXuEC1O1PQssoU1uHfTM5jOHpH1KHis >>> yUL1z2/WV8c7engx+CNtGPxnRewC1UFKBZcHaAyXHNxQM+jsYf+NkUo4PDlKkzfi >>> /JIn+SGOlwZKJUYarnAJbt0CdZG7f8auvMLsoovR8iNitSAdyH5AkRt9i25YFndW >>> Nm0lYO1CPJzKp3CVhDS0Lxs6sSD21xsMvuauzMmS4ZpYhXXEdOf4jqNkIYdJbSHz >>> nBHx8sjlJaKNKO3OWs1S5T7DxlRz+VYGw1IZ1BUgpBBD3LxDIOwTLG7NNjWRG2lB >>> nTB+WK02fvh0T+oJORVuKmgoXG5WKvZjFOa4oVqdbbzM6V4ZJSx9Sw== >>> =bLQp >>> -----END PGP SIGNATURE----- >>> >>> >> >> >> >> > - -- Steffen Kaiser > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > > iQEVAwUBU3yY9Hz1H7kL/d9rAQIIpwf/bfNNbI3zCEuJs3xYq5Nl+Td2QGX0uUzk > 8PA4taMNrq00W3jBtTi8J4/ZlqT+l15r5nDr6O/VSgffymi9l0JmRMRIfUyzfjBy > IThSQTrbjx9t+gCJa15Q2JISYEhXC0WYDpseEZle5vFyIKxWT01FYH5cJe45n9ci > LcY3QmCdrQ4JYuYPiECfOx5rFw7dvZBnS4YDLg/A/O3dUzx7BV6V+cSepAecpoom > 4U5udqoWRF1pDgKywn0elB0WorEbgnyOHLSrd5uPOuQuP9aW2bcWJGSpr1/j5tQk > tOYd/czhNhpPEKbzH/MJyn6mbhu4F3DGMAfuD9tweIAD25A41HgVpQ== > =6w4r > -----END PGP SIGNATURE----- > -- Selçuk YAZAR http://www.selcukyazar.blogspot.com

1 0

Re: [Dovecot] Per-user Sieve script location question
by Selcuk Yazar 21 May '14

21 May '14

Hi, Steffen i changed my 90-sieve.conf to sieve = /var/sieve-scripts/%u.sieve sieve_dir = /home/vmail/domains/sieve/%n/.sieve and it works. thank you. On Wed, May 21, 2014 at 12:10 PM, Steffen Kaiser < skdovecot(a)smail.inf.fh-brs.de> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Wed, 21 May 2014, Selcuk Yazar wrote: > > my dovecot conf is >> >> doveconf -n >> # 2.0.9: /etc/dovecot/dovecot.conf >> > [...] > >> mail_location = mbox:/home/vmail/domains/%d/%u >> > [...] > >> userdb { >> args = /etc/dovecot/conf.d/dovecot-ldap.conf.ext >> driver = ldap >> } >> >> you're right we have mail_location , >> >> should i add mail_home value >> > > That depends on if your LDAP configuration contains a (for the mailserver > usable) home for the individual user. > > mail_home = /home/vmail/domains/%d/%u >> > > The value shows that you did not followed my advice from the last > response: "Read the link above about why not store Sieve files below an > user's mail location." maybe because you missed it because you toppost. > > to 10-mail.conf file ? >> > > never use the same dir for mail location and user's home. > > > On Wed, May 21, 2014 at 11:43 AM, Steffen Kaiser < >> skdovecot(a)smail.inf.fh-brs.de> wrote: >> >> -----BEGIN PGP SIGNED MESSAGE----- >>> >> > On Wed, 21 May 2014, Selcuk Yazar wrote: >>> >>> our users stored OpenLdap and users home folder like below: >>> >>>> >>>> >>> without seeing your current doveconf -n output and the ldap configuration >>> file, I would guess that your users have no home directory: >>> http://wiki2.dovecot.org/VirtualUsers/Home >>> >>> >>> >>> /home/vmail/domains/domainname.edu.tr/username/... >>>> >>>> now when i used default settings for dovecot sieve >>>> >>>> sieve = ~/.dovecot.sieve >>>> sieve_dir = ~/sieve >>>> >>>> sieve script write and work globaly and stored, >>>> /home/vmail/domains/sieve >>>> >>>> i looked up Dovecot docs for per user but i don't understand clearly >>>> >>>> can i replace sieve parameters like >>>> >>>> sieve = /home/vmail/domains/..................edu.tr/%n/.dovecot.sieve >>>> sieve_dir = /home/vmail/domains/.........................edu.tr/%n/. >>>> sieve >>>> >>>> for per user scirpt. >>>> >>>> >>> Read the link above about why not store Sieve files below an user's mail >>> location. >>> >> > - -- Steffen Kaiser > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > > iQEVAwUBU3xtn3z1H7kL/d9rAQIu1wf/XMXuEC1O1PQssoU1uHfTM5jOHpH1KHis > yUL1z2/WV8c7engx+CNtGPxnRewC1UFKBZcHaAyXHNxQM+jsYf+NkUo4PDlKkzfi > /JIn+SGOlwZKJUYarnAJbt0CdZG7f8auvMLsoovR8iNitSAdyH5AkRt9i25YFndW > Nm0lYO1CPJzKp3CVhDS0Lxs6sSD21xsMvuauzMmS4ZpYhXXEdOf4jqNkIYdJbSHz > nBHx8sjlJaKNKO3OWs1S5T7DxlRz+VYGw1IZ1BUgpBBD3LxDIOwTLG7NNjWRG2lB > nTB+WK02fvh0T+oJORVuKmgoXG5WKvZjFOa4oVqdbbzM6V4ZJSx9Sw== > =bLQp > -----END PGP SIGNATURE----- > -- Selçuk YAZAR http://www.selcukyazar.blogspot.com

2 1

[Dovecot] dovecot auth ldap attributes - unused?
by Maciej Uhlig 21 May '14

21 May '14

Please explain the following dovecot (2.2.13) behaviour: I run dovecot in ldap auth debug mode and log file excerpt follows: 2014-05-21T08:22:01+02:00 dovecot/ip dovecot: auth: Debug: ldap(user@domain,pcip,<bdKvA+P5HQCbnmFI>): bind search: base=o=tree,dc=do,dc=ma,dc=in filter=(&(objectClass=MailAccount)(accountActive=TRUE)(mail=user@domain)) 2014-05-21T08:22:01+02:00 dovecot/ip dovecot: auth: Debug: ldap(user@domain,pcip,<bdKvA+P5HQCbnmFI>): result: mail=user@domain; mail unused 2014-05-21T08:22:01+02:00 dovecot/ip dovecot: auth: Debug: ldap(user@domain,pcip,<bdKvA+P5HQCbnmFI>): result: mail=user@domain 2014-05-21T08:22:01+02:00 dovecot/ip dovecot: auth: Debug: client passdb out: OK 24 user=user@domain 2014-05-21T08:22:01+02:00 dovecot/ip dovecot: auth: Debug: ldap(user@domain,pcip,<bdKvA+P5HQCbnmFI>): user search: base=o=tree,dc=do,dc=ma,dc=in scope=subtree filter=(&(objectClass=MailAccount)(accountActive=TRUE)(mail=user@domain)) fields=mail,quota,mailbox 2014-05-21T08:22:01+02:00 dovecot/ip dovecot: auth: Debug: ldap(user@domain,pcip,<bdKvA+P5HQCbnmFI>): result: mailbox=maildir:/mail/domain/user/mail/ quota=1G mail=user@domain; mail,mailbox,quota unused 2014-05-21T08:22:01+02:00 dovecot/ip dovecot: auth: Debug: ldap(user@domain,pcip,<bdKvA+P5HQCbnmFI>): result: mailbox=maildir:/mail/domain/user/mail/ quota=1G mail=user@domain 2014-05-21T08:22:01+02:00 dovecot/ip dovecot: auth: Debug: master userdb out: USER 3606315009 user@domain quota_rule=*:bytes=1G mail=maildir:/mail/domain/user/mail/ home=/mail/domain/user Question: why are there two ldap result log lines while the first line shows unused attributes and the second doesn't. Does the first occurence show some code being excessive somehow? Thanks. MU

2 1

[Dovecot] allow_nets + default + ldap
by Andreas Schulze 21 May '14

21 May '14

Hello, I'm playing with allow_nets function. It is really cool! In a filebased passwd backend you simply add "allow_nets=192.0.2.143/32" as mentioned in http://wiki2.dovecot.org/PasswordDatabase/ExtraFields/AllowNets But if I use an LDAP backend it looks different. Following http://wiki2.dovecot.org/AuthDatabase/LDAP/AuthBinds and http://wiki2.dovecot.org/AuthDatabase/LDAP/Userdb#Attribute_templates_.28v2… my pass_attrs looks this: pass_attrs = =user=%{ldap:uid}, \ =allow_nets=%{ldap:allownets} Using this syntax I could add an attribute "allownets" in the ldapserver to limit access for a user. A problem occour if the attribute is not present. For example if a user should not be limited or only some but not any user should be limited. So I extend my pass_attrs with a default. pass_attrs = =user=%{ldap:uid}, \ =allow_nets=%{ldap:allownets:10.0.0.0/8} Again, that's fine. Any user was allowed to connect from my private network. But then some users connect via ipv6. I tried to extend my default to pass_attrs = =user=%{ldap:uid}, \ =allow_nets=%{ldap:allownets:10.0.0.0/8,fec0::/16} That syntax, a comma separated list, produces errors no matter if quoting using " or ' or no quoting at all. So I looked at the source (thanks, it's open!) and wrote a little patch to allow simple defaults: - ALL -> allow any address - NONE -> deny any address Now I could write pass_attrs = =user=%{ldap:uid}, =allow_nets=%{ldap:allownets:ALL} or pass_attrs = =user=%{ldap:uid}, =allow_nets=%{ldap:allownets:NONE} to allow or deny any ldap account not having an attribute allownets. Maybe there are other solutions, but that's my way... Andreas

2 3

Re: [Dovecot] Per-user Sieve script location question
by Selcuk Yazar 21 May '14

21 May '14

Hi my dovecot conf is doveconf -n # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-131.6.1.el6.x86_64 x86_64 Red Hat Enterprise Linux Server release 6.0 (Santiago) ext4 auth_debug = yes auth_debug_passwords = yes auth_default_realm = hostname.domainname.edu.tr auth_mechanisms = plain login auth_verbose = yes debug_log_path = /var/log/dovecot.debug disable_plaintext_auth = no first_valid_uid = 97 info_log_path = /var/log/dovecot.info last_valid_uid = 5000 mail_debug = yes mail_gid = 1001 mail_location = mbox:/home/vmail/domains/%d/%u mail_uid = 1001 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 mbox_write_locks = fcntl passdb { args = /etc/dovecot/conf.d/dovecot-ldap.conf.ext driver = ldap } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap pop3 lmtp sieve service auth { unix_listener auth-userdb { mode = 0600 user = vmail } } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } ssl = no ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { args = /etc/dovecot/conf.d/dovecot-ldap.conf.ext driver = ldap } protocol lda { debug_log_path = /var/log/dovecot-lda-errors.log info_log_path = /var/log/dovecot-lda.log log_path = /var/log/dovecot-lda-errors.log mail_plugins = " sieve" } you're right we have mail_location , should i add mail_home value mail_home = /home/vmail/domains/%d/%u to 10-mail.conf file ? thanks. On Wed, May 21, 2014 at 11:43 AM, Steffen Kaiser < skdovecot(a)smail.inf.fh-brs.de> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > On Wed, 21 May 2014, Selcuk Yazar wrote: > > our users stored OpenLdap and users home folder like below: >> > > without seeing your current doveconf -n output and the ldap configuration > file, I would guess that your users have no home directory: > http://wiki2.dovecot.org/VirtualUsers/Home > > > >> /home/vmail/domains/domainname.edu.tr/username/... >> >> now when i used default settings for dovecot sieve >> >> sieve = ~/.dovecot.sieve >> sieve_dir = ~/sieve >> >> sieve script write and work globaly and stored, /home/vmail/domains/sieve >> >> i looked up Dovecot docs for per user but i don't understand clearly >> >> can i replace sieve parameters like >> >> sieve = /home/vmail/domains/..................edu.tr/%n/.dovecot.sieve >> sieve_dir = /home/vmail/domains/.........................edu.tr/%n/.sieve >> >> for per user scirpt. >> > > Read the link above about why not store Sieve files below an user's mail > location. > > - -- Steffen Kaiser > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > > iQEVAwUBU3xnMHz1H7kL/d9rAQIiRAgAmZYxZo1fn/5Iw0WHB2v3FpF1snq1VH4t > tvyhS/ISj3snMB7dbViUkjvYhzaIsWQKP9eXM3YtOmwpSdlwozqwq/5PvckQgAkU > cI8UIyXCErsdsvp7/aod/n+Qd+tnjf91b3PY9R7xYd6Qjf/8H7lSmX/xBMBltu7N > AVqwgHTivR9dwsDyTkIqQIfULWvwcWf5eXbKzP1YxamYzF+lMk6ippK7RebMrspe > CTg1BLCCLiHMTdSQrOrnfmNjgS/rAZctOEyc3/M98U8HxmEhT6ZFpTjQ4i0T0/17 > +9DQovMUi2/bZ1IhgBpS9u+YkPeuu+y4vAhMqCAT+fcEW1+MgfK2Lg== > =Sc/m > -----END PGP SIGNATURE----- > -- Selçuk YAZAR http://www.selcukyazar.blogspot.com

2 1

[Dovecot] Per-user Sieve script location question
by Selcuk Yazar 21 May '14

21 May '14

Hi, after some problems, i successfuly ran my dovecot delivery and pigeonhole service in redhat EL 6. our users stored OpenLdap and users home folder like below: /home/vmail/domains/domainname.edu.tr/username/... now when i used default settings for dovecot sieve sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve script write and work globaly and stored, /home/vmail/domains/sieve i looked up Dovecot docs for per user but i don't understand clearly can i replace sieve parameters like sieve = /home/vmail/domains/..................edu.tr/%n/.dovecot.sieve sieve_dir = /home/vmail/domains/.........................edu.tr/%n/.sieve for per user scirpt. thanks in advance. -- Selçuk YAZAR

2 1

[Dovecot] Setting mail location in SQL?
by Marc Perkel 21 May '14

21 May '14

Trying to figure out the syntax to set a mail_location for SQL. This doesn't work: userdb { driver = sql args = /etc/dovecot/master-combined-sql.conf override_fields = mail_location=maildir:/fakedir/%d/%n:INBOX=/fakedir:LAYOUT=fs } Does anyone know the proper syntax? Thanks in advance

2 3

[Dovecot] Dict SQL lookups without username_field
by Andrew Beverley 20 May '14

20 May '14

Dear all, Is it possible to perform dict lookups with a SQL backend, without specifying the username_field in the SQL query? I am using the dict to retrieve a Sieve script. My dict configuration looks like this: map { pattern = priv/sieve/data/$id table = sieve_scripts username_field = email value_field = data fields { id = $id } } I don't want to specify the username though, as the sieve scripts are valid for all users. However, when I remove "username_field" I get the error "data with id `1' for script `main script' not found at path priv/sieve/data/1" Thanks, Andy

1 0

[Dovecot] Performing an action on mail receipt
by Andrew Beverley 20 May '14

20 May '14

Dear all, I would like to perform an action for certain users each time a mail arrives via LMTP. I would like to send an email notification to an external email address when new mail has arrived for certain users (note: not a forward). I am assuming that creating my own plugin using the existing "notify" plugin is the way to go. However, before I go down that route, I'd like to check that is the best approach? Or would it be better to perform this sort of thing before the mail reaches Dovecot? Assuming writing a plugin is answer, do they have to be written in C? Dovecot version: 2.1.7 Thanks, Andy

4 6

[Dovecot] Solr/Tika
by Alex Crow 20 May '14

20 May '14

|Hi list, If I've added the tika stuff to my tomcat/solr setup, ie copied: | ||solr-4.7.2/dist/solr-cell-*| solr-4.7.2/contrib/extraction/lib/* to ||/var/lib/tomcat6/webapps/solr/WEB-INF/lib/ how do I get dovecot to index attachments? Do I just need to add| fts-solr =/index-attachments url=http://localhost:8080/solr-4.7.2/ /to the 90-plugin.conf? Or do I need to so something like fts_tika =/http://localhost:8080/solr-4.7.2// IE the same uri I have for the solr? Thanks Alex

1 0

[Dovecot] Notifications from dovecot
by Joakim Seeberg 20 May '14

20 May '14

Hi list, im trying to build a web based system for secure communication build with standard linux software, instead of using CMS based systems. One of the requirements is to send notifications to users when receiving mail. Can a script find information about the mail address of received mails in dovecot logs or is there a better way. -seeberg

4 4

[Dovecot] Dovecot 2.2.13+ and master user db
by Juan C. Blanco 20 May '14

20 May '14

Hello, I'm upgrading one of our servers to the last HG 2.2.13 versión and I've found some problems with our configuration which has been working fine with previous versions. We have a LDAP userdb for the users and a master userdb for user assistance, Until now the definition of usersdb in 10-auth.conf was: !include auth-master.conf.ext !include auth-system.conf.ext !include auth-ldap.conf.ext With the 2.2.12 version this worked fine but with 2.2.13+ version the LDAP users can't login in dovecot (IMAP), however the master users can login fine. However, if I comment out the master userdb or change the order, i.e. !include auth-system.conf.ext !include auth-ldap.conf.ext !include auth-master.conf.ext In this case LDAP and master users can login normally. Is this configuration change required for the new version or it's a bug? Follows the log sections for both configurations Regards Juan C. Blanco There is the log for the first case (master before ldap) with debugging activated: May 20 08:57:43 master: Info: Dovecot v2.2.13 starting up for imap, pop3, lmtp, sieve (core dumps disabled) May 20 08:57:51 auth: Debug: Loading modules from directory: /usr/lib64/dovecot/auth May 20 08:57:51 auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_mysql.so May 20 08:57:51 auth: Debug: Loading modules from directory: /usr/lib64/dovecot/auth May 20 08:57:51 auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libauthdb_ldap.so May 20 08:57:51 auth: Debug: Read auth token secret from /var/run/dovecot/auth-token-secret.dat May 20 08:57:51 auth: Debug: passwd-file /nas/mail/etc/passwd.master: Read 1 users in 0 secs May 20 08:57:51 auth: Debug: auth client connected (pid=22482) May 20 08:57:56 auth: Debug: client in: AUTH 1 PLAIN service=imap secured session=T/5QZs/54gB/AAAB lip=127.0.0.1 rip=127.0.0.1 lport=143 rport=56290 resp=<hidden> May 20 08:57:56 auth: Debug: ldap(user1,127.0.0.1,<T/5QZs/54gB/AAAB>): cache miss May 20 08:57:56 auth: Debug: ldap(user1,127.0.0.1,<T/5QZs/54gB/AAAB>): bind search: base=dc=some,dc=domain,dc=es filter=(uid=user1) May 20 08:57:56 auth: Debug: ldap(user1,127.0.0.1,<T/5QZs/54gB/AAAB>): result: Mailbox=/mail/user1 MailQuotaSize=10240; Mailbox,MailQuotaSize unused May 20 08:57:56 auth: Debug: ldap(user1,127.0.0.1,<T/5QZs/54gB/AAAB>): result: Mailbox=/mail/user1 MailQuotaSize=10240 May 20 08:57:56 auth: Debug: client passdb out: OK 1 user=user1 May 20 08:57:56 auth: Debug: master in: REQUEST 4005167105 22482 1 f14d67dfcbfd5fdffe206fba32ef320b session_pid=22485 request_auth_token May 20 08:57:56 auth: Debug: passwd-file(user1,127.0.0.1,<T/5QZs/54gB/AAAB>): userdb cache miss May 20 08:57:56 auth: Debug: passwd-file(user1,127.0.0.1,<T/5QZs/54gB/AAAB>): lookup: user=user1 file=/nas/mail/etc/passwd.master May 20 08:57:56 auth: Info: passwd-file(user1,127.0.0.1,<T/5QZs/54gB/AAAB>): unknown user May 20 08:57:56 auth: Debug: prefetch(user1,127.0.0.1,<T/5QZs/54gB/AAAB>): success May 20 08:57:56 auth: Debug: master userdb out: USER 4005167105 user1 auth_token=51719362e64e34996d44dfbde00993c989be6580 May 20 08:57:56 imap-login: Info: Login: user=<user1>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=22485, secured, session=<T/5QZs/54gB/AAAB> May 20 08:57:56 imap: Debug: Loading modules from directory: /usr/lib64/dovecot May 20 08:57:56 imap: Debug: Module loaded: /usr/lib64/dovecot/lib01_acl_plugin.so May 20 08:57:56 imap: Debug: Module loaded: /usr/lib64/dovecot/lib02_imap_acl_plugin.so May 20 08:57:56 imap: Debug: Module loaded: /usr/lib64/dovecot/lib10_quota_plugin.so May 20 08:57:56 imap: Debug: Module loaded: /usr/lib64/dovecot/lib11_imap_quota_plugin.so May 20 08:57:56 imap: Debug: Added userdb setting: plugin/=yes May 20 08:57:56 imap(user1): Debug: Effective uid=98, gid=12, home= May 20 08:57:56 imap(user1): Debug: Quota root: name=User quota backend=maildir args= May 20 08:57:56 imap(user1): Debug: Quota rule: root=User quota mailbox=* bytes=10485760 messages=0 May 20 08:57:56 imap(user1): Debug: Quota rule: root=User quota mailbox=Trash bytes=+1048576 (10%) messages=0 May 20 08:57:56 imap(user1): Debug: Quota warning: bytes=9961472 (95%) messages=0 reverse=no command=quota-warning 95 user1 May 20 08:57:56 imap(user1): Debug: Quota warning: bytes=8388608 (80%) messages=0 reverse=no command=quota-warning 80 user1 May 20 08:57:56 imap(user1): Debug: Quota grace: root=User quota bytes=1048576 (10%) May 20 08:57:56 imap(user1): Debug: Namespace inbox: type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/Maildir May 20 08:57:56 imap(user1): Error: user user1: Initialization failed: Namespace '': Home directory not set for user. Can't expand ~/ for mail root dir in: ~/Maildir May 20 08:57:56 imap(user1): Error: Invalid user settings. Refer to server log for more information. Log for second case (master after LDAP) May 20 09:06:38 master: Info: Dovecot v2.2.13 starting up for imap, pop3, lmtp, sieve (core dumps disabled) May 20 09:06:43 auth: Debug: Loading modules from directory: /usr/lib64/dovecot/auth May 20 09:06:43 auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_mysql.so May 20 09:06:43 auth: Debug: Loading modules from directory: /usr/lib64/dovecot/auth May 20 09:06:43 auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libauthdb_ldap.so May 20 09:06:43 auth: Debug: Read auth token secret from /var/run/dovecot/auth-token-secret.dat May 20 09:06:43 auth: Debug: passwd-file /nas/mail/etc/passwd.master: Read 1 users in 0 secs May 20 09:06:43 auth: Debug: auth client connected (pid=22533) May 20 09:06:50 auth: Debug: client in: AUTH 1 PLAIN service=imap secured session=RRYchs/55AB/AAAB lip=127.0.0.1 rip=127.0.0.1 lport=143 rport=56292 resp=<hidden> May 20 09:06:50 auth: Debug: ldap(user1,127.0.0.1,<RRYchs/55AB/AAAB>): cache miss May 20 09:06:50 auth: Debug: ldap(user1,127.0.0.1,<RRYchs/55AB/AAAB>): bind search: base=dc=some,dc=domain,dc=es filter=(uid=user1) May 20 09:06:50 auth: Debug: ldap(user1,127.0.0.1,<RRYchs/55AB/AAAB>): result: Mailbox=/mail/user1 MailQuotaSize=10240; Mailbox,MailQuotaSize unused May 20 09:06:50 auth: Debug: ldap(user1,127.0.0.1,<RRYchs/55AB/AAAB>): result: Mailbox=/mail/user1 MailQuotaSize=10240 May 20 09:06:50 auth: Debug: client passdb out: OK 1 user=user1 May 20 09:06:50 auth: Debug: master in: REQUEST 899284993 22533 1 5497b866fa520f52f65b72b700b3e460 session_pid=22535 request_auth_token May 20 09:06:50 auth: Debug: prefetch(user1,127.0.0.1,<RRYchs/55AB/AAAB>): success May 20 09:06:50 auth: Debug: master userdb out: USER 899284993 user1 home=/mail/user1 quota_rule=*:storage=10240 acl_groups=ccmail auth_token=672454c1a2671c22f334923aa11916aab58ed954 May 20 09:06:50 imap-login: Info: Login: user=<user1>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=22535, secured, session=<RRYchs/55AB/AAAB> May 20 09:06:50 imap: Debug: Loading modules from directory: /usr/lib64/dovecot May 20 09:06:50 imap: Debug: Module loaded: /usr/lib64/dovecot/lib01_acl_plugin.so May 20 09:06:50 imap: Debug: Module loaded: /usr/lib64/dovecot/lib02_imap_acl_plugin.so May 20 09:06:50 imap: Debug: Module loaded: /usr/lib64/dovecot/lib10_quota_plugin.so May 20 09:06:50 imap: Debug: Module loaded: /usr/lib64/dovecot/lib11_imap_quota_plugin.so May 20 09:06:50 imap: Debug: Added userdb setting: plugin/acl_groups=ccmail May 20 09:06:50 imap: Debug: Added userdb setting: plugin/quota_rule=*:storage=10240 May 20 09:06:50 imap(user1): Debug: Effective uid=98, gid=12, home=/mail/user1 May 20 09:06:50 imap(user1): Debug: Quota root: name=User quota backend=maildir args= May 20 09:06:50 imap(user1): Debug: Quota rule: root=User quota mailbox=* bytes=10485760 messages=0 May 20 09:06:50 imap(user1): Debug: Quota rule: root=User quota mailbox=Trash bytes=+1048576 (10%) messages=0 May 20 09:06:50 imap(user1): Debug: Quota warning: bytes=9961472 (95%) messages=0 reverse=no command=quota-warning 95 user1 May 20 09:06:50 imap(user1): Debug: Quota warning: bytes=8388608 (80%) messages=0 reverse=no command=quota-warning 80 user1 May 20 09:06:50 imap(user1): Debug: Quota grace: root=User quota bytes=1048576 (10%) May 20 09:06:50 imap(user1): Debug: Namespace inbox: type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/Maildir May 20 09:06:50 imap(user1): Debug: maildir++: root=/mail/user1/Maildir, index=, indexpvt=, control=, inbox=/mail/user1/Maildir, alt= May 20 09:06:50 imap(user1): Debug: acl: initializing backend with data: vfile May 20 09:06:50 imap(user1): Debug: acl: acl username = user1 May 20 09:06:50 imap(user1): Debug: acl: owner = 1 May 20 09:06:50 imap(user1): Debug: acl vfile: Global ACLs disabled May 20 09:06:50 imap(user1): Debug: Namespace : type=shared, prefix=shared/%u/, sep=/, inbox=no, hidden=no, list=children, subscriptions=no location=maildir:%h/Maildir:INDEX=~/Maildir/shared/%u May 20 09:06:50 imap(user1): Debug: shared: root=/var/run/dovecot, index=, indexpvt=, control=, inbox=, alt= May 20 09:06:50 imap(user1): Debug: acl: initializing backend with data: vfile May 20 09:06:50 imap(user1): Debug: acl: acl username = user1 May 20 09:06:50 imap(user1): Debug: acl: owner = 0 May 20 09:06:50 imap(user1): Debug: acl vfile: Global ACLs disabled May 20 09:06:53 imap(user1): Info: Disconnected: Logged out in=8 out=417 -- +----------------------------------------------------------------+ | Juan C. Blanco | | | | Centro de Calculo | | | Facultad de Informatica U.P.M. | E-mail: jcblanco(a)fi.upm.es | | Campus de Montegancedo | | | Boadilla del Monte | Tel.: (+34) 91 336 7466 | | 28660 MADRID (Spain) | Fax : (+34) 91 336 6913 | +----------------------------------------------------------------+

1 0

[Dovecot] / vs. </
by Boris 19 May '14

19 May '14

The default configuration file for Dovecot in Debian uses: ssl_cert = </path/to/cert I checked my current configuration and I use: ssl_cert =/path/to/cert What is the difference? (pipe?) And is the former better somehow?

3 6

[Dovecot] imapc Proxy to IMAPS Exchangeserver?
by Ralf Hildebrandt 19 May '14

19 May '14

I'm trying to adapt http://wiki2.dovecot.org/HowTo/ImapcProxy to our Exchange Server, which has LOGINDISABLED on Port 143, and I offering LOGIN on Port 993. How do I go about this? Simply changing imapc_port to: imapc_port = 993 doesnt work: Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot (Ubuntu) ready. . LOGIN hildeb password . NO [UNAVAILABLE] Temporary authentication failure. [mproxy:2014-05-16 09:33:23] . LOGOUT * BYE Logging out . OK Logout completed. Connection closed by foreign host. Logs: May 16 11:33:04 mproxy dovecot: master: Dovecot v2.2.9 starting up (core dumps disabled) May 16 11:33:21 mproxy dovecot: auth: Error: imapc(exchange-imap.charite.de:143): Command '2 LOGIN "hildeb" "password"' failed with BAD: 2 Command received in Invalid state. May 16 11:33:21 mproxy dovecot: auth: Error: imap(hildeb,::1,<bjeUGoH53AAAAAAAAAAAAAAAAAAAAAAB>): Disconnected from server May 16 11:33:21 mproxy dovecot: auth: Error: imapc(exchange-imap.charite.de:143): Authentication failed: Command received in Invalid state. May 16 11:33:26 mproxy dovecot: imap-login: Aborted login (auth failed, 1 attempts in 8 secs): user=<hildeb>, method=PLAIN, rip=::1, lip=::1, secured, session=<bjeUGoH53AAAAAAAAAAAAAAAAAAAAAAB> But why is it still using port 143? -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de

3 5

[Dovecot] logging of failed SASL usernames
by Reindl Harald 19 May '14

19 May '14

as far as i understand postfix has no way to know the username of such failed logins like below, IMHO dovecot internally does because it verifies against the sql-userdatabase is there a way that dovecot logs the username? after ask the users to change their passwords for safety caused by Heartbleed it was easy to write a tool find forgotten devices in case of IMAP/POP3 but especially Apple clients force to enter the new password seperated for incoming and outgoing server and don't tell the user if things don't work so there is really a need support them and fuzzy logic based on the last successful IMAP/POP3 login from a IP and failed send attempts from the same IP shortly after receive mail leaves a bad taste of only a guess May 18 11:19:09 mail postfix/smtpd[5173]: warning: unknown[177.139.182.86]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 May 18 11:19:15 mail postfix/smtpd[5173]: warning: unknown[177.139.182.86]: SASL LOGIN authentication failed: UGFzc3dvcmQ6

2 2

[Dovecot] Configuration of dovecot 2.0.19 to authenticate users via LDAP
by Danylo Esterman 19 May '14

19 May '14

I am trying to get dovecot 2.0.19 authenticate users via LDAP (OpenLDAP 2.4.28) and using Wireshark to debug the process. It looks like the basic configuration of dovecot is fine, but it doesn't pull it off to send the right request to the LDAP server. First of all, this is how my LDAP-entries look: # ht dn: dc=ht objectClass: top objectClass: dcObject objectClass: organization o: ip dc: ht # admin, ht dn: cn=admin,dc=ht objectClass: simpleSecurityObject objectClass: organizationalRole cn: admin description: LDAP administrator userPassword:: e1NTSEF9cFY1b0ZZVUhack1aRTVvaUg1T3c2cytVWHV4aUNvaHI= # people, ht dn: ou=people,dc=ht objectClass: organizationalUnit objectClass: top ou: people # groups, ht dn: ou=groups,dc=ht objectClass: organizationalUnit objectClass: top ou: groups # ipusers, groups, ht dn: cn=ipusers,ou=groups,dc=ht gidNumber: 500 cn: ipusers objectClass: posixGroup objectClass: top # Max Mustermann, people, ht dn: cn=Max Mustermann,ou=people,dc=ht cn: Max Mustermann givenName: Max gidNumber: 500 homeDirectory: /home/users/mmustormann sn: Mustermann objectClass: inetOrgPerson objectClass: posixAccount objectClass: top uidNumber: 1000 uid: mmustermann userPassword:: e01ENX1ETUYxdWNEeHRxZ3h3NW5pYVhjbVlRPT0= loginShell: /bin/bash mail: mustorm(a)test.com Now, I use the following configuration for dovecot (/etc/dovecot/dovecot-ldap.conf.ext) hosts = 10.1.2.1 dn = cn=admin,dc=ht dnpass = a auth_bind = yes auth_bind_userdn = uid=%u,ou=people,dc=ht ldap_version = 3 scope = subtree base = ou=people,dc=ht user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid user_filter = (&(objectClass=posixAccount)(uid=%u)) pass_attrs = uid=user,userPassword=password pass_filter = (&(objectClass=posixAccount)(uid=%u)) This is what I see in Wireshark: http://i.stack.imgur.com/ICzDe.png Dovecot cannot authenticate itself for some reason... If i change the configuration as follows: auth_bind = no #auth_bind_userdn = uid=%u,ou=people,dc=ht Then I get following picture: http://i.stack.imgur.com/tb5vo.png It doesn't pick up the setting base = ou=people,dc=ht. But what is more crucial is that even looking at the whole tree "<ROOT>" wholeSubTree it can't find the required entry. I am really desperate and don't know how to make it work. Can somebody please give me a clue how to solve this problem?

2 1

[Dovecot] Signal 11 with dovecot-lda
by Jim Dishaw 19 May '14

19 May '14

dovecot version: 2.2.13 NetBSD 5.1 on an amd64 architecture Based on the log file, I think this problem first manifested itself when I upgrade from 2.2.9 to 2.2.12. I tried to go back to 2.2.9, but I would have had to rollback some of the other dependencies. I built 2.2.13 and the problem still exists. Mail gets successfully delivered, but the sender get a non-delivery message. I've hacked a temporary workaround to prevent the non-delivery from being sent by having the bounce service run discard instead of bounce. Logfile excerpt: May 18 04:37:07 chaos postfix/smtp[27935]: 39F8B2134F: to=<XXXX(a)YYYY.ZZZ>, relay=127.0.0.1[127.0.0.1]:10024, delay=21, delays=1.9/0.13/0.69/18, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 0538621350) May 18 04:37:07 chaos postfix/qmgr[19537]: 39F8B2134F: removed May 18 04:37:07 chaos dovecot: lda(XXXX(a)YYYY.ZZZ): msgid=<MAILSM200e8021240fd744d9d8094cd0c3e82dfc2@MAILSM200>: saved mail to INBOX May 18 04:37:07 chaos postfix/pipe[12775]: 0538621350: to=<XXXX(a)YYYY.ZZZ>, relay=dovecot, delay=0.54, delays=0.07/0.3/0/0.18, dsn=5.3.0, status=bounced (Command died with signal 11: "/usr/pkg/libexec/dovecot/dovecot-lda") May 18 04:37:07 chaos postfix/cleanup[2233]: 88C0221353: message-id=<20140518043707.88C0221353(a)chaos.dishaw.org> May 18 04:37:07 chaos postfix/bounce[18857]: 0538621350: sender non-delivery notification: 88C0221353 May 18 04:37:07 chaos postfix/qmgr[19537]: 88C0221353: from=<>, size=14448, nrcpt=1 (queue active) May 18 04:37:07 chaos postfix/qmgr[19537]: 0538621350: removed May 18 04:37:08 chaos postfix/smtp[20299]: 88C0221353: to=<AAAA(a)BBBB.CCC>,relay=site.careerbuilder.com[208.82.4.130]:25, delay=0.89, delays=0.03/0.03/0.25/0.58, dsn=2.6.0, status=sent (250 2.6.0 message received) May 18 04:37:08 chaos postfix/qmgr[19537]: 88C0221353: removed Backtrace: #0 0x00007f7ffc907270 in ?? () #1 0x00007f7ffd778498 in lib_signals_deinit () from /usr/pkg/lib/dovecot/libdovecot.so.0 #2 0x00007f7ffd725739 in master_service_deinit () from /usr/pkg/lib/dovecot/libdovecot.so.0 #3 0x0000000000403021 in main ()

1 0

[Dovecot] RFE: please add Return-Path: to sieve sent mail headers
by Maciej Uhlig 18 May '14

18 May '14

May I ask to add Return-Path: some meaningful header line to sieve sent mail headers in vacation message? Now the header line isn't generated at all and the effect is as follows: on receiving MTA: 2014-05-09T15:04:32+02:00 host/ip postfix/qmgr[2408]: 41F2F6024E: from=<>, size=900, nrcpt=1 (queue active) in received mail body: Return-Path: <> Would be nice to get: Return-Path: <user@domain> Copy of From: header line could be sufficient. Thanks. MU

11 28

[Dovecot] antispam plugin doesn't recognize spam folder
by Paul DiSciascio 18 May '14

18 May '14

After a recent upgrade to dovecot 2.2.9 (caused by an ubuntu upgrade to 14.04), the antispam plugin has stopped recognizing my spam folders as spam. I see the plugin initializes properly, but when moving a message, the mailbox_is_spam() function always returns 0. The version of dovecot-antispam that ships with ubuntu is 2.0+20130822-2build1. I also compiled the latest version in the git repository (last update 9/12/2013) and had the same results. This worked fine prior to the upgrade, with dovecot version 2.0.19 and dovecot-antispam version 2.0+20120225-2. Here are the logs from initialization: May 18 07:48:45 lebeau imap: antispam: plugin initialising (2.0-7-gabdad24) May 18 07:48:45 lebeau imap: antispam: verbose debug enabled May 18 07:48:45 lebeau imap: antispam: "SPAM" is exact match spam folder May 18 07:48:45 lebeau imap: antispam: "Spam" is exact match spam folder May 18 07:48:45 lebeau imap: antispam: "Junk" is exact match spam folder May 18 07:48:45 lebeau imap: antispam: no unsure folders May 18 07:48:45 lebeau imap: antispam: "trash" is exact match trash folder May 18 07:48:45 lebeau imap: antispam: "Trash" is exact match trash folder May 18 07:48:45 lebeau imap: antispam: "Deleted Items" is exact match trash folder May 18 07:48:45 lebeau imap: antispam: "Deleted Messages" is exact match trash folder May 18 07:48:45 lebeau imap: antispam: dspam binary set to /usr/bin/dspam May 18 07:48:45 lebeau imap: antispam: dspam extra arg --user May 18 07:48:45 lebeau imap: antispam: dspam extra arg thenut(a)bytemonkey.net May 18 07:48:45 lebeau imap: antispam: signature header line is "X-DSPAM-Signature" And then from the message move: May 18 07:50:06 lebeau imap: antispam: mailbox_is_unsure(SPAM): 0 May 18 07:50:06 lebeau imap: antispam: mailbox_is_trash(INBOX): 0 May 18 07:50:06 lebeau imap: antispam: mailbox_is_trash(SPAM): 0 May 18 07:50:06 lebeau imap: antispam: mail copy: from trash: 0, to trash: 0 May 18 07:50:06 lebeau imap: antispam: mailbox_is_spam(INBOX): 0 May 18 07:50:06 lebeau imap: antispam: mailbox_is_spam(SPAM): 0 May 18 07:50:06 lebeau imap: antispam: mailbox_is_unsure(INBOX): 0 May 18 07:50:06 lebeau imap: antispam: mail copy: src spam: 0, dst spam: 0, src unsure: 0 Clearly mailbox_is_spam(SPAM) should return 1. The other folders I have designated as spam (Junk and Spam) produce the same results. ~Paul

1 0

[Dovecot] Feature Request doveadm acl command
by Thomas Leuxner 18 May '14

18 May '14

I have switched to global ACLs for public namespaces which eases their administration greately. Now while running housekeeping scripts (e.g. expunge old mails/archive mails etc.) this requires temporary overriding the global ACLs with mailbox specifix ACLs to expunge mails. The scripts would then revoke the temporary changes (delete flags) and the global ACL would take precedence again. Ideally I would want to get rid of the 'dovecot-acl' file after the scripts ran so the global ACL kicks in. There seems to be no interface command to purge 'dovecot-acl' files so this is handled by the scripts for now: [...] # Get actual path of dovecot-acl file and remove it as it is handled by global ACL acl_path=$(doveadm acl debug -u $mailbox_owner "$source_mailbox_base/$1" 2>&1 | sed -n "s/$.*$$debug_acl_mailbox_path//p") [ -f $acl_path/dovecot-acl ] && rm $acl_path/dovecot-acl It would be nice if purging a specific dovecot-acl would be handled by doveadm to avoid custom-scripting. Regards Thomas

1 0

[Dovecot] User not found when using shadow for passdb
by John J. Stimson III 17 May '14

17 May '14

I am getting "user unknown" when trying to connect to the dovecot server using IMAP. The client gets an authentication failed message and does not download mail. The host system uses shadow passwords in /etc/shadow. I would like to use the same passwords for IMAP sessions, so I have set the passdb driver to shadow. The system is Slackware, which does not use PAM. Here is the dovecot version and configuration output: # dovecot -n # 2.1.17: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 3.6.5 i686 Slackware 13.1.0 auth_debug_passwords = yes auth_verbose = yes namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = blocking=no driver = shadow } service auth { unix_listener auth-userdb { user = root } } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { args = blocking=no driver = passwd } Here are the dovecot auth_passwd_debug level log messages when the client tries to connect: May 2 09:05:07 harlie dovecot: auth: Debug: Loading modules from directory: /usr/local/lib/dovecot/auth May 2 09:05:07 harlie dovecot: auth: Debug: auth client connected (pid=22181) May 2 09:05:07 harlie dovecot: auth: Debug: client in: AUTH^I1^IPLAIN^Iservice=imap^Isecured^Isession=ABCDEFGHIJKLMNOP^Ilip=96.229.223.7^Irip=10.0.0.181^Ilport=993^Irport=51898^Iresp=zxywvutsrqponmlkji== May 2 09:05:07 harlie dovecot: auth: Debug: shadow(john,10.0.0.181,<ABCDEFGHIJKLMNOP>): lookup May 2 09:05:07 harlie dovecot: auth: shadow(john,10.0.0.181,<ABCDEFGHIJKLMNOP>): unknown user May 2 09:05:09 harlie dovecot: auth: Debug: client passdb out: FAIL^I1^Iuser=john May 2 09:05:09 harlie dovecot: imap-login: Disconnected (auth failed, 1 attempts in 2 secs): user=<john>, method=PLAIN, rip=10.0.0.181, lip=96.229.223.7, TLS, session=<ABCDEFGHIJKLMNOP> The user john is a real account on the host machine and has entries in both /etc/passwd and /etc/shadow. Help? -- john(a)idsfa.net John Stimson http://www.idsfa.net/~john/ HMC Physics '94

1 1

[Dovecot] RFE: please add mail queue id to 'sent vacation response' log line
by Maciej Uhlig 17 May '14

17 May '14

May I ask to add receiving smtp server mail queue id to sieve 'sent vacation response' log line? Now: 2014-05-09T15:04:32+02:00 name/ip dovecot: lmtp(8164, user1@domain): YvJFLVbSbFPkHwAASpgOhg: sieve: msgid=<000301cf6b87$36be4570$a43ad050$(a)us.edu.pl> size=46850: sent vacation response to <user2@domain> Asked for something like this: 2014-05-09T15:04:32+02:00 name/ip dovecot: lmtp(8164, user1@domain): YvJFLVbSbFPkHwAASpgOhg: sieve: msgid=<000301cf6b87$36be4570$a43ad050$(a)us.edu.pl> size=46850: sent vacation response to <user2@domain> (smtp:[ip]:port): 250 2.0.0 Ok: queued as mailqueueid) <<< In case there are more than one vacation response recipients there is no way to identify who had received the response and who hadn't. Thanks. MU

5 7

[Dovecot] pigeonhole installation postfix+dovecot+openldap
by Selcuk Yazar 17 May '14

17 May '14

Hi, we have running system postfix+dovecot+openldap. i have installed pigeon hole, and afterlogic webmail php my test system. when i try to connect with telnet [root@....mail postfix]# telnet 0 4190 Trying 0.0.0.0... Connected to 0. Escape character is '^]'. "IMPLEMENTATION" "Dovecot Pigeonhole" "SIEVE" "fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date imapflags notify" "NOTIFY" "mailto" "SASL" "PLAIN LOGIN" "VERSION" "1.0" OK "Dovecot ready." my dovecot configuration lijke this [root@trakyamail ~]# dovecot -n # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-131.6.1.el6.x86_64 x86_64 Red Hat Enterprise Linux Server release 6.0 (Santiago) ext4 auth_debug = yes auth_debug_passwords = yes auth_default_realm = ..................edu.tr auth_mechanisms = plain login auth_verbose = yes debug_log_path = /var/log/dovecot.debug disable_plaintext_auth = no first_valid_uid = 97 info_log_path = /var/log/dovecot.info last_valid_uid = 5000 mail_debug = yes mail_gid = 1001 mail_location = mbox:/home/vmail/domains/%d/%u mail_uid = 1001 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 imapflags notify mbox_write_locks = fcntl passdb { args = /etc/dovecot/conf.d/dovecot-ldap.conf.ext driver = ldap } plugin { sieve = /home/vmail/domains/.......edu.tr/%n/.dovecot.sieve sieve_dir = /home/vmail/domains/................edu.tr/%n/sieve sieve_extensions = +notify +imapflags sieve_user_log = /home/vmail/domains/................... edu.tr/%n/.dovecot.sieve.log } protocols = imap pop3 lmtp sieve service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } ssl = no ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { args = /etc/dovecot/conf.d/dovecot-ldap.conf.ext driver = ldap } protocol lmtp { mail_plugins = " sieve" } protocol lda { mail_plugins = " sieve" } also my postfix main.cf mailbox_command = /usr/bin/procmail but my sieve scripts doesnt work, also, how can i enable sieve debug/logging ? thanks in advance -- Selçuk YAZAR

5 5

[Dovecot] dovecot.map.index corrupted: missing map extension
by Francisco Wagner C. Freire 16 May '14

16 May '14

Hello, I have a dovecot setup on top of NFS server, and i get this error on some accounts: Warning: fscking index file ..../cache/storage/dovecot.map.index Warning: mdbox .../mdbox/storage: rebuilding indexes Error: mdbox map.../cache/storage/dovecot.map.index corrupted: missing map extension I tried force-resync, index and cant rebuild the indexes, any idea how to repair then? Thanks Dovecot version: 2.1.17

1 0

[Dovecot] Problems setting up extprograms in combination with crm114
by Patrick Winnertz 16 May '14

16 May '14

Hello, I've troubles to configure sieve correctly to call the mailreaver script in order to parse mails for spam. I've the task to migrate a existing procmail setup to a sieve setup, and to keep the mail filtering step within sieve. I've added in /usr/lib/dovecot/sieve-filters/ a script called "mailreaver", which contains basically only one line - calling the right mailreaver.crm script: exec /usr/share/crm114/mailreaver.crm -u ~/.crm114 This script is then called in the sieve file using "filter "mailreaver". Indeed the script is invoked for every mail, however the signature is appended at the very end of the mail, not at the end of the header. Invoking the /usr/lib/dovecot/sieve-filters/mailreaver manually this way: cat test-email | /usr/lib/dovecot/sieve-filters/mailreaver or this way: /usr/lib/dovecot/sieve-filters/mailreaver < test-email results in both cases in a correct formatted way, so I don't know what is going wrong here. Adding a | tee /tmp/test-output resulted in the complete mail in /tmp/test-output, as I first thought that maybe the headers are not piped into the script - but this seems to be not the case obviously. Does anybody has a clue, as this seems not to be related to crm114 (as it obviously works on cmd), but to the way sieve calls this script. Or it would help to understand how the external filtering program is called - maybe my assumptions are wrong here (or I've simply missunderstood the documentation available online). Greetings Winnie

1 0

[Dovecot] Static Passdb
by Marc Perkel 16 May '14

16 May '14

Tried this but it doesn't work. Says Unknown setting: password passdb { driver = static pass word = secret } The real file doesn't have a space in pass word. What am I doing wrong? Thanks in advance.

2 2

Re: [Dovecot] Pigeonhole and Dovecot deliver
by Selcuk Yazar 16 May '14

16 May '14

Hi, i've read LDA/Postfix Virtual users section , and i added dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/local/libexec/dovecot/dovecot-lda -f ${sender} -d ${recipient} my master.cf, also I added dovecot_destination_recipient_limit = 1 virtual_transport = dovecot but I didnt find anything mailbox_command for virtual users then i removed it. also when i set sieve and sieve dir for per user i added 20-managesieve and 90-sieve sieve = /home/vmail/domains/........................edu.tr/%n/.dovecot.sieve sieve_dir = /home/vmail/domains/....................edu.tr/%n/.sieve values. unfortunately in maillog just see postfix hold information. thanks in advance. On Fri, May 16, 2014 at 12:12 PM, Steffen Kaiser < skdovecot(a)smail.inf.fh-brs.de> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Fri, 16 May 2014, Selcuk Yazar wrote: > > yes i try to change deliver to dovecot. >> > > Please don't top post. > > What about the logs (last sentences in my previous mail)? > > >> On Fri, May 16, 2014 at 11:49 AM, Steffen Kaiser < >> skdovecot(a)smail.inf.fh-brs.de> wrote: >> >>> On Fri, 16 May 2014, Selcuk Yazar wrote: >>> >>> ok first our deliver command procmail. >>> >>>> >>>> >>> you mean that your current MDA is procmail, which you want to replace by >>> Dovecot deliver? >>> >>> in master.cf i added >>> >>>> dovecot unix - n n - - pipe >>>> flags=DRhu user=vmail:vmail argv=/usr/libexec/dovecot/dovecot-lda -f >>>> ${sender} -a ${recipient} -d ${user}@${nexthop} >>>> >>>> in main.cf >>>> mailbox_command = /usr/libexec/dovecot/dovecot-lda -a "$RECIPIENT" >>>> dovecot_destination_recipient_limit = 1 >>>> virtual_transport = dovecot >>>> virtual_mailbox_domains = ldap:domains >>>> >>>> >>> but mail don't deliver, waitin hold queue >>> >>>> >>>> 77CBB22736! 2667 Fri May 16 11:15:54 selcuk.yazar(a)gmail.com >>>> selcukyazar@................... >>>> edu.tr >>>> >>>> 76228227F9! 3028 Fri May 16 10:19:12 selcuk.yazar(a)gmail.com >>>> selcukyazar@.................. >>>> .. >>>> edu.tr >>>> >>>> any advice or solution >>>> >>>> >>> postfix and/or Dovecot are to log something, post the log lines of >>> Dovecot >>> and postfix. Did you've read http://wiki2.dovecot.org/LDA/Postfix ? >>> >> > - -- Steffen Kaiser > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > > iQEVAwUBU3XWe3z1H7kL/d9rAQI/bwf+P4tSirb7b1KpGFuDPJkHwnlKdYp/x1+z > /4Ea5FmuXZDr2qcodOaV0u6Vk416d6T6uNwEsN0bUjVQegxb6LdIemtIsh14TGpN > dAtYToSrlZPK0OTMR0OxjXYRq/1dyM+jGntmDI3gzMPgBNf/paUENAZs4fsn27hs > bqwJDt1T1kmcC5FguNSSGIBJ6YSXpYbu1h63dv7OtBftF46Syi4WSUyjTHuA1NxE > SkpcgYTt+sPKLty8vg1wfvn2EVgETctd+GpfDnEbrxFje/PKmnRp13dr93rJzLMB > 8xWJ2+dtFmSjRnF0gYCHmku1zS5+vsl1Jmeap3EchS1ZSOlVKYfcXA== > =r4AG > -----END PGP SIGNATURE----- > -- Selçuk YAZAR http://www.selcukyazar.blogspot.com

1 0

Re: [Dovecot] Pigeonhole and Dovecot deliver
by Selcuk Yazar 16 May '14

16 May '14

Hi, stefan, yes i try to change deliver to dovecot. thanks. On Fri, May 16, 2014 at 11:49 AM, Steffen Kaiser < skdovecot(a)smail.inf.fh-brs.de> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > On Fri, 16 May 2014, Selcuk Yazar wrote: > > ok first our deliver command procmail. >> > > you mean that your current MDA is procmail, which you want to replace by > Dovecot deliver? > > > in master.cf i added >> dovecot unix - n n - - pipe >> flags=DRhu user=vmail:vmail argv=/usr/libexec/dovecot/dovecot-lda -f >> ${sender} -a ${recipient} -d ${user}@${nexthop} >> >> in main.cf >> mailbox_command = /usr/libexec/dovecot/dovecot-lda -a "$RECIPIENT" >> dovecot_destination_recipient_limit = 1 >> virtual_transport = dovecot >> virtual_mailbox_domains = ldap:domains >> > > but mail don't deliver, waitin hold queue >> >> 77CBB22736! 2667 Fri May 16 11:15:54 selcuk.yazar(a)gmail.com >> selcukyazar@................... >> edu.tr >> >> 76228227F9! 3028 Fri May 16 10:19:12 selcuk.yazar(a)gmail.com >> selcukyazar@.................... >> edu.tr >> >> any advice or solution >> > > postfix and/or Dovecot are to log something, post the log lines of Dovecot > and postfix. Did you've read http://wiki2.dovecot.org/LDA/Postfix ? > > - -- Steffen Kaiser > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > > iQEVAwUBU3XRNXz1H7kL/d9rAQKuUwgAk1bBYiPAgH+dXe70KXSnYZoSCkgQdI73 > AjUCj7zCs3L5BF09QGD7oamjvzSAltEvFBvN2HTsh4k7+9tiDz1//5QfPtgc9yVy > ditUUf2Tppa+ls3cZKxJ5IehKJxlSrTIDssqThR3Q4Wp5b1o1y/cEZXGT2mq93ge > Rhjnm5fo2LdysqtDMtY4Wbt4UeoZr/ICi73yxzvB6OrT6OqY3pvpWrU4LlVTRnES > 5GyQkAQjN65BxggEAYKbGiY/5scuNu03YkQBAzBMeDnqtXL3ApjwK4P+c/OyTW/r > 9udykdk93s6zMtV1bbNJ8qEgTcGxaCwxcvNzfwvXkwX86Fue02WX6g== > =wiMy > -----END PGP SIGNATURE----- > -- Selçuk YAZAR http://www.selcukyazar.blogspot.com

2 1

[Dovecot] Pigeonhole and Dovecot deliver
by Selcuk Yazar 16 May '14

16 May '14

Hi, i still try to sieve system. ok first our deliver command procmail. our user accounts stored in openldap, mail files are in Maildir folders in 15-lda.conf recommented protocol lda { # Space separated list of plugins to load (default is global mail_plugins). mail_plugins = $mail_plugins sieve log_path = info_log_path = } after that, in master.cf i added dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/libexec/dovecot/dovecot-lda -f ${sender} -a ${recipient} -d ${user}@${nexthop} in main.cf mailbox_command = /usr/libexec/dovecot/dovecot-lda -a "$RECIPIENT" dovecot_destination_recipient_limit = 1 virtual_transport = dovecot virtual_mailbox_domains = ldap:domains İN 90-sieve.conf sieve = /home/vmail/domains/..................edu.tr/%n/.dovecot.sieve sieve_dir = /home/vmail/domains/.........................edu.tr/%n/.sieve and also i successfuly add my filters, shown in attachment. but mail don't deliver, waitin hold queue 77CBB22736! 2667 Fri May 16 11:15:54 selcuk.yazar(a)gmail.com selcukyazar@................... edu.tr 76228227F9! 3028 Fri May 16 10:19:12 selcuk.yazar(a)gmail.com selcukyazar@.................... edu.tr any advice or solution thanks in advance -- Selçuk YAZAR http://www.selcukyazar.blogspot.com

2 1

[Dovecot] syncing problems Dovecot 2.2.13
by Götz Reinicke - IT Koordinator 16 May '14

16 May '14

Hi, we still migrate a couple of users from mbox to maildir. Most of them are fine without any problem. Some crash and dont get all mails synced. first I sync backup the mbox to a maildir-NEW, than copy mbox to a new name, mv maildir-NEW to maildir. Now some problematic mailusers miss some mails from the old mbox, so I start a dsync mirror and BAM crash. e.g.: dsync(s108019): Panic: file mbox-lock.c: line 799 (mbox_lock): assertion failed: (lock_type == F_RDLCK || mbox->mbox_lock_type != F_RDLCK) dsync(s108019): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0 [0x333fe67f2a] -> /usr/lib64/dovecot/libdovecot.so.0(default_fatal_handler+0x35) [0x333fe68025] -> /usr/lib64/dovecot/libdovecot.so.0 [0x333fe67073] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mbox_lock+0x11c) [0x334025826c] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mbox_save_begin+0x98d) [0x334025a5ad] -> /usr/lib64/dovecot/lib10_quota_plugin.so [0x2b5b619183c2] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_save_begin+0x51) [0x334027b3f1] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_storage_copy+0x66) [0x3340275716] -> /usr/lib64/dovecot/lib15_notify_plugin.so [0x2b5b61b1f215] -> /usr/lib64/dovecot/lib10_quota_plugin.so [0x2b5b6191852d] -> /usr/lib64/dovecot/lib01_acl_plugin.so [0x2b5b61707b37] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_copy+0x72) [0x334027b282] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_move+0x1d) [0x334027b36d] -> dsyn [0x42f7a5] -> dsyn [0x43351a] -> dsyn(dsync_mailbox_import_changes_finish+0x165) [0x4339b5] -> dsyn(dsync_brain_sync_mails+0x58c) [0x42ed6c] -> dsyn(dsync_brain_run+0x594) [0x42af94] -> dsyn [0x429550] -> dsyn [0x411eef] -> dsyn(doveadm_mail_try_run+0x25c) [0x41231c] -> dsyn(main+0x32e) [0x41a92e] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x3d3161d9c4] -> dsyn [0x411699] ANY help and suggestion is very welcome on how to procede. Regards . Götz -- Götz Reinicke IT-Koordinator Tel. +49 7141 969 82 420 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

1 0

[Dovecot] Disconnected from database, retrying commit?
by Ralf Hildebrandt 15 May '14

15 May '14

In my log I have a lot of log entries like this one (covering one hour of logs here): May 15 09:00:49 dict: Info: maildatabase: Disconnected from database, retrying commit May 15 09:17:10 dict: Info: maildatabase: Disconnected from database, retrying commit May 15 09:22:30 dict: Info: maildatabase: Disconnected from database, retrying commit May 15 09:31:07 dict: Info: maildatabase: Disconnected from database, retrying commit May 15 09:37:15 dict: Info: maildatabase: Disconnected from database, retrying commit May 15 09:39:36 dict: Info: maildatabase: Disconnected from database, retrying commit May 15 09:50:49 dict: Info: maildatabase: Disconnected from database, retrying commit 7 times per hour, that's quite a bit. Dovecot 2.1.17 Related logs look like: ======================= May 15 00:16:44 imap(username): Info: save: box=Sent, uid=1196, msgid=<5373EB4A.90306(a)sys4.de>, size=11152 May 15 00:16:44 dict: Info: maildatabase: Disconnected from database, retrying commit or: May 14 16:10:34 lmtp(7225, username@domain): Info: NTuhEvF1c1M5HAAAcnFQ7Q: msgid=<20090714161800.121200(a)gmx.net>: saved mail to INBOX May 14 16:10:34 dict: Info: maildatabase: Disconnected from database, retrying commit May 14 16:10:34 dict: Info: mysql(sql.sys4.de): Connected to database maildatabase So it's reconnecting, but why is it disconnecting/being disconnected in the first place? Does it matter? should I worry? -- [*] 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

1 0

[Dovecot] v2.2.13 released
by Timo Sirainen 15 May '14

15 May '14

http://dovecot.org/releases/2.2/dovecot-2.2.13.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.13.tar.gz.sig A few minor changes since v2.2.13.rc1, mainly making the Pigeonhole tests pass. * Fixed a DoS attack against imap/pop3-login processes. If SSL/TLS handshake was started but wasn't finished, the login process attempted to eventually forcibly disconnect the client, but failed to do it correctly. This could have left the connections hanging arond for a long time. (Affected Dovecot v1.1+) + mdbox: Added mdbox_purge_preserve_alt setting to keep the file within alt storage during purge. (Should become enforced in v2.3.0?) + fts: Added support for parsing attachments via Apache Tika. Enable with: plugin { fts_tika = http://tikahost:9998/tika/ } + virtual plugin: Delay opening backend mailboxes until it's necessary. This requires mailbox_list_index=yes to work. (Currently IMAP IDLE command still causes all backend mailboxes to be opened.) + mail_never_cache_fields=* means now to disable all caching. This may be a useful optimization as doveadm/dsync parameter for some admin tasks which shouldn't really update the cache file. + IMAP: Return SPECIAL-USE flags always for LSUB command. - pop3 server was still crashing in v2.2.12 with some settings - maildir: Various fixes and improvements to handling compressed mails, especially when they have broken/missing S=sizes in filenames. - fts-lucene, fts-solr: Fixed crash on search when the index contained duplicate entries. - Many fixes and performance improvements to dsync and replication - director was somewhat broken when there were exactly two directors in the ring. It caused errors about "weak users" getting stuck. - mail_attachment_dir: Attachments with the last base64-encoded line longer than the rest wasn't handled correctly. - IMAP: SEARCH/SORT PARTIAL was handled completely wrong in v2.2.11+ - acl: Global ACL file handling was broken when multiple entries matched the mailbox name. (Only the first entry was used.)

8 14

[Dovecot] v2.2.13.rc1 released
by Timo Sirainen 15 May '14

15 May '14

http://dovecot.org/releases/2.2/rc/dovecot-2.2.13.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.13.rc1.tar.gz.sig There have been a ton of smaller and some larger changes since v2.2.12, so I thought I'd first make a RC release and the final v2.2.13 tomorrow. Please try it out! BTW. I've read most of the mails again in Dovecot mailing list, but there are still a few reported bugs I decided to leave until later. Anyway feel free to re-send any bug reports for things that haven't been fixed in v2.2.13 yet. * Fixed a DoS attack against imap/pop3-login processes. If SSL/TLS handshake was started but wasn't finished, the login process attempted to eventually forcibly disconnect the client, but failed to do it correctly. This could have left the connections hanging arond for a long time. (Affected Dovecot v1.1+) + mdbox: Added mdbox_purge_preserve_alt setting to keep the file within alt storage during purge. (Should become enforced in v2.3.0?) + fts: Added support for parsing attachments via Apache Tika. Enable with: plugin { fts_tika = http://tikahost:9998/tika/ } + virtual plugin: Delay opening backend mailboxes until it's necessary. This requires mailbox_list_index=yes to work. (Currently IMAP IDLE command still causes all backend mailboxes to be opened.) + mail_never_cache_fields=* means now to disable all caching. This may be a useful optimization as doveadm/dsync parameter for some admin tasks which shouldn't really update the cache file. + IMAP: Return SPECIAL-USE flags always for LSUB command. - pop3 server was still crashing in v2.2.12 with some settings - maildir: Various fixes and improvements to handling compressed mails, especially when they have broken/missing S=sizes in filenames. - fts-lucene, fts-solr: Fixed crash on search when the index contained duplicate entries. - Many fixes and performance improvements to dsync and replication - director was somewhat broken when there were exactly two directors in the ring. It caused errors about "weak users" getting stuck. - mail_attachment_dir: Attachments with the last base64-encoded line longer than the rest wasn't handled correctly. - IMAP: SEARCH/SORT PARTIAL was handled completely wrong in v2.2.11+ - acl: Global ACL file handling was broken when multiple entries matched the mailbox name. (Only the first entry was used.)

4 8

[Dovecot] 2.2.12 RPM Needed
by Asai 15 May '14

15 May '14

Greetings, I'm not very experienced in building Source RPMs and we're in need of a Dovecot RPM for version 2.2.12 for CentOS 5. It seems that the ATRPMs repo maintained by Axel Thimm hasn't seen much activity lately and the task of updating a source RPM is more than I have time for as a busy developer who does systems admin on the side. Could anybody recommend another repo where there would be the latest Dovecot binaries? Or perhaps tell me of any gotchas and catches which might arise if I go ahead and build 2.2.12 from source over the RPM I currently have installed (2.2.10)? Thanks. -- --Asai

4 6