- dovecot - dovecot.org

[Dovecot] v2.1.10: Director director_servers order issue
by Bertrand Jacquin 23 Nov '12

23 Nov '12

Hi, I'm setting up an IMAP/POP cluster using dovecot director for some NFS reasons and I'm getting some troubles with director_servers directive. Configuration is shared on both nodes : director_servers = 10.0.50.50 10.0.50.51 director_mail_servers = 192.168.0.150 192.168.0.151 director_user_expire = 15 min service director { unix_listener login/director { mode = 0666 } fifo_listener login/proxy-notify { mode = 0600 user = $default_login_user } unix_listener director-userdb { mode = 0600 } inet_listener { port = 9090 } } service ipc { unix_listener ipc { user = $default_login_user } } Here 10.0.50.50 is node1, 10.0.50.51 is node2 # ring status on node1 director ip port type last failed 10.0.50.50 9090 self never 10.0.50.51 9090 never # ring status on node2 director ip port type last failed 10.0.50.50 9090 self never 10.0.50.51 9090 never self is the same on both nodes, and that generate some cases that can be observed on logs : # logs on node1 dovecot: director: Error: Remote director thinks it's someone else (connected to 10.0.50.51:9090, remote says it's 10.0.50.50:9090) And this is true, TCP packet contain bad DATA : # tcpdump -i eth0 -nn src host 10.0.50.51 and port 9090 -s 0 -w - -l | strings | egrep '^ME' ME 10.0.50.50 9090 # logs on node2 dovecot: director: Error: connect(10.0.50.51:9090) failed: Invalid argument Invalid argument is present as bind() is not done with the appropriate IP : # strace -p 6063 -fF -s 1024 -e trace=bind,connect bind(28, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("10.0.50.50")}, 16) = 0 connect(28, {sa_family=AF_INET, sin_port=htons(9090), sin_addr=inet_addr("10.0.50.51")}, 16) = -1 EINVAL (Invalid argument) Also, during this time, CPU is ~100% used. bind() is done with node1 IP address. I also tested using a DNS : director_servers = director-all director-all is two A entries, first containing 10.0.50.50, second 10.0.50.51 and the result here is exactly the same. Using two configurations : # director_servers on node1 director_servers = 10.0.50.50 10.0.50.51 # director_servers on node2 director_servers = 10.0.50.51 10.0.50.50 Give the same result as showed before : # ring status on node1 director ip port type last failed 10.0.50.50 9090 self never 10.0.50.51 9090 never # ring status on node2 director ip port type last failed 10.0.50.50 9090 self never 10.0.50.51 9090 never It seems that first sorted entry in director_servers is considered as "self". I'm using dovecot 2.1.10-0~auto+55 debian package from rename-it repository. Thanks for your help. -- Beber

2 3

[Dovecot] doveadm fails with passdb authentication binds (dovecot 2.0.16)
by mailing lists 23 Nov '12

23 Nov '12

Hello, I'm testing passdb auth binds with dovecot 2.0.16, but for some reason dovedm fails to work with the configuration showed below. The network trace shows the successful bind for the administrative user (uid=mailapp), but nothing for the mail user (uid=user001). what am i missing here? # doveadm mailbox list -u user001 doveadm(user001): Error: user user001: Auth PASS lookup failed doveadm(user001): Fatal: passdb lookup failed 10-auth.conf: ==================== disable_plaintext_auth = no auth_cache_size = 0 auth_cache_ttl = 0 auth_cache_negative_ttl = 0 auth_mechanisms = plain !include auth-ldap.conf.ext auth-ldap.conf.ext: ===================================== passdb { driver = ldap args = /etc/dovecot/passdb-dovecot-ldap.conf.ext } userdb { driver = ldap args = /etc/dovecot/userdb-dovecot-ldap.conf.ext } passdb-dovecot-ldap.conf.ext: ===================================== uris = ldap://ldap.example.com dn = uid=mailapp,ou=People,dc=example,dc=com dnpass = xxxxxxxxxx sasl_bind = no tls = no auth_bind = yes ldap_version = 3 base = dc=example,dc=com deref = never scope = subtree pass_attrs = uid=user pass_filter = (uid=%n) userdb-dovecot-ldap.conf.ext: ==================================== uris = ldap://ldap.example.com dn = uid=mailapp,ou=People,dc=example,dc=com dnpass = xxxxxxxxxx sasl_bind = no tls = no auth_bind = yes ldap_version = 3 base = dc=example,dc=com deref = never scope = subtree user_attrs = mailbox=mail=maildir:/var/maildir/%$,homeFilter=home,mailQuota=quota_rule=*:bytes=%$ user_filter = (&(objectClass=posixAccount)(uid=%n)) pass_attrs = uid=user,userPassword=password,\ mailbox=userdb_mail=maildir:/var/maildir/%$,homeFilter=userdb_home,mailQuota=userdb_quota_rule=*:bytes=%$ pass_filter = (&(objectClass=posixAccount)(uid=%n)) iterate_attrs = uid=user iterate_filter = (objectClass=posixMailAccount)

2 1

[Dovecot] whoson plugin for 2.0
by Chuck Cochems 23 Nov '12

23 Nov '12

I have found a plugin at ftp://ftp.ufanet.ru/pub/boco/dovecot/whoson-plugin/ I was able to make it function on a dovecot 1.2.8 server, by changing __attr_unused__ to ATTR_UNUSED and strlcpy to i_strocpy (since glibc doesn't HAVE strlcpy, on purpose). However, it doesn't work with 2.1 this is, of course, because getenv() no longer functions lie it used to in plugins. so i need a replacement for getenv("IP") and getenv("USER") to make this work. i know, pop before SMTP is stupid, but the isp i'm doing this for hs customers that have used pop before smtp for ages. so I MUST make a whoson plugin. as i said, the remote ip and the email address are required to interface with whoson. (this is superior to DRAC, which just opens the IP)

3 6

[Dovecot] Initial status notification not received
by Nicolas KOWALSKI 23 Nov '12

23 Nov '12

Hello, We have SLES-11 SP2 Xen VMs running dovecot as IMAP proxies. At VMs startup, dovecot almost always shows these errors: Nov 16 14:29:19 server dovecot: master: Dovecot v2.1.10 starting up (core dumps disabled) Nov 16 14:29:55 server dovecot: master: Error: service(anvil): Initial status notification not received in 30 seconds, killing the process Nov 16 14:29:55 server dovecot: master: Error: service(log): Initial status notification not received in 30 seconds, killing the process Nov 16 14:29:55 server dovecot: master: Error: service(ssl-params): Initial status notification not received in 30 seconds, killing the process Nov 16 14:29:55 server dovecot: master: Error: service(log): child 3591 killed with signal 9 As the last line tells, dovecot stops logging information. We have to restart the dovecot processes to get back normal behaviour. I also tried to set idle_kill values to services definitions, without success. Is there a way to prevent these errors? Here is the dovecot -n output: # 2.1.10: /etc/dovecot/dovecot.conf # OS: Linux 3.0.42-0.7-xen x86_64 SUSE Linux Enterprise Server 11 (x86_64) default_client_limit = 4096 default_idle_kill = 5 mins default_process_limit = 16384 listen = 10.254.251.18 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap sieve service anvil { client_limit = 65536 idle_kill = 0 } service auth { client_limit = 32768 } service imap-login { inet_listener imap { port = 0 } } service imap { process_limit = 0 } service log { idle_kill = 0 } service managesieve { process_limit = 0 } service ssl-params { idle_kill = 0 } ssl_ca = </etc/dovecot/ssl/ca.pem ssl_cert = </etc/dovecot/ssl/server-crt.pem ssl_key = </etc/dovecot/ssl/server-key.pem userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocol sieve { passdb { args = /etc/dovecot/dovecot-ldap-sieve.conf.ext driver = ldap } } Thanks, -- Nicolas

2 3

[Dovecot] User iteration with static userdb
by Radek Novotný 23 Nov '12

23 Nov '12

Hi all, can someone explain me, please, why user iteration (iterate_query) doesn't work with static userdb? There isn't reason why it shouldn't work. In my opinion. However static userdb doesn't mean that user list not exist. Thanks Radek

2 1

[Dovecot] Is there a hook for a plugin to do some transient operation on the mail body ...
by Jay 23 Nov '12

23 Nov '12

... when the MUA has issued a FETCH? I am a Dovecot newbie ... so please bear with me if this is obvious. Basically what I am trying to do is process the mail body (in my own specific way) before Dovecot serves it up to the MUA. I want to do it as a transient operation in memory. So think of the scenario as ... - the MUA issues a FETCH - Dovecot intercepts the FETCH - Dovecot internally gets the mail from the storage into a buffer in memory ----> This is where I'd like to apply a function to the mail body and modify the mail body in the buffer (not in the storage) - Dovecot serves up the (modified) mail to the MUA Looking for a hook that allows me to do it using a plugin. Looks like the zlib plugin does something similar ... applies a decompression function ... but I am not 100% sure. Thanks for your help. -- J.

2 1

[Dovecot] Hardlink with Maildir a brief help
by Davide 23 Nov '12

23 Nov '12

Hi to all, my question is: Is possible implementing SIS (with hardlink) with maildir instead of *dbox format? If yes in dovecot.conf it's only necessary the below parameters or what else? mail_attachment_dir = /var/qmail/attachments I have also acting the zlib plugin it is not a problem isn't it? Thanks in advance for any response -- */Davide Marchi /Teorema Ferrara Srl /(Tel: /**/+39 0532 783161)/**/ (Fax: +/**/39 0532 783368/**/)/**//**/ /**//**/Davide.Marchi(a)mail.cgilfe.it <mailto:davide.marchi@mail.cgilfe.it?subject=Info> /CONFIDENZIALITA’ *** Questo messaggio, inclusi gli eventuali allegati, è indirizzato solo ai destinatari e può contenere informazioni riservate e confidenziali. Se avete ricevuto il messaggio senza esserne un destinatario, siete pregati di non utilizzare, copiare o distribuire questo messaggio o i suoi allegati. Se avete ricevuto il messaggio per errore, siete pregati di cancellarlo dal vostro sistema, assieme a tutti gli allegati, e di informare immediatamente il mittente,sia ai sensi dell'art. 616 c.p., sia ai sensi del DL n. 196/03. *CONFIDENTIALITY*** This message and any attachments are intended only for the use of the addressee(s) and may contain information that is privileged and/or confidential. If the reader of the message is not the intended recipient(s) or an authorized representative of the intended recipient(s), please do not use, copy, distribute this email or its attachments or take action based on them. If you have received this communication in error, please notify us immediately by email and delete the message and any attachments from your system. *Teorema FerraraSrl - Via Spronello, 7 - 44121 Ferrara Italia - P. IVA 01244490387** P**S**tampa questo messaggio solo se veramente necessario, pensa alla natura! - Please consider whether it is necessary to print this e-mail*

2 1

[Dovecot] IMAP session state inconsistent
by list＠airstreamcomm.net 23 Nov '12

23 Nov '12

Running Dovecot 1.2.12 (we are in the process of upgrading to 2.1.x) Didn't find much in old threads, but we are seeing the following in the logs this morning: dovecot: imap-login: Login: user=<wajabrun>, method=PLAIN, rip=x.x.x.x, lip=y.y.y.y dovecot: IMAP(wajabrun): Disconnected: IMAP session state is inconsistent, please relogin. bytes=443/1146 dovecot: imap-login: Login: user=<wajabrun>, method=PLAIN, rip=x.x.x.x, lip=y.y.y.y dovecot: IMAP(wajabrun): Disconnected: IMAP session state is inconsistent, please relogin. bytes=561/1637 dovecot: imap-login: Login: user=<wajabrun>, method=PLAIN, rip=x.x.x.x, lip=y.y.y.y dovecot: IMAP(wajabrun): file_dotlock_open() failed with file /mail/w/a/wajabrun/Maildir/.INBOX.02 ORDERS.Gaiam/dovecot.index.log: No such file or directory dovecot: IMAP(wajabrun): file_dotlock_open() failed with file /mail/w/a/wajabrun/Maildir/.INBOX.02 ORDERS.Gaiam/dovecot.index.log: No such file or directory Not sure what to make of this sequence?

2 1

[Dovecot] maildir and end-of-line encoding
by Christoph Anton Mitterer 23 Nov '12

23 Nov '12

Hi. I just wondered, the following: My MDA may get mails that use LF or CR/LF end of line encodings and deliver them into maildirs. I couldn't find any information about, whether one should or must convert all into one format, cause AFAIK at least on the IMAP side, CR/LF is always used? How does this work on the maildir/backend side of dovcot? Can it work with both and simply automatically convert LF into CR/LF? Thanks, Chris.

2 3

[Dovecot] Is there any Documentation or Howto/Guide for Dovecot Replication or do i have to wait for dovecot 2.2.x?
by weber＠zackbummfertig.de 23 Nov '12

23 Nov '12

dear timo, can you help me? best regards marko, from hamburg

3 2