- dovecot - dovecot.org

[Dovecot] How does sieve's vacation keep track of duplicates?
by ben＠electricembers.net 01 Oct '10

01 Oct '10

I see the .dovecot.lda-dupes file that is created, but it doesn't seem like just plain text, and it doesn't seem to include strings of the senders, just the recipient. But I know the vacation functionality is clever enough to keep track of who it's already autoreplied to. On a related note, I'm curious about other smarts built in to sieve's vacation responder -- what other things does it check, like Precedence header? Benjamin

2 1

[Dovecot] Vacation script execution question.
by Lauro Costa G. Borges 30 Sep '10

30 Sep '10

dovecot 1.2.9 --- I wanna know how the vacation script works. I don't understand why it tries to find locally (using LDAP) a recipient for the "vacation notification email". On the log, "sender_email(a)gmail.com" is the person sending email to "lauro(a)my.domain.org", which is on vacation. Deliver tries to find locally "sender_email(a)gmail.com", to send the vacation notification message: ---- imap dovecot: deliver(lauro(a)my.domain.org): sieve: msgid=<AANLkTim2HNbM=7WNoMOySg3UXgrikGnVdXR+wjhOG7(a)mail.gmail.com>: sent vacation response to <sender_email(a)gmail.com> imap dovecot: deliver(lauro(a)my.domain.org): Namespace : Using permissions from /var/mail/mailboxes/my.domain.org/lauro~my.domain.org: mode=0700 gid=-1 imap postfix/cleanup[21083]: 3E01140A59: message-id=<dovecot-sieve-1285855441-226458-0@imap> imap postfix/qmgr[21051]: 3E01140A59: from=<>, size=615, nrcpt=1 (queue active) imap postfix/trivial-rewrite[21082]: dict_ldap_debug: ldap_build_search_req ATTRS: associatedDomain imap postfix/local[21089]: warning: dict_ldap_open: /etc/postfix/ldap-domain-maps.cf: Fixed query_filter (objectclass=domainRelatedObject) is probably useless imap postfix/pipe[21090]: warning: dict_ldap_open: /etc/postfix/ldap-domain-maps.cf: Fixed query_filter (objectclass=domainRelatedObject) is probably useless imap dovecot: deliver(sender_email(a)gmail.com): Loading modules from directory: /usr/lib/dovecot/modules/lda imap dovecot: deliver(sender_email(a)gmail.com): Module loaded: /usr/lib/dovecot/modules/lda/lib10_quota_plugin.so imap dovecot: deliver(sender_email(a)gmail.com): Module loaded: /usr/lib/dovecot/modules/lda/lib90_sieve_plugin.so imap dovecot: auth(default): master in: USER#0111#011sender_email(a)gmail.com#011service=deliver imap dovecot: auth(default): prefetch(sender_email(a)gmail.com): passdb didn't return userdb entries, trying the next userdb imap dovecot: auth(default): ldap(sender_email(a)gmail.com): user search: base=ou=gmail.com,ou=mail,ou=services,dc=ufsc,dc=br scope=subtree filter=(& (cn=sender_email)(objectclass=nisMailAlias)(ContaAtiva=TRUE) ) fields=rfc822MailMember,EmailQuota,EmailQuotaSpecial,eduPersonPrincipalName imap dovecot: auth(default): ldap(sender_email(a)gmail.com): ldap_search((& (cn=sender_email)(objectclass=nisMailAlias)(ContaAtiva=TRUE) )) failed: No such object : Why is that? ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

1 0

[Dovecot] dovecot-lda segfaults with some sieve scripts
by interfaSys sàrl 30 Sep '10

30 Sep '10

Hello, One account couldn't get emails all the sudden. dovecot-lda was crashing with "signal 11 (segmentation fault)". There was absolutely nothing in the dovecot logs, even with mail_debug=yes. I found out that it was because of the following lines in a sieve script that were generated by a script generator (Ingo). if true { keep; stop; } I'm using the latest revision of pigeonhole with Dovecot 2.0.4. Cheers, Olivier

2 9

[Dovecot] Fwd: NFS question
by Nick Edwards 30 Sep '10

30 Sep '10

Resent to list, since my previous direct emails to Timo have gone unanswered I am NOT a member of this list so Timo please reply direct I do not wish responses from those who are not developers of dovecot, many I have since had discussions with on another list and spam binned (abusive souls like charlie marcus) some for trolling, I seek a definitive answer and there is only one man who can give this, but I likely was mailing a old address he doesn't read ---------- Forwarded message ---------- From: Nick Edwards <nick.z.edwards(a)gmail.com> Date: Fri, Sep 24, 2010 at 6:15 PM Subject: NFS question To: timo(a)iki.fi After reading the archives recently on a few threads about NFS I have concerns over our plans to move from cyrus to dovecot, we initially discounted dovecot as a choice over it, but since dovecot and sieve go well together, I am just re-capping everything before we approve move to courier or back to dovecot, having re read those threads over a couple of times, am I right in assuming that this caching problem, is really only a problem if using imap and the chances of it being an issue with pop3 is very rare? If this is the case, then we certainly would approve move to dovecot. I note some people who have apparently much larger systems than us, say that they have seen no problems but others say they may have had just not noticed. So, if smtp3 delivers to storage MailDir and pop3-1 connects to get mail - at the same time: no problem just wont see that message until next refresh at the same time: will see message if smtp3 and smtp1 deliver at same time there lies the corruption issue? If so, it will be reindexed at next delivery or pop3? Just trying to understand where it will be a problem, we will use postfix setting of virtual_transport = dovecot and dovecot_destination_recipient_limit = 1 We dont allow multiple logins either, we have only intention for one imap server, to compliment our two pop3's and 4 smtp's. We intend to use - pop3_lock_session=yes maildir_very_dirty_syncs=yes auth_verbose = yes auth_cache_size = 512 auth_cache_ttl = 3600 auth_cache_negative_ttl = 0 mail_location = maildir:/var/vmail/%1d/%d/%n/Maildir mmap_disable = yes mail_nfs_storage = yes mail_nfs_index = yes protocol lda { mail_plugins = quota cmusieve quota_full_tempfail = yes auth_socket_path = /var/run/dovecot/auth-master } Also, will this be more of a problem if we use dovecot v1.2 or v2.0 ? (only examples of configs we have for our move is for v1.2 at present for debian) Hope you do not mind me asking this in private, but given how those threads ended up in personal attacks, I would rather not reignite any fires. Nick

6 8

[Dovecot] Problem with dovecot/deliver and SSL in 2.0.4
by Rainer Ophoven 30 Sep '10

30 Sep '10

I'm facing a problem with dovecot/deliver and SSL in 2.0.4 which did not occur in earlier releases: I get this error message: postfix/local[18259]: 687CE86514: to=<rainer(a)homenet.local>, relay=local, delay=0.08, delays=0.02/0/0/0.06, dsn=5.3.0, status=bounced (Command died with status 89: "/usr/libexe c/dovecot/deliver". Command output: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf: ssl enabled, but ssl_key not set ) My System is: Linux mylfs 2.6.27.53 #1 Mon Aug 30 14:28:06 CEST 2010 i686 pentium3 i386 GNU/Linux and dovecot -n reads like this: # 2.0.3: /etc/dovecot/dovecot.conf # OS: Linux 2.6.27.53 i686 auth_mechanisms = plain login digest-md5 cram-md5 disable_plaintext_auth = no mail_location = maildir:~/Maildir passdb { args = dovecot driver = pam } passdb { args = /etc/mail/dovecot/dovecot-cram-md5.pwd driver = passwd-file } service auth { user = root } service imap-login { inet_listener imap { address = * } inet_listener imaps { address = * } } service pop3-login { inet_listener pop3 { address = 192.168.1.2 } inet_listener pop3s { address = 192.168.1.2 } } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = passwd } protocol pop3 { pop3_client_workarounds = outlook-no-nuls pop3_uidl_format = %08Xu%08Xv } protocol lda { postmaster_address = postmaster(a)homenet.local sendmail_path = /usr/bin/mutt } I reverted to 2.0.3 and the error does not occur anymore. Rainer Ophoven

3 3

[Dovecot] 1.2.14 --- auth(default) Error: LDAP: Connection lost to LDAP server, reconnecting
by Denny Schierz 30 Sep '10

30 Sep '10

hi, I see in dovecots logfile some error messages: Sep 29 15:33:43 auth(default): Error: LDAP: Connection lost to LDAP server, reconnecting Sep 29 15:34:15 auth(default): Error: LDAP: Connection lost to LDAP server, reconnecting Sep 29 15:34:50 auth(default): Error: LDAP: Connection lost to LDAP server, reconnecting Sep 29 15:35:22 auth(default): Error: LDAP: Connection lost to LDAP server, reconnecting Sep 29 15:36:01 auth(default): Error: LDAP: Connection lost to LDAP server, reconnecting Sep 29 15:36:37 auth(default): Error: LDAP: Connection lost to LDAP server, reconnecting Sep 29 15:37:16 auth(default): Error: LDAP: Connection lost to LDAP server, reconnecting Sep 29 15:37:52 auth(default): Error: LDAP: Connection lost to LDAP server, reconnecting Sep 29 15:38:24 auth(default): Error: LDAP: Connection lost to LDAP server, reconnecting I don't know, what could be the problem. I upgraded Dovecot from 1.2.13 to 1.2.14 to solving the problem, but ... no success. Our LDAP Server is 2.4.23 and works for our network without any problems. If I try to use ldapsearch from the Dovecot host, while I see the messages, ldapsearch works withouch any timeout. I enabled caching for auth too, but the problem still exists. My DoveCot Config: http://pastebin.com/W7zHf4fT the LDAP part: hosts = ldap ldap2 auth_bind = yes ldap_version = 3 base = cn=accounts, dc=foo user_attrs = postalAddress=domain, homeDirectory=/imap/spool/%d/%1n/%n, myMailQuota=quota_rule=*:storage=%$M user_filter = (&(objectClass=posixAccount)(uid=%n)) pass_attrs = postalAddress=domain, uid=user, userPassword=password pass_filter = (&(objectClass=posixAccount)(uid=%n)) default_pass_scheme = MD5 any suggestions? cu denny ps. when does dovecot switches to ldap2?

3 6

[Dovecot] Can we retrieve Dovecot Proxys 'hostName' from Director instead of LDAP?
by Edward Carraro 30 Sep '10

30 Sep '10

We have a Dovecot installation of several nodes that share an NFS mount for the user data. We are trying to configure Dovecot Proxy with Director in order to have Director select the appropriate IMAP server for a given user on behave of Dovecot Proxy. So far all examples I've seen on the dovecot site require the proxy to know the exact mail server to pass the user to by way of an LDAP lookup. Does anyone know of a way to have Dovecot Proxy pick a server from Directors status list instead of looking it up from LDAP? Also, how does Director discover that an IMAP server is up or down so that it can adjust in the case of a server failure? Is this something that Director does automatically or do we need to manually change the mail servers vhost count in case of an IMAP node failure? Thanks

3 8

[Dovecot] Doveadm expunge purge optimize
by Thiago Henrique 30 Sep '10

30 Sep '10

Hello, I'm testing Dovecot 2.0.3. I plan to use Dovecot with 10 thousands domains per server (~50 thousands accounts). I use 'mdbox' as mailbox format. So, I have two cron jobs before backup: ################################################################################ 01 22 * * * root nice -n 19 /usr/bin/doveadm expunge -A mailbox SPAM BEFORE 60d 01 00 * * * root nice -n 19 /usr/bin/doveadm purge -A 01 02 * * * root nice -n 19 My_Backup_aplication ################################################################################ Each doveadm command walks through the whole file system. Is there a way to run the two operations into a single walk? Does anyone have a suggestion that helps optimize this? Thank you in advance. Best Regards My confs : ################################################################################ root@server:# dovecot -n # 2.0.3 (02a9cf90ad02): /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-24-server x86_64 Ubuntu 10.04.1 LTS auth_cache_negative_ttl = 3600 s auth_cache_size = 33554432 auth_master_user_separator = * auth_mechanisms = plain login auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@= auth_worker_max_count = 10 disable_plaintext_auth = no listen = server.com login_greeting = Dovecot server ! mail_gid = dovemail mail_plugins = $mail_plugins quota mail_uid = dovemail managesieve_sieve_capability = fileinto reject envelope vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include imapflags notify mmap_disable = yes passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } passdb { args = /etc/dovecot/dovecot-sql-master.conf.ext driver = sql master = yes pass = yes } plugin { autocreate = SPAM autosubscribe = SPAM quota = dict:User quota::file:/var/lib/imap/user/%2.256RHn/% n/dovecot-quota quota_rule = *:storage=1GB sieve = /var/lib/imap/sieve/%2.256RHn/%n/phpscript.script sieve_dir = /var/lib/imap/sieve/%2.256RHn/%n sieve_extensions = comparator-i;ascii-numeric copy envelope fileinto imapflags include notify regex reject relational subaddress vacation sieve_max_script_size = 512KB sieve_quota_max_scripts = 2 } protocols = imap pop3 lmtp sieve service auth-worker { user = $default_internal_user } service auth { process_limit = 1 process_min_avail = 1 } service imap-login { inet_listener imap { address = server.com port = 143 } } service imap { process_limit = 1024 process_min_avail = 10 } service lmtp { inet_listener { address = server.com port = 2003 } process_limit = 256 process_min_avail = 10 } service managesieve-login { inet_listener sieve { address = server.com port = 4190 } inet_listener sieve_deprecated { address = server.com port = 2000 } } service managesieve { process_limit = 20 process_min_avail = 10 } service pop3-login { inet_listener pop3 { address = server.com port = 110 } } service pop3 { process_limit = 256 process_min_avail = 10 } ssl = no userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } verbose_proctitle = yes protocol imap { imap_idle_notify_interval = 120 s imap_max_line_length = 65536 mail_max_userip_connections = 10 mail_plugins = $mail_plugins quota imap_quota autocreate } protocol lmtp { mail_plugins = $mail_plugins sieve quota autocreate } protocol sieve { mail_plugins = $mail_plugins sieve managesieve_implementation_string = Dovecot ManageSieve Pigeonhole server managesieve_logout_format = bytes=%i/%o managesieve_max_line_length = 65536 managesieve_sieve_capability = comparator-i;ascii-numeric copy envelope fileinto imapflags include notify regex reject relational subaddress vacation } protocol pop3 { mail_plugins = $mail_plugins quota autocreate } root@server:# ################################################################################ -- []'s Thiago Henrique Network Administration Digirati Networks K8 Networks

2 1

[Dovecot] Problem with dovecot-acl
by dss 30 Sep '10

30 Sep '10

I have a problem with dovecot-acl. Some of our users need to use the same Mailbox with all folders: Inbox (with subfolders), Outbox, Send and Deleted, (some users need in full righs, some - readonly) so I choosed Symlinking mailboxes and tried to use dovecot-acl file. cat dovecot-acl: user=t1 lrwsti user=operolegs lrwsti user=operantona lrwsti user=operdss lr User operdss have lrwsti rights in this shared mailbox unstead of lr! But if I comment out other users in the dovecot-acl: #user=t1 lrwsti #user=operolegs lrwsti #user=operantona lrwsti user=operdss lr User operdss have lr rights. Whats wrong? It seems, that dovecot-acl is working only for one user. How can I fix it? === Here is my configs. imap:~# dovecot -n # 1.2.13: /etc/dovecot/dovecot.conf # OS: Linux 2.6.26-2-686 i686 Debian 5.0.6 log_timestamp: %Y-%m-%d %H:%M:%S disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_privileged_group: mail mbox_write_locks: fcntl dotlock mail_plugins: acl imap_acl auth default: passdb: driver: pam userdb: driver: passwd plugin: acl: vfile ---- imap:~# ls -l /home/t1/Maildir lrwxrwxrwx 1 root root 21 2010-09-22 16:03 /home/t1/Maildir -> /var/mail/720/Maildir imap:~# ls -l /home/operolegs/Maildir lrwxrwxrwx 1 root root 21 2010-09-23 16:00 /home/operolegs/Maildir -> /var/mail/720/Maildir imap:~# ls -l /home/operantona/Maildir lrwxrwxrwx 1 root root 21 2010-09-23 16:00 /home/operantona/Maildir -> /var/mail/720/Maildir imap:~# ls -l /home/operdss/Maildir lrwxrwxrwx 1 root root 16 2010-09-28 16:32 /home/operdss/Maildir -> /home/t1/Maildir --- imap:/home/t1/Maildir# ls -l total 112 drwxrws--- 2 t1 mshare 4096 2010-09-27 10:46 cur -rw-rw---- 1 t1 mshare 99 2010-09-29 15:56 dovecot-acl -rw-rw---- 1 operdss mshare 312 2010-09-29 16:43 dovecot-acl-list -rw-rw---- 1 operolegs mshare 1144 2010-09-24 12:16 dovecot.index -rw-rw---- 1 t1 mshare 41984 2010-09-28 16:39 dovecot.index.cache -rw-rw---- 1 t1 mshare 25068 2010-09-28 16:38 dovecot.index.log -rw-rw---- 1 operantona mshare 17 2010-09-23 16:41 dovecot-keywords -rw-rw---- 1 operantona mshare 1941 2010-09-27 10:46 dovecot-uidlist -rw-rw---- 1 t1 mshare 8 2010-09-29 16:43 dovecot-uidvalidity -rw-rw---- 1 t1 mshare 0 2010-09-22 10:54 dovecot-uidvalidity.4c99a82f drwxrws--- 2 t1 mshare 4096 2010-09-27 10:46 new -rw-rw---- 1 operdss mshare 327 2010-09-29 16:43 subscriptions drwxrws--- 2 t1 mshare 4096 2010-09-27 10:46 tmp ----- imap:/home/t1/Maildir# dpkg --list|grep dovecot ii dovecot-common 1:1.2.13-1~bpo50+1 secure mail server that supports mbox and maildir mailboxes ii dovecot-imapd 1:1.2.13-1~bpo50+1 secure IMAP server that supports mbox and maildir mailboxes dovecot packages - from backports --- Linux: Debian Lenny up2date

2 1

[Dovecot] problems and dovecot & manegesieve
by Jose Luis Faria 29 Sep '10

29 Sep '10

Hello, my server is working with dovecot-2.0.2+dovecot-2.0-pigeonhole-0.2.0. but if activate managesieve, is not listening in 4190! any help? I setup this: ---------------------------------- ## ## ManageSieve specific settings ## # Service definitions service managesieve-login { inet_listener sieve { port = 4190 } #inet_listener sieve_deprecated { # port = 2000 #} # Number of connections to handle before starting a new process. Typically # the only useful values are 0 (unlimited) or 1. 1 is more secure, but 0 # is faster. <doc/wiki/LoginProcess.txt> #service_count = 1 # Number of processes to always keep waiting for more connections. #process_min_avail = 0 # If you set service_count=0, you probably need to grow this. #vsz_limit = 64M } service managesieve { # Max. number of ManageSieve processes (connections) #process_count = 1024 } # Service configuration protocol sieve { # Maximum ManageSieve command line length in bytes. ManageSieve usually does # not involve overly long command lines, so this setting will not normally need # adjustment #managesieve_max_line_length = 65536 # Maximum number of ManageSieve connections allowed for a user from each IP address. # NOTE: The username is compared case-sensitively. #mail_max_userip_connections = 10 # Space separated list of plugins to load (none known to be useful so far). Do NOT # try to load IMAP plugins here. #mail_plugins = # MANAGESIEVE logout format string: # %i - total number of bytes read from client # %o - total number of bytes sent to client #managesieve_logout_format = bytes=%i/%o # To fool ManageSieve clients that are focused on CMU's timesieved you can specify # the IMPLEMENTATION capability that the dovecot reports to clients. # For example: 'Cyrus timsieved v2.2.13' #managesieve_implementation_string = Dovecot Pigeonhole # Explicitly specify the SIEVE and NOTIFY capability reported by the server before # login. If left unassigned these will be reported dynamically according to what # the Sieve interpreter supports by default (after login this may differ depending # on the user). #managesieve_sieve_capability = #managesieve_notify_capability = # The maximum number of compile errors that are returned to the client upon script # upload or script verification. #managesieve_max_compile_errors = 5 # Refer to 90-sieve.conf for script quota configuration and configuration of # Sieve execution limits. } -- :) cumprimentos ---------------------- José Luís Faria Network Eng./Administrador de Sistemas Departamento de Informática Universidade do Minho Braga, Portugal

2 3