December 2011 - dovecot

[Dovecot] overriding userdb connection host for doveadm-user
by Micah Anderson 10 Dec '11

10 Dec '11

I've got my users in a replicated database setup and dovecot configured with two connect lines in dovecot-sql.conf: connect = host=127.0.0.1 port=3306 dbname=users user=user password=pass connect = host=127.0.0.2 port=3306 dbname=users user=user password=pass this works really well to help balance the load. However, when a new user is created, the replication information sometimes has not made it to the slave database before my user creation process tries to send that new user an email about their new email account. If it hasn't and the email gets sent, then it bounces because postfix thinks the user doesn't exist yet. Replication usually happens within seconds, but could be delayed due to problems. I would like a way to see if the new user's information has been replicated yet before sending the email. I was thinking I could use 'doveadm user' to lookup the user, but I am not sure that I can specify one of the specific 'connect' lines in my configuration to check. Is there a way to override that configuration variable to do this test? I tried various incarnations of passing '-o connect=host='... but doveadm user would just ignore them. thanks for any suggestions! micah ps - yes, I can make my user creation process just 'sleep' for an arbitrary amount of time and by that time the replication should have occured, but that is a bit of a shot in the dark, and doesn't handle longer replication delays that could potentially happen. --

3 3

[Dovecot] lmtp panic in proxy lmtp director
by Xavier Pons 10 Dec '11

10 Dec '11

Hi, we are getting some core dumps with signal 6 in ltmp on a dovecot director proxy server, like this: Dec 5 14:31:51 sproxy1 dovecot: lmtp(29999): Panic: file lmtp-proxy.c: line 376 (lmtp_proxy_output_timeout): assertion failed: (proxy->data_input->eof) Dec 5 14:31:51 sproxy1 dovecot: lmtp(29999): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0() [0x363323d99a] -> /usr/lib64/dovecot/libdovecot.so.0() [0x363323d9e6] -> /usr/lib64/dovecot/libdovecot.so.0(i_error+0) [0x3633216f8f] -> dovecot/lmtp() [0x406e57] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handle_timeouts+0xd4) [0x3633248ff4] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x5b) [0x3633249bdb] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x28) [0x3633248c58] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x3633236fc3] -> dovecot/lmtp(main+0x154) [0x403f84] -> /lib64/libc.so.6(__libc_start_main+0xfd) [0x373cc1ec5d] -> dovecot/lmtp() [0x403d69] Dec 5 14:31:51 sproxy1 abrt[30067]: saved core dump of pid 29999 (/usr/libexec/dovecot/lmtp) to /var/spool/abrt/ccpp-1323091911-29999.new/coredump (1368064 bytes) Dec 5 14:31:51 sproxy1 dovecot: master: Error: service(lmtp): child 29999 killed with signal 6 (core dumped) we have something misconfigured or it's a bug on this dovecot version? our doveconf -n is: # 2.0.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-71.29.1.el6.x86_64 x86_64 CentOS Linux release 6.0 (Final) auth_cache_size = 3 k auth_cache_ttl = 15 mins auth_verbose = yes base_dir = /var/run/dovecot/ default_client_limit = 30000 default_process_limit = 5000 director_doveadm_port = 990 director_mail_servers = 10.80.82.21 10.80.82.22 director_servers = 10.80.82.11 10.80.82.12 doveadm_proxy_port = 24245 lmtp_proxy = yes managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave passdb { args = proxy=y nopassword=y starttls=any-cert driver = static } postmaster_address = xavier.pons(a)uib.es protocols = imap pop3 lmtp sieve service auth { client_limit = 27048 unix_listener /var/spool/postfix/private/auth { mode = 0666 } unix_listener auth-userdb { group = dovecot mode = 0660 } } service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { port = 991 } inet_listener director-doveadm { port = 990 } unix_listener director-userdb { mode = 0660 } unix_listener login/director { mode = 0666 } } service doveadm { inet_listener { port = 24245 } } service imap-login { executable = imap-login director inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service lmtp { inet_listener lmtp { port = 30025 } } service managesieve-login { executable = managesieve-login director } service pop3-login { executable = pop3-login director inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } ssl = required ssl_cert = </etc/pki/tls/certs/imap.crt ssl_key = </etc/pki/tls/private/imap.uib.es_privatekey.pem syslog_facility = local1 verbose_proctitle = yes protocol lmtp { auth_socket_path = director-userdb passdb { args = /etc/dovecot/dovecot-ldap-pass.conf.lmtp driver = ldap } } protocol doveadm { auth_socket_path = director-userdb } protocol imap { mail_max_userip_connections = 20 } protocol pop3 { pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } Xavier -- xavier.pons(a)uib.es Centre de Tecnologies de la Informació Universitat Illes Balears

4 3

[Dovecot] Make entire mailbox read-only (ACLs?)
by David Jonas 10 Dec '11

10 Dec '11

Hello, Is there a way of locking a mailbox, effectively making it read-only to IMAP clients? I've read through http://wiki2.dovecot.org/ACL. I created dovecot-acl with the content "owner lr" in .INBOX which seems to keep me from copying messages into the folder, but not out. I have the plugin configured correctly, it seems, since MYRIGHTS command shows the correct value: 30 MYRIGHTS "INBOX" * MYRIGHTS "INBOX" lr Am I barking up the wrong tree? Is there an easier way to lock a mailbox? post-login scripting perhaps? Thanks!

2 3

[Dovecot] Major bug with hardlinks and lmtp
by Brad Schuetz 10 Dec '11

10 Dec '11

In working on trying to fix the crash issue from my last email I had enabled LMTP delivery to try it out instead of using the LDA. I have discovered that when a single piece of email is to be delivered to multiple users the message is being hard linked instead of copied into each mail box. This is a major problem that makes LMTP unusable in an environment where each mailbox has it's own UID since the hard linked file will only be readable by one of the users. I assume this is related to "maildir_copy_with_hardlinks=yes", however this setting doesn't say anything about hardlinking across different email accounts. -- Brad Schuetz

2 1

[Dovecot] Per-User MySQL Quota (postfixadmin)
by Sehic, Haris 09 Dec '11

09 Dec '11

Hi, need some help setting per-user quota and postfixadmin. Setup is working on 1.2 dovecot. Tryin 2.1 dovecot now, quota is working but overriden quota rule set by 'user_query =' in /etc/dovecot/dovecot-sql.conf.ext takes no efffekt. What's wrong here? Greets Haris

2 2

[Dovecot] Wish list item: %g/%{gid} variable
by Pascal Volk 09 Dec '11

09 Dec '11

I think it would be very useful to have a user's GID in a variable. So i could use for example: mail_attachment_dir = /srv/mail/.SiS/%{gid} I use one GID per domain and the aliases fqhns of the domain. When for example example.com would be an alias for exmaple.net (gid: 12345), the attachments would be stored inside /srv/mail/.SiS/12345/, no matter if a message was sent to john.doe(a)example.com or to john.doe(a)example.net. "quota = dict:domain:%{gid}:proxy::quota" would then also work. Regards, Pascal -- The trapper recommends today: c01dcofe.1134217(a)localdomain.org

2 1

[Dovecot] "Unstable" vs "Development" vs "Nightly"
by Terry Carmen 09 Dec '11

09 Dec '11

I'm currently running v2.1rc1, but have been seeing errors like: Dec 8 11:31:55 it kernel: auth[18914]: segfault at 48 ip 00fe2f74 sp bfcaccd0 error 4 in libauthdb_imap.so[fdd000+f000] The unstable and nightly builds are newer, but are they likely to be more or less stable than the version I'm currently running? I'd like to install a newer version, but am trying to get a feel for how usable they're likely to be. Thanks, Terry

2 2

[Dovecot] Error: Corrupted index cache file /xxx/yyy/zzz/indexes/.INBOX/dovecot.index.cache: invalid record size
by florent＠coppint.com 09 Dec '11

09 Dec '11

Hi all, I got a problem with a Dovecot IMAP/POP installation. Since a recent failure of our distributed file system (no loss of data btw), Dovecot seems to have a problem with index cache files. For a lot of accounts, I have this error in logs: Error: Corrupted index cache file /xxx/yyy/zzz/indexes/.INBOX/dovecot.index.cache: invalid record size If I delete all files from /indexes/ directory, it still occurs... Do you see what can cause this problem ? Or what information can I provide to help ? Our distributed FS is MooseFS. Dovecot is configured like if it was NFS (no mmap, etc...). Thank you for your help :) Flo

2 1

Re: [Dovecot] sql dict: commit failed: MySQL server has gone away
by Mark Zealey 08 Dec '11

08 Dec '11

Thanks Timo, this patch applied clean against 2.0.16 just running it on live for the past few minutes & seems to have fixed the issues. Mark ________________________________________ From: Mark Zealey Sent: 08 December 2011 07:14 To: Timo Sirainen Cc: dovecot(a)dovecot.org Subject: RE: [Dovecot] sql dict: commit failed: MySQL server has gone away Correct we're not enforcing the quotas at present just want an easy way to monitor everyone's mailbox usage. Thanks for the patch; will it work ok against 2.0.16? if so I'll recompile and give it a test today. Mark

1 0

[Dovecot] 2.1.rc1 (1e118913348b): Panic: file mail-user.c: line 128 (mail_user_ref): assertion failed: (user->refcount > 0)
by Pascal Volk 08 Dec '11

08 Dec '11

Hi Timo, right after delivering the message to the INBOX the lmtp crashes. I wonder about the "Sent" in the attached backtrace. Regards, Pascal -- The trapper recommends today: c01dcofe.1134117(a)localdomain.org

2 2