- dovecot - dovecot.org

[Dovecot] dovecot not logging after upgrade to 2.1.7 on debian
by Steinar Bang 09 May '13

09 May '13

After upgrading my IMAP server to the new debian stable, and upgrading dovecot from 1.x to 2.1.7 in the process, dovecot no longer logs anything to /var/log/mail.*. The last entries there are from before the upgrade, and no starts or error messages or failed login attempts, since then, have been logged. Does anyone know what might cause this? "doveconf -n" doesn't mention any of the log settings. Maybe the log settings aren't picked up? What could be done to make sure they are picked up? Here's the content of the /etc/dovecot/conf.d/10-logging.conf file: ## ## Log destination. ## # Log file to use for error messages. "syslog" logs to syslog, # /dev/stderr logs to stderr. log_path = syslog # Log file to use for informational messages. Defaults to log_path. #info_log_path = # Log file to use for debug messages. Defaults to info_log_path. #debug_log_path = # Syslog facility to use if you're logging to syslog. Usually if you don't # want to use "mail", you'll use local0..local7. Also other standard # facilities are supported. syslog_facility = mail ## ## Logging verbosity and debugging. ## # Log unsuccessful authentication attempts and the reasons why they failed. #auth_verbose = no # In case of password mismatches, log the attempted password. Valid values are # no, plain and sha1. sha1 can be useful for detecting brute force password # attempts vs. user simply trying the same password over and over again. #auth_verbose_passwords = no # Even more verbose logging for debugging purposes. Shows for example SQL # queries. #auth_debug = no # In case of password mismatches, log the passwords and used scheme so the # problem can be debugged. Enabling this also enables auth_debug. #auth_debug_passwords = no # Enable mail process debugging. This can help you figure out why Dovecot # isn't finding your mails. #mail_debug = no # Show protocol level SSL errors. #verbose_ssl = no # mail_log plugin provides more event logging for mail processes. plugin { # Events to log. Also available: flag_change append #mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename # Available fields: uid, box, msgid, from, subject, size, vsize, flags # size and vsize are available only for expunge and copy events. #mail_log_fields = uid box msgid size } ## ## Log formatting. ## # Prefix for each line written to log file. % codes are in strftime(3) # format. #log_timestamp = "%b %d %H:%M:%S " # Space-separated list of elements we want to log. The elements which have # a non-empty variable value are joined together to form a comma-separated # string. #login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c # Login log format. %$ contains login_log_format_elements string, %s contains # the data we want to log. #login_log_format = %$: %s # Log prefix for mail processes. See doc/wiki/Variables.txt for list of # possible variables you can use. #mail_log_prefix = "%s(%u): " # Format to use for logging mail deliveries. You can use variables: # %$ - Delivery status message (e.g. "saved to INBOX") # %m - Message-ID # %s - Subject # %f - From address # %p - Physical size # %w - Virtual size #deliver_log_format = msgid=%m: %$

4 6

[Dovecot] Released Pigeonhole v0.3.5 for Dovecot v2.1.16
by Stephan Bosch 09 May '13

09 May '13

Hello Dovecot users, Before I release the first version of Pigeonhole v0.4, I quickly release a few small but important fixes for Pigeonhole v0.3. Changelog v0.3.5: - Sieve editheader extension: fixed interaction with the Sieve body extension. If used together, the deleteheader action could fail after a body test was performed. - Test suite: fixed a time zone dependency in the Sieve date extension tests. The release is available as follows: http://www.rename-it.nl/dovecot/2.1/dovecot-2.1-pigeonhole-0.3.5.tar.gz http://www.rename-it.nl/dovecot/2.1/dovecot-2.1-pigeonhole-0.3.5.tar.gz.sig Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this new release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

[Dovecot] Permission problem with LDA and dovecot 2.2.1
by Tobi 09 May '13

09 May '13

Hello list today I built dovecot 2.2.1 from sources. But I have permission problems with LDA The "normal" imap part works fine, users can login and see their boxes. deliver is called as LDA from postfix master.cf as follows << dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/local/libexec/dovecot/deliver -f ${sender} -d ${user}@${nexthop} >> but when I try to send a testmail then I get the following in the logs << 2013 May 6 18:37:59 nordkap lda: Fatal: Internal error occurred. Refer to server log for more information. May 6 18:37:59 nordkap dovecot: lda: Error: userdb lookup: connect(/var/run/dovecot/auth-userdb) failed: Connection refused May 6 18:37:59 nordkap dovecot: lda: Fatal: Internal error occurred. Refer to server log for more information. >> For me it looks odd because the auth-userdb is defined as << base_dir = /usr/local/var/run/dovecot/ service auth { unix_listener auth-userdb { mode = 0777 user = vmail group = vmail } .... >> The rights on the file should be correct according to the config above << ls -al /usr/local/var/run/dovecot/auth-userdb srwxrwxrwx 1 vmail vmail 0 May 6 20:11 /usr/local/var/run/dovecot/auth-userdb >> I cannot explain why the lda tries to access << Error: userdb lookup: connect(/var/run/dovecot/auth-userdb) >> I grepped through all the configfiles but could not find the "wrong" path from the error message above. Would it might be a "fix" to symlink /usr/local/var/run/dovecot to /var/run/dovecot ? Or would that break something with dovecot? Thanks for any hint or idea tobi

5 12

[Dovecot] SSL problems on dovecot 2.1.7
by Steinar Bang 09 May '13

09 May '13

When I upgraded my debian-based imap server from squeeze to wheezy yesterday, SSL stopped working. I am using a http://cacert.org signed server sertificate, and I am reusing the certificates that were used on the 1.x dovecot of debian squeeze. My three MUAs that worked against the previous 1.x dovecot with the same certificate, now fails in various ways. Any hints and guesses as to how to debug this further will be highly appreciated. Even more appreciated will be a pin point of the issue. :-) Here are the error messages from the MUAs: - Opera 12.15 on Windows 7 just reports: "The connection with the IMAP server was unexpectedly interrupted." - Emacs24(w/linked-in gnutls)/Ma Gnus 0.8 (Gnus git HEAD) on Windows 7 says "imap.mydomain.com certificate could not be verified." - Emacs23/Ma Gnus 0.8 (also Gnus git HEAD) on debian testing (with Emacs23 gnutls-cli is run in a subprocess), says: "Opening connection to imap.mydomain.com via tls... Opening TLS connection to `imap.mydomain.com'... Opening TLS connection with `gnutls-cli --insecure -p 993 imap.mydomain.com'...done Opening TLS connection to `imap.mydomain.com'...done Unable to open server nnimap+privat due to: Process *nnimap* not running" When I try running gnutls-cli from the command line of the debian testing machine (the same gnutls-cli that is used by the emacs23/gnus combo), it seems to connect ok (the transcript of that session is below). The config for the SSL, from /etc/dovecot/conf.d/10-ssl.conf, is: # SSL/TLS support: yes, no, required. <doc/wiki/SSL.txt> ssl = yes # PEM encoded X.509 SSL/TLS certificate and private key. They're opened before # dropping root privileges, so keep the key file unreadable by anyone but # root. Included doc/mkcert.sh can be used to easily generate self-signed # certificate, just make sure to update the domains in dovecot-openssl.cnf ssl_cert = </etc/ssl/certs/imap_mydomain_com.pem ssl_key = </etc/ssl/private/imap_mydomain_com.key The access privileges of the files, are: -rw-r--r-- 1 root root 2077 Mar 27 12:45 /etc/ssl/certs/imap_mydomain_com.pem -rw------- 1 root root 3243 Jul 12 2011 /etc/ssl/private/imap_mydomain_com.key What follows, is the transcript from the gnutls-cli session from a debian testing machine to the server (which seems to be working as far as I can tell...): sb@edwards:~$ gnutls-cli -p 993 rainey.mydomain.com WARNING: gnome-keyring:: couldn't connect to: /home/sb/.cache/keyring-yeEdM3/pkcs11: No such file or directory Resolving 'rainey.mydomain.com'... Connecting to '212.110.185.190:993'... - Ephemeral Diffie-Hellman parameters - Using prime: 1024 bits - Secret key: 1023 bits - Peer's public key: 1023 bits - Certificate type: X.509 - Got a certificate list of 1 certificates. - Certificate[0] info: - subject `CN=imap.mydomain.com', issuer `O=Root CA,OU=http://www.cacert.org,CN=CA Cert Signing Authority,EMAIL=support(a)cacert.org', RSA key 4096 bits, signed using RSA-SHA1, activated `2013-03-27 12:43:30 UTC', expires `2013-09-23 12:43:30 UTC', SHA-1 fingerprint `86f8a501bca1e2b0eadc677bf05b103d298ce247' - The hostname in the certificate does NOT match 'rainey.mydomain.com' sb@edwards:~$ gnutls-cli -p 993 imap.mydomain.com WARNING: gnome-keyring:: couldn't connect to: /home/sb/.cache/keyring-yeEdM3/pkcs11: No such file or directory Resolving 'imap.mydomain.com'... Connecting to '212.110.185.190:993'... - Ephemeral Diffie-Hellman parameters - Using prime: 1024 bits - Secret key: 1022 bits - Peer's public key: 1021 bits - Certificate type: X.509 - Got a certificate list of 1 certificates. - Certificate[0] info: - subject `CN=imap.mydomain.com', issuer `O=Root CA,OU=http://www.cacert.org,CN=CA Cert Signing Authority,EMAIL=support(a)cacert.org', RSA key 4096 bits, signed using RSA-SHA1, activated `2013-03-27 12:43:30 UTC', expires `2013-09-23 12:43:30 UTC', SHA-1 fingerprint `86f8a501bca1e2b0eadc677bf05b103d298ce247' - The hostname in the certificate matches 'imap.mydomain.com'. - Peer's certificate issuer is unknown - Peer's certificate is NOT trusted - Version: TLS1.2 - Key Exchange: DHE-RSA - Cipher: AES-128-CBC - MAC: SHA1 - Compression: NULL - Handshake was completed - Simple Client Mode: * OK Waiting for authentication process to respond.. - Peer has closed the GnuTLS connection

1 0

[Dovecot] dovecot stats
by Jan-Frode Myklebust 09 May '13

09 May '13

I just upgraded one of our servers to dovecot v2.1.16 (ee), and am looking into the stats feature. Am I interpreting the wiki correct in reading that the "doveadm stats dump command" only returns statistics about IMAP commands? Is it possible to collect info about POP3 and LMTP commands also ? Also, is "doveadm stats dump command" telling me the results of all commands that has finished the last stats_command_min_time, or will it maybe contain much more than 1 minute of activity ? -jf

3 5

[Dovecot] AuthenticationFailedException: [IN-USE] Couldn't open INBOX: Permission denied
by Earles, Jill 09 May '13

09 May '13

I've been pouring over the documentation for dovecot, but can't find a solution to this problem. I recently took over administration of the dovecot email service at the University where I work, and things were going smoothly. We've been creating email accounts for use with JIRA, a bug reporting/tracking system, and one day recently, when I tried to add a new account to JIRA, I got this error returned from dovecot: "AuthenticationFailedException: [IN-USE] Couldn't open INBOX: Permission denied" I got help from Atlassian, the creators of JIRA, and they sent me links to some forum posts that said that changing the permissions of that user's /var/mail/ directory to 0600 would solve the problem. I changed that and no longer got the error. Being satisfied that this was a solution, I created a bunch of new email accounts today to replace exchange accounts, and then changed the permissions on all the /var/mail/ directories to 0600. Now I'm getting that error again, even for pre-existing email addresses, including the one that I had previously fixed by changing the permissions the same way. I tried changing some of the older accounts back to 0660, which is what they had before, and I still get the error even after restarting dovecot. JIRA uses POP, port 110, to connect to the dovecot mail server. I've also had the same problem trying to connect from Mac Mail. Our JIRA application is used for tracking issues for the UBC Libraries, and those email addresses are critical for the creation of tickets and adding comments to tickets. I am at a loss for what to do. Can anyone help? Thank you very much for your time. # dovecot -n # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-131.0.15.el6.x86_64 x86_64 Red Hat Enterprise Linux Server release 6.4 (Santiago) auth_debug = yes auth_debug_passwords = yes disable_plaintext_auth = no mail_access_groups = mail mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u mail_privileged_group = mail mbox_write_locks = fcntl passdb { driver = pam } ssl_cert = </etc/pki/dovecot/certs/server.crt ssl_key = </etc/pki/dovecot/private/server.key userdb { driver = passwd } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } Here's an except of the maillog from a recent attempt: May 8 17:46:49 moose dovecot: auth: Debug: pam(lib.sysadmin,{ip removed}): lookup service=dovecot May 8 17:46:49 moose dovecot: auth: Debug: pam(lib.sysadmin,{ip removed}): #1/1 style=1 msg=Password: May 8 17:46:49 moose dovecot: auth: Debug: client out: OK#0111#011user=lib.sysadmin May 8 17:46:49 moose dovecot: auth: Debug: master in: REQUEST#0111028653057#01128298#0111#011a60ed90501af39d7e353a14e027255cd May 8 17:46:49 moose dovecot: auth: Debug: passwd(lib.sysadmin,{ip removed}): lookup May 8 17:46:49 moose dovecot: auth: Debug: master out: USER#0111028653057#011lib.sysadmin#011system_groups_user=lib.sysadmin#011uid=523#011gid=524#011home=/home/lib.sysadmin May 8 17:46:49 moose dovecot: pop3-login: Login: user=<lib.sysadmin>, method=PLAIN, rip={ip removed}, lip={ip removed}, mpid=28302 May 8 17:46:49 moose dovecot: pop3(lib.sysadmin): Error: stat(/var/spool/mail/lib.sysadmin) failed: Permission denied May 8 17:46:49 moose dovecot: pop3(lib.sysadmin): Error: stat(/var/spool/mail/lib.sysadmin) failed: Permission denied May 8 17:46:49 moose dovecot: pop3(lib.sysadmin): Error: Couldn't open INBOX: Permission denied May 8 17:46:49 moose dovecot: pop3(lib.sysadmin): Couldn't open INBOX top=0/0, retr=0/0, del=0/0, size=0 May 8 17:46:50 moose dovecot: auth: Debug: auth client connected (pid=28303) May 8 17:46:50 moose dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=pop3#011lip={ip removed}#011rip={ip removed}#011lport=110#011rport=64420#011resp=AGJ2YXV3LnJlbGFpcwByM2xAaXMuYnZAdXc=

2 8

[Dovecot] change inbox dotlock name
by Chris Saldanha 08 May '13

08 May '13

Hi, Is there a configuration element that would allow me to change the dot-lock name for the user's /var/mail inbox when it is locked? dovecot (correctly) acquires <username>.lock, but I'm having a problem with procmail where some obscure code path is preventing procmail's acquisition of a lock when it's that default name in /var/mail. The issue is not permissions (using a world-writeable and sticky-bit config for /var/mail). I'll dig into the procmail code if needed, but if dovecot could use a different filename for such locks, then that would solve my issue. procmail has such an option, and I only need to do this for inboxes. Thanks, Chris -- Chris Saldanha Parliant Corporation

2 1

[Dovecot] sieve redirect envelope address problem
by Костырев Александр Алексеевич 08 May '13

08 May '13

Good day! I have a problem with mail redirection through sieve rules. I've configured sieve rule that redirects any mail coming to user to gmail mailbox (or whatever external mail system there is). But when sieve redirects any mail it puts vmail@%dovecot_hostname% into envelope address, gives it to my exim for delivery and gmail rejects my mail because user vmail@%dovecot_hostname% do not exist. Please, advice for what can be done about this behavior. my `doveconf -n` http://pastebin.com/0dyL9Jgs Thanks in advance! -- С уважением, Костырев Александр администратор Linux-систем

4 4

[Dovecot] CATENATE mis-reads literal after bad URL
by Mike Abbott 08 May '13

08 May '13

Dovecot-2.2.1 plus Timo's recent CATENATE and URLAUTH fixes mishandles literals after bad URLs. (As before remember that the "foobar" text below is really "foobarCRLF" hence the length of 8. Also, last time some MTA discarded an important single leading space character in the snippet I quoted so this time I'm prefixing all the lines to avoid that. In case it's lost again, there's a space before the word "url" below.) | b append inbox catenate (text {8} | + OK | foobar | url /a-bad-url text {8} | b NO [BADURL /a-bad-url] Invalid messagepart IMAP URL. | c noop | d noop | d OK NOOP completed. | e logout | * BYE Logging out | e OK Logout completed. Note that the command with tag "c" is lost. I think it shouldn't be, because the NO was reported to the client without sending a continuation (+ OK) so the client knows not to send the literal. Plus it appears only one line is discarded regardless of the size of the literal.

2 2

[Dovecot] URLAUTH assertion failures in 2.2.1
by Mike Abbott 07 May '13

07 May '13

Testing URLAUTH in dovecot-2.2.1 plus Timo's recent CATENATE and URLAUTH fixes eventually trips some assertions. No simple sequence of commands always hits these; they appear to be timing-dependent. The first one is: May 02 17:47:17 imap(pid 50490 user submit): Panic: file imap-client.c: line 643 (client_command_free): assertion failed: (client->output_cmd_lock == NULL) The line number doesn't match dovecot-2.2.1 due to Apple's unrelated modifications. 0 libsystem_kernel.dylib 0x00007fff8a9f7d4a __pthread_kill + 10 1 libsystem_pthread.dylib 0x00007fff8f728705 pthread_kill + 92 2 libsystem_c.dylib 0x00007fff8f48b17b abort + 125 3 libdovecot.0.dylib 0x000000010db8d2bb default_fatal_finish + 68 4 libdovecot.0.dylib 0x000000010db8df66 i_internal_error_handler + 0 5 libdovecot.0.dylib 0x000000010db8d53d i_panic + 158 6 imap 0x000000010da468fe client_command_free + 446 7 imap 0x000000010da47a33 client_output_cmd + 37 8 imap 0x000000010da46497 client_output + 143 9 libdovecot.0.dylib 0x000000010dba5610 stream_send_io + 53 10 libdovecot.0.dylib 0x000000010db9bc74 io_loop_call_io + 46 11 libdovecot.0.dylib 0x000000010db9cc85 io_loop_handler_run + 214 12 libdovecot.0.dylib 0x000000010db9be1f io_loop_run + 77 13 libdovecot.0.dylib 0x000000010db5b0c6 master_service_run + 24 14 imap 0x000000010da4fa66 main + 1010 15 libdyld.dylib 0x00007fff8f7887bd start + 1 The second one is: May 02 19:23:29 imap(pid 60229 user mja): Panic: file index-mail.c: line 1274 (index_mail_close_streams_full): assertion failed: (!mail->data.destroying_stream) 0 libsystem_kernel.dylib 0x00007fff8a9f7d4a __pthread_kill + 10 1 libsystem_pthread.dylib 0x00007fff8f728705 pthread_kill + 92 2 libsystem_c.dylib 0x00007fff8f48b17b abort + 125 3 libdovecot.0.dylib 0x00000001054c42bb default_fatal_finish + 68 4 libdovecot.0.dylib 0x00000001054c4f66 i_internal_error_handler + 0 5 libdovecot.0.dylib 0x00000001054c453d i_panic + 158 6 libdovecot-storage.0.dylib 0x00000001053aaebb index_mail_close_streams_full + 199 7 libdovecot-storage.0.dylib 0x00000001053aaf29 index_mail_close + 44 8 libdovecot-storage.0.dylib 0x00000001053ab6bd index_mail_free + 48 9 libdovecot-storage.0.dylib 0x000000010538a19a mail_free + 15 10 libdovecot-storage.0.dylib 0x00000001053dd3b3 imap_msgpart_url_free + 65 11 imap 0x000000010532d563 imap_urlauth_fetch_abort_local + 30 12 imap 0x000000010532cb96 imap_urlauth_fetch_abort + 38 13 imap 0x000000010532cb54 imap_urlauth_fetch_deinit + 24 14 imap 0x00000001053218bd cmd_urlfetch_finish + 45 15 imap 0x0000000105321aa3 cmd_urlfetch_continue + 167 16 imap 0x0000000105323ef8 command_exec + 55 17 imap 0x0000000105323a20 client_output_cmd + 18 18 imap 0x0000000105322497 client_output + 143 19 libdovecot.0.dylib 0x00000001054dc610 stream_send_io + 53 20 libdovecot.0.dylib 0x00000001054d2c74 io_loop_call_io + 46 21 libdovecot.0.dylib 0x00000001054d3c85 io_loop_handler_run + 214 22 libdovecot.0.dylib 0x00000001054d2e1f io_loop_run + 77 23 libdovecot.0.dylib 0x00000001054920c6 master_service_run + 24 24 imap 0x000000010532ba66 main + 1010 25 libdyld.dylib 0x00007fff8f7887bd start + 1

2 2

[Dovecot] Dovecot Postfix Quota Policy Service
by Daniel Luttermann 07 May '13

07 May '13

Hallo zusammen, über den Policy Service von Dovecot zum Abfragen der User Quotas wurde ja schon diskutiert - auch gibt es eine gute Anleitung zum Einrichten, nur leider bekomme ich den Policy Server nicht korrekt konfiguriert. Folgende Fehler werden protokolliert: May 3 22:00:13 mail postfix/smtpd[17463]: warning: access table unix:private/quota-status entry has empty value May 3 22:00:42 mail dovecot: quota-status(daniel(a)dlutt.de): Error: user daniel(a)dlutt.de: Error reading configuration: net_connect_unix(/usr/var/run/dovecot/config) failed: Permission denied Es ist dabei so, dass nach einem Reload der Dienste die erste Mail noch zugestellt wird, die folgende, eingehende Mail dann jedoch abgelehnt wird. Nachfolgend die kompletten Logeinträge: May 3 22:00:12 mail postfix/smtpd[17463]: connect from mail-ie0-x236.google.com[2607:f8b0:4001:c03::236] May 3 22:00:13 mail postfix/smtpd[17463]: warning: access table unix:private/quota-status entry has empty value May 3 22:00:13 mail postfix/smtpd[17463]: 0EB81172391A: client=mail-ie0-x236.google.com[2607:f8b0:4001:c03::236] May 3 22:00:13 mail postfix/cleanup[17475]: 0EB81172391A: message-id=<CAKrzS114MaJGND9BxYUiixMMtORmXJqTA3W13B=QAr0YW_nkUg(a)mail.gmail.com> May 3 22:00:13 mail postfix/qmgr[17429]: 0EB81172391A: from=<sender(a)googlemail.com>, size=5409, nrcpt=1 (queue active) May 3 22:00:13 mail postfix/smtpd[17463]: disconnect from mail-ie0-x236.google.com[2607:f8b0:4001:c03::236] May 3 22:00:13 mail klms-smtp_proxy: Message from sender(a)googlemail.com to daniel(a)dlutt.de passed May 3 22:00:14 mail postfix/smtpd[17482]: connect from localhost[127.0.0.1] May 3 22:00:14 mail postfix/smtpd[17482]: 00776172391C: client=localhost[127.0.0.1], orig_client=mail-ie0-x236.google.com[2607:f8b0:4001:c03::236] May 3 22:00:14 mail postfix/cleanup[17475]: 00776172391C: message-id=<CAKrzS114MaJGND9BxYUiixMMtORmXJqTA3W13B=QAr0YW_nkUg(a)mail.gmail.com> May 3 22:00:14 mail postfix/qmgr[17429]: 00776172391C: from=<sender(a)googlemail.com>, size=6195, nrcpt=1 (queue active) May 3 22:00:14 mail postfix/smtpd[17482]: disconnect from localhost[127.0.0.1] May 3 22:00:14 mail postfix/smtp[17476]: 0EB81172391A: to=<daniel(a)dlutt.de>, relay=127.0.0.1[127.0.0.1]:10025, delay=1.2, delays=0.54/0.02/0/0.65, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 00776172391C) May 3 22:00:14 mail postfix/qmgr[17429]: 0EB81172391A: removed May 3 22:00:14 mail dovecot: lmtp(17484): Connect from local May 3 22:00:14 mail dovecot: lmtp(17484, daniel(a)dlutt.de) dEa8BE4XhFFMRAAAG4AjPw: sieve: msgid=<CAKrzS114MaJGND9BxYUiixMMtORmXJqTA3W13B=QAr0YW_nkUg(a)mail.gmail.com>: stored mail into mailbox 'INBOX' May 3 22:00:14 mail dovecot: lmtp(17484): Disconnect from local: Successful quit May 3 22:00:14 mail postfix/lmtp[17483]: 00776172391C: to=<daniel(a)dlutt.de>, relay=mail.dlutt.de[private/dovecot-lmtp], delay=0.11, delays=0.05/0.02/0.01/0.03, dsn=2.0.0, status=sent (250 2.0.0 <daniel(a)dlutt.de> dEa8BE4XhFFMRAAAG4AjPw Saved) May 3 22:00:14 mail postfix/qmgr[17429]: 00776172391C: removed May 3 22:00:36 mail postfix/postscreen[17433]: CONNECT from [2607:f8b0:4001:c03::230]:43653 to [2a00:1828:2000:206::2]:25 May 3 22:00:42 mail postfix/postscreen[17433]: PASS NEW [2607:f8b0:4001:c03::230]:43653 May 3 22:00:42 mail postfix/smtpd[17463]: connect from mail-ie0-x230.google.com[2607:f8b0:4001:c03::230] May 3 22:00:42 mail dovecot: quota-status(daniel(a)dlutt.de): Error: user daniel(a)dlutt.de: Error reading configuration: net_connect_unix(/usr/var/run/dovecot/config) failed: Permission denied May 3 22:00:42 mail postfix/smtpd[17463]: NOQUEUE: reject: RCPT from mail-ie0-x230.google.com[2607:f8b0:4001:c03::230]: 450 4.7.1 <daniel(a)dlutt.de>: Recipient address rejected: Internal error occurred. Refer to server log for more information.; from=<absender(a)googlemail.com> to=<daniel(a)dlutt.de> proto=ESMTP helo=<mail-ie0-x230.google.com> May 3 22:00:42 mail postfix/smtpd[17463]: disconnect from mail-ie0-x230.google.com[2607:f8b0:4001:c03::230] May 3 22:00:53 mail postfix/postfix-script[17560]: stopping the Postfix mail system May 3 22:00:53 mail postfix/master[17425]: terminating on signal 15 May 3 22:02:51 mail dovecot: master: Warning: Killed with signal 15 (by pid=17681 uid=0 code=kill) Das Problem tritt mit dem unix_listener, aber auch mit dem inet_listener auf - beide Male beschwert sich Dovecot über den Zugriff auf den Service "config". Ich habe auch mal versucht, die Berechtigungen für den Service "config" auf World-Readable zu setzen, leider hat dies auch nicht geklappt, wobei ich nicht weiß, ob dieser unbedingt mit dem Problem etwas zu tun hat. Auch beim Debug-Logging sind leider nicht mehr Infos zum Fehler zu finden. Zum Einsatz kommt aktuell Postfix 2.10.0 und Dovecot 2.2.1. Die Dovecot Quota Konfiguration sieht so aus, wie bei sys4 beschrieben: service quota-status { executable = quota-status -p postfix unix_listener /var/spool/postfix/private/quota-status { group = postfix mode = 0660 user = postfix } client_limit = 1 } Mittlerweile habe ich schon einige Optionen und Berechtigungen ausprobiert, aber der Fehler bleibt leider der gleiche. Hat vielleicht jemand noch einen Tip? Danke schon mal. -- Daniel

6 18

[Dovecot] pop3 login ok then disconnects right away..outlook
by markh 07 May '13

07 May '13

I have dovecot with postfix on ubuntu server 12 I cannot log into outgoing server with outlook. It logs into incoming server ok with outlook. I can telnet pop3 and imap ok. Looking at mail log it looks like dovecot auths: ok then shows pop3-login: Login: user=<user> USER#etc ok ... then next line shows..same second pop3(user): disconnected: Logged out top/0/0 etc. I have tried a lot of combinations with ssl ,tls none Any suggestions...thanks -- View this message in context: http://dovecot.2317879.n4.nabble.com/pop3-login-ok-then-disconnects-right-a… Sent from the Dovecot mailing list archive at Nabble.com.

2 1

[Dovecot] v2.2.1 released
by Timo Sirainen 07 May '13

07 May '13

http://dovecot.org/releases/2.2/dovecot-2.2.1.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.1.tar.gz.sig - mailbox_list_index=yes was broken. - LAYOUT=index didn't list subscriptions. - auth: Multiple master passdbs didn't work. - Message parsing (e.g. during search) crashed when multipart message didn't actually contain any parts.

15 25

[Dovecot] Upgrading from 2.0 to 2.2
by Asai 06 May '13

06 May '13

Greetings, Is this possible to upgrade directly from 2.0 to 2.2? If so, is there a guide for doing this? Thank you. -- --Asai

2 1

[Dovecot] imap crash during URLFETCH
by Mike Abbott 06 May '13

06 May '13

Dovecot-2.2.1's imap processes crash reliably when they use an IMAP URL with an invalid access specifier. A backtrace and some debug output follows. The crash is likely caused by imap_urlauth_fetch_parsed() returning 0 without having set *mpurl_r to NULL, and then imap_urlauth_fetch_local() freeing an uninitialized pointer. Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000001059 0 libdovecot-storage.0.dylib 0x000000010b06a383 imap_msgpart_url_free + 17 1 imap 0x000000010afc71cc imap_urlauth_fetch_local + 770 2 imap 0x000000010afc6dcf imap_urlauth_fetch_url + 439 3 imap 0x000000010afbb489 cmd_urlfetch + 580 4 imap 0x000000010afbdf4d command_exec + 55 5 imap 0x000000010afbdabb client_command_input + 34 6 imap 0x000000010afbdc7c client_command_input + 483 7 imap 0x000000010afbd351 client_handle_input + 239 8 imap 0x000000010afbc613 client_input + 119 9 libdovecot.0.dylib 0x000000010b111c74 io_loop_call_io + 46 10 libdovecot.0.dylib 0x000000010b112c85 io_loop_handler_run + 214 11 libdovecot.0.dylib 0x000000010b111e1f io_loop_run + 77 12 libdovecot.0.dylib 0x000000010b0d10c6 master_service_run + 24 13 imap 0x000000010afc5aba main + 1010 14 libdyld.dylib 0x00007fff89e5f7bd start + 1 Apr 29 20:00:31 imap(pid 82429 user mja): Debug: Fetching local URLAUTH imap://mja@duck.example.com/INBOX;uidvalidity=1366726248/;uid=19;urlauth=submit+mja:internal:012c9c6a3d74db6509e4a3802a0f5edf64546608b8 Apr 29 20:00:31 imap(pid 82429 user mja): Debug: Failed to fetch URLAUTH "imap://mja@duck.example.com/INBOX;uidvalidity=1366726248/;uid=19;urlauth=submit+mja:internal:012c9c6a3d74db6509e4a3802a0f5edf64546608b8": No 'submit+mja' access allowed for user mja Apr 29 20:00:31 imap(pid 82429 user mja): Fatal: master: service(imap): child 82429 killed with signal 11 (core dumps disabled)

2 3

[Dovecot] doveadm search causes replication error message
by Oli Schacher 06 May '13

06 May '13

Hi # 2.2.1 (83d83f55e5c2+) / dsync replicated setup I just noticed that 'doveadm search' apparently tries to replicate mailboxes and spits out errors if a mailbox in the search query is not found: #doveadm search -u user(a)example.com mailbox Spamreport doveadm(user(a)example.com): Error: Syncing mailbox Spamreport failed: Mailbox doesn't exist: Spamreport this is especially problematic with -A searches as this causes a error message for every user which doesn't have that folder. Is this a bug or intended behaviour? Should I just 2>/dev/null these errors in doveadm scripts? Thanks Oli -- message transmitted on 100% recycled electrons

2 2

[Dovecot] SELECT/EXAMINE don't report URLMECH
by Mike Abbott 06 May '13

06 May '13

In dovecot-2.2.1 neither the SELECT nor the EXAMINE commands include an untagged URLMECH reply. (Note, this is not the one mandated by the RESETKEY command.) AFAICT RFC 4467 does not require an URLMECH reply to SELECT or EXAMINE but without it clients have no way of knowing about authorization mechanisms other than INTERNAL. Now I know dovecot-2.2 supports only the INTERNAL mechanism at present so this is probably harmless, but still I think it's worthwhile to ask: Is the absence of the URLMECH reply intentional or an oversight? For comparison Apple's enhanced dovecot replies: c1 select inbox [...] * OK [URLMECH INTERNAL] Mechanisms supported c1 OK [READ-WRITE] Select completed.

2 1

[Dovecot] many SSH connexions with dsynx/SSH replication
by Emmanuel Dreyfus 06 May '13

06 May '13

Hi I am trying replication over dsync/ssh, as explained there: http://wiki2.dovecot.org/Replication I added the options below to dovecot.conf. It works, but it seems there is a new SSH connexion for each user, which is a bit overkill performance-wise. Since I sync as root, I guess there is a way of haing everything on the same SSH connexion? --- cut here --- mail_plugins = $mail_plugins notify replication service replicator { process_min_avail = 1 } dsync_remote_cmd = ssh -lroot %{host} doveadm dsync-server -u%u plugin { mail_replica = remote:root@mail1.example.net } service aggregator { fifo_listener replication-notify-fifo { user = dovecot } unix_listener replication-notify { user = dovecot } } service replicator { unix_listener replicator-doveadm { mode = 0600 } } service doveadm { inet_listener { port = 12345 ssl = yes } } doveadm_port = 12345 ssl_client_ca_file = /etc/openssl/certs/ca.crt doveadm_proxy_port = 0 --- cut here --- -- Emmanuel Dreyfus manu(a)netbsd.org

2 1

[Dovecot] dsyncing lazy_expunge namespace
by Angel L. Mateo 06 May '13

06 May '13

Hello, I'm in the process of migrating mailbox from one dovecot server running dovecot 2.1.9 with mailboxes stored in maildir format to a newer one running 2.1.16 with mailboxes stored in mdbox format. To migrate mailboxes I'm using dsync as explained at http://wiki2.dovecot.org/Tools/Dsync. The command I'm running in the newer server is: sudo dsync -o mailbox_list_index=no mirror -R -u <user> imapc: The mailbox of the user is correctly synced to the newer server, except the lazy_expunge namespace, which is not synced at all. The config in my old server is: namespace { # hidden = yes # list = no # Temporally, only for migration hidden = no list = yes location = maildir:~/Maildir/expunged prefix = BORRADOS. separator = . } and in the newer one is: namespace { hidden = yes list = no location = mdbox:%h/expunged:INDEX=/mail/indexes/%2Ln/%Ln/expunged prefix = BORRADOS/ separator = / } With a tcpdump I have checked that old servers list the namefolder, this is the IMAP dialog for an example user: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN] Dovecot ready. 2 AUTHENTICATE PLAIN YW5nZWwubHVpcwBtYXN0ZXIAVkFzR293ZW0= 2 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS SPECIAL-USE QUOTA ACL RIGHTS=texk] Logged in 1 LIST "" "" * LIST (\Noselect) "." "" 1 OK List completed. 3 LIST "" "*" * LIST (\HasNoChildren) "." "SPAM" * LIST (\HasNoChildren) "." "Trash" * LIST (\HasNoChildren) "." "Drafts" * LIST (\HasNoChildren) "." "INBOX" * LIST (\Noselect \HasNoChildren) "." "BORRADOS" 3 OK List completed. 4 STATUS "SPAM" (UIDNEXT UIDVALIDITY) * STATUS "SPAM" (UIDNEXT 3 UIDVALIDITY 1316372649) 4 OK Status completed. 5 EXAMINE "SPAM" * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) ... But "BORRADOS" is never selected in the rest of the dialog. Any idea? -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información y las Comunicaciones Aplicadas (ATICA) http://www.um.es/atica Tfo: 868889150 Fax: 868888337

2 1

[Dovecot] XFS vs EXT4 for mail storage
by Charles Marcus 05 May '13

05 May '13

Hello, I'm in the process of finalizing the spec for my new dovecot VM, and this is the last question I need to address... I've read until I'm just about decided on XFS, but I have no experience with it (been using reiserfs on my old box (@ 8 yrs old now), and never had a problem (knock on wood), but considering its current situation (little to no development support for reasons everyone is aware of), I've decided now is the time to switch. It came down to XFS or EXT4, and I like what I've read about XFS, but am unsure how to tune it (or even if I should). I've decided to use mdbox for storage (been using maildir), and will enable SIS for attachments. So, anyone (Stan?) have any suggestions? Should I go with EXT4? Or XFS with just the defaults? Or XFS with one or more tuned parameters? Appreciate any suggestions (including links to docs dealing with tuning XFS for my mail storage conditions that are written more at the layman level) or comments from anyone experienced using both... Thanks, -- Best regards, Charles

11 37

Re: [Dovecot] qmail-ldap LDA Delivery and sieve
by Deepak 04 May '13

04 May '13

Hi I used the below filter in my dovecot-ldap-userdb.conf file, user_attrs = homeDirectory=home, uidNumber=uid, gidNumber=gid user_filter = (&(objectClass=posixAccount)(|(mail=%u)(mailAlternateAddress=%u) (uid=%u))) This above filter was working fine for me, and it's delivering fine for all the domains. seive is also working fine. The "-d" in dovecot-lda will do userdb lookup with ldap.

1 0

[Dovecot] dovecot antispam plugin is not woking
by Ravi Kanchan 04 May '13

04 May '13

Hi All, I am using dovecot version 2.0.9 DSPAM Anti-Spam Suite 3.10.2 (agent/library) ClamAV 0.97.7/17102 and dspam antispam plugin dovecot-antispam-plugin-43880985e3dd and plugin configuration is given below: protocol imap { mail_plugins = " antispam autocreate" } protocol pop3 { mail_plugins = antispam autocreate } plugin { antispam_allow_append_to_spam = YES antispam_backend = dspam antispam_crm_args = --config=/home/vmail antispam_dspam_args = --client;--user vmail antispam_dspam_binary = /usr/bin/dspam antispam_dspam_notspam = --class=innocent antispam_dspam_result_header = X-DSPAM-Result antispam_dspam_spam = --class=spam antispam_mail_tmpdir = /tmp antispam_signature = X-DSPAM-Signature antispam_signature_missing = error antispam_spam = Spam } dspam bin path: [root@sogo ~]# which dspam /usr/bin/dspam but my dspam plugin configuration is not working. and I am not getting any log from dspam. My dspam server is working prefect. cna anyone help me Regard's Ravi Kanchan Sharma

4 8

[Dovecot] Dovecot has no understandable configuration any more
by forum 04 May '13

04 May '13

Hello, for many years i used an mailserver with dovecot V1 very satisfied! http://mailserver.decotrain.de/ One of the reasons to use dovecot was a simply configuration. Dovecot was the best choice for IMAP for me! Now i updated the server to Debian testing with dovecot 2.1.7. It's not possible for me to get a running authentication for virtual mail users! I recently found this mailing and have the same problem: http://www.dovecot.org/list/dovecot/2012-March/064181.html The documentation says *nothing* about my problem how to authenticate with mysql! http://wiki2.dovecot.org/VirtualUsers I can solve the problem only with try and error without a chance in this complex system. It's nice to have all this possibilites but they are not useful if not documented. There should be some clear examples for different scenarios to be found in your wiki. My problem at this time: I don't know how to configure the userdb to work with mysql authentification? All mail is running under the special user mail. dovecot.conf ============ disable_plaintext_auth = yes passdb { driver = sql # Path for SQL configuration file, see example-config/dovecot-sql.conf.ext args = /etc/dovecot/dovecot-sql.conf } userdb { driver = prefetch } first_valid_uid = 8 last_valid_uid = 8 first_valid_gid = 8 last_valid_gid = 8 mail_location = maildir:/srv/mail/%d/%n dovecot-sql.conf ================ driver = mysql connect = host=/var/run/mysqld/mysqld.sock dbname=... => WORKS! default_pass_scheme = SHA1 password_query = SELECT password, '/srv/mail/%d/%n' AS home, 'mail' AS uid, 'mail' AS gid FROM user WHERE username = '%n' AND domain = '%d' AND IMAP_allowed = 'YES' Errors ====== Apr 30 10:28:22 auth: Debug: client out: OK 1 user=xxxx@yyyy home=/srv/mail/yyyy/xxxx uid=mail gid=mail Apr 30 10:28:22 auth: Debug: master in: REQUEST 3163291649 5347 1 87066c907eef8f4e5ed71319b560dd2a Apr 30 10:28:22 auth: Error: prefetch(xxxx@yyyy,::1,<doTKyI/brgAAAAAAAAAAAAAAAAAAAAAB>): userdb lookup not possible with only userdb prefetch Apr 30 10:28:22 auth: Error: userdb(xxxx@yyyy,::1,<doTKyI/brgAAAAAAAAAAAAAAAAAAAAAB>): user not found from userdb prefetch Apr 30 10:28:22 auth: Debug: master out: NOTFOUND 3163291649 Apr 30 10:28:22 imap: Error: Authenticated user not found from userdb, auth lookup id=3163291649 (client-pid=5347 client-id=1) Apr 30 10:28:22 imap-login: Info: Internal login failure (pid=5347 id=1) (internal failure, 1 succesful auths): user=<karsten(a)dct.mine.nu>, method=PLAIN, rip=::1, lip=::1, mpid=5352, secured, session=<doTKyI/brgAAAAAAAAAAAAAAAAAAAAAB> I have no idea how to solve the problem and up to know i could not find an example with google. Please help. Best regards Karsten

8 11

[Dovecot] Accessing mail files not owned by imap login user
by PaulM47 03 May '13

03 May '13

Hi, I have managed to set up a 'maildir' based mail system using fetchmail and procmail that delivers sorted mail to folders /var/spool/mail/user1, ../user2 etc. 'user1', 'user2' etc. are real users but the mail system is run under logged in user 'mailserver'. The mail folders are owned by 'user1', 'user2' etc. but mail files, when delivered, are owned by 'mailserver'. I've been unable to find a way to change this behaviour :-( Dovecot is configured by adding the single line 'mail_location = maildir:/var/spool/mail/%u' to 'dovecot.conf', everything else is as installed. When I make an imap connection as 'user1' the logon is successful, the mail files are moved from ../new/ to ../cur/ but are invisible to the imap client. If I 'chown' the mail files to 'user1' they instantly become visible to the imap client. I gather from googling info on dovecot I can configure dovecot to allow 'user1', when logged in, to access the mail files owned by 'mailserver'. Is this simple to do, and if so how do I do it please ? Thanks PaulM -- View this message in context: http://dovecot.2317879.n4.nabble.com/Accessing-mail-files-not-owned-by-imap… Sent from the Dovecot mailing list archive at Nabble.com.

3 3

[Dovecot] feature request: pipe for custom quota dict queries
by Jeff Gustafson 03 May '13

03 May '13

Just a followup to my previous post. I appears that a pipe for quota queries via dict is not supported right now. Because of the way we group things we need more flexibility. I'd like to propose that dovecot should support quota queries just like userdb dict queries. My expertise is not C, but I might try to poke around and see if I can make something work. ...Jeff

1 0

[Dovecot] sieve: deleteheader sometimes fails [bug]
by Daniel Piddock 03 May '13

03 May '13

Hi, We're using Dovecot 2.1.16 with Pigeonhole 0.3.4. Mail is delivered by exim4 to the dovecot LDA. Sometimes users are unable to delete headers. I've narrowed the problem down to preceding the deleteheader command with a query against the body. A simple example: """ require ["body", "editheader", "fileinto"]; if body :contains "!TEST!" { fileinto "INBOX.Trash"; stop; } deleteheader "Subject"; addheader "Subject" "Testing"; """ Putting the "deleteheader" above the "if body" causes it to be deleted correctly. Although I've used Subject in this example it happens for other headers. Cheers, Dan

2 5

[Dovecot] dovecot 1.2.5 Fatal: setgid(5000(vmail)) Operation not permitted
by Mosh Mage 03 May '13

03 May '13

This is the error I'm getting (whenever i recieve and email): *deliver() : Fatal: setgid(5000(vmail)) failed with euid=5000(vmail), gid=8(mail), egid=8(mail): Operation not permitted (This binary should probably be called with process group set to 5000(vmail) instead of 8(mail)) * I am at loss. I have tried "everything" i could think of (besides purging the machine and do it all over again, which is not an option -- unless it is). Can anyone help me fix this? # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 3.2.13-grsec-xxxx-grs-ipv6-64-vps x86_64 Debian 6.0.6 ext3 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 verbose_proctitle: yes mail_uid: vmail mail_gid: vmail mail_location: maildir:/var/zpanel/vmail/%d/%n mail_debug: yes mbox_write_locks: fcntl dotlock auth default: mechanisms: plain login verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 432 user: vmail group: vmail plugin: trash: /etc/dovecot/dovecot-trash.conf # /etc/dovecot/dovecot-sql.conf driver = mysql connect = host=localhost dbname=zpanel_postfix user=USERNAME password=AWESOMEPASSWORD default_pass_scheme = PLAIN password_query = \ SELECT name, domain, password \ FROM mailbox WHERE name = '%n' AND domain = '%d' user_query = \ SELECT maildir \ FROM mailbox WHERE name = '%n' AND active = '1' AND domain = '%d' #This is my ls -la drwxrwsrwx 5 vmail vmail 4096 May 2 18:39 vmail #and this is inside vmail/ drwx--S--- 3 vmail vmail 4096 May 2 18:39 asfaltotejo.com drwx--S--- 3 vmail vmail 4096 May 2 12:35 gestaoconteudos.pt drwx--S--- 17 vmail vmail 4096 May 2 15:34 tribanet.com #/var/run/dovecot srw-rw---- 1 vmail vmail 0 May 2 19:46 auth-master srw------- 1 root root 0 May 2 19:46 auth-worker.6564 srwxrwxrwx 1 root root 0 May 2 19:46 dict-server lrwxrwxrwx 1 root root 25 May 2 19:46 dovecot.conf -> /etc/dovecot/dovecot.conf drwxr-x--- 2 root dovecot 4096 May 2 19:46 login

1 0

[Dovecot] CATENATE allows zero parts
by Mike Abbott 03 May '13

03 May '13

I'm pleased to see that dovecot-2.2 includes support for RFCs 4467 and 4469 (URLAUTH and CATENATE). I have begun testing these features (in dovecot-2.2.1) and comparing their functionality against Apple's implementation. So far I have discovered a few inconsistencies. I will report each of these, and any more that I may find, in separate threads. The first issue is that using CATENATE with no message parts works but, IMO, shouldn't: a2 append inbox catenate () a2 OK [APPENDUID 1366726248 9] Append completed. For comparison this is how Apple's enhanced dovecot in OS X Server handles this request: a2 append inbox catenate () a2 BAD Invalid arguments. According to RFC 4469 section 3 CATENATE requires "one or more message parts." This is formalized in section 5: append-data =/ "CATENATE" SP "(" cat-part *(SP cat-part) ")" and in RFC 3501 section 9 which states that "[ABNF] rules MUST be followed strictly." I believe that permitting zero cat-parts is contrary to the RFC, although I can understand permitting it under the general doctrine of "servers should be liberal in what they accept, and clients strict in what they send." Is accepting zero cat-parts an intentional exception to the RFC or an oversight?

2 2

[Dovecot] CATENATE doesn't support literal+ url
by Mike Abbott 03 May '13

03 May '13

Dovecot-2.2.1 does not appear to support URLs specified via non-synchronizing literals (RFC 2088 LITERAL+), and also does not read and discard the literal+ input after reporting the error. This results in the literal+ input being interpreted as IMAP commands, which could alter the user's mail store in unexpected ways and/or lead to the abrupt disconnection of the client for exceeding the maximum number of bad IMAP commands. Example using dovecot-2.2.1 (note that the text nonsync literal includes the invisible CRLFs: "foobarCRLFbarbazCRLF"): a3 append inbox catenate (url {9+} /some-url text {16+} foobar barbaz ) a4 noop a3 BAD Error in IMAP command APPEND: Invalid arguments. foobar BAD Error in IMAP command : Unknown command. barbaz BAD Error in IMAP command : Unknown command. ) BAD Error in IMAP command : Unknown command. a4 OK NOOP completed. Example using Apple's enhanced dovecot in OS X Server: a3 append inbox catenate (url {9+} /some-url text {16+} foobar barbaz ) a4 noop a3 NO [BADURL /some-url] missing or invalid uid a4 OK NOOP completed. I believe the RFCs indicate that nonsync literal URLs should be permitted. RFC 4469 section 5: append-data =/ "CATENATE" SP "(" cat-part *(SP cat-part) ")" cat-part = text-literal / url url = "URL" SP astring RFC 3501 section 9: astring = 1*ASTRING-CHAR / string string = quoted / literal RFC 2088 section 4: literal ::= "{" number ["+"] "}" CRLF *CHAR8

2 4

[Dovecot] Tuning!
by Rafael VOlpe TI 02 May '13

02 May '13

Hi Buddies, I have 2 servers running dovecot + postfix for pop/imap users. The users mailbox are in a Nfs storage. The load of server is ranging at 3.0 to 15.0. I really dont know what happened.. I read a lot about tuning of dovecot, and the changes are applied, how you can see. The Hardware of server is really good! The host have 8GB of mem and 2 sockets with 2 cores anyone. The server receives 900-1000 user connections in pop and imap. How i can aprimmorate this processes? Some errors are displayed on the console randomly when the load rises. Example: May 02 13:57:42 pop3(user(a)domain.com): Error: Timeout (180s) while waiting for lock for transaction log file //var/vmail/ domain.com/user//dovecot.index.log May 02 13:57:42 pop3(user(a)domain.com): Error: Couldn't init INBOX: Internal error occurred. Refer to server log for more information. [2013-05-02 13:54:40] May 02 13:57:42 pop3(user(a)domain.com): Info: Mailbox init failed top=0/0, retr=0/0, del=0/0, size=0 I really appreciate any suggestion! Thanks and Regards, Rafael Volpe Dovecot conf: # 2.0.19: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-40-generic x86_64 Ubuntu 12.04.2 LTS auth_mechanisms = plain login auth_verbose = yes debug_log_path = /var/log/dovecot-debug.log disable_plaintext_auth = no dotlock_use_excl = no first_valid_gid = 125 first_valid_uid = 125 last_valid_gid = 125 last_valid_uid = 125 log_path = /var/log/dovecot.log mail_debug = yes mail_fsync = always mail_location = maildir:/%Lh/:INDEX=/%Lh/ mail_nfs_index = yes mail_nfs_storage = yes mmap_disable = yes passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocols = " imap pop3" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } service_count = 0 } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } ssl_cert = </etc/postfix/ssl/wildcard.domain.com.crt ssl_key = </etc/postfix/ssl/wildcard.domain.com.key userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } verbose_proctitle = yes protocol imap { imap_idle_notify_interval = 2 mins mail_max_userip_connections = 150 } protocol pop3 { pop3_lock_session = no pop3_uidl_format = %08Xu%08Xv } Postfix conf: alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases append_dot_mydomain = no biff = no bounce_queue_lifetime = 1d broken_sasl_auth_clients = yes config_directory = /etc/postfix content_filter = smtp-amavis:[127.0.0.1]:10024 inet_interfaces = all mailbox_size_limit = 0 maximal_queue_lifetime = 1d message_size_limit = 20240000 myhostname = myname.mydomain.com mynetworks = 127.0.0.0/8 myorigin = /etc/mailname policy-spf_time_limit = 3600s readme_directory = no recipient_bcc_maps = mysql:/etc/postfix/mysql_bcc.cf recipient_delimiter = + relay_domains = proxy:mysql:/etc/postfix/mysql_relay_domains_maps.cf relayhost = sender_bcc_maps = mysql:/etc/postfix/mysql_bcc.cf smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtpd_banner = Welcome to $myhostname smtpd_client_restrictions = permit_mynetworks, permit_sasl_authenticated, check_client_access mysql:/etc/postfix/mysql_access.cf, reject_unknown_client, reject_unknown_client_hostname, reject_unauth_pipelining, reject_rbl_client bl.spamcop.net, reject_rbl_client zen.spamhaus.org, reject_rbl_client b.barracudacentral.org smtpd_end_of_data_restrictions = check_policy_service inet:127.0.0.1:10031 smtpd_helo_required = yes smtpd_helo_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_non_fqdn_helo_hostname, reject_invalid_helo_hostname, reject_invalid_hostname smtpd_recipient_restrictions = reject_unknown_sender_domain, reject_unknown_recipient_domain, reject_non_fqdn_sender, reject_non_fqdn_recipient, reject_unlisted_recipient, check_policy_service inet:127.0.0.1:10031, permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination, check_policy_service unix:private/policy-spf smtpd_reject_unlisted_sender = yes smtpd_sasl_auth_enable = yes smtpd_sasl_local_domain = $mydomain smtpd_sasl_path = private/auth smtpd_sasl_security_options = noanonymous smtpd_sasl_type = dovecot smtpd_sender_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_pipelining, reject_unauth_destination smtpd_timeout = 30 smtpd_tls_cert_file = /etc/postfix/ssl/wildcard.domain.com.crt smtpd_tls_key_file = /etc/postfix/ssl/wildcard.domain.com.key smtpd_tls_security_level = may smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache transport_maps = mysql:/etc/postfix/mysql_transport.cf vacation_destination_recipient_limit = 1 virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_maps.cf virtual_gid_maps = static:125 virtual_mailbox_base = /var/vmail virtual_mailbox_domains = mysql:/etc/postfix/mysql_virtual_domains_maps.cf virtual_mailbox_limit = 51200000 virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailbox_maps.cf virtual_minimum_uid = 125 virtual_transport = virtual virtual_uid_maps = static:125

3 2

[Dovecot] Dovecot vs MBox
by Gregory Sloop 02 May '13

02 May '13

I'm still in the "what's wrong" stage of figuring out what's going on. But I've got a mail user who isn't getting new messages. Postfix accepts it and drops it in the users mbox. [This is verified. If I tail the Mbox, I can see the new messages.] "Mail" will see the messages too. But dovecot doesn't seem to know they exist. I don't think the MBox is corrupt, as I've tossed the first few messages in hopes that it would then read the rest, but no luck. Any ideas where to look next, what I might do to force dovecot to forget message ID's etc - that might force it to read the whole mailbox file again? [Or a pointer as to where it might be most productive to poke next?] TIA -Greg -- Gregory Sloop, Principal: Sloop Network & Computer Consulting 503.251.0452 x121 Voice | 503.251.0452 Fax www.sloop.net mailto:gregs@sloop.net

5 7

[Dovecot] CATENATE allows empty messages
by Mike Abbott 02 May '13

02 May '13

Dovecot-2.2.1 allows empty messages to be APPENDed when using CATENATE: b1 append inbox catenate (text {0+} ) b1 OK [APPENDUID 1366726248 12] Append completed. Contrast this with regular APPEND: b2 append inbox {0+} b2 NO Can't save a zero byte message. Note that zero-size literals are OK but zero-size messages are not. So while "b1" above should fail like "b2", this should continue to succeed: b3 append inbox catenate (text {0+} text {8+} foobar ) b3 OK [APPENDUID 1366726248 13] Append completed.

3 6

[Dovecot] Slow DNS warnings (proxy/auth)
by Christian Balzer 02 May '13

02 May '13

Hello, I've just finished transiting our proxies from perdition to dovecot (2.1.7-7 Debian). Yesterday 12 messages (all within the same second) like this caught my attention: --- Apr 25 17:19:09 pp11 dovecot: auth: Warning: proxy(redacted(a)gol.com,xx.xx.xx.xx,<26hUEivbfQBlMrMS>): DNS lookup for mb04.dentaku.gol.com took 5.002 s --- Now this machine at that time was handling a load of about 2 logins per second, about 20% of what it previously handled with perdition w/o a hiccup. It also runs a local caching nameserver and the A record for the mailbox server in question was most definitely cached at the time (verified via TTL). The machine in question was very bored and certainly capable of handling hundreds if not thousands of DNS queries per second at that moment. In short, I can't see any reason how the lookup could have taken so long, so my guess is there are some issues with the dns-helper (locking, stepping on each others feet, not being spawned fast enough) causing this. Some general remarks, dovecot as proxy feels "heavier" than perdition. In the CPU area that's probably a more subjective impression, because all the little helper processes make it clear what's going on where. Though the "config" process being rather active is something that perdition definitely doesn't do, it reads the config once at start time and that's it. All the IPC and central processes of course also make dovecot rather file handle hungry. Memory wise it's about 35% bigger than perdition and that's not subjective at all. ^o^ About one MB per proxy process/connection for dovecot in my case. Caveat emptor. ^o^ Regards, Christian -- Christian Balzer Network/Systems Engineer chibi(a)gol.com Global OnLine Japan/Fusion Communications http://www.gol.com/

2 1

Re: [Dovecot] XFS vs EXT4 for mail storage
by Reindl Harald 02 May '13

02 May '13

Am 02.05.2013 17:31, schrieb Charles Marcus: > On 2013-05-02 10:45 AM, Reindl Harald <h.reindl(a)thelounge.net> wrote: >> "man mount" is very generic and doe snot cover any option >> there is also no "man mount.ntfs" while "mount.ntfs" command exists > > ? > > man mount, at least mine, shows first the FILESYSTEM INDEPENDENT MOUNT OPTIONS, then as you scroll down, you'll get > to all of the additional filesystem specific options, ie, for xfs... > > So, not sure what you mean by 'does not cover any option'... typo - meant "does not cover ALL options" someone has to write the manpages, there are millions of options all over the software-world which did it not make into manpages google for "xfs delaylog" leads to http://xfs.org/index.php/XFS_FAQ http://xfs.org/index.php/XFS_FAQ#Q:_I_want_to_tune_my_XFS_filesystems_for_.… For mount options, the only thing that will change metadata performance considerably are the logbsize and delaylog mount options so how can it be redhat-specific if it is mentioned upstream?

1 0

[Dovecot] NTLM authentication with Outlook 2010
by Kevin Bridges 01 May '13

01 May '13

All, I have a Ubuntu 12.04.2 box running Dovecot 2.0.19. I have it configured for our active directory. WBinfo and ntlm_auth work great. I am trying to get sso to work with ntlm. Gssapi with thunderbird works like it should. I just cant get ntlm with outlook 2010 to work for sso. I get prompted for my password each time I open outlook. I have attached my config for dovecot. Any help would be much appreciated. # 2.0.19: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-39-virtual x86_64 Ubuntu 12.04.2 LTS auth_debug = yes auth_debug_passwords = yes auth_mechanisms = gssapi ntlm auth_use_winbind = yes auth_verbose = yes auth_verbose_passwords = plain debug_log_path = /var/log/dovecot_debug.log log_path = /var/log/dovecot.log mail_location = mdbox:~/mdbox passdb { driver = pam } plugin { quota_rule = *:storage=2G quota_warning = storage=95%% quota-warning 95 %u } protocols = " imap" service auth-worker { user = root } service auth { user = root } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = passwd } protocol imap { mail_plugins = " quota imap_quota" }

2 2

[Dovecot] Antispam r49 breaks Dovecot v2.1
by Steffen Kaiser 30 Apr '13

30 Apr '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear Eugene, patch 49 breaks compilation with Dovecot v2.1. Attached patch encloses the change in a #if. To feed the #if the actual Dovecot version, I've introduced an extra variable in extra.mk, but I cannot help with making the GNU configure stuff doing it right away. There will be numerous other ways to get the Dovecot version into the source ... . Maybe, Timo would add a binary version of the Dovecot version in its config.h ? In order to be able to built version-aware plugins. Regards, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBUNLvT2oxLS8a3A9mAQIzfwgAvf7zcN9RwKD/kTmFkfx5djKd5H0dRXt8 423csD3bCU6qcOtR2MHR0ApNp07aXK84MPgIazbne41Iekqk0daoOhnPoc0mHy8u kj9EYFGVlQTKa2vcSUEu8Phddc/YHvzQba9m2Dg9P4STuJ6EcRqkhvufspERGphF Y+IY20BQc9/Flu8TIxtt6pSiIioq0WWntCGnyPP9BX90JYYO+5zAm5FnG4GH4Q0Z 44dZSKM7iP0/nMhmsraX/5alxy0mvx3ZfhO/Ktx/wd92WmLROAlicBClIZC9XCH2 6HD/ryr73DrEeEZdmwHcnmZrtWc++EJcAetfv45Fov8XagUtFJ0D4A== =G+d/ -----END PGP SIGNATURE-----

2 1

[Dovecot] Dovecot has no understandable configuration any more
by forum 30 Apr '13

30 Apr '13

Hello, my last problem could be solved now with userdb { driver = static args = uid=mail gid=mail home=/srv/mail/%d/%n } I can connect to dovecot locally with an webmailer. But there is no listener process to be seen outside of the server? Locally this ports are working, but not outside: # netstat -tulpn | grep dove tcp6 0 0 :::110 :::* LISTEN 5741/dovecot tcp6 0 0 :::143 :::* LISTEN 5741/dovecot tcp6 0 0 :::993 :::* LISTEN 5741/dovecot tcp6 0 0 :::995 :::* LISTEN 5741/dovecot Is this a configuration problem inside dovecot? Another problem is the migration from the existant emails from V1 to V2: In the log i can find: Apr 30 11:14:57 imap(xxxx@yyyy): Error: Broken file /srv/mail/yyyy/xxxx/.INBOX.dir.09/dovecot-uidlist line 1: Broken header (uidvalidity = 0, next_uid=697) How can i recover this? Delete all the index files? Has someone an idea how to migrate the emails from charset ISO8859-1 to UTF-8? Best regards Karsten

2 1

[Dovecot] Dovecot Antispam Plugin is not working
by Ravi Kanchan 30 Apr '13

30 Apr '13

Hi All, I am using dovecot version 2.0.9 DSPAM Anti-Spam Suite 3.10.2 (agent/library) ClamAV 0.97.7/17102 and dspam antispam plugin dovecot-antispam-plugin-43880985e3dd and plugin configuration is given below: protocol imap { mail_plugins = " antispam autocreate" } protocol pop3 { mail_plugins = antispam autocreate } plugin { antispam_allow_append_to_spam = YES antispam_backend = dspam antispam_crm_args = --config=/home/vmail antispam_dspam_args = --client;--user vmail antispam_dspam_binary = /usr/bin/dspam antispam_dspam_notspam = --class=innocent antispam_dspam_result_header = X-DSPAM-Result antispam_dspam_spam = --class=spam antispam_mail_tmpdir = /tmp antispam_signature = X-DSPAM-Signature antispam_signature_missing = error antispam_spam = Spam } dspam bin path: [root@sogo ~]# which dspam /usr/bin/dspam and dspam.conf has attached with this mail. but my dspam plugin configuration is not working. and also I am not getting any log from dspam. My dspam server is working prefect. but I guess plugin is not working properly can anyone helpme. and my configuration for this is following:Regard's Ravi Kanchan Sharma Sr. System Administrator Infinite Computer Solutions (I) Ltd. Bglr. Mo. 9997154666

1 0

[Dovecot] help with LMTP setup
by jeep＠rahul.net 30 Apr '13

30 Apr '13

Im trying to convert my dovecot-lda setup to use LMTP for better security. My setup is postfix + dovecot + mysql with virtual users. Im setting up dovecot 2.2.1 w/postfix 2.10.0 Im still learning dovecot so Im not totally sure where Im going wrong. Can someone point out why Im getting permission problems? Im also concerned with server security, so if you notice anything that should be better, please point that out. I am the only user on this Linux box. Thank you! ls -l /opt/imapdata/j/jeff/INBOX total 8 drwxr-xr-x 2 vmail vmail 4096 Apr 27 14:21 ./ drwxr-xr-x 3 vmail vmail 4096 Apr 27 14:21 ../ Dovecot is running with the following users: root 20847 0.0 0.0 15572 1108 ? Ss 10:23 0:00 /opt/optdovecot/sbin/dovecot dovenull 20848 0.0 0.0 46752 2724 ? S 10:23 0:00 dovecot/imap-login dovenull 20849 0.0 0.0 46752 2720 ? S 10:23 0:00 dovecot/imap-login vmail 20850 0.0 0.0 13408 1068 ? S 10:23 0:00 dovecot/anvil root 20851 0.0 0.0 13540 1192 ? S 10:23 0:00 dovecot/log root 20853 0.0 0.0 16504 2128 ? S 10:23 0:00 dovecot/config vmail 20854 0.0 0.0 136448 2972 ? S 10:23 0:00 dovecot/auth Im getting the following when an email comes in: Apr 29 10:11:57 fed8 postfix/virtual[20666]: D88F3DF3BD: to=<jeff(a)mydomain.com>, relay=virtual, delay=370, delays=370/0.03/0/0.07, dsn=4.2.0, status=deferred (delivery failed to mailbox ///opt/imapdata/j/jeff/INBOX/inbox: unable to create lock file ///opt/imapdata/j/jeff/INBOX/inbox.lock: Permission denied) my postfix/master.cf entry: dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/opt/dovecot/libexec/dovecot/lmtp -f ${sender} -d ${recipient} doveconf -n: # 2.2.1: /opt/dovecot221/etc/dovecot/dovecot.conf # OS: Linux 3.8.5-201.fc18.x86_64 x86_64 Fedora release 18 (Spherical Cow) auth_debug = yes auth_debug_passwords = yes auth_verbose = yes auth_verbose_passwords = plain default_internal_user = vmail first_valid_gid = 2000 first_valid_uid = 2000 listen = * lock_method = flock login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c mail_debug = yes mail_gid = vmail mail_privileged_group = vmail mail_uid = vmail mbox_lock_timeout = 1 mins mbox_write_locks = fcntl passdb { args = /opt/dovecot/etc/dovecot/conf.d/dovecot-sql.conf.ext driver = sql } plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size } postmaster_address = jeff(a)otherdomain.com protocols = imap lmtp sendmail_path = /usr/lib/sendmail service auth { inet_listener { port = 12345 } unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { mode = 0660 user = vmail } user = $default_internal_user } service imap-login { inet_listener imaps { port = 993 ssl = yes } process_min_avail = 2 service_count = 1 vsz_limit = 64 M } service lmtp { executable = lmtp -L inet_listener lmtp { address = 192.168.1.22 127.0.0.1 port = 24 } unix_listener lmtp { mode = 0666 } user = vmail } ssl = required ssl_cert = </opt/dovecot/etc/dovecot/conf.d/ssl/certs/dovecot.pem ssl_cipher_list = ALL:!LOW:!MEDIUM:!SSLv1:!SSLv2:!MD5:!SSL1:!SSL2:!EXP-ADH-DES-CBC-SHA:!EXP-EDH-RSA-DES-CBC-SHA:!EXP-DES-CBC-SHA:!EXP-EDH-RSA-DES-CBC-SHA:!EXP-ADH-DES-CBC-SHA:!EXP-DES-CBC-SHA:!ADH-AES256-SHA:!ADH-AES128-SHA:!ADH-DES-CBC3-SHA:!EXP-ADH-DES-CBC-SHA:!EXP-ADH-DES-CBC-SHA:!ADH-DES-CBC3-SHA:TLSv1 ssl_key = </opt/dovecot/etc/dovecot/conf.d/ssl/private/dovecot.pem userdb { args = uid=vmail gid=vmail home=/opt/imapdata/%1n/%n driver = static } userdb { args = /opt/dovecot/etc/dovecot/conf.d/dovecot-sql.conf.ext driver = sql } userdb { args = /opt/dovecot/etc/dovecot/conf.d/dovecot-sql.conf.ext driver = sql } verbose_ssl = yes protocol lmtp { info_log_path = /var/log/dovelmtp.log mail_plugins = " sieve" } protocol lda { info_log_path = /var/log/doveinfo.log log_path = /var/log/dovelda.log } protocol imap { imap_idle_notify_interval = 1 mins imap_max_line_length = 64 k mail_max_userip_connections = 5 } /mf/home/jeep/shell/.signature

2 4

[Dovecot] last login timestamp
by Oscar A. Jara 30 Apr '13

30 Apr '13

Hello, I am settiing up a dovecot (imap, pop, sieve, lda) + openldap infrastructure. I need to store the timestamp of the last login of each user in an attribute of its corresponding ldap object. I could not find a way of doing this through configuration options so I am thinking of coding this task into the dovecot-auth source code, maybe in the passdb-ldap.c file. What do you recomend about this? Thanks. __________ Information from ESET Mail Security, version of virus signature database 8278 (20130429) __________ The message was checked by ESET Mail Security. http://www.eset.com

6 9

[Dovecot] mailbox_list_index_parse_header crash
by Kyle Wheeler 29 Apr '13

29 Apr '13

Hi, I got all excited about IMAP NOTIFY support and tried enabling mailbox_list_index on my server. Unfortunately, I rather quickly ran into trouble of the segfault variety. This prevented me from doing basic things like seeing the contents of some of my folders. Disabling mailbox_list_index got me back up and running, but... darnit, that's annoying. The only message I got in my log file was this: imap(user@domain): Fatal: master: service(imap): child 6899 killed with signal 11 (core dumped) If I can help track this down, please let me know. Here's the backtrace: #0 hash_table_insert_node (table=0x10eff60, key=0x103, value=0x10fd8b0, check_existing=<value optimized out>) at hash.c:268 node = 0x69616d2d746e6573 prev = 0x10fbee0 hash = <value optimized out> __FUNCTION__ = "hash_table_insert_node" #1 0x00007fad738a11be in hash_table_insert (table=0x10eff60, key=0x1, value=0x101) at hash.c:285 node = 0x0 #2 0x00007fad73b81e68 in mailbox_list_index_parse_header (list=<value optimized out>, view=0x11095f0, force=<value optimized out>) at mailbox-list-index.c:196 data = 0x10f5f30 i = 4980 len = 1 size = 8192 id = 1 #3 mailbox_list_index_parse (list=<value optimized out>, view=0x11095f0, force=<value optimized out>) at mailbox-list-index.c:317 ilist = 0x10edc80 hdr = <value optimized out> error = 0x10f5820 "`▒\016\001" __FUNCTION__ = "mailbox_list_index_parse" #4 0x00007fad73b86b03 in mailbox_list_index_sync_begin (list=0x10ed890, sync_ctx_r=0x7fff2ad61ee0) at mailbox-list-index-sync.c:247 ilist = 0x10edc80 sync_ctx = <value optimized out> index_sync_ctx = <value optimized out> view = 0x11095f0 trans = <value optimized out> hdr = <value optimized out> #5 0x00007fad73b86ffb in mailbox_list_index_sync (list=0x10eff60) at mailbox-list-index-sync.c:382 sync_ctx = 0x1107300 ret = <value optimized out> #6 0x00007fad73b8233f in mailbox_list_index_refresh (list=0x10ed890) at mailbox-list-index.c:376 ilist = 0x10edc80 view = 0x1107300 ret = <value optimized out> #7 0x00007fad73b85e19 in index_list_update_mailbox (box=0x10f40a0) at mailbox-list-index-status.c:363 list_sync_ctx = 0x1107140 list_view = <value optimized out> list_trans = <value optimized out> changes = {status = {messages = 718675880, recent = 32767, unseen = 4294967295, uidvalidity = 0, uidnext = 68, first_unseen_seq = 0, first_recent_uid = 1, last_cached_seq = 0, highest_modseq = 3176264, highest_pvt_modseq = 17854784, keywords = 0x10f40a0, permanent_flags = 17778368, permanent_keywords = 0, allow_new_keywords = 0, nonpermanent_modseqs = 0, have_guids = 0}, guid = "p ▒*▒\177\000\000D\000\000\000\000\000\000", seq = 17750944, rec_changed = false, msgs_changed = false, hmodseq_changed = false} __FUNCTION__ = "index_list_update_mailbox" #8 0x00007fad73b86089 in index_list_sync_deinit (ctx=0x1107140, status_r=0x7fff2ad62070) at mailbox-list-index-status.c:470 box = 0x10f40a0 #9 0x00007fad73b70f4a in mailbox_sync_deinit (_ctx=0x0, status_r=0x1) at mail-storage.c:1655 ctx = 0x10eff60 box = 0x10f40a0 errormsg = <value optimized out> error = <value optimized out> ret = <value optimized out> #10 0x00007fad73b7100b in mailbox_sync (box=<value optimized out>, flags=<value optimized out>) at mail-storage.c:1681 ctx = 0x0 status = {sync_delayed_expunges = 0} #11 0x00007fad73b9af72 in index_storage_get_status (box=0x10f40a0, items=17, status_r=<value optimized out>) at index-status.c:39 No locals. #12 0x00007fad72cabde4 in fts_mailbox_get_status (box=0x10f40a0, items=17, status_r=0x7fff2ad621b0) at fts-storage.c:86 seq = <value optimized out> #13 0x00007fad73b864e6 in index_list_get_status (box=0x10f40a0, items=17, status_r=0x7fff2ad621b0) at mailbox-list-index-status.c:162 No locals. #14 0x000000000041c8da in imap_status_get (cmd=0x10f1880, ns=0x10e8b00, mailbox=0x10cc2c8 "Flight.RV", items=0x7fff2ad62240, result_r=0x7fff2ad621b0) at imap-status.c:84 client = 0x10f0ce0 box = 0x10f40a0 errstr = <value optimized out> ret = <value optimized out> #15 0x000000000041219d in cmd_status (cmd=0x10f1880) at cmd-status.c:40 client = 0x10f0ce0 args = 0x10d7a38 list_args = 0x10d7be0 items = {status = 17, metadata = 0} result = {status = {messages = 0, recent = 0, unseen = 0, uidvalidity = 0, uidnext = 0, first_unseen_seq = 0, first_recent_uid = 0, last_cached_seq = 0, highest_modseq = 0, highest_pvt_modseq = 0, keywords = 0x0, permanent_flags = 0, permanent_keywords = 0, allow_new_keywords = 0, nonpermanent_modseqs = 0, have_guids = 1}, metadata = {guid = "PY\r\001", '\000' <repeats 11 times>, virtual_size = 17651520, cache_fields = 0x7fad73836e40, precache_fields = 1934521552, backend_ns_prefix = 0x7fad74012000 "", backend_ns_type = 1080}, error = 4294967295, errstr = 0xffffffffffffffa8 <Address 0xffffffffffffffa8 out of bounds>} ns = <value optimized out> mailbox = 0x10cc2c8 "Flight.RV" orig_mailbox = 0x10d7b98 "Flight.RV" #16 0x00000000004160ad in command_exec (cmd=0x10f1880) at imap-commands.c:156 hook = 0x10d5d90 ret = <value optimized out> #17 0x0000000000415200 in client_command_input (cmd=0x10f1880) at imap-client.c:775 client = 0x10f0ce0 command = <value optimized out> __FUNCTION__ = "client_command_input" #18 0x00000000004152ed in client_command_input (cmd=0x10f1880) at imap-client.c:836 client = 0x10f0ce0 command = 0x0 __FUNCTION__ = "client_command_input" #19 0x000000000041556d in client_handle_next_command (client=0x10f0ce0) at imap-client.c:874 No locals. #20 client_handle_input (client=0x10f0ce0) at imap-client.c:886 _data_stack_cur_id = 3 ret = 208 remove_io = <value optimized out> handled_commands = false __FUNCTION__ = "client_handle_input" #21 0x00000000004158ef in client_input (client=0x10f0ce0) at imap-client.c:928 cmd = <value optimized out> output = 0x10f16d8 bytes = <value optimized out> __FUNCTION__ = "client_input" #22 0x00007fad738abdf6 in io_loop_call_io (io=0x10f1780) at ioloop.c:387 ioloop = 0x10d4720 t_id = 2 #23 0x00007fad738ace6f in io_loop_handler_run (ioloop=<value optimized out>) at ioloop-epoll.c:215 ctx = 0x10d4aa0 event = 0x10d4b10 list = 0x10f17d0 io = 0x10eff60 tv = {tv_sec = 1799, tv_usec = 999580} msecs = <value optimized out> ret = 1 i = 0 call = false __FUNCTION__ = "io_loop_handler_run" #24 0x00007fad738abd98 in io_loop_run (ioloop=0x10d4720) at ioloop.c:406 No locals. #25 0x00007fad738621b3 in master_service_run (service=0x10d45b0, callback=0x1) at master-service.c:560 No locals. #26 0x000000000041eb67 in main (argc=1, argv=0x10d4390) at main.c:400 set_roots = {0x426200, 0x0} login_set = {auth_socket_path = 0x10cc050 "(", postlogin_socket_path = 0x0, postlogin_timeout_secs = 60, callback = 0x41ed60 <login_client_connected>, failure_callback = 0x41ed00 <login_client_failed>, request_auth_token = 1} service_flags = <value optimized out> storage_service_flags = MAIL_STORAGE_SERVICE_FLAG_DISALLOW_ROOT username = 0x0 c = <value optimized out> ~Kyle -- For every complex problem, there is a solution that is simple, neat, and wrong. -- H. L. Mencken

2 4

[Dovecot] Dovecot 2.1.16 doveadm purge -A segfault
by Daniel Parthey 29 Apr '13

29 Apr '13

Hi, I know that a lot of work has been done regarding doveadm server, but I'm still experiencing easily reproducible segfault crashes of doveadm-server with 2.1.16 when running the following command in a 4 node director/mailbox cluster: /usr/bin/doveadm -c /etc/dovecot-director/dovecot-director.conf -D purge -A The dovecot-error.log shows the following errors (addresses anonymized): Apr 29 15:45:14 10.129.3.233 dovecot: doveadm: Error: purge: invalid option -- '' Apr 29 15:45:14 10.129.3.233 dovecot: doveadm(x.xxxxxx(a)xxx-xxxxxx.xx): Error: doveadm purge: Client sent unknown parameter: ? Apr 29 15:45:14 10.129.3.233 dovecot: doveadm: Error: purge: invalid option -- '�' Apr 29 15:45:14 10.129.3.233 dovecot: doveadm(x.xxxxxx(a)xxx-xxxxxx.xx): Error: doveadm purge: Client sent unknown parameter: ? Apr 29 15:45:14 10.129.3.249 dovecot: doveadm: Error: purge: invalid option -- '�' Apr 29 15:45:14 10.129.3.249 dovecot: doveadm(x.xxxxxx(a)xxx-xxxxxx.xx): Error: doveadm purge: Client sent unknown parameter: ? Apr 29 15:45:14 10.129.3.249 dovecot: doveadm: Error: purge: invalid option -- 'r' Apr 29 15:45:14 10.129.3.249 dovecot: doveadm(x.xxxxxx(a)xxx-xxxxxx.xx): Error: doveadm purge: Client sent unknown parameter: ? Apr 29 15:45:14 10.129.3.213 dovecot: doveadm: Error: purge: invalid option -- 'e' Apr 29 15:45:14 10.129.3.213 dovecot: doveadm(xxxxx(a)xxxxxx.xx): Error: doveadm purge: Client sent unknown parameter: ? Apr 29 15:45:14 10.129.3.213 dovecot: doveadm: Error: purge: invalid option -- 'g' Apr 29 15:45:14 10.129.3.213 dovecot: doveadm(xxxxx(a)xxxxxx.xx): Error: doveadm purge: Client sent unknown parameter: ? Apr 29 15:45:14 10.129.3.213 dovecot: doveadm: Error: purge: invalid option -- 'e' Apr 29 15:45:14 10.129.3.213 dovecot: doveadm(xxxxx(a)xxxxxx.xx): Error: doveadm purge: Client sent unknown parameter: ? Apr 29 15:45:14 10.129.3.213 dovecot: doveadm: Error: purge: invalid option -- '-' Apr 29 15:45:14 10.129.3.213 dovecot: doveadm(xxxxx(a)xxxxxx.xx): Error: doveadm purge: Client sent unknown parameter: ? Apr 29 15:45:14 10.129.3.249 dovecot: doveadm: Error: purge: invalid option -- '' Apr 29 15:45:14 10.129.3.249 dovecot: doveadm(xxxxxxxxxx(a)xxxxxxxxxx.xx): Error: doveadm purge: Client sent unknown parameter: ? Apr 29 15:45:14 10.129.3.213 dovecot: doveadm(xxxxx(a)xxxxxx.xx): Fatal: master: service(doveadm): child 6316 killed with signal 11 (core dumped) There seems to something wrong with the doveadm command parser: # gdb /usr/lib/dovecot/doveadm-server /var/tmp/6316 (gdb) bt full #0 0x00007f52f0dc7cca in ?? () from /lib/libc.so.6 No symbol table info available. #1 0x00007f52f0dc8dab in ?? () from /lib/libc.so.6 No symbol table info available. #2 0x00007f52f0dc8e18 in getopt () from /lib/libc.so.6 No symbol table info available. #3 0x00000000004138ce in doveadm_mail_cmd_server_parse (conn=0xe09ad0) at client-connection.c:69 getopt_args = 0xdfa6b8 "AS:u:" c = <value optimized out> cmd = 0xe062c8 add_username_header = false #4 client_handle_command (conn=0xe09ad0) at client-connection.c:223 ctx = 0xe0dae0 flags = <value optimized out> cmd_name = <value optimized out> input = {module = 0x0, service = 0x4210f0 "doveadm", username = 0xdfa59a "xxxxxxx(a)xxxxxxxx.xx", session_id = 0x0, local_ip = {family = 0, u = {ip6 = {__in6_u = {__u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, ip4 = {s_addr = 0}}}, remote_ip = {family = 0, u = {ip6 = {__in6_u = {__u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, ip4 = {s_addr = 0}}}, local_port = 0, remote_port = 0, userdb_fields = 0x0, flags_override_add = 0, flags_override_remove = 0, no_userdb_lookup = 0} argc = <value optimized out> #5 client_connection_input (conn=0xe09ad0) at client-connection.c:326 args = <value optimized out> _data_stack_cur_id = 3 line = <value optimized out> ok = <value optimized out> #6 0x00007f52f10e6166 in io_loop_call_io (io=0xe097e0) at ioloop.c:379 ioloop = 0xe026a0 t_id = 2 #7 0x00007f52f10e71ef in io_loop_handler_run (ioloop=<value optimized out>) at ioloop-epoll.c:213 ctx = 0xe054f0 event = 0xe05560 list = 0xe09950 io = 0xdfa5c8 tv = {tv_sec = 2147483, tv_usec = 0} msecs = <value optimized out> ret = <value optimized out> i = 0 call = false #8 0x00007f52f10e6108 in io_loop_run (ioloop=0xe026a0) at ioloop.c:398 No locals. #9 0x00007f52f10d15a3 in master_service_run (service=0xe02550, callback=0) at master-service.c:544 No locals. #10 0x0000000000414111 in main (argc=1, argv=0xe02370) at main.c:90 set_roots = {0x422780, 0x0} error = 0x0 Regards Daniel -- https://plus.google.com/103021802792276734820

1 0

[Dovecot] Dovecot Solr Panic
by Andre Rodier 29 Apr '13

29 Apr '13

Hello Everyone, I have a small base of users (30), but a lot of emails. I have an error again when I am indexing a virtual folder with a large number of folders. I appreciate this is a special case, but I am using dovecot and solr as it is, according to the documentation, the favourite way. One user is using a large number of archives sub folders, by years, months and subfolders, since 5 years. I am convincing this user to give up this organisation, but in the mean time, I hope to solve this problem. The virtual folder, called Archives, references all the sub folders in the Archive folder. There is about 380 folders, and worst of all, 55k characters with their names concatenated. On solr, I have increased the value of headerBufferSize to a huge value, but I have still this error. Anyway, this is the error I have when I try to index this virtual folder: ---8<--------------------------------------------------------------------------------------------------------------------------------------- root@lapetus:/mnt/emails/indiefield.co.uk/jsmith/Mails/Virtual# doveadm -v index -u 'john smith' 'Search/Archives' doveadm(john smith): Info: Search/Archives: Caching mails seq=109580..127362 1800/17783doveadm(john smith): Panic: file solr-connection.c: line 416 (solr_connection_select): assertion failed: (!conn->posting) doveadm(john smith): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x4414a) [0x7fcb7b5b014a] -> /usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7fcb7b5b020a] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fcb7b58782a] -> /usr/lib/dovecot/modules/lib21_fts_solr_plugin.so(+0x754a) [0x7fcb790fa54a] -> /usr/lib/dovecot/modules/lib21_fts_solr_plugin.so(+0x4037) [0x7fcb790f7037] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(fts_backend_get_last_uid+0x5a) [0x7fcb79b2f66a] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0xc1fd) [0x7fcb79b341fd] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0xc689) [0x7fcb79b34689] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0xc51e) [0x7fcb79b3451e] -> doveadm(+0x16719) [0x7fcb7bf71719] -> doveadm(+0x13346) [0x7fcb7bf6e346] -> doveadm(+0x13e21) [0x7fcb7bf6ee21] -> doveadm(doveadm_mail_try_run+0x161) [0x7fcb7bf6f2e1] -> doveadm(main+0x3d1) [0x7fcb7bf6def1] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7fcb7b200ead] -> doveadm(+0x13125) [0x7fcb7bf6e125] Aborted ---8<--------------------------------------------------------------------------------------------------------------------------------------- On the solr side: ---8<--------------------------------------------------------------------------------------------------------------------------------------- 28-Apr-2013 17:13:33 org.apache.solr.update.processor.LogUpdateProcessor finish INFO: {add=[1/70af772eafc17c51fb350000812a8a77/john smith(a)indiefield.co.uk, 2/70af772eafc17c51fb350000812a8a77/john smith(a)indiefield.co.uk, 3/70af772eafc17c51fb350000812a8a 77/john smith(a)indiefield.co.uk, 4/70af772eafc17c51fb350000812a8a77/john smith(a)indiefield.co.uk, 5/70af772eafc17c51fb350000812a8a77/john smith(a)indiefield.co.uk, 6/70af772ea fc17c51fb350000812a8a77/john smith(a)indiefield.co.uk, 7/70af772eafc17c51fb350000812a8a77/john smith(a)indiefield.co.uk, 8/70af772eafc17c51fb350000812a8a77/john smith@indiefie ld.co.uk, ... (8 added)]} 0 19141 28-Apr-2013 17:13:33 org.apache.solr.common.SolrException log SEVERE: org.apache.solr.common.SolrException: ParseError at [row,col]:[1188418,131] Message: Premature end of file. at org.apache.solr.handler.XMLLoader.load(XMLLoader.java:72) at org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:54) at org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:131) at org.apache.solr.core.SolrCore.execute(SolrCore.java:1317) at org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:338) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:241) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:943) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:843) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1188418,131] Message: Premature end of file. at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:592) at org.apache.solr.handler.XMLLoader.readDoc(XMLLoader.java:273) at org.apache.solr.handler.XMLLoader.processUpdate(XMLLoader.java:138) at org.apache.solr.handler.XMLLoader.load(XMLLoader.java:69) ... 22 more ---8<--------------------------------------------------------------------------------------------------------------------------------------- Kind regards, Andre Rodier

3 3

[Dovecot] dovecot-sql.conf - Unknown setting: driver
by jeep＠rahul.net 27 Apr '13

27 Apr '13

Im upgrading my dovecot from 2.1.14 to dovecot 2.2.1 on linux. Im using the same configuration file against my MySQL db and getting the following error: doveconf -n # 2.2.1: /opt/dovecot221/etc/dovecot/dovecot.conf doveconf: Fatal: Error in configuration file /opt/dovecot221/etc/dovecot/conf.d/dovecot-sql.conf line 2: Unknown setting: driver dovecot-sql.conf: # The mysqld.sock socket may be in different locations in different systems driver = mysql # Use "host= ... pass=foo#bar" if your password has '#' character connect = host=/var/run/mysqld/mysqld.sock dbname=mydb user=username password=pass password_query = SELECT userid AS username, domain, password \ FROM users WHERE userid = '%n' AND domain = '%d' user_query = SELECT home, uid, gid FROM users WHERE userid = '%n' AND domain = '%d' home=/opt/ii/%1n/%n/INBOX # For using doveadm -A: iterate_query = SELECT userid AS username, domain FROM users That file worked fine in the last version. Looking at the docs 'driver' is still a valid setting. Can someone help me figure out why its complaining? Ive even Im lost as to why this error is occuring unless the error itself is actually another problem and the wrong error is popping up. Been working on this for a day and cant figure it out. Thanks in advance! /mf/home/jeep/shell/.signature

2 3

[Dovecot] Replication fails with "Remote dsync doesn't use compatible protocol"
by Rich Wales 27 Apr '13

27 Apr '13

I can't get replication to work in Dovecot 2.2.1. I'm getting the following error on the machine where I'm initiating the replication: richatwork dovecot: doveadm: Error: dsync-remote(richatwork): Error: dsync(local): Remote dsync doesn't use compatible protocol Both the local and remote servers are running identical versions of Dovecot (2.2.1), so I don't understand why I would be having any sort of "compatible protocol" problem. Any ideas? I posted the "dovecot -n" output for both servers in my earlier e-mail on this issue, which I sent about 24 hours ago (and which I assume was too long for people to be willing to read). Rich Wales richw(a)richw.org

1 1

[Dovecot] ios clients and namespace trouble
by Kelsey Cummings 27 Apr '13

27 Apr '13

We migrated to dovecot from courier and maintained a courier compatible namespace configuration. This resulted in ios clients needing to be manually configured in order to use the special folders correctly (delete messages, save drafts, etc) either by being given the correct "Path Prefix" or by manually selecting the special folders. I can't fathom why apple has chosen not to support or can't detect namespace correctly and require manual configuration but if they haven't done it by now they must have some reason for it and aren't going to fix it any time soon. Are there any creative solutions to fixing the i-clients and preventing them from needing manual configuration? -K

2 3

[Dovecot] .dovecot.sieve/tmp)failed: Not a directory
by JC Putter 25 Apr '13

25 Apr '13

stat(/var/spool/vmail/example.com/user/.dovecot.sieve/tmp)failed: Not a directory auth_mechanisms = plain login disable_plaintext_auth = no first_valid_uid = 2000 last_valid_uid = 2000 mail_gid = 2000 mail_location = maildir:/var/spool/vmail/%d/%n mail_uid = 2000 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/dovecot-sql.conf.ext driver = sql } service auth { unix_listener auth-userdb { group = vmail mode = 0600 user = vmail } } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } According to the Wiki "It is not wise to place this link inside your mail store, as it may be mistaken for a mail folder. Inside a maildir for instance, the default .dovecot.sieve would show up as phantom folder */dovecot/sieve* in your IMAP tree." Sorry i am a bit of a noob, the docs don't explain clearly what to do...

3 2

[Dovecot] Replication -- multiple users, three or more servers?
by Rich Wales 24 Apr '13

24 Apr '13

I'm running Dovecot 2.2.1 on an Ubuntu 12.04.2 server, with half a dozen accounts for various family members. I want to set up replication involving at least three Ubuntu servers, with different users replicated on different sets of servers. For example, I might have mail for "user1" replicated on "server1", "server2", and "server3"... while mail for "user2" would be on "server1" and "server2"... and mail for "user3" would be on "server1" and "server3". I've read the wiki page (http://wiki2.dovecot.org/Replication) but I'm still confused. I'd love to see an example that clearly shows how to set up specific individual mail users to be replicated on a different set of servers for each user, like what I described above. Rich Wales richw(a)richw.org

2 3

[Dovecot] login crashes - maybe too many simultan connections
by Frank Leonhardt 24 Apr '13

24 Apr '13

Hallo, since a few days, users sometimes have problems connecting to our mailserver, in the mail.err are many lines like this: Apr 23 11:14:25 psy2 dovecot: dovecot: child 17607 (login) killed with signal 11 (core dumps disabled) (ip=xx.xx.146.84) Users who are already logged in keep connected, but new connections are not possible.This happens only between 10 am and 3 pm, never in the early morning or at night, so i assume, maybe this is caused by too many simultaneous connections? After restarting dovecot the problem is temporary solved, new users may connect, but after one or a few days, this may happen again. # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.1 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login mail_privileged_group: alle mail_location: maildir:~/Maildir fsync_disable: yes mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 auth default: passdb: driver: pam args: dovecot userdb: driver: passwd May anybody help? Thanks in advance! Greetings from Frank.

2 1

[Dovecot] Strange issue with doveadm user
by Antoine Nguyen 24 Apr '13

24 Apr '13

Dear all, I encounter a strange issue with the *doveadm user* command. (dovecot 2.1.16) I try to retrieve information about a specific user but dovecot says it doesn't exist (whereas I just created it). The following command fails: $ sudo -u vmail doveadm user pouet(a)domain.tld userdb lookup: user pouet(a)domain.tld doesn't exist If I try a more global lookup, the user is properly found: $ sudo -u vmail doveadm user *(a)domain.tld user1(a)domain.tld *pouet(a)domain.tld* Sending a query for another user works well. For example : $ sudo -u vmail doveadm user user1(a)domain.tld userdb: user1(a)domain.tld home : /var/vmail/domain.tld/user1 uid : 500 gid : 500 quota_rule: *:bytes=100M I really don't understand what's happening... The only difference I see between the users is that user1 was created when I was using dovecot 1.2... Thanks for your help.

1 1