March 2012 - dovecot - dovecot.org

[Dovecot] dovecot and cloudfile systems
by jackie sparks 24 Mar '12

24 Mar '12

I'm trying to store mailboxes in a cloudfile system and I am running into alot of problems using courier, between time skew, file locking and cache creation problems. I was wondering if dovecot has any problems using maildirs across a limited fuse file system. I cant lock files, This is accessed using the fuse library. I thought taking out the standard checking for return values would be a work around because everything imap daemon is doing can be done from a shell by hand except filelocking and setting times on files. I am doing this on Rack Spaces cloud files. This is something that not many if any are doing. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--=-=-= This e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. Sections 2510-2521, is confidential, and is intended solely for the use of the individuals or entities to whom it is addressed. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, printing, or copying of this e-mail and any file attachments is strictly prohibited. If you have received this e-mail in error, please immediately notify me by email at jackie.craig.sparks(a)live.com. You must destroy the original transmission and its contents.

2 3

Re: [Dovecot] kernel problem in RedHat? -- RH specific, or what linux kernels does this affect?
by Linda Walsh 24 Mar '12

24 Mar '12

Is this redhat's version of the kernel only? Or does it apply to other linux kernels and other distros? Any idea what linux kernel versions might cause this? (from main dovecot webpage news) Thu Mar 22 14:38:53 EET 2012 Red Hat/CentOS users: A recent kernel update <https://bugzilla.redhat.com/show_bug.cgi?id=681578> causes Dovecot to start failing after it has reached 1000 child processes. To fix this, downgrade your kernel until Red Hat releases a fixed kernel.

2 1

[Dovecot] Problems with upgrade 2.0.16 -> 2.1.3
by Joseph Tam 24 Mar '12

24 Mar '12

I ran into two issues trying to upgrade our dovecot installation (Solaris 10). 1) Does not compile with OpenSSL 0.9.7 Not a big deal, as I was able to successfully against OpenSSL 0.9.8, but does dovecot require OpenSSL >= 0.9.8 now? libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-test -std=gnu99 -O3 -fomit-frame-pointer -mcpu=ultrasparc -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -MT istream-openssl.lo -MD -MP -MF .deps/istream-openssl.Tpo -c istream-openssl.c -fPIC -DPIC -o .libs/istream-openssl.o iostream-openssl-context.c:9:28: openssl/engine.h: No such file or directory iostream-openssl-context.c: In function `ssl_iostream_deinit_global': iostream-openssl-context.c:431: warning: implicit declaration of function `ENGINE_finish' iostream-openssl-context.c:432: warning: implicit declaration of function `ENGINE_cleanup' ... 2) Dovecot's LDA does not work After stopping the the old dovecot, and starting dovecot 2.1.3 using tghe exact same config file, local mail delivery tempfails: Mar 23 02:51:51 server dovecot: auth: Error: getpeerucred() failed: Bad address Mar 23 02:51:51 server dovecot: auth: Error: userdb connection: Failed to get peer's credentials Mar 23 02:51:51 server dovecot: lda: Error: userdb lookup(j.tam): Disconnected unexpectedly Mar 23 02:51:51 server dovecot: lda: Fatal: Internal error occurred. Refer to server log for more information. # Sendmail reports stat=Deferred: local mailer (/var/dovecot/libexec/dovecot-lda) exited with EX_TEMPFAIL After seeing 2) in the logs, I had to revert back to 2.0.16. Any hints on what could be wrong? Joseph Tam <jtam.home(a)gmail.com> # 2.0.16: /var/dovecot/etc/dovecot/dovecot.conf # OS: SunOS 5.10 sun4u nfs auth_cache_negative_ttl = 10 mins auth_cache_size = 64 k auth_cache_ttl = 1 days auth_failure_delay = 5 secs auth_master_user_separator = * auth_socket_path = /var/dovecot/run/auth-userdb auth_username_chars = abcdefghijklmnopqrstuvwxyz01234567890.-_ auth_worker_max_count = 1 base_dir = /var/dovecot/run default_vsz_limit = 64 M deliver_log_format = first_valid_gid = 10000 first_valid_uid = 10000 hostname = our.mail.domain last_valid_gid = 19999 last_valid_uid = 19999 lda_mailbox_autocreate = yes log_timestamp = login_greeting = Ready. mail_location = mbox:/nfs/home/%n/mail:INBOX=/nfs/mail/%n:INDEX=/data/dc-cache/%n mail_nfs_storage = yes mail_temp_dir = /var/tmp mbox_very_dirty_syncs = yes mbox_write_locks = dotlock_try fcntl namespace { inbox = yes location = prefix = separator = / } namespace { hidden = yes list = no location = prefix = / separator = / } namespace { hidden = yes list = no location = prefix = ~/mail/ separator = / } namespace { hidden = yes list = no location = prefix = mail/ separator = / } passdb { args = /var/dovecot/etc/master-users driver = passwd-file master = yes pass = yes } passdb { args = /var/yp/etc/passwd driver = passwd-file } postmaster_address = MAILER-DAEMON(a)our.mail.domain protocols = imap pop3 sendmail_path = /usr/lib/sendmail service auth-worker { user = dovecot } service auth { idle_kill = 1 hours } service imap-login { process_limit = 2 service_count = 0 } service imap { process_limit = 512 } service pop3-login { process_limit = 1 service_count = 0 } service pop3 { process_limit = 64 } shutdown_clients = no ssl_cert = </var/dovecot/etc/ssl/imap.pem ssl_key = </var/dovecot/etc/ssl/imap.pem syslog_facility = local0 userdb { args = /var/dovecot/etc/passwd driver = passwd-file } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep imap_id_log = * mail_max_userip_connections = 12 ssl_cert = </var/dovecot/etc/ssl/imap.pem ssl_key = </var/dovecot/etc/ssl/imap.pem } protocol pop3 { mail_max_userip_connections = 3 pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_logout_format = io=%i/%o top=%t/%p, retr=%r/%b, del=%d/%m, size=%s uid=%u pop3_reuse_xuidl = yes ssl_cert = </var/dovecot/etc/ssl/pop.pem ssl_key = </var/dovecot/etc/ssl/pop.pem }

2 2

Re: [Dovecot] Dovecot 2.1.3 Proxy creates mailbox on proxy
by Ed Nitido 23 Mar '12

23 Mar '12

Ooops, didn't email the list... it working now thanks to Timo, solution below On Fri, Mar 23, 2012 at 4:14 PM, Timo Sirainen <tss(a)iki.fi> wrote: > >> On 23.3.2012, at 22.01, Ed Nitido wrote: >> >> > pass_attrs = >> uid=user,userPassword=password,=proxy,=master=doveadmin,=pass=xxxxxx >> >> I guess it doesn't like the "=proxy" part. I guess I should fix it. For >> now just set "=proxy=y". >> > >

1 0

[Dovecot] Advice for new dovecot / imap proxy? setup
by Luca Lesinigo 23 Mar '12

23 Mar '12

Hello list. I'm planning a new mail servers for our company's customers to replace the oldish Courier-IMAP based one, we already started to deploy some mail accounts on a dovecot-2.0 server as an early test. I'd like to implement the new system with dovecot-2 (I'll probably go straight to dovecot-2.1.x) and I'd like to get it right from the beginning so I'm here asking for some advice. The issue I'm investigating right now is how to manage a single IMAP / POP / SMTP / webmail "entry point" for multiple mail servers... in other words an IMAP proxy. It would be desirable for multiple reasons: - graceful migration from the current system: we'd make the mailserver hostname point to the proxy (along with its SSL certificates) and then the proxy would route each domain to the correct IMAP non-ssl server on our LAN. No need to update customer's systems configuration and we can move one domain at a time from the old to the new server, behind the scenes - be ready for similar migrations in the future (eg. right now we're still keeping the imap servers with the qmail MTA, but we'd like to switch to postfix+dovecot in the future) - be ready for sharding mail domains on multiple IMAP servers (if/when current hardware reach its capacity or needs to be swapped out for new gear) - be ready to serve traffic over IPv6 without touching our precious mailbox servers - isolate the mailbox servers from direct external access and just run IMAP on them, let other systems run ssl, pop3, smtp, webmail, etc... Ideally the 'proxy' system would run dovecot imap and pop3 (SSL protected) and Roundcube webmail (PHP, on https) and just speak IMAP to the underlying mail servers on our internal LAN. We'd like to support all the recent IMAP goodies to make modern users happy (IMAP IDLE, LEMONADE, etc) and possibly implement Maildir quota on the new backend mailbox server to improve our operations (currently we just run du in a cronjob once a day on the current mailserver, IMAP clients including the webmail do not know about quota and thus cannot show amount of free space). In addition to that, customer's will hit the SMTP server running on that 'proxy' system and this is good to keep its configuration separated from the SMTP server of the actual mail servers (which has a different configuration and is restricted to get connections only from our MX systems and not from outside sources). I'd like to know if that plan sounds reasonable or if there's something stupid in it. Also, is the proxy going to support all kind of IMAP stuff of the backend server (IDLE, CONDSTORE, Maildir quota, immediate notification of IDLE clients thanks to linux inotify, etc...) or will it limit me somehow? thanks, -- Luca Lesinigo

4 5

[Dovecot] Dovecot 2.1.3 Proxy creates mailbox on proxy
by Ed Nitido 23 Mar '12

23 Mar '12

Hey all, I've upgraded from a working Dovecot 2.0.17 Proxy with a master user setup to Dovecot 2.1.3 and I've merged my conf settings from 2.0.17 into 2.1.3. I'm able to start up dovecot proxy and telnet localhost, however it creates the users home director on the proxy server instead of going to the backend dovecot server (which has already been successfully upgraded to 2.1.3 from 2.0.17). In my old 2.0.17, I had the entire namespace section commented out in 10-mail.conf. To achieve the same in 2.1.3 I had to remove the file 15-mailboxes.conf, otherwise my error log would have the following if I just commented out the namespace section and left that file in place: *Error: user edward(a)dev.domain.com: Initialization failed: namespace configuration error: inbox=yes namespace missing* *Error: Invalid user settings. Refer to server log for more information.* So now I'm trying to figure out why the proxy doesn't get the mail server IP from director, when doveadm has the backend server listed *# doveadm director status* *mail server ip vhosts users* *192.168.12.205 100 0* Can anyone see something I've missed? Here's my doveconf output: # 2.1.3: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-openvz-amd64 i686 Debian 6.0.4 auth_debug = yes auth_debug_passwords = yes auth_master_user_separator = * auth_mechanisms = plain login auth_socket_path = /usr/local/var/run/dovecot/auth-master auth_verbose = yes debug_log_path = /var/log/dovecot-debug.log director_doveadm_port = 542 director_mail_servers = 192.168.12.205 director_servers = 192.168.12.209 disable_plaintext_auth = no info_log_path = /var/log/dovecot-info.log listen = * lmtp_proxy = yes log_path = /var/log/dovecot-err.log mail_debug = yes mail_gid = vmail mail_location = maildir:%h/Maildir mail_plugins = " quota" mail_uid = vmail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave passdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile acl_shared_dict = file:/home/%d/shared-mailboxes quota = maildir:User quota quota_rule = *:storage=1G sieve = %h/.dovecot.sieve sieve_dir = ~/sieve sieve_max_actions = 32 sieve_max_redirects = 4 sieve_max_script_size = 1M sieve_quota_max_scripts = 0 sieve_quota_max_storage = 0 } postmaster_address = postmaster(a)dev.domain.com protocols = imap pop3 lmtp sieve quota_full_tempfail = yes service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { mode = 0666 user = dovecot } } service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { port = 541 } inet_listener { port = 542 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director inet_listener imap { port = 143 } } service lmtp { inet_listener lmtp { port = 24 } unix_listener /var/spool/postfix/private/dovecot-lmtp { user = postfix } } service managesieve-login { executable = managesieve-login director inet_listener sieve { port = 4190 } process_min_avail = 0 service_count = 1 vsz_limit = 64 M } service pop3-login { executable = pop3-login director inet_listener pop3 { port = 110 } } ssl_cert = </usr/local/etc/dovecot/dovecot.pem ssl_key = </usr/local/etc/dovecot/dovecot.key userdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf.ext driver = ldap } userdb { args = uid=vmail gid=vmail home=/home/%d/%u driver = static } verbose_proctitle = yes protocol lmtp { auth_socket_path = /usr/local/var/run/dovecot/director-userdb mail_plugins = " quota quota sieve" passdb { args = proxy=y nopassword=y port=24 driver = static } } protocol lda { info_log_path = /var/log/dovecot-lda.log log_path = /var/log/dovecot-lda-errors.log mail_plugins = " quota sieve" } protocol imap { mail_plugins = " quota imap_quota imap_acl acl" } protocol sieve { mail_max_userip_connections = 10 mail_plugins = managesieve_implementation_string = Dovecot Pigeonhole managesieve_logout_format = bytes=%i/%o managesieve_max_compile_errors = 5 managesieve_max_line_length = 65536 managesieve_notify_capability = managesieve_sieve_capability = } protocol pop3 { mail_plugins = " quota quota" pop3_fast_size_lookups = no pop3_uidl_format = %08Xu%08Xv }

2 2

[Dovecot] dovecot 2.1.3 dsync Unexpected finish reply
by Micah Anderson 23 Mar '12

23 Mar '12

I've been moving users from one system to another by doing a dsync mirror operation. The first dsync mirror takes some time, because of the number of users involved, so I am doing an initial sync, and then I direct the users to the new location and do a final 'freshening' sync to get any changes that happened during the longer sync. The problem seems to be with this freshening sync, it seems quite fragile breaking with things like: dsync-local(user(a)example.com): Error: msg-get failed: box=Spam uid=3034 guid=1ad456015ae9694f083b00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69096 guid=c22b541a71e4694fc93700001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69097 guid=4b6d6b13d0e9694f505700001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69098 guid=175b1c2e4aea694fc97100001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69099 guid=bfb08c1b3bee694f133e00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69100 guid=fa5d630c17ef694fa75f00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69101 guid=7ca96011dcef694f3f0400001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69102 guid=ef547107eff1694ff96700001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69103 guid=5597bc0519f2694f2e7000001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69104 guid=8336a53a54f5694fb21000001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69105 guid=96169d13c8fd694f831800001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69106 guid=af21a5183f036a4f263200001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69107 guid=d0fde3348e036a4ff44000001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69108 guid=4ce01d1a59056a4fee2200001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69109 guid=497f96066e056a4f322700001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69110 guid=ef34f505c0066a4fc26b00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69111 guid=81adcb2c6e076a4f751100001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69112 guid=a110841e8a076a4fa21500001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69113 guid=60d8e70a970d6a4fae2100001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69114 guid=7c6cb41572106a4ff13c00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69115 guid=aaf4d32b2f126a4ff21000001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69116 guid=ab52f43a58126a4ffd1800001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69117 guid=eb543a2179186a4fe45800001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69118 guid=cd7cb408a12a6a4f272100001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69119 guid=2ec02e2ef2326a4f9e1100001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69120 guid=e7a4552ff8336a4f7f6700001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69121 guid=0724b023d33a6a4f1b3300001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69122 guid=9985c91afe3b6a4f127100001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69123 guid=9300751b913d6a4f7a4000001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69124 guid=822ff806ae3f6a4f293b00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69125 guid=eac8ed1f2b426a4f164200001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69126 guid=4109561ae3426a4ff26700001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69127 guid=30bc832e5e496a4f563600001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69128 guid=c0b36410bd4b6a4f102b00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69129 guid=38a9d41a534d6a4ff40200001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69130 guid=b8e84d239b4d6a4fd11000001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69131 guid=f060ef22154f6a4f2b5c00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69132 guid=e2999c107c4f6a4f5a7600001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69133 guid=8d09280aae506a4f073500001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69134 guid=43d7ec3aa6556a4f963a00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69135 guid=c5800130d2556a4f594200001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69136 guid=83a91e08b4566a4f197100001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69137 guid=50cf9721f95e6a4f7e4400001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69138 guid=fda2a82886606a4f881700001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69139 guid=97ee1d1ad1636a4fc94d00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69140 guid=4f50671f85666a4f306100001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69141 guid=0fea590fb4666a4f7a6b00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69142 guid=f3210b02a5676a4ffa1f00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69143 guid=8d325a06686a6a4f2b3600001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69144 guid=0cbf1839f1756a4f8f6800001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69145 guid=d6209a2898796a4f671a00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69146 guid=576ade31da7d6a4f5f5700001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69147 guid=70a15b34247e6a4f445a00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69148 guid=3ff92631cd886a4ffd6300001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69149 guid=3ff2081568916a4f134d00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69150 guid=d1a67b0907ab6a4f546000001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69151 guid=3d4cb1197ee96a4fbf5f00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=INBOX uid=69152 guid=aae2542818266b4f7d1e00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=sent-mail uid=2077 guid=c5a0930248e8694fb77c00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=sent-mail uid=2078 guid=dce63e1a6bee694f470200001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=sent-mail uid=2079 guid=dde63e1a6bee694f470200001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=sent-mail uid=2080 guid=dee63e1a6bee694f470200001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=sent-mail uid=2081 guid=dfe63e1a6bee694f470200001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=sent-mail uid=2082 guid=a110b53585056a4fe81b00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=sent-mail uid=2083 guid=a210b53585056a4fe81b00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=sent-mail uid=2084 guid=93afeb1f7d0b6a4f694e00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=sent-mail uid=2085 guid=ef2bb1098a2e6a4fcf1b00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=sent-mail uid=2086 guid=d8ba601bee2e6a4f982f00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=sent-mail uid=2087 guid=d9ba601bee2e6a4f982f00001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=sent-mail uid=2088 guid=7e5b483b433d6a4fd93600001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=sent-mail uid=2089 guid=7f5b483b433d6a4fd93600001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=sent-mail uid=2090 guid=b08c5205ba646a4f106700001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=sent-mail uid=2091 guid=805b483b433d6a4fd93600001d12b59f dsync-local(user(a)example.com): Error: msg-get failed: box=sent-mail uid=2092 guid=815b483b433d6a4fd93600001d12b59f dsync-local(user(a)example.com): Error: Unexpected finish reply: by ims-d13.mx.aol.com (8.14.1/8.14.1) with ESMTP id q2LEhqXZ017169; dsync-local(user(a)example.com): Error: Unexpected reply from server: Wed, 21 Mar 2012 10:43:52 -0400 dsync-local(user(a)example.com): Warning: Mailbox changes caused a desync. You may want to run dsync again. those final "Unexpected finish reply" and "Unexpected reply from server" are a bit surprising results. Running dsync again seems to resolve things, but there seems to be a bug here that is causing unexpected results to leak through to the dsync process? thanks, micah

1 1

Re: [Dovecot] sysconfdir depreacted
by Joseph Tam 23 Mar '12

23 Mar '12

On Fri, 23 Mar 2012, dovecot-request(a)dovecot.org wrote: >> See http://dovecot.org/list/dovecot/2009-January/036131.html > > Yes, I was also thinking about that, but it's about removing the > dovecot/ suffix from other directories as well. That might be > something worth doing (--without-package-suffix or something?). +1. I fake it now with symlinks (e.g. etc/dovecot -> .). Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] Dovecot v2.1.3 (f30437ed63dc) Auth/Login Issues
by Thomas Leuxner 23 Mar '12

23 Mar '12

Hi, some change between ff5c341f8838 and f30437ed63dc seems to have broken auth: => Bad Login Mar 23 09:01:46 spectre dovecot: master: Dovecot v2.1.3 (f30437ed63dc) starting up [...] Mar 23 10:25:44 spectre dovecot: auth: Debug: auth client connected (pid=7266) Mar 23 10:25:45 spectre dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=imap#011secured#011lip=188.138.0.199#011rip=80.187.102.243#011lport=143#011rport=62388#011resp=<hidden> Mar 23 10:25:45 spectre dovecot: auth: Debug: cache(tlx(a)leuxner.net,80.187.102.243): hit: <hidden>#011userdb_quota_rule=*:storage=5G#011userdb_acl_groups=PublicMailboxAdmins Mar 23 10:25:45 spectre dovecot: auth: Debug: client out: OK#0111#011user=tlx(a)leuxner.net Mar 23 10:25:45 spectre dovecot: auth: Debug: master in: REQUEST#0113958898689#0117266#0111#011bfc44f32051961b909e2b458440d645f Mar 23 10:25:45 spectre dovecot: auth: Debug: userdb-cache(tlx(a)leuxner.net,80.187.102.243): hit: tlx@leuxner.net#011uid=5000#011gid=5000#011home=/var/vmail/domains/leuxner.net/tlx#011quota_rule=*:storage=5G#011acl_groups=PublicMailboxAdmins Mar 23 10:25:45 spectre dovecot: auth: Debug: master out: USER#0113958898689#011tlx@leuxner.net#011uid=xxx#011gid=xxx#011home=/var/vmail/domains/leuxner.net/tlx#011quota_rule=*:storage=5G#011acl_groups=PublicMailboxAdmins Mar 23 10:25:45 spectre dovecot: imap-login: Login: user=<tlx(a)leuxner.net>, method=PLAIN, rip=80.187.102.243, lip=188.138.0.199, mpid=7267, TLS Mar 23 10:25:45 spectre dovecot: imap(tlx(a)leuxner.net): Connection closed in=0 out=319uthentication/login: => Good Login Mar 23 10:26:37 spectre dovecot: master: Dovecot v2.1.3 (ff5c341f8838) starting up [...] Mar 23 10:27:18 spectre dovecot: auth: Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Mar 23 10:27:18 spectre dovecot: auth: Debug: auth client connected (pid=9832) Mar 23 10:27:19 spectre dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=imap#011secured#011lip=188.138.0.199#011rip=80.187.102.243#011lport=143#011rport=51647#011resp=<hidden> Mar 23 10:27:19 spectre dovecot: auth: Debug: cache(tlx(a)leuxner.net,80.187.102.243): miss Mar 23 10:27:19 spectre dovecot: auth: Debug: passwd-file /var/vmail/auth.d/leuxner.net/passwd: Read 1 users in 0 secs Mar 23 10:27:19 spectre dovecot: auth: Debug: passwd-file(tlx(a)leuxner.net,80.187.102.243): lookup: user=tlx(a)leuxner.net file=/var/vmail/auth.d/leuxner.net/passwd Mar 23 10:27:19 spectre dovecot: auth: Debug: client out: OK#0111#011user=tlx(a)leuxner.net Mar 23 10:27:19 spectre dovecot: auth: Debug: master in: REQUEST#0113656384513#0119832#0111#0114782efcbd0324b228bb85aaae916cfe6 Mar 23 10:27:19 spectre dovecot: auth: Debug: userdb-cache(tlx(a)leuxner.net,80.187.102.243): miss Mar 23 10:27:19 spectre dovecot: auth: Debug: passwd-file(tlx(a)leuxner.net,80.187.102.243): lookup: user=tlx(a)leuxner.net file=/var/vmail/auth.d/leuxner.net/passwd Mar 23 10:27:19 spectre dovecot: auth: Debug: master out: USER#0113656384513#011tlx@leuxner.net#011uid=xxx#011gid=xxx#011home=/var/vmail/domains/leuxner.net/tlx#011quota_rule=*:storage=5G#011acl_groups=PublicMailboxAdmins Mar 23 10:27:19 spectre dovecot: imap-login: Login: user=<tlx(a)leuxner.net>, method=PLAIN, rip=80.187.102.243, lip=188.138.0.199, mpid=9835, TLS Regards Thomas

1 0

[Dovecot] 2.1.2 (pop3|imap)-login crash
by Luca Palazzo 22 Mar '12

22 Mar '12

Hi Timo, hi all, after upgrading my server (both backends and load balancer) to 2.1.2 (from 2.0.17), I'm getting a log of login processes crashed in load balancer. Log lines are like: Mar 20 10:05:45 mailgw-lb dovecot: pop3-login: Fatal: master: service(pop3-login): child 27764 killed with signal 11 (core dumps disabled) Mar 20 10:06:17 mailgw-lb dovecot: imap-login: Fatal: master: service(imap-login): child 28468 killed with signal 11 (core dumps disabled) Stack trace of a crashed process is like: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1220163904 (LWP 27764)] 0xb77cd176 in ssl_proxy_is_handshaked (proxy=0x0) at ssl-proxy-openssl.c:710 710 { (gdb) bt #0 0xb77cd176 in ssl_proxy_is_handshaked (proxy=0x0) at ssl-proxy-openssl.c:710 #1 0xb77c7295 in client_get_log_str (client=0x807b830, msg=0x804e290 "proxy(aaaaaa(a)dddddd.it): disconnecting x.x.x.x (Disconnected by server)") at client-common.c:469 #2 0xb77c73c6 in client_log (client=0x807b830, msg=0x804e290 "proxy(aaaaaaa(a)dddddd.it): disconnecting x.x.x.x (Disconnected by server)") at client-common.c:553 #3 0xb77c9a45 in login_proxy_free_reason (_proxy=<value optimized out>, reason=0x804e248 "Disconnected by server") at login-proxy.c:373 #4 0xb77ca9b5 in server_input (proxy=0x0) at login-proxy.c:93 #5 0xb7793762 in io_loop_call_io (io=0x8094180) at ioloop.c:380 #6 0xb7794cc9 in io_loop_handler_run (ioloop=0x8055480) at ioloop-epoll.c:213 #7 0xb77936f9 in io_loop_run (ioloop=0x8055480) at ioloop.c:399 #8 0xb777e4c8 in master_service_run (service=0x80553b0, callback=0xb77cc110 <client_connected>) at master-service.c:544 #9 0xb77cbcee in login_binary_run (binary=0x804ad80, argc=2, argv=0x80551c0) at main.c:406 #10 0x08049812 in main (argc=0, argv=0x0) at client.c:303 The strange part of the story is that not all process crash. I'm trying to figure out if only TLS/SSL process crash. Any idea? Thanks Luca

2 5