- dovecot - dovecot.org

[Dovecot] When you send an email with specific characters are included, dovecot.sieve is aborted.
by Atsuko Tanaka 07 May '14

07 May '14

Hello. I found a problem of dovecot.sieve. When you send an email with specific characters are included, dovecot.sieve is aborted. Are you sure I report details to this mailing list? Please reply. Thank you. -- ---------------------------------------- Atsuko Tanaka DesigNET Inc. e-mail：tanaka(a)designet.co.jp ----------------------------------------

2 2

[Dovecot] Some Information about compression rates to expect using zlib/xz compression
by Robert Nowotny 07 May '14

07 May '14

compression : xz, Level 6 here some compression rates I experienced : Diskspace usage : user1: uncompressed : 2.3GB --> compressed 1 GB user2: uncompressed : 6.2GB --> compressed 3.9 GB just for your reference Ing. Robert Nowotny Rotek GmbH Vienna/Austria

1 0

Re: [Dovecot] LMTP, TLS/SSL, authentication, proxy
by Stanislas SABATIER 06 May '14

06 May '14

Hello, unfortunatly, TLS doesn't seem to work on LMTP, anyway, not by simply put ssl=yet to the lmtp inet_listener. I've tried and when I *openssl s_client -connect* to the lmtp listener I've got the following response : CONNECTED(00000003) 34379118248:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:/usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s23_clnt.c:766: My postfix server can't neither establish a TLS connection on LMTP listener. On 22.10.2013, at 14.37, Jogi Hofmüller <jogi(a)mur.at> wrote: Can dovecot use TLS/SSL on LTMP inet socket? Oct 26, 2013 8:11:19 am , Timo Sirainen <tss(a)iki.fi> replied: Probably. Try adding ssl=yes to the inet_listener {}. --------------------------------------------------------------- Stanislas SABATIER s.sabatier(a)pobox.com ---------------------------------------------------------------

1 0

[Dovecot] Status of sieve-extdata?
by Jiri Bourek 06 May '14

06 May '14

Hi, I'd like to ask about status of extdata plugin for sieve. The wiki page (http://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/Extdata) mentions versions for PigeonHole 0.2 and 0.3, but there seems to be no version for 0.4 and Dovecot 2.2. Is the plugin dead or is it planned to make version for Dovecot 2.2 (when time allows I guess)? Regards J.

2 5

[Dovecot] on High Load using IMAPSYNC : Panic: file ostream-lzma.c: line 147: unreached. Dovecot 2.2.12 with zlib/XZ compression
by Robert Nowotny 06 May '14

06 May '14

when syncing Mailboxes with IMAPSYNC, using xz compression the dbox file gets corrupted. the same configuration was working ok on low load with xz compression. Dovecot Version 2.2.12 Linux Mint 16 EXT4 Filesystem another dovecot user already reported the same problem on the mailinglist, using dsync. That user switched to bz2 compression what worked for him. the answer was : > are you on latest patchlevel ? > there are some dsync fixes since 2.2.12 but it is not a problem of dsync. when looking at the code, we get here an unexpected returnvalue when flushing. I propose it would be good practice to write some logging in the default switch cases, to see the unexpected returnvalues in the errorlog. something like : ostream-lzma.c : -- Line 147 : i_unreached(); ++ Line 147 : i_fatal("unexpected lzma errorcode when flushing : %s", ret); I will try to change it and let You know. maybe You can also investigate and let me know when fixed. Here the log : May 5 14:53:10 vm-imap dovecot: imap(rrernboeck): Panic: file ostream-lzma.c: line 147: unreached May 5 14:53:10 vm-imap dovecot: imap(rrernboeck): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x67450) [0x7ff99d8ce450] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x6752e) [0x7ff99d8ce52e] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7ff99d88955e] -> /usr/local/lib/dovecot/lib20_zlib_plugin.so(+0x4f0a) [0x7ff99ce87f0a] -> /usr/local/lib/dovecot/libdovecot.so.0(o_stream_flush+0x3e) [0x7ff99d8e6dbe] -> /usr/local/lib/dovecot/libdovecot.so.0(o_stream_nflush+0xf) [0x7ff99d8e71df] -> /usr/local/lib/dovecot/libdovecot.so.0(o_stream_nfinish+0x9) [0x7ff99d8e7229] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(dbox_save_end+0x29) [0x7ff99db7cfa9] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mdbox_save_finish+0x39) [0x7ff99db76619] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_save_finish+0x4d) [0x7ff99dbb6a4d] -> dovecot/imap [rrernboeck 127.0.0.1 APPEND]() [0x40be09] -> dovecot/imap [rrernboeck 127.0.0.1 APPEND](command_exec+0x3c) [0x416cfc] -> dovecot/imap [rrernboeck 127.0.0.1 APPEND]() [0x40b491] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x27) [0x7ff99d8de527] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xd7) [0x7ff99d8df2b7] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7ff99d8de0c8] -> /usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7ff99d88e753] -> dovecot/imap [rrernboeck 127.0.0.1 APPEND](main+0x2af) [0x40b06f] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7ff99d4c0de5] -> dovecot/imap [rrernboeck 127.0.0.1 APPEND]() [0x40b1cc] May 5 14:53:10 vm-imap dovecot: imap(rrernboeck): Fatal: master: service(imap): child 47957 killed with signal 6 (core dumped) May 5 14:53:10 vm-imap dovecot: imap(rrernboeck): Error: Corrupted dbox file /home/vmail/virtualmailboxes/rrernboeck/storage/m.1 (around offset=1302): msg header has bad magic value

1 0

[Dovecot] doveadm auth and the "nologin" extra field
by Axel Luttgens 05 May '14

05 May '14

Hello, Still busy with details... Considering, as in my previous example, a password_query returning '!' or NULL for the "nologin" column, depending on an account's status (suspended or not). Let's consider a suspended user "some.user". In the case of a successful authentication, one has: sh-3.2# doveadm auth test some.user goodpassword; echo $? passdb: some.user auth succeeded extra fields: user=some.user nologin 0 On the other hand, in the case of an authentication failure: sh-3.2# doveadm auth test some.user badpassword; echo $? passdb: some.user auth failed extra fields: user=some.user nologin=! 77 So, this is similar to what happens in a connection (pop3, imap...): when present, the nologin info is always taken into account, even in the case of an authentication failure. Again, this may raise some concerns about the consistency of such a behavior. Is this guaranteed to always behave that way, because of some rationale I'm currently missing, or does it go about some overlooked combination, liable to be inadvertently "corrected" in the future? I haven't been able to find a definitive answer in the wiki or in the code about such matters. This is particularly important in the case of doveadm, since its output requires parsing for extracting such informations (the exit code alone isn't sufficient); should above behavior be changed without notice, and a script could suddenly take the worst decisions... BTW, why: nologin in the first output, and: nologin=! in the second output? TIA, Axel

2 2

[Dovecot] Segfault in dovecot-lda when resolver is unavailable
by Marcin Mirosław 05 May '14

05 May '14

Hi list! Recently I noticed that dovecot-lda throws segfault when resolver is unavailable and with imapc configured. $ cat /etc/resolv.conf search . nameserver 127.0.0.1 backtrace: # gdb -q /usr/libexec/dovecot/dovecot-lda 'core-1398282784-8-11-!usr!libexec!dovecot!dovecot-lda-8805' [...] Core was generated by `/usr/libexec/dovecot/deliver -d marcin(a)mejor.pl'. Program terminated with signal 11, Segmentation fault. #0 0x000002b612afaf72 in _int_free (av=0x2b612e215c0 <main_arena>, p=0x1b23bfabe0, have_lock=0) at malloc.c:3903 3903 unlink(p, bck, fwd); (gdb) bt #0 0x000002b612afaf72 in _int_free (av=0x2b612e215c0 <main_arena>, p=0x1b23bfabe0, have_lock=0) at malloc.c:3903 #1 0x000002b612e96a4e in buffer_free (_buf=_buf@entry=0x1b23bfa948) at buffer.c:144 #2 0x000002b612ebeca8 in array_free_i (array=0x1b23bfa948) at array.h:108 #3 priorityq_deinit (_pq=_pq@entry=0x1b23bfabb0) at priorityq.c:38 #4 0x000002b612eafa57 in io_loop_destroy (_ioloop=_ioloop@entry=0x395a4da91d0) at ioloop.c:495 #5 0x000002b61306f225 in imapc_client_run_post (client=<optimized out>) at imapc-client.c:175 #6 imapc_client_run (client=0x1b23bda930) at imapc-client.c:181 #7 0x000002b613067158 in imapc_list_try_get_root_sep (list=0x1b23bd7b60, sep_r=sep_r@entry=0x395a4da9247 "") at imapc-list.c:297 #8 0x000002b6130671ae in imapc_list_get_hierarchy_sep (_list=<optimized out>) at imapc-list.c:310 #9 0x000002b613065d9f in imapc_list_get_fs_name (list=0x1b23bd7b60, name=0x0) at imapc-list.c:396 #10 0x000002b613066031 in imapc_list_get_path (_list=0x1b23bd7b60, name=0x0, type=MAILBOX_LIST_PATH_TYPE_MAILBOX, path_r=0x395a4da9338) at imapc-list.c:437 #11 0x000002b613089785 in mailbox_list_get_root_path (list=<optimized out>, type=type@entry=MAILBOX_LIST_PATH_TYPE_MAILBOX, path_r=path_r@entry=0x395a4da9338) at mailbox-list.c:1276 #12 0x000002b612ff8eb5 in quota_add_user_namespace (quota=0x1b23bcea80, ns=0x1b23bd7a10) at quota.c:745 #13 0x000002b61300073a in quota_mailbox_list_created (list=0x1b23bfd9c0) at quota-storage.c:590 #14 0x000002b613084581 in hook_mailbox_list_created (list=list@entry=0x1b23bfd9c0) at mail-storage-hooks.c:328 #15 0x000002b61308836f in mailbox_list_create (driver=driver@entry=0x2b6130e677b "maildir++", ns=0x1b23bd7a10, set=set@entry=0x395a4da94a0, flags=<optimized out>, list_r=list_r@entry=0x1b23bd7d60, error_r=error_r@entry=0x395a4da9498) at mailbox-list.c:210 #16 0x000002b613065cf6 in imapc_list_get_fs (list=list@entry=0x1b23bd7b60) at imapc-list.c:379 #17 0x000002b61306601e in imapc_list_get_path (_list=0x1b23bd7b60, name=0x0, type=MAILBOX_LIST_PATH_TYPE_MAILBOX, path_r=0x395a4da9588) at imapc-list.c:433 #18 0x000002b613089785 in mailbox_list_get_root_path (list=<optimized out>, type=type@entry=MAILBOX_LIST_PATH_TYPE_MAILBOX, path_r=path_r@entry=0x395a4da9588) at mailbox-list.c:1276 #19 0x000002b612ff8eb5 in quota_add_user_namespace (quota=0x1b23bcea80, ns=0x1b23bd7a10) at quota.c:745 #20 0x000002b61300073a in quota_mailbox_list_created (list=0x1b23bd7b60) at quota-storage.c:590 #21 0x000002b613084581 in hook_mailbox_list_created (list=list@entry=0x1b23bd7b60) at mail-storage-hooks.c:328 #22 0x000002b61308836f in mailbox_list_create (driver=driver@entry=0x2b6130e6d1b "imapc", ns=ns@entry=0x1b23bd7a10, set=set@entry=0x395a4da9720, flags=<optimized out>, list_r=list_r@entry=0x395a4da9708, error_r=error_r@entry=0x395a4da9810) at mailbox-list.c:210 #23 0x000002b61307f500 in mail_storage_create_full (ns=ns@entry=0x1b23bd7a10, driver=<optimized out>, driver@entry=0x0, data=<optimized out>, flags=flags@entry=(unknown: 0), storage_r=storage_r@entry=0x395a4da97c0, error_r=error_r@entry=0x395a4da9810) at mail-storage.c:356 #24 0x000002b61307f7cc in mail_storage_create (ns=ns@entry=0x1b23bd7a10, driver=driver@entry=0x0, flags=flags@entry=(unknown: 0), error_r=error_r@entry=0x395a4da9810) at mail-storage.c:407 #25 0x000002b613077a48 in namespace_add (user=user@entry=0x1b23bcf7e0, ns_set=0x1b23bd0db8, unexpanded_ns_set=0x1b23bcff30, mail_set=mail_set@entry=0x1b23bd07e8, ns_p=ns_p@entry=0x1b23bd3b00, error_r=error_r@entry=0x395a4da9950) at mail-namespace.c:170 #26 0x000002b613078aaf in mail_namespaces_init (user=0x1b23bcf7e0, error_r=error_r@entry=0x395a4da9950) at mail-namespace.c:344 #27 0x000002b6130901bf in mail_storage_service_init_post (error_r=0x395a4da9950, mail_user_r=0x395a4da9b18, priv=0x395a4da9960, user=0x1b23bbde50, ctx=<optimized out>) at mail-storage-service.c:685 #28 mail_storage_service_next (ctx=ctx@entry=0x1b23bbd4f0, user=0x1b23bbde50, mail_user_r=mail_user_r@entry=0x395a4da9b18) at mail-storage-service.c:1223 #29 0x000002b6130904b5 in mail_storage_service_lookup_next (ctx=0x1b23bbd4f0, input=input@entry=0x395a4da9b80, user_r=user_r@entry=0x395a4da9a70, mail_user_r=mail_user_r@entry=0x395a4da9b18, error_r=error_r@entry=0x395a4da9a60) at mail-storage-service.c:1258 #30 0x0000001b22341ccb in main (argc=3, argv=0x1b23bbb060) at main.c:412 # doveconf -n # 2.2.12: /etc/dovecot/dovecot.conf # OS: Linux 3.13.8-hardened x86_64 Gentoo Base System release 2.2 auth_cache_size = 1 k auth_master_user_separator = * auth_mechanisms = login digest-md5 cram-md5 plain deliver_log_format = msgid=%m: from=%f: phys=%p: virt=%w %$ dict { quota = pgsql:/etc/dovecot/dovecot-dict-sql.conf.ext } first_valid_uid = 8 last_valid_uid = 8 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_attachment_dir = /dane/domeny/zalaczniki mail_attachment_min_size = 10000 k mail_cache_min_mail_count = 20 mail_gid = mail mail_log_prefix = "%s(%u) <%{session}>: " mail_plugins = quota notify mail_log stats zlib mail_privileged_group = mail mail_uid = mail maildir_stat_dirs = yes managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy inc$ ude variables body enotify environment mailbox date ihave mdbox_preallocate_space = yes mdbox_rotate_interval = 60 days mdbox_rotate_size = 50 M namespace inbox { inbox = yes list = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = . subscriptions = yes } passdb { args = /etc/dovecot/.master.user driver = passwd-file master = yes pass = yes } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { quota = dict:User quota::proxy::quota sieve = ~/.dovecot.sieve sieve_dir = ~/sieve stats_command_min_time = 1 mins stats_domain_min_time = 12 hours stats_ip_min_time = 12 hours stats_memory_limit = 1M stats_refresh = 30 s stats_session_min_time = 15 mins stats_track_cmds = yes stats_user_min_time = 1 hours zlib_save = bz2 zlib_save_level = 2 } postmaster_address = postmaster(a)mejor.pl protocols = imap pop3 sieve service auth { unix_listener auth-userdb { group = mail mode = 0660 user = root } } service dict { unix_listener dict { user = mail } } service stats { fifo_listener stats-mail { mode = 0600 user = mail } } ssl_cert = </etc/ssl/gwiazdka.mejor.pl.pem ssl_key = </etc/ssl/gwiazdka.mejor.pl.pem userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } verbose_proctitle = yes protocol lda { mail_plugins = quota notify mail_log stats zlib sieve } protocol imap { mail_max_userip_connections = 25 mail_plugins = quota notify mail_log stats zlib imap_quota imap_stats imap_zlib } Thanks, Marcin

2 2

[Dovecot] %{orig_user} missing in checkpassword-Script
by dovecot.pkoch＠dfgh.net 05 May '14

05 May '14

Dear dovecot maintainers: I'm using SSL client certificates together with a checkpassword scripts to authenticate our users. My problem is: In the checkpassword script the AUTH_USER environment variable will either contain the username that was configured in the mailclient (if auth_ssl_username_from_cert=false) or the username from the certificate (if auth_ssl_username_from_cert=true). I would like to compare both values, i.e. the %{user} Dovecot-variable and the %{orig_user} Dovecot-variable. But the environment of a checkpassword-script has only one of them. I tried myself and found the following: - the environment of a checkpassword script is setup by checkpassword_setup_env() in db-checkpassword.c - checkpassword_setup_env() calls env_put_auth_vars() - env_put_auth_vars() creates AUTH_xxx environment variables for all entries of the auth_request_get_var_expand_table() - the auth_request_get_var_expand_table_full() routine does not contain the original user, but the auth_request-struct does. So I changed the dovecot sourcecode (version 2.2.12) as follows In src/auth/auth-request.h line 152 I replaced #define AUTH_REQUEST_VAR_TAB_COUNT 27 by #define AUTH_REQUEST_VAR_TAB_COUNT 30 In src/auth/auth-request.c around line 2027 I replaced the following lines at the end of auth_request_var_expand_static_tab { '\0', NULL, "session_pid" }, /* be sure to update AUTH_REQUEST_VAR_TAB_COUNT */ { '\0', NULL, NULL } }; by { '\0', NULL, "session_pid" }, { '\0', NULL, "orig_user" }, { '\0', NULL, "orig_username" }, { '\0', NULL, "orig_domain" }, /* be sure to update AUTH_REQUEST_VAR_TAB_COUNT */ { '\0', NULL, NULL } }; In src/auth/auth-request.c around line 2116 I replaced the following lines at the end of function auth_request_get_var_expand_table_full() tab[26].value = auth_request->session_pid == (pid_t)-1 ? NULL : dec2str(auth_request->session_pid); return ret_tab; by tab[26].value = auth_request->session_pid == (pid_t)-1 ? NULL : dec2str(auth_request->session_pid); if (auth_request->original_username != NULL) { tab[27].value = escape_func(auth_request->original_username, auth_request); tab[28].value = escape_func(t_strcut(auth_request->original_username, '@'), auth_request); tab[29].value = strchr(auth_request->original_username, '@'); if (tab[29].value != NULL) { tab[29].value = escape_func(tab[29].value+1, auth_request); } } return ret_tab; This will add AUTH_ORIG_USER, AUTH_ORIG_USERNAME and AUTH_ORIG_DOMAIN environment variables to the environment of every checkpassword script. If this is the correct way to extend the environment of a chackpassword-script then you might consider adding these minor changes to the dovecot-source. Kind regards and thanks very much for this wonderful project Peter Koch

2 1

[Dovecot] CONTEXT=SORT
by Michael M Slusarz 05 May '14

05 May '14

Any reason this is not listed in the CAPABILITY string? I see it listed as a TODO here: http://wiki2.dovecot.org/Roadmap But it seems to work fine (as of 2.2.12): 1 UID SORT RETURN (CONTEXT COUNT) (SUBJECT) UTF-8 UNDELETED * ESEARCH (TAG "1") UID COUNT 12 1 OK Sort completed (0.000 secs). 2 UID SORT RETURN (UPDATE COUNT) (SUBJECT) UTF-8 UNDELETED * ESEARCH (TAG "2") UID COUNT 12 2 OK Sort completed (0.000 secs). [Add message to mailbox] 3 NOOP * 13 EXISTS * 1 RECENT * ESEARCH (TAG "2") UID ADDTO (0 62475) 3 OK NOOP completed. 4 CANCELUPDATE "2" 4 OK Updates cancelled. 5 UID SORT RETURN (PARTIAL 1:10) (SUBJECT) UTF-8 UNDELETED * ESEARCH (TAG "5") UID PARTIAL (1:10 NIL) 5 OK Sort completed (0.000 secs). michael

2 2

[Dovecot] Dovecot proxy
by Alex Ferrara 05 May '14

05 May '14

Hi everyone, I have a problem that hopefully has an easy solution. I am setting up an IMAP proxy in a DMZ network. It will connect to the real IMAP server and authenticate using "driver = imap", and this I have working really nicely. What I want to do is have it look up a list of users that are allowed to connect through the proxy before proxying the connection, as not all users with an account are permitted to access their email from the internet. I thought that using a post-login script would get me out of trouble, but it isn't possible in a relay configuration. dovecot.conf ## Dovecot configuration file mail_uid = dovecot mail_gid = dovecot protocols = imap listen = *, :: passdb { driver = imap # IMAP server to authenticate against args = host=192.168.1.1 # IMAP server to connect to for mailbox default_fields = proxy=yes host=192.168.1.1 } userdb { driver = prefetch } auth_mechanisms = plain login # This is the auth service used by Postfix to do dovecot auth. service auth { unix_listener auth-userdb { } inet_listener { port = 12345 } } ## ## SSL settings ## # These will need to ba adjusted to point to *your* certificates, not mine 8-) # The ssl_ca line refers to the intermediate certificate bundle which may or may not be required by your SSL provider ssl_cert = </etc/ssl/certs/mail.domain.com.au.pem ssl_key = </etc/ssl/private/mail.domain.com.au.key #ssl_ca = </etc/pki/tls/certs/ca.crt ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:!aNULL

2 2

[Dovecot] Dsyncing mail in director setup
by Murray Trainer 05 May '14

05 May '14

Hi All, I have a pair of dovecot director proxies and six dovecot backend mailstores using NFS v4.1 to access five filesystems on EMC VNX NFS storage. This is all working fine until I try and dsync new email mailboxes via one of the mailstores onto the NFS storage. I get major NFS lockups at random on one or more of the mailstores with none of the NFS mounts accessible on one or more of the mailstores. I am getting our storage guy to look into it to see if it is just a performance issue. I can understand there may be locking issues but I wouldn't have thought it would have this effect. I also wonderif there is a better way to run dsync so it handle writing to NFS? Maybe passing it some of the nfs related dovecot options? Thanks Murray

1 0

[Dovecot] Dovecot/Postfix Auth, howto not working ?
by Matt . 05 May '14

05 May '14

Hi Guys, I'm trying to auth Dovecot agains FreeIPA using this tut: http://www.freeipa.org/page/Dovecot_IMAPS_Integration_with_FreeIPA_using_Si… (and also Postfix using this: https://www.dalemacartney.com/2013/03/14/deploying-postfix-with-ldap-freeip… it should be working with dovecot at the end I believe) I'm having some issues here and get the following errors no matter what I do: May 4 23:13:18 mail-01 dovecot: auth: Fatal: No passdbs specified in configuration file. LOGIN mechanism needs one May 4 23:13:18 mail-01 postfix/smtpd[2949]: error: open database /etc/aliases.db: No such file or directory May 4 23:13:18 mail-01 postfix/smtpd[2949]: warning: dict_nis_init: NIS domain name not set - NIS lookups disabled May 4 23:13:18 mail-01 dovecot: master: Error: service(auth): command startup failed, throttling May 4 23:13:18 mail-01 postfix/smtpd[2949]: connect from unknown[xxx.xxx.xxx.xxx] May 4 23:13:28 mail-01 dovecot: imap-login: Disconnected (no auth attempts): rip=xxx.xxx.xxx.xxx, lip=xxx.xxx.xxx.xxx May 4 23:13:28 mail-01 postfix/smtpd[2949]: fatal: no SASL authentication mechanisms May 4 23:13:29 mail-01 postfix/master[1627]: warning: process /usr/lib/postfix/smtpd pid 2949 exit status 1 May 4 23:13:29 mail-01 postfix/master[1627]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling May 4 23:14:18 mail-01 dovecot: auth: Fatal: No passdbs specified in configuration file. LOGIN mechanism needs one May 4 23:14:18 mail-01 dovecot: master: Error: service(auth): command startup failed, throttling May 4 23:15:09 mail-01 postfix/anvil[2952]: statistics: max connection rate 1/60s for (smtp:xxx.xxx.xxx.xxx) at May 4 23:13:18 May 4 23:15:09 mail-01 postfix/anvil[2952]: statistics: max connection count 1 for (smtp:xxx.xxx.xxx.xxx) at May 4 23:13:18 May 4 23:15:09 mail-01 postfix/anvil[2952]: statistics: max cache size 1 at May 4 23:13:18 Outside the issue that it cannot find the aliasses db, I'm kinda stuck here... the tut should be working "out of the box", but I have the feeling I'm missing something here. I hope someone can help me out! Thanks! Matt

1 0

[Dovecot] Unknown user when sending internal email
by SIW 04 May '14

04 May '14

I use MySQL to store my virtual users, domains and aliases. My database is setup as follows: |CREATE| |TABLE| |`dovecot_passwords` (| |||`username` ||varchar||(100) ||NOT| |NULL||,| |||`appname` ||varchar||(50) ||NOT| |NULL||,| |||`||password||` varbinary(256) ||NOT| |NULL||,| |||PRIMARY| |KEY| |(`username`,`appname`)| |) I then add a users: | |INSERT| |INTO| |dovecot_passwords (username, appname, ||password||) ||VALUES||( ||'test(a)domain.com'||, ||'desktop'||, MD5(||'password'||) ); My /usr/local/etc/dovecot/dovecot-sql.conf.ext has: | |driver = mysql | |connect = host=127.0.0.1 dbname=mailserver user=mailuser password=blahblah| |default_pass_scheme = PLAIN password_query = SELECT NULL AS password,'Y' as nopassword, username AS user||||FROM dovecot_passwords||||WHERE username = '%u' AND password=MD5(REPLACE('%w',' ','')) Logging in works great and I can use a desktop email client or webmail just fine to check email. The problem occurs when I try to email another user in MY domain. When I send an email from user1(a)domain.com to user2(a)domain.com I get the following error in the logs: to=<user1(a)domain.com>, relay=mail.domain.com[private/dovecot-lmtp], delay=0.08, delays=0.05/0.01/0/0.02, dsn=5.1.1, status=bounced (host mail.domain.com[private/dovecot-lmtp] said: 550 5.1.1 <user1(a)domain.com> User doesn't exist: user1(a)domain.com (in reply to RCPT TO command)) | I thought it may have something to do with this: http://wiki2.dovecot.org/DomainLost To quote: SQL password_query gets often misconfigured to drop the domain if username and domain are stored separately. For example: # BROKEN: password_query = SELECT username AS user, password FROM users WHERE username = '%n' AND domain = '%d' The "username AS user" changes the username permanently and the domain is dropped. You can instead use: # MySQL: password_query = SELECT concat(username, '@', domain) AS user, password FROM users WHERE username = '%n' AND domain = '%d' Despite the above I didn't have any luck. From what I can tell in the logs it is using the username AND domain for the user (and not dropping off the domain). Does anyone know how I can get local mail delivery to work again? I have changed the way my users are stored in MySQL so that I can make use of "Application Specific Passwords". If I revert back to using the previous user database internal mail works fine again. I can't seem to figure this out so appreciate any help! Any questions please ask. The details: Dovecot version: |2.2.12 # OS: FreeBSD 10.0-STABLE amd64 zfs auth_debug = yes auth_mechanisms = plain login auth_verbose = yes imap_id_log = * imap_id_send = * log_path = /var/log/dovecot.log login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k mail_location = maildir:/var/mail/vhosts/%d/%n mail_privileged_group = mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace inbox { inbox = yes location = mailbox Junk { auto = subscribe special_use = \Junk } prefix = } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = /var/mail/dovecotsieve/%d/%n/.dovecot.sieve sieve_default = /var/mail/sieve/default.sieve sieve_dir = /var/mail/dovecotsieve/%d/%n/sieve sieve_global_dir = /var/mail/sieve/ } protocols = imap lmtp sieve service auth-worker { user = vmail } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { mode = 0600 user = vmail } user = dovecot } service imap-login { inet_listener imap { port = 0 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service pop3-login { inet_listener pop3 { port = 0 } inet_listener pop3s { port = 0 } } ssl = required ssl_cert = </usr/local/openssl/certs/mail.domain.com.chained.dovecot.sha256.crt ssl_cipher_list = HIGH:EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+SHA384:EECDH+ECDSA+SHA256:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EECDH:EDH+aRSA:ECDHE-RSA-AES256-SHA:+DHE-RSA-AES256-SHA:!AES256-SHA256:!AES256-GCM-SHA384:!CAMELLIA256-SHA:!AES128:!CAMELLIA128:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS:!SSLv2:!RC4:!SEED:+AES256-SHA ssl_key = </usr/local/openssl/certs/mail.domain.com.sha256.key ssl_prefer_server_ciphers = yes userdb { args = uid=vmail gid=vmail home=/var/mail/vhosts/%d/%n driver = static } protocol imap { mail_max_userip_connections = 2000 } protocol lmtp { mail_plugins = " sieve" } |

1 0

[Dovecot] IMAP clients can't connect while dovecot 2.0.9 is configured for LDAP
by Matthew Badeau 03 May '14

03 May '14

Good evening, Currently, it’s using mySQL for the passdb and userdb. This works fine but when I switch to LDAP it starts having problems. I’m trying to set up dovecot to use LDAP as its userdb and passdb. I’ve read the docs but I think I may be missing something obvious or I didn’t understand something right. The clients can’t connect through IMAP using MD5-Challenge Response. They also don’t work with plain auth.. When I run the command ` doveadm auth user(a)domain.com ` , it works! When I run ` doveadm auth -x service=imap user(a)domain.com ` that also works! What am I doing wrong??? I get the following error: Error: Apr 29 02:04:02 servername dovecot: auth: Fatal: CRAM-MD5 mechanism can't be supported with given passdbs Here is my config: # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-431.5.1.el6.x86_64 x86_64 CentOS release 6.5 (Final) ext4 auth_debug = yes auth_verbose = yes mail_location = maildir:/home/mailuser/%u 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-ldap.conf.ext driver = ldap } plugin { sieve_dir = ~/sieve sieve_global_dir = /var/lib/dovecot/sieve/ sieve_global_path = /var/lib/dovecot/sieve/default.sieve } protocols = pop3 imap sieve lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = mailuser mode = 0640 user = mailuser } } service managesieve-login { inet_listener sieve { port = 4190 } } ssl_cert = </etc/ssl/certs/servernameredacted.crt ssl_key = </etc/ssl/certs/servernameredacted.key userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf.ext driver = ldap } protocol lmtp { mail_plugins = " sieve" } protocol lda { mail_plugins = " sieve" } Thank you for any help or links to docs!

1 0

[Dovecot] BINARY FETCH conversion issue
by Michael M Slusarz 03 May '14

03 May '14

Given this test message, with admittedly incorrect QP encoding: ---- From: Test <test(a)example.com> Subject: Test Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain To: Test <test(a)example.com> Date: Tue, 29 Apr 2014 00:54:10 +0000 Message-Id: <1(a)example.com> https://example.com/?from=bsu&url=http%3A//www.example.com/ ---- Dovecot 2.2 returns this: C: 5 UID FETCH 4464 (BINARY.PEEK[1]) S: * 1 FETCH (UID 4464 BINARY[1] NIL) S: 5 OK Fetch completed. Contrast with, e.g., Cyrus 2.4: C: 6 UID FETCH 1 (BINARY.PEEK[1]) S: * 1 FETCH (UID 1 BINARY[1] {57} S: [LITERAL DATA: 57 bytes] S: ) S: 6 OK Completed (0.000 sec) (Cyrus FETCH output strips out the spurious non-encoding '=', IIRC). Not sure if this is an example of Cyrus' QP decoder being more robust (or lenient) than Dovecot's. Or whether this is intentional to return NIL for this kind of bad data. Although if intentional, output should probably be a NO response with UNKNOWN-CTE response code, since this appears to be an instance of "the server does not know how to decode the section's CTE". (RFC 3516 [4.3]). michael

2 2

[Dovecot] core dump in mail_cache_header_fields_read()
by Wesley Huang 02 May '14

02 May '14

We're seeing a core dump for a user connecting from IPHONE. The user mail are in NFS mount. # dovecot --version 2.2.12 # doveconf -n # 2.2.12: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.4 auth_cache_negative_ttl = 0 auth_cache_size = 20 M auth_verbose = yes default_client_limit = 4000 default_process_limit = 1000 default_vsz_limit = 2 G director_mail_servers = <server_ip_address> disable_plaintext_auth = no first_valid_uid = 100 imap_client_workarounds = tb-extra-mailbox-sep delay-newmail tb-lsub-flags log_timestamp = "%Y-%m-%d %H:%M:%S " mail_fsync = always mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = " quota" mbox_dotlock_change_timeout = 1 mins mbox_lock_timeout = 1 mins mmap_disable = yes namespace inbox { hidden = no inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = / type = private } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { quota = fs:Disk quota } pop3_client_workarounds = outlook-no-nuls oe-ns-eoh protocols = " imap pop3" service auth-worker { user = root } service auth { user = $default_internal_user } service imap-login { client_limit = 2000 process_min_avail = 4 service_count = 1 } service imap-postlogin { executable = script-login /usr/local/dovecot-scripts/imap.sh user = root } service imap { executable = imap imap-postlogin process_limit = 4096 } service pop3-login { client_limit = 2000 service_count = 1 } service pop3-postlogin { executable = script-login /usr/local/dovecot-scripts/ipop3.sh user = root } service pop3 { executable = pop3 pop3-postlogin process_limit = 2048 } ssl_ca = </etc/dovecot/mailhost-ca.crt ssl_cert = </etc/dovecot/mailhost.crt ssl_key = </etc/dovecot/mailhost.key userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } verbose_ssl = yes protocol imap { mail_max_userip_connections = 1000 mail_plugins = " quota imap_quota" } protocol pop3 { mail_max_userip_connections = 1000 } -------------------------------------------------------------------------------------- # gdb /usr/lib/dovecot/imap ./5040 GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/lib/dovecot/imap...Reading symbols from /usr/lib/debug/usr/lib/dovecot/imap...done. done. [New LWP 5040] warning: Can't read pathname for load map: Input/output error. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `dovecot/imap imap-postlogin'. Program terminated with signal 11, Segmentation fault. #0 0x00007fca22f0ca85 in mail_cache_header_fields_read (cache=cache@entry=0x7fca24a04f70) at mail-cache-fields.c:369 369 for (p = names; p != end && *p != '\0'; p++) ; (gdb) bt full #0 0x00007fca22f0ca85 in mail_cache_header_fields_read (cache=cache@entry=0x7fca24a04f70) at mail-cache-fields.c:369 field_hdr = 0x7fca21d37010 field = {name = 0x0, idx = 0, type = MAIL_CACHE_FIELD_FIXED_SIZE, field_size = 0, decision = MAIL_CACHE_DECISION_NO, last_used = 0} last_used = 0x7fca21d3701c sizes = 0x7fca79d3701c types = 0x7fcad1d3701c <Address 0x7fcad1d3701c out of bounds> decisions = 0x7fcae7d3701c <Address 0x7fcae7d3701c out of bounds> p = 0x7fcafdd3701c <Address 0x7fcafdd3701c out of bounds> names = 0x7fcafdd3701c <Address 0x7fcafdd3701c out of bounds> end = 0x7fcb1dd47010 <Address 0x7fcb1dd47010 out of bounds> orig_key = 0x48800 <Address 0x48800 out of bounds> orig_value = 0x8000 fidx = <optimized out> new_fields_count = <optimized out> dec = <optimized out> max_drop_time = 0 offset = 23204 i = <optimized out> #1 0x00007fca22f0a4d6 in mail_cache_open_and_verify (cache=0x7fca24a04f70) at mail-cache.c:497 ret = <optimized out> #2 0x00007fca22f0c905 in mail_cache_register_get_list (cache=0x7fca24a04f70, pool=0x7fca249d7480, count_r=count_r@entry=0x7fff0c4c7aec) at mail-cache-fields.c:194 list = <optimized out> i = <optimized out> #3 0x00007fca22ef93b3 in index_mail_parse_header_register_all_wanted (mail=0x7fca24a14ce0) at index-mail-headers.c:169 _mail = 0x7fca24a14ce0 all_cache_fields = <optimized out> i = <optimized out> count = <optimized out> #4 index_mail_parse_header_init (mail=mail@entry=0x7fca24a14ce0, headers=headers@entry=0x0) at index-mail-headers.c:230 _data_stack_cur_id = 4 data = 0x7fca24a14e50 match = 0x7fca24a05e00 "\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377a" i = <optimized out> field_idx = <optimized out> match_count = <optimized out> __FUNCTION__ = "index_mail_parse_header_init" #5 0x00007fca22ef9d08 in index_mail_cache_parse_init (_mail=0x7fca24a14ce0, input=0x7fca24a1b178, input@entry=0x7fca24a1b738) at index-mail-headers.c:376 mail = 0x7fca24a14ce0 input2 = 0x7fca24a24ef8 __FUNCTION__ = "index_mail_cache_parse_init" #6 0x00007fca22eb4202 in mbox_save_get_input_stream (input=0x7fca24a1ab88, ctx=0x7fca24a14930) at mbox-save.c:421 filter = 0x0 ---Type <return> to continue, or q <return> to quit---

2 3

[Dovecot] Segfault in auth (when talked to by postfix lda)
by Darac Marjal 02 May '14

02 May '14

Afternoon all. I'm seeing a segfault in dovecot 2.2.12 (debian package 1:2.2.12-2). I can log into dovecot fine with mutt, but the segfaults seem to occur when postfix (2.11.0, debian package 2.11.0-1+b1) tries to deliver a message. This was working fine under 2.2.9 (I can downgrade to that and delivery works). Can anyone help? Doveconf -n, and backtrace follow. ------------------------------ --8<-- doveconf -n ---------- # 2.2.12: /etc/dovecot/dovecot.conf # OS: Linux 3.12-1-686-pae i686 Debian jessie/sid xfs auth_debug = yes auth_mechanisms = digest-md5 cram-md5 plain info_log_path = /var/log/dovecot.info lda_mailbox_autosubscribe = yes log_path = /var/log/dovecot.log log_timestamp = "%Y-%m-%d %H:%M:%S " login_log_format_elements = service=%s user=<%u> session=%{session} method=%m rip=%r lip=%l mpid=%e %c %k mail_access_groups = mail users mail_location = mdbox:/var/mail/%u/Mail mail_max_userip_connections = 50 mail_plugins = " zlib stats" mail_privileged_group = mail 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 namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } passdb { args = /etc/dovecot/passwd driver = passwd-file } plugin { antispam_backend = dspam antispam_crm_binary = /bin/false antispam_debug_target = syslog antispam_dspam_args = --client;--mode=teft;--deliver;--user;%u antispam_dspam_binary = /usr/bin/dspam antispam_pipe_program = /usr/sbin/sendmail antispam_pipe_tmpdir = /tmp antispam_signature = X-DSPAM-Signature antispam_signature_missing = move antispam_spam_pattern_ignorecase = SPAM antispam_trash_pattern_ignorecase = trash;Deleted * sieve = ~/.dovecot.sieve sieve_dir = ~/sieve stats_refresh = 30 secs stats_track_cmds = yes } postmaster_address = postmaster(a)darac.org.uk protocols = " imap lmtp sieve" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0666 } } service lmtp { inet_listener lmtp { address = 192.168.123.254 port = 20024 } unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0666 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service stats { fifo_listener stats-mail { mode = 0600 user = vmail } } ssl_cert = </etc/dovecot/mail.www.ssl-bundle.crt ssl_key = </etc/dovecot/private/mail.www.ssl.key userdb { driver = passwd } userdb { args = uid=vmail gid=vmail home=/var/mail/%u driver = static } protocol lmtp { mail_fsync = optimized mail_plugins = " zlib sieve" } protocol lda { mail_fsync = optimized mail_plugins = " zlib sieve" } protocol imap { mail_plugins = " zlib zlib imap_zlib antispam stats imap_stats" } ----8<---- backtrace ------- Core was generated by `dovecot/auth'. Program terminated with signal 11, Segmentation fault. #0 auth_fields_find_idx (fields=fields@entry=0x0, key=key@entry=0xb84ae448 "uid", idx_r=idx_r@entry=0xbfc07d0c) at auth-fields.c:44 44 auth-fields.c: No such file or directory. (gdb) bt full #0 auth_fields_find_idx (fields=fields@entry=0x0, key=key@entry=0xb84ae448 "uid", idx_r=idx_r@entry=0xbfc07d0c) at auth-fields.c:44 i = <optimized out> count = <optimized out> #1 0xb77bed33 in auth_fields_add (fields=0x0, key=key@entry=0xb84ae448 "uid", value=value@entry=0xb84a6312 "1120", flags=flags@entry=(unknown: 0)) at auth-fields.c:68 field = <optimized out> idx = 3091882770 __FUNCTION__ = "auth_fields_add" #2 0xb77bb03b in auth_request_set_userdb_field (request=request@entry=0xb84b9218, name=0xb84ae448 "uid", value=0xb84a6312 "1120") at auth-request.c:1605 uid = <optimized out> gid = <optimized out> #3 0xb77d2fb5 in userdb_template_export (tmpl=0xb84ae410, auth_request=auth_request@entry=0xb84b9218) at userdb-template.c:83 table = 0xb84a6110 str = 0xb84a5ff0 value = <optimized out> i = 0 count = 6 __FUNCTION__ = "userdb_template_export" #4 0xb77d230a in static_lookup_real (auth_request=auth_request@entry=0xb84b9218, callback=0xb77ba9b0 <auth_request_userdb_callback>) at userdb-static.c:32 _module = <optimized out> module = <optimized out> #5 0xb77d23ae in static_credentials_callback (result=PASSDB_RESULT_OK, credentials=0xb84b5bb7 "Mananozu", size=8, auth_request=0xb84b9218) at userdb-static.c:52 ctx = 0xb84bb860 #6 0xb77bc039 in auth_request_lookup_credentials_finish (result=PASSDB_RESULT_OK, credentials=credentials@entry=0xb84b5bb7 "Mananozu", size=size@entry=8, request=request@entry=0xb84b9218) at auth-request.c:820 No locals. #7 0xb77bc136 in auth_request_lookup_credentials_callback (result=PASSDB_RESULT_OK, credentials=0xb84b5bb7 "Mananozu", size=8, request=0xb84b9218) at auth-request.c:858 passdb = 0xb84ae248 cache_cred = 0x0 cache_scheme = 0xb77f1abc "\234\211\004" __FUNCTION__ = "auth_request_lookup_credentials_callback" #8 0xb77cc66e in passdb_handle_credentials (result=result@entry=PASSDB_RESULT_OK, password=0xb84b5bb7 "Mananozu", scheme=0xb84a5cb8 "PLAIN", callback=callback@entry=0xb77bc0c0 <auth_request_lookup_credentials_callback>, auth_request=auth_request@entry=0xb84b9218) at passdb.c:165 credentials = 0xb84b5bb7 "Mananozu" size = 8 #9 0xb77ce62c in passwd_file_lookup_credentials (request=0xb84b9218, callback=0xb77bc0c0 <auth_request_lookup_credentials_callback>) at passdb-passwd-file.c:106 _module = <optimized out> module = <optimized out> pu = <optimized out> crypted_pass = 0xb84b5bb7 "Mananozu" scheme = 0xb84a5cb8 "PLAIN" #10 0xb77bc317 in auth_request_lookup_credentials (request=request@entry=0xb84b9218, scheme=0xb84b9450 "", callback=0xb77d2320 <static_credentials_callback>) at auth-request.c:907 passdb = 0xb84ae248 cache_key = <optimized out> cache_cred = 0x0 cache_scheme = 0xb77f1abc "\234\211\004" result = -1216406852 __FUNCTION__ = "auth_request_lookup_credentials" #11 0xb77bc0b4 in auth_request_lookup_credentials_finish ( result=PASSDB_RESULT_SCHEME_NOT_AVAILABLE, credentials=credentials@entry=0xb774f693 <uchar_nul> "", size=size@entry=0, request=request@entry=0xb84b9218) at auth-request.c:802 No locals. #12 0xb77bc136 in auth_request_lookup_credentials_callback ( result=result@entry=PASSDB_RESULT_SCHEME_NOT_AVAILABLE, credentials=0xb774f693 <uchar_nul> "", size=size@entry=0, request=request@entry=0xb84b9218) at auth-request.c:858 passdb = 0xb84ae180 cache_cred = 0xb84b93b8 "\001" cache_scheme = 0x0 __FUNCTION__ = "auth_request_lookup_credentials_callback" #13 0xb77bc396 in auth_request_lookup_credentials (request=request@entry=0xb84b9218, scheme=scheme@entry=0xb77dd7bd "", callback=callback@entry=0xb77d2320 <static_credentials_callback>) at auth-request.c:900 passdb = 0xb84ae180 cache_key = <optimized out> cache_cred = 0x1 <Address 0x1 out of bounds> cache_scheme = 0xb7780e78 "x\r\r" result = -1217270382 __FUNCTION__ = "auth_request_lookup_credentials" #14 0xb77d253c in static_lookup (auth_request=0xb84b9218, callback=0xb77ba9b0 <auth_request_userdb_callback>) at userdb-static.c:100 ctx = 0xb84bb860 callback = 0xb77ba9b0 <auth_request_userdb_callback> auth_request = 0xb84b9218 _module = <optimized out> module = <optimized out> #15 0xb77bae3b in auth_request_lookup_user (request=request@entry=0xb84b9218, callback=0xb77b5c80 <user_callback>) at auth-request.c:1141 userdb = 0xb84ae3e8 cache_key = <optimized out> #16 0xb77bac6d in auth_request_userdb_callback (result=<optimized out>, result@entry=USERDB_RESULT_USER_UNKNOWN, request=<optimized out>) at auth-request.c:1062 userdb = <optimized out> next_userdb = 0xb84ae3c8 result_rule = <optimized out> userdb_continue = <optimized out> #17 0xb77d091c in user_callback (reply=<optimized out>, context=0xb84b9218) at userdb-blocking.c:46 request = 0xb84b9218 result = USERDB_RESULT_USER_UNKNOWN args = 0xb84b9863 "" #18 0xb77c1caf in auth_worker_request_handle (request=0xb84b93b8, request=0xb84b93b8, line=0xb84b985a "NOTFOUND\t", conn=<optimized out>) at auth-worker-server.c:281 No locals. #19 worker_input (conn=0xb84b9600) at auth-worker-server.c:376 line = 0xb84b9859 "\tNOTFOUND\t" id_str = <optimized out> id = 1 #20 0xb7726928 in io_loop_call_io (io=0xb84b97f0) at ioloop.c:388 ioloop = 0xb84ad4d0 t_id = 2 #21 0xb77278be in io_loop_handler_run (ioloop=ioloop@entry=0xb84ad4d0) at ioloop-epoll.c:220 ctx = 0xb84b2538 list = 0xb84b9820 io = <optimized out> tv = {tv_sec = 0, tv_usec = 996120} events_count = <optimized out> msecs = <optimized out> ret = 1 i = 0 j = 0 call = <optimized out> __FUNCTION__ = "io_loop_handler_run" #22 0xb7726458 in io_loop_run (ioloop=0xb84ad4d0) at ioloop.c:412 __FUNCTION__ = "io_loop_run" #23 0xb76ce8c8 in master_service_run (service=0xb84ad400, callback=0xb77c6010 <client_connected>) at master-service.c:566 No locals. #24 0xb77b2fae in main (argc=1, argv=0xb84ad1d8) at main.c:393 c = <optimized out>

2 2

[Dovecot] output of doveconf in conflict with order of settings in conf.d/*-*.conf files
by Steffen Kaiser 02 May '14

02 May '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I wanted to enable stats, so I added the settings from http://wiki2.dovecot.org/Statistics into conf.d/99-stats.conf: mail_plugins = $mail_plugins stats protocol imap { mail_plugins = $mail_plugins imap_stats } plugin { # how often to session statistics stats_refresh = 30 secs # track per-IMAP command statistics stats_track_cmds = yes } reloaded dovecot, see output of doveconf -n below, but I got the error: imap: Error: Can't load plugin imap_stats_plugin: Plugin stats must be loaded also (you must set: mail_plugins=$mail_plugins stats) If I move the line "mail_plugins = $mail_plugins stats" from 99-stats.conf into 15-stats.conf, the output of doveconf -n looks the same, but the stats is working. I tried finding information about the significance of the order of settings - I mean which number should a conf-file has - , but failed in the Wiki and mailing list. Is this a bug or should there be a documentation? ===== # 2.2.10 (5432b55a2b87): /usr/local/dovecot-2.2.10/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.8 auth_cache_size = 10 M auth_mechanisms = plain login base_dir = /var/run/dovecot2.2/ default_vsz_limit = 512 M deliver_log_format = msgid=%m: %$ %p/%w "%f" "%s" dict { acl = pgsql:/usr/local/dovecot-2.2.10/etc/dovecot/dovecot-dict-sql.conf.ext quota = pgsql:/usr/local/dovecot-2.2.10/etc/dovecot/dovecot-dict-sql.conf.ext } disable_plaintext_auth = no instance_name = dovecot2.2 lda_mailbox_autocreate = yes lmtp_save_to_detail_mailbox = yes log_path = /var/log/dovecot/dovecot2.2.log log_timestamp = "%F %H:%M:%S " mail_gid = vmail mail_log_prefix = "%Us(%u) [%p]: " mail_max_userip_connections = 0 mail_plugins = " quota notify mail_log zlib acl stats" mail_shared_explicit_inbox = yes 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 imapflags namespace { list = children location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u prefix = users.%%u. separator = . type = shared } namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /usr/local/dovecot-2.2.10/etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile acl_shared_dict = proxy::acl antispam_allow_append_to_spam = yes antispam_backend = spool2dir antispam_spam = SPAM+ReportAsSPAM antispam_spool2dir_notspam = /tmp/spamspool/%%020lu-%%05lu-%u-H antispam_spool2dir_spam = /tmp/spamspool/%%020lu-%%05lu-%u-S antispam_trash = trash;TRASH;Trash;spam;SPAM;Spam;junk;JUNK;Junk;Deleted Items;Deleted Messages;Gel&APY-schte Elemente;Gel&APY-schte Objekte;Junk E-mail;Junk-E-Mail;INBOX.Trash;INBOX.TRASH;INBOX.trash mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size vsize from subject quota = dict:User quota::proxy::quota quota_rule = *:storage=300MB quota_rule2 = Trash:storage=+30M recipient_delimiter = + sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +imapflags sieve_max_actions = 0 sieve_quota_max_storage = 3M stats_command_min_time = 1 mins stats_domain_min_time = 12 hours stats_ip_min_time = 12 hours stats_memory_limit = 128 M stats_refresh = 30 secs stats_session_min_time = 15 mins stats_track_cmds = yes stats_user_min_time = 1 hours } postmaster_address = postmaster(a)inf.h-brs.de protocols = imap pop3 lmtp sieve quota_full_tempfail = yes service auth { unix_listener auth-client { mode = 0766 } unix_listener auth-userdb { mode = 0766 user = vmail } } service dict { unix_listener dict { group = vmail mode = 0660 user = vmail } } service doveadm { unix_listener doveadm-server { mode = 0666 } } service imap-login { process_min_avail = 4 service_count = 0 vsz_limit = 768 M } service imap { process_limit = 10000 vsz_limit = 768 M } service lmtp { vsz_limit = 768 M } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service pop3-login { process_min_avail = 5 service_count = 0 vsz_limit = 512 M } service stats { fifo_listener stats-mail { mode = 0600 user = vmail } } ssl_ca = </etc/ssl/certs/ca.crt ssl_cert = </etc/ssl/certs/imap.pem ssl_key = </etc/ssl/private/imap.key userdb { driver = prefetch } userdb { args = /usr/local/dovecot-2.2.10/etc/dovecot/dovecot-ldap.conf.ext default_fields = home=/home/%u uid=vmail gid=vmail driver = ldap } verbose_proctitle = yes protocol lmtp { mail_plugins = " quota notify mail_log zlib acl quota sieve" } protocol lda { mail_plugins = " quota notify mail_log zlib acl quota sieve" } protocol imap { mail_plugins = " quota notify mail_log zlib acl imap_quota imap_zlib imap_acl antispam imap_stats" } - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBUwHPOnD1/YhP6VMHAQJ4Gwf/S+Vve0EOamXd0qok6Q8soRkmbXbU+lgm Fc2759gkZo05N9cNgHTe5T5ulSvZ+XcOt0DnResyHhz0/r6UlxCeR4pQyvxFHG9K eKsej2IlsG5ilT3xKCMHaB+wQg9f2lb4PQzD1flLANPESU3LSVZMpPCxy7O3LWN2 JQahrRNNjyK8mNOAw0M3F8SbT604co37acO47S90BEMcd2lfIZpHiAkH8NV22l9E /vM9yzvPwMADWXeFbMnvb8lSSb78zTe+P2tl/IOlxrBOODPF4+Whh790zpu5K8DO yLddMVFsGmC07aPGI70BldITvTkc0LzHurB2dTLH3mdoN5tgD1JhtA== =uqLL -----END PGP SIGNATURE-----

2 3

[Dovecot] maildir compressed message fix patch
by Richard Platel 02 May '14

02 May '14

When a compressed maildir message has a bad S= size in its filename it puts the user in an unrecoverable state, since maildir's do_fix_size function just does a stat() on the maildir file and saves the compressed size in the filename. This (quick, rough, barely tested) patch addresses this issue, it's inefficient, but we're already in a hopefully rare emergency situation. --- maildir-mail.c 2014-02-11 22:23:37.000000000 +0000 +++ maildir-mail.c.new 2014-04-24 20:41:25.000000000 +0000 @@ -8,6 +8,7 @@ #include "maildir-filename.h" #include "maildir-uidlist.h" #include "maildir-sync.h" +#include "compression.h" #include <stdio.h> #include <stdlib.h> @@ -640,6 +641,10 @@ { const char *fname, *newpath, *extra, *info, *dir; struct stat st; + const struct stat * stp; + const struct compression_handler * handler; + struct istream * fstream; + struct istream * cstream; fname = strrchr(path, '/'); i_assert(fname != NULL); @@ -650,13 +655,29 @@ info = strchr(fname, MAILDIR_INFO_SEP); if (info == NULL) info = ""; + fstream = i_stream_create_file(path, 1024); + handler = compression_detect_handler(fstream); + if (handler != NULL && handler->create_istream != NULL) + { + cstream = handler->create_istream(fstream, TRUE); + if (i_stream_stat(cstream, TRUE, &stp) < 0) + { + return -1; + } + st = *stp; /* dumb copy */ + i_stream_unref(&cstream); + } + else + { if (stat(path, &st) < 0) { if (errno == ENOENT) return 0; mail_storage_set_critical(&mbox->storage->storage, "stat(%s) failed: %m", path); return -1; - } + } + } + i_stream_unref(&fstream); newpath = t_strdup_printf("%s/%s,S=%"PRIuUOFF_T"%s", dir, t_strdup_until(fname, extra),

3 2

[Dovecot] ID command and dovecot
by Jernej Porenta 02 May '14

02 May '14

Heya, we are seeing some strange issues with IMAP ID command using latest Roundcube builds on dovecot 2.2.10 responding "Input buffer full, aborting". Roundcube webmail connects to IMAP server and issues ID command first with some long arguments to ID command, however shorter than 1024 octets, which are specified in RFC2971 for ID IMAP extension. The situation is easily reproducible (see http://pastebin.com/q4HX4wqb) # telnet hostname 143 * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN] Server ready. . ID ("name" "Roundcube" "version" "1.0-git" "php" "5.3.3" "os" "Linux" "command" "<$long_less_than_1024_octets_string>") * BYE Input buffer full, aborting However, this problem does not occur when user is already logged in. RFC2971 is saying "Field strings MUST NOT be longer than 30 octets. Value strings MUST NOT be longer than 1024 octets. Implementations MUST NOT send more than 30 field-value pairs." IMHO, dovecot is handling ID command before successful login successfully only if the length of the whole command is less than 1024 octets (exactly 861 octets is working fine, over that "Input buffer full" occurs). I tried finding the reference in the source code, however I am unable to find where this limit actually occurs (maybe IMAP_ARG_STRING imap_arg->type?) thank you in advance, regards, Jernej

2 1

[Dovecot] Finding memory leaks
by Philipp Brüll 02 May '14

02 May '14

Hello, I try to find a memory leak in a dovecot plugin that I develop. In order to find it, it would be helpful to print the total amount of memory that is currently allocated. This print could than spread over the source code and the memory consumption can be tracked. I've tried i_debug("pool size %u", (unsigned int)pool_alloconly_get_total_alloc_size(system_pool)); But that failed. Does someone has a good advice? I would like to avoid complex solutions like valgrind. Best regards, Philipp

2 1

Re: [Dovecot] LMTP error
by Joseph Tam 02 May '14

02 May '14

IT geek 31 <itgeek31(a)googlemail.com> writes: > I've recently switched to LMTP as I'm now using mdbox. However since > switching, mails sent to the root account do not get delivered due to the > following error: > > May 1 18:20:17 Server1 postfix/lmtp[13019]: CAEE91F851: to=<root(a)test.com>, > relay=mail.test.com[private/dovecot-lmtp], delay=1097, > delays=1096/0.45/0.43/0.46, dsn=4.3.0, status=deferred (host > mail.test.com[private/dovecot-lmtp] > said: 451 4.3.0 <root(a)test.com> Invalid user settings. Refer to server log > for more information. (in reply to RCPT TO command)) This setting: > first_valid_uid = 1010 will need to be changed to "0", or better yet, as others have suggested, alias root to some user with UID within 1010..1020. The dovecot logs that you ought to see will be something like May 1 16:12:11 viol dovecot: lda: Error: user root: Mail access for users with UID 0 not permitted (see first_valid_uid in config file, uid from userdb lookup). Joseph Tam <jtam.home(a)gmail.com>

3 2

[Dovecot] Imap user via proxy with starttls - how to rawlogs on proxy ?
by askforstatus 02 May '14

02 May '14

Hello, Is there any way to log user imap dialog with starttls when going via dovecot acting as imap proxy ? My intention is to log each and every user command similar to rawlogs feature. As per my current imap proxy config pre-login working like a charm but post-login is not possible due as i think the nature of proxy feature. Any idea ? Regards -- View this message in context: http://dovecot.2317879.n4.nabble.com/Imap-user-via-proxy-with-starttls-how-… Sent from the Dovecot mailing list archive at Nabble.com.

2 1

[Dovecot] Not backing up cache files
by Jesus Cea 02 May '14

02 May '14

I am using mdbox for dovecot storage. I wonder if I could skip "dovecot.index.cache" files and, in general, "*.cache" files when doing mail backup. Those files are big and change frequently. What I feel from reading documentation [1][2] is that they could be dropped in the backups, to be recreated on the fly if needed. But I would like expert confirmation. [1] http://wiki2.dovecot.org/IndexFiles [2] http://wiki2.dovecot.org/Design/Indexes/Cache Thanks!. -- Jesús Cea Avión _/_/ _/_/_/ _/_/_/ jcea(a)jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz

5 5

[Dovecot] BUG dovecot and nginx
by Tobias Oetiker 02 May '14

02 May '14

we have setup a two level proxy configuration for our zimbra server: [ dovecot 2.2.12 (imap proxy mode) ] V [ nginx (imap proxy mode) ] V [ zimbra imap server] and it does not work ... after tying a login, the connection just hangs and ends after 30 seconds with a timeout. - if I try again rightaway in the same dovecot connection, the login goes though without trouble. - looking at this with tshark I can see that on the second attempt, there is no capabilities query, dovecot just goes ahead and connects. if we drop nginx from the setup all is well also (login works directly as expected) - investigating the traffic differences between the setups with and without nginx, we find that for some reason dovecot does not react to the capabily answer from nginx. while it seems to happily accept the same answer when it is coming from zimbra directly. - the only difference I can see on the wire is that nginx is much quicker (2.5ms) in responding than the zimbra (25ms) server and that the position of the STARTTLS and SASL=PLAIN capabilities in the capability answer differs between the two. any ideas ? cheers tobi -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland www.oetiker.ch tobi(a)oetiker.ch +41 62 775 9902 *** We are hiring IT staff: www.oetiker.ch/jobs ***

2 1

[Dovecot] Rebuilding message guid in sdbox
by Renaud Allard 02 May '14

02 May '14

Hello, I am running dovecot 2.2.12 Current mail storage is sdbox and I am trying to compress all emails, which works fine, except for a few old mailboxes. If I run the following dsync command "dsync -u flea -o "mail_plugins=zlib" mirror maildir:~/ndbox" It fails with: dsync(flea): Error: Exporting mailbox INBOX failed: Backend doesn't support GUIDs, sync with header hashes instead Doing "doveadm dump flea/dbox/mailboxes/INBOX/dbox-Mails/dovecot.index" reveals that there are very old mails (about 5 years ago) without any guid like that one: RECORD: seq=1, uid=1560, flags=0x00 - ext 1 modseq : 16043 (ab3e000000000000) - ext 3 cache : 396 (8c010000) - cache offset=396 size=20, prev_offset = 0 - guid: So, my question is: is there a way to force dovecot to assign a guid to those messages? Best Regards

2 1

[Dovecot] Dovecot Director and MasterUsers
by Daniel Parthey 02 May '14

02 May '14

Hi, the Dovecot Director determines the backend host in some way by hashing the username: http://wiki2.dovecot.org/Director For normal logins username(a)example.org, the director always gets the same hash for the same username and ensures that the login is always proxied to the same backend. But what about MasterUsers in combination with Dovecot Director? http://wiki2.dovecot.org/Authentication/MasterUsers Which configuration directives should be used to make sure that logins username@example.org*masteruser1@example.org username@example.org*masteruser2@example.org username@example.org*masteruser3@example.org go to the same mailbox backend, in order to avoid NFS caching conflicts for mailbox username(a)example.org which should always reside on the same NFS client? Is the master user cut off from behind the master_user_separator? How is the director hash exactly calculated? Can the director hashing algorithm be configured in some way? Regards Daniel

2 1

[Dovecot] BUG: Authentication client sent unknown handshake command
by Jean-Yves Moulin 02 May '14

02 May '14

Hi everybody, I'm using dovecot-2.2.11 on NetBSD. After a kernel upgrade, while using the same dovecot binaries (they were working perfectly until today), I'm experiencing this error (more log at the end of my email): BUG: Authentication client sent unknown handshake command: REQUEST?227672066?18807?2?c717631d60216b2e9ec57a2fa69674b8?session_pid=16343?... I tried to build a newer version of dovecot (2.2.12) but same issue. I know this should come from my system and not dovecot, but how can I debug this kind of problem ? I already enabled various debug (auth_verbose, auth_debug, mail_debug) but I need more information. This issue have already been discussed on dovecot mailing list without solution :-) Thank you very much. Best, jym Log: Apr 16 16:29:16 dodo dovecot: imap-login: Debug: SSL: where=0x2002, ret=1: SSL negotiation finished successfully [::1] Apr 16 16:29:17 dodo dovecot: auth: Debug: client in: AUTH 2 PLAIN service=imap secured session=cE/PvSn3qgAAAAAAAAAAAAAAAAAAAAAB lip=::1 rip=::1 lport=993 rport=65450 resp=<hidden> Apr 16 16:29:17 dodo dovecot: auth: Debug: cache(mylogin@myhost.org,::1,<cE/PvSn3qgAAAAAAAAAAAAAAAAAAAAAB>): hit: <hidden> Apr 16 16:29:17 dodo dovecot: auth: Debug: client passdb out: OK 2 user=mylogin(a)myhost.org Apr 16 16:29:17 dodo dovecot: auth: Error: BUG: Authentication client sent unknown handshake command: REQUEST?227672066?18807?2?c717631d60216b2e9ec57a2fa69674b8?session_pid=16343?... Apr 16 16:29:17 dodo dovecot: imap: Error: Authentication server didn't send valid SPID as expected: MECH PLAIN plaintext Apr 16 16:29:17 dodo dovecot: imap: Error: Disconnected from auth server, aborting (client-pid=18807 client-id=2) Apr 16 16:29:17 dodo dovecot: imap-login: Internal login failure (pid=18807 id=2) (internal failure, 1 successful auths): user=<mylogin(a)myhost.org>, method=PLAIN, rip=::1, lip=::1, mpid=16343, TLS, session=<cE/PvSn3qgAAAAAAAAAAAAAAAAAAAAAB> Apr 16 16:29:17 dodo dovecot: imap-login: Debug: SSL alert: close notify [::1]

2 1

Re: [Dovecot] nfs flush/fsync config settings problem
by Wesley Huang 02 May '14

02 May '14

Hi Alessio, After days sorting the Heartbleed mess, I managed to set up Debian Squeeze amd64 for the test and I'm seeing the same error message: Fatal: nfs flush requires mail_fsync=always # doveconf -n | egrep 'fsync|nfs' mail_fsync = always mail_nfs_index = yes mail_nfs_storage = yes Cheers, Wesley On 14-04-03 09:24 AM, Alessio Cecchi wrote: > Hi, > > I'm using Maildir on Debian 6 64bit, try to "grep" for "fsync" on all > configuration files. > > Try also to install the same dovecot+configuration on Debian 6. > > Let me know! > Ciao > > Il 03/04/2014 15:12, Wesley Huang ha scritto: >> Hi Alessio, >> >> I have 2.2.12 installed in Debian Wheezy amd64 server. mail_fsync is >> specified and detected. Are you using mbox or maildir or dbox? We're >> using mbox and seeing the error. >> >> # dovecot --version >> 2.2.12 >> >> # dovecot -n | grep -E 'sync|nfs' >> mail_fsync = always >> mail_nfs_index = yes >> mail_nfs_storage = yes >> >> >> # egrep 'nfs|fsync' 10-mail.conf | egrep -v '#' >> mail_fsync=always >> mail_nfs_storage = yes >> mail_nfs_index = yes >> >> # uname -r >> 3.2.0-4-amd64 >> >> Cheers, >> >> Wesley >> >> On 14-04-03 04:22 AM, Alessio Cecchi wrote: >>> Il 08/01/2014 09:23, Troton_admin ha scritto: >>>> Hi, >>>> >>>> I need to place a maildir storage on a NFS filesystem, so I set up >>>> the config like this: >>>> >>>> mmap_disable = yes >>>> mail_nfs_storage = yes >>>> mail_nfs_index = yes >>>> mail_fsync = always >>>> lock_method = dotlock (also tried fcntl - local lockd is running, no >>>> success, now using dotlock, to be sure while debugging) >>>> >>>> The problem is that Dovecot (2.2.9/2.2.10 - the relevant code in >>>> mail-index.c is the same) logs a fatal error and quits the session >>>> (no daemon crash/coredump). >>> >>> Hi, >>> >>> I have a similar configuration but with dovecot 2.2.12 and NFS for me >>> works fine. Have you insert the "mail_fsync = always" in the right >>> place? Is there only one "mail_fsync" setting in your config? First >>> check this: >>> >>> root@mx:/etc/dovecot# grep mail_fsync /etc/dovecot/ -R >>> conf.d/10-mail.conf:mail_fsync = always >>> >>> root@mx:/etc/dovecot# dovecot -n | grep -E 'sync|nfs' >>> mail_fsync = always >>> mail_nfs_index = yes >>> mail_nfs_storage = yes >>> maildir_very_dirty_syncs = yes >>> >>> # 2.2.12: /etc/dovecot/dovecot.conf >>> # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.9 >>> >>> Let me know. >>> Ciao >> > >

3 3

[Dovecot] Assert Crash with HG 49e9d9743f6e
by Thomas Leuxner 02 May '14

02 May '14

New crash most likely related to Virtual plugin again: Apr 26 07:40:40 spectre dovecot: imap(tlx(a)leuxner.net): Panic: file mail-storage.c: line 1836 (mailbox_transaction_begin): assertion failed: (box->opened) Apr 26 07:40:40 spectre dovecot: imap(tlx(a)leuxner.net): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x6bc0f) [0x7fdfce48ac0f] -> /usr/lib/dovecot/libdovecot.so.0(+0x6bc6e) [0x7fdfce48ac6e] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fdfce4442ce] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x82299) [0x7fdfce777299] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(+0x9f1b) [0x7fdfccc2df1b] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(virtual_storage_sync_init+0x564) [0x7fdfccc2eb84] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x33) [0x7fdfce776e53] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x27) [0x7fdfce776f77] -> dovecot/imap [tlx(a)leuxner.net 95.223.79.50 EXAMINE](cmd_select_full+0x173) [0x412c13] -> dovecot/imap [tlx(a)leuxner.net 95.223.79.50 EXAMINE](command_exec+0x3c) [0x41839c] -> dovecot/imap [tlx(a)leuxner.net 95.223.79.50 EXAMINE]() [0x417400] -> dovecot/imap [tlx(a)leuxner.net 95.223.79.50 EXAMINE]() [0x4174ba] -> dovecot/imap [tlx(a)leuxner.net 95.223.79.50 EXAMINE](client_handle_input+0x115) [0x417775] -> dovecot/imap [tlx(a)leuxner.net 95.223.79.50 EXAMINE](client_input+0x72) [0x417b22] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x4e) [0x7fdfce49b9fe] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd7) [0x7fdfce49c9f7] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x9) [0x7fdfce49ba89] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fdfce49bb08] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fdfce449673] -> dovecot/imap [tlx(a)leuxner.net 95.223.79.50 EXAMINE](main+0x298) [0x40c128] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7fdfce0b2ead] -> dovecot/imap [tlx(a)leuxner.net 95.223.79.50 EXAMINE]() [0x40c28d] Apr 26 07:40:40 spectre dovecot: imap(tlx(a)leuxner.net): Fatal: master: service(imap): child 31334 killed with signal 6 (core not dumped) Disabling virtual prevents Dovecot from crashing.

2 2

[Dovecot] Dovecot permission denied error in logs
by Andrew Stuart 02 May '14

02 May '14

dovecot --version 2.1.7 I am getting he following errors in the logs eve though there is no 'apply' user in /etc/dovecot/users I'm not sure wat to do next to diagnose. Can anyone advise please? It says 'refer to server log for more information' but I thought this was the server log? May 1 22:40:44 ip-xx-xxx-xx-xx postfix/local[18901]: 1B17763738: to=<apply@localhost>, orig_to=<apply(a)example.org>, relay=local, delay=147501, delays=147501/0.54/0/0.06, dsn=4.3.0, status=deferred (temporary failure) May 1 22:40:44 ip-xx-xxx-xx-xx dovecot: lda(apply): Error: user apply: Initialization failed: Namespace '': mkdir(/home/vmail//apply) failed: Permission denied (euid=1001(apply) egid=1001(apply) missing +w perm: /home/vmail/, dir owned by 5000:5000 mode=0755) May 1 22:40:44 ip-xx-xxx-xx-xx dovecot: lda(apply): Error: user apply: Initialization failed: Namespace '': mkdir(/home/vmail//apply) failed: Permission denied (euid=1001(apply) egid=1001(apply) missing +w perm: /home/vmail/, dir owned by 5000:5000 mode=0755) May 1 22:40:44 ip-xx-xxx-xx-xx dovecot: lda(apply): Fatal: Invalid user settings. Refer to server log for more information. May 1 22:40:44 ip-xx-xxx-xx-xx dovecot: lda(apply): Fatal: Invalid user settings. Refer to server log for more information. May 1 22:40:44 ip-xx-xxx-xx-xx postfix/local[18926]: 9E5376357A: to=<apply@localhost>, orig_to=<apply(a)example.org>, relay=local, delay=235638, delays=235637/0.6/0/0.06, dsn=4.3.0, status=deferred (temporary failure) May 1 22:40:44 ip-xx-xxx-xx-xx postfix/local[18908]: 252106364B: to=<apply@localhost>, orig_to=<apply(a)example.org>, relay=local, delay=218930, delays=218929/0.6/0/0.06, dsn=4.3.0, status=deferred (temporary failure) May 1 22:40:44 ip-xx-xxx-xx-xx dovecot: lda(apply): Error: user apply: Initialization failed: Namespace '': mkdir(/home/vmail//apply) failed: Permission denied (euid=1001(apply) egid=1001(apply) missing +w perm: /home/vmail/, dir owned by 5000:5000 mode=0755) May 1 22:40:44 ip-xx-xxx-xx-xx dovecot: lda(apply): Fatal: Invalid user settings. Refer to server log for more information. May 1 22:40:44 ip-xx-xxx-xx-xx postfix/local[18900]: 9A94063274: to=<apply@localhost>, orig_to=<apply(a)example.org>, relay=local, delay=306900, delays=306900/0.66/0/0.03, dsn=4.3.0, status=deferred (temporary failure) May 1 22:41:23 ip-xx-xxx-xx-xx dovecot: pop3-login: Login: user=<my.name(a)example.org >, method=PLAIN, rip=101.103.174.186, lip=10.172.21.51, mpid=18952, session=<mc9XXV74CwBlZ666> May 1 22:41:24 ip-xx-xxx-xx-xx dovecot: pop3(my.name(a)example.org): Disconnected: Logged out top=0/0, retr=0/0, del=0/424, size=57179196 [/var/log] dovecot -n # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.11.0-19-generic x86_64 Ubuntu 13.10 ext4 auth_mechanisms = plain login disable_plaintext_auth = no mail_location = maildir:/home/vmail/%d/%n managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded- character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = scheme=CRYPT username_format=%u /etc/dovecot/passdb driver = passwd-file } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap pop3 sieve service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } } ssl_cert = </etc/dovecot/mail.example.org.pem ssl_cipher_list = ALL:!LOW:!SSLv2:ALL:!aNULL:!ADH:!eNULL:!EXP:RC4+RSA: +HIGH:+MEDIUM ssl_key = </etc/dovecot/private/mail.example.org.key userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } protocol lda { deliver_log_format = msgid=%m: %$ mail_plugins = sieve postmaster_address = postmaster quota_full_tempfail = yes rejection_reason = Your message to <%t> was automatically rejected: %n%r } protocol imap { imap_client_workarounds = delay-newmail mail_max_userip_connections = 10 } protocol pop3 { mail_max_userip_connections = 10 pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } [/etc/dovecot]

1 0

Re: [Dovecot] LMTP error
by Reindl Harald 01 May '14

01 May '14

Am 01.05.2014 19:43, schrieb IT geek 31: > On 1 May 2014 19:41, Reindl Harald: > > that you are working with unix-accounts and the root uid 0 > is prohibited for (good) saftey reasons > > Okay, that sounds good. How do I deliver mail to the root account then, and stop this error/warning/message? As > mails are now backing up in the queue and cannot be delivered... keep your responses on the list! * set a alias on the postfix side to another mail-address * that way dovecot never see the root-address as destination * use "postsuper -d queue_id" to kill the messages from the queue ______________________________ cat /etc/aliases | grep root # Person who should get root's mail root: h.reindl(a)thelounge.net ______________________________ don't forget calling "newaliases" after changes in that file if you have implemented aliases on postfix in a different way follow the documentation

2 1

[Dovecot] LMTP error
by IT geek 31 01 May '14

01 May '14

Hi, I've recently switched to LMTP as I'm now using mdbox. However since switching, mails sent to the root account do not get delivered due to the following error: May 1 18:20:17 Server1 postfix/lmtp[13019]: CAEE91F851: to=<root(a)test.com>, relay=mail.test.com[private/dovecot-lmtp], delay=1097, delays=1096/0.45/0.43/0.46, dsn=4.3.0, status=deferred (host mail.test.com[private/dovecot-lmtp] said: 451 4.3.0 <root(a)test.com> Invalid user settings. Refer to server log for more information. (in reply to RCPT TO command)) This obviously fills up my mail queue. All other mails to all other mailboxes deliver fine. I'm obviously missing something in my config... any ideas? I'm using Dovecot 2.2.12 on NetBSD 5.2.2. Many thanks, -Mark dovecot -n # 2.2.12: /usr/pkg/etc/dovecot/dovecot.conf # OS: NetBSD 5.2.2 cobalt auth_username_format = %Ln doveadm_password = secret doveadm_port = 12345 first_valid_uid = 1010 last_valid_uid = 1020 listen = 192.168.1.1 login_greeting = test.com mail_location = mdbox:~/mdbox mail_plugins = " notify replication" namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = passwd } passdb { driver = passwd } plugin { mail_replica = tcp:Server2.test.com } protocols = imap lmtp service aggregator { fifo_listener replication-notify-fifo { mode = 0666 } unix_listener replication-notify { mode = 0600 } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = root } service imap-login { inet_listener imap { port = 0 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0777 } } ssl_cert = </etc/openssl/certs/mail.test.com.crt ssl_key = </etc/openssl/private/mail.test.com.key userdb { driver = passwd } userdb { driver = passwd } protocol lda { postmaster_address = postmaster(a)test.com }

3 7

[Dovecot] fts-lucene configuration
by Gregory Finch 01 May '14

01 May '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, Is there a configuration option to set where fts-lucene stores its indexes? I know it defaults to lucene-indexes in the mail root directory. I'm looking to store it in the home directory. Thank you, Greg -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJTYmPZAAoJECD7Htp+IT9epBIQAKnR+cBtMZ8kkpvTefI/oVG6 ANu/gB/VGamrommOl0w+9/E0YwowdfqB3IqQuavR47KtPHE6X8gxyRf4p26p3dfC X13KCrdBvDQ0AArqi1RH4Blig2zFcLvC85QyBOvGKnYKg90wBKRODYdw9it8cU0P 1eJMkURCR5llIKUEnFQH1OBUr1rJ4c+tkke0fuxeikcoaS3DtW7LdPCQaJyYpUdS NmFehIG+n3jDQqx1jDJNBBQMlfSEz+svXFuHzAR/YCeQS8ETBQdQ7cC5ES5gBijy Z0f1bTRWhLOC9rcg3VzcbGm1ky+rAJeEVL1HGXluPOJjqLhjWvaDE+ola2cDHtNk IiVXtL4WdIAvSJ51kR8X3ubSWtHd+2mo93ryQqCE+AdhWh0lMNzxMB/r8LmVHMKY eMjFmu1QvC+W1Z20xUT5SZKFIIOnXzHZbzugkz2zKZEQbJw9AtdTrIwJ+CyxY+YN yREwPFJ2dGzglWtzk/lxAgRZUizAJEvmcLQ8n5ZPi4aX6SfZyYcD0t7nkAOVD3ff VsJdvYJeiPcoWLrQnemI4wAaClINw+7vLg4D+uiGLswyTtR4ccTg0wOUG6Bp8Jkv dMFRWLwJsK3dLYubLud9T2nlyMBG63hEyoDjgE8WxXXuIAYaYTTMUuGAf89fdwLN bgpfg40wgCfheu18qD9d =EDIQ -----END PGP SIGNATURE-----

1 0

[Dovecot] Problems with login_log_format (possible bug?)
by Trever L. Adams 01 May '14

01 May '14

login_log_format = %$: %s login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c session=<%{session}> These are the defaults, at least on a Fedora system. According to http://wiki2.dovecot.org/Variables, this should record for user@REALM when seeing the following Apr 30 18:08:40 TeaSet dovecot: auth: Debug: auth(user,...,<JhKid0v4bAAKAQG6>): username changed user -> user@REALM. If I wanted just user, user=<%u> should be changed to user=<%orig_user>. However, I only get user not user@REALME in imap-login log lines. I wouldn't mind this, but auth_username_format cannot be used in passed{} and I haven't been able to get pam_krb5 to uppercase the realm for it alone. (Everything else depends on it being lowercase.) I can make this work by just passing the user name part of username in the client, but then imap-login still doesn't have the required information for the same reason. Anyone have any suggestions? Thank you, Trever

1 0

[Dovecot] Dovecot 2.0.16 question...
by Farokh Irani 30 Apr '14

30 Apr '14

I'm running Dovecot 2.0.16 on OS X Server 10.7.5 and I've got a problem with IMAP searches. There are a couple of accounts that are unable to search using an IMAP search, but I can't seem to find anything wrong. Any pointers on what I can do? Is there a search index file that I can delete to force a rebuild, or a script or app that will do that? I tried to use update-fts-index.pl, but to no avail. Thanks! Farokh ---------------------------------------------------------------------------- MCF Software...simply dependably engineered For all your computer and networking needs including hosting solutions for every need. Phone: 845-735-0210 Cell: 914-262-1594

1 0

[Dovecot] doveadm import : Error creating new mailbox
by Administrator BCS 29 Apr '14

29 Apr '14

Hello, I'm new to dovecot. I managed to set up a system running dovecot/mysql/postfix/postfixadmin with a virtual maildir setup on Ubuntu 12.04 I can add and remove users, send and receive mail, create folders, move mail between them etc so all ok. Now trying to manually import some mbox files from the old server into dovecot. Copied a mbox file to the new system, converted it to Maildir with mb2md resulting in a directory containing the new, cur en tmp. Looks ok, old email messages are all there. When importing this folder using doveadm import it fails with the message: Error: Couldn't create mailbox maildir:/home/vmail/bezoekerscentrumsonsbeek.nl/techniek/.INBOX: Invalid mailbox name What am I doing wrong? Martin output from doveadm -D import: > ┌─(adje@BCS:pts/0)──────────────────────────────────────────────────────────────────────────────────────────────────────(~)─┐ > └─(89:10:33:%)── sudo doveadm -D import -u > techniek(a)bezoekerscentrumsonsbeek.nl > maildir:/mnt/multimedia/mailoudeserver/testmap/techniek > maildir:/home/vmail/bezoekerscentrumsonsbeek.nl/techniek/ all > doveadm(root): Debug: Loading modules from directory: > /usr/lib/dovecot/modules/doveadm > doveadm(root): Debug: Skipping module doveadm_acl_plugin, because > dlopen() failed: > /usr/lib/dovecot/modules/doveadm/lib10_doveadm_acl_plugin.so: undefined > symbol: acl_user_module (this is usually intentional, so just ignore > this message) > doveadm(root): Debug: Skipping module doveadm_expire_plugin, because > dlopen() failed: > /usr/lib/dovecot/modules/doveadm/lib10_doveadm_expire_plugin.so: > undefined symbol: expire_set_deinit (this is usually intentional, so > just ignore this message) > doveadm(root): Debug: Skipping module doveadm_quota_plugin, because > dlopen() failed: > /usr/lib/dovecot/modules/doveadm/lib10_doveadm_quota_plugin.so: > undefined symbol: quota_user_module (this is usually intentional, so > just ignore this message) > doveadm(root): Debug: Skipping module doveadm_zlib_plugin, because > dlopen() failed: > /usr/lib/dovecot/modules/doveadm/lib10_doveadm_zlib_plugin.so: undefined > symbol: i_stream_create_deflate (this is usually intentional, so just > ignore this message) > doveadm(root): Debug: Effective uid=0, gid=0, home=/home/adje > doveadm(root): Debug: maildir++: > root=/mnt/multimedia/mailoudeserver/testmap/techniek, index=, control=, > inbox=/mnt/multimedia/mailoudeserver/testmap/techniek, alt= > doveadm(techniek(a)bezoekerscentrumsonsbeek.nl): Debug: Added userdb > setting: mail=maildir:/home/vmail/bezoekerscentrumsonsbeek.nl/techniek > doveadm(techniek(a)bezoekerscentrumsonsbeek.nl): Debug: Added userdb > setting: plugin/quota=dirsize:storage=0 > doveadm(techniek(a)bezoekerscentrumsonsbeek.nl): Debug: Effective uid=150, > gid=8, home=/home/vmail/bezoekerscentrumsonsbeek.nl/techniek > doveadm(techniek(a)bezoekerscentrumsonsbeek.nl): Debug: maildir++: > root=/home/vmail/bezoekerscentrumsonsbeek.nl/techniek, index=, control=, > inbox=/home/vmail/bezoekerscentrumsonsbeek.nl/techniek, alt= > doveadm(techniek(a)bezoekerscentrumsonsbeek.nl): Debug: Namespace : > /home/vmail/bezoekerscentrumsonsbeek.nl/techniek/.maildir:/home/vmail/bezoekerscentrumsonsbeek.nl/techniek/.INBOX doesn't exist yet, using default > permissions > doveadm(techniek(a)bezoekerscentrumsonsbeek.nl): Debug: Namespace : Using > permissions from /home/vmail/bezoekerscentrumsonsbeek.nl/techniek: > mode=0700 gid=-1 > doveadm(techniek(a)bezoekerscentrumsonsbeek.nl): Debug: Namespace : > /home/vmail/bezoekerscentrumsonsbeek.nl/techniek/.maildir:/home/vmail/bezoekerscentrumsonsbeek.nl/techniek/.INBOX doesn't exist yet, using default > permissions > doveadm(techniek(a)bezoekerscentrumsonsbeek.nl): Debug: Namespace : Using > permissions from /home/vmail/bezoekerscentrumsonsbeek.nl/techniek: > mode=0700 gid=-1 > doveadm(techniek(a)bezoekerscentrumsonsbeek.nl): Error: Couldn't create > mailbox maildir:/home/vmail/bezoekerscentrumsonsbeek.nl/techniek/.INBOX: > Invalid mailbox name Output of dovecot -n > # 2.0.19: /etc/dovecot/dovecot.conf > # OS: Linux 3.11.0-20-generic x86_64 Ubuntu 12.04.4 LTS ext4 > auth_mechanisms = plain login > first_valid_uid = 150 > last_valid_uid = 150 > mail_gid = mail > mail_location = maildir:/home/vmail/%d/%n > mail_uid = vmail > passdb { > args = /etc/dovecot/dovecot-sql.conf.ext > driver = sql > } > postmaster_address = adje(a)bezoekerscentrumsonsbeek.nl > protocols = " imap pop3" > service auth { > unix_listener /var/spool/postfix/private/auth { > group = postfix > mode = 0660 > user = postfix > } > unix_listener auth-userdb { > group = mail > mode = 0600 > user = vmail > } > } > ssl_cert = </etc/ssl/certs/dovecot.pem > ssl_key = </etc/ssl/private/dovecot.pem > userdb { > args = /etc/dovecot/dovecot-sql.conf.ext > driver = sql > } -- Systeembeheer Bezoekerscentrum Sonsbeek

3 6

[Dovecot] [repost] log sasl auth
by Roberto Tagliaferri - Tosnet srl 29 Apr '14

29 Apr '14

Excuse for the previous post. Hi, i've in use dovecot for pop3, imap and for sasl authenticator (for postfix). Can i log all sasl auth in a sql db (or in a flat file, or to a pipe)? -- Roberto Tagliaferri Tosnet srl

1 0

[Dovecot] log auth in a dn
by Roberto Tagliaferri - Tosnet srl 28 Apr '14

28 Apr '14

ÿØÿáExifII*ÿìDuckydÿáohttp://ns.adobe.com/xap/1.0/<?xpacket begin="ï»¿" id="W5M0MpCehiHzreSzNTczkc9d"?> <x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 5.3-c011 66.145661, 2012/02/06-14:56:27 "> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> <rdf:Description rdf:about="" xmlns:xmpMM="http://ns.adobe.com/xap/1.0/mm/" xmlns:stRef="http://ns.adobe.com/xap/1.0/sType/ResourceRef#" xmlns:xmp="http://ns.adobe.com/xap/1.0/" xmpMM:OriginalDocumentID="xmp.did:F57A6890EE79E311A005A1F913A30D81" xmpMM:DocumentID="xmp.did:67FAA6F27A1311E3B506EF72D9F2709E" xmpMM:InstanceID="xmp.iid:67FAA6F17A1311E3B506EF72D9F2709E" xmp:CreatorTool="Adobe Photoshop CS6 (Windows)"> <xmpMM:DerivedFrom stRef:instanceID="xmp.iid:F57A6890EE79E311A005A1F913A30D81" stRef:documentID="xmp.did:F57A6890EE79E311A005A1F913A30D81"/> </rdf:Description> </rdf:RDF> </x:xmpmeta> <?xpacket end="r"?>ÿîAdobedÀÿÛÿÀdÿÄ !1#"A$5'w( !1AQa"q2BR#±²Â3s4¡Ñr¢dÿÚ?ŸŸB¹WÞýEØ&SqêõsÑðÌzL+ØÔÖ¹1s*7Iå\Þ£ÐGh»stIIêITwÌI-(nA!¹Âãð²a4û&$¶R|:°:ü+-Ìs\ÇbÃÀõñBd2:Öàýße!5Çþ¹ ¹[U=Ó|d'·³<=Uî7$é¥Å@*ÊñÚérTkÂÜ°µ#øFúv®?Û.IFµüÊ£øê«yÜ¿YbÜ)3°Ûþž^Ö¿aÉiy$ÓH$ÃIÏ¯©F°eç»šãßÏ·Yªú }ú(£¢®äN¹Õ ºÕ qŽRÙÙæiòqYŠ©<¶úÚfÐù`ËML)d?ÉOf¢(€NÂFN0Â ò1¥3æ/x!·{v÷UFo/!2O ?ú#)(o íñí_Ÿ-bý%VôëÍ¿ì%«¹ñ¢M,pÍdØDRFÉj×£m]Í<$=))Mf| fàEÜ<à_«3ÁèÇÞæDÝðó2Ý€0óF\ù0°ÇG{üÄÅ·ð·©nÞätµ?Q|Úè«ëO]Meèf×ú+SÇONâ¡|Íú/sÈP·üJM»:g€dïï.Ö7ugQuQsásoÖj'(#yªÄB ~Êð(uÅKI/Uë¶¬%ñÊªÍbÙŒÞ7eÒ!aÿ#`{%®ISÊs$; h@yp2Á9ÆJ ÛyZÖÆ÷éJ{ìOlùàcG»s6Ü5îKÓóS|/È÷â|_äñÝñŒ^~ÿg»ÅïÛÛßþŸÝAMÒ·Ÿ9Î4wrœ=¿ê®Âþñ$»©ñºúúÅ)ýßÒÝ5>v*-©[ïÇMÑ®uÓvjÉ²¶6ãBJ×ÕšéªäŠHH¶FðbT 8` ¡ñ8ê÷²y(qÓçu}®ÕúW67éÌŸBp}êBÁ t6°® ?nTbÍž©6Æ5®U¿Ùd5ÅhÎòl6ü¢2Q,$ÍõÜÍÁÑ¥Ø¡5åîJžÁ/VQÁ`$¿é_ü^94°$°»/bMl & ÅXsñ·%žžû"*¥RTŒNÖ6úäXÕmy{]9²Ü2tÇx=Ç k{Þý~e©ÉtHÒ d©H,d\dû¿œª×CŸ3s»fá/µQG?î h9ÚÝzhÆÂúpzSTr+ÅçŠJË`ÄZåHVÕÖì«ÔÆÈKìò²t¶ý« hŸÛ`·(NnàRme}¿ŠÛÂÐÙF¥à÷6èÜA¥ÙA1FëZy5+QŠÇ&dxx¬ñOÃ+©k;nnüoni~##å 'óÉ $2$Lª¬ ±XÂ»ØÊê®å{jnJuSÁ·]Š-Ø²9UâÆHYç`ylPó±·«ôé@MÏzGmUbÀ0®F)JI $±â$|n>9c6ä?aEŸ?9žÿ:ÓM7>J0H¹ÔdI a¥Ò±÷ékTÑ¡e[Oæ\oí|¥tªÿ¡ãå4uÈùý'mŸŠåYLÐûDÕb ySn× DTr~x¹t( ¬¥ã80åG Ëùoó/à~Ñð=WÃM-Lñ¹Êü^uÎDBñ¹7õ¢ÒÏþµ'd£ñYþWZFõnO× (^QX»m{ò É^Ø^`ÏÏàÆ¥3u×60¿M€Â-Fcmu\ÔYsy\Æ 66¿}A9Ëy8þ¶H°ÃcÖÃbaÚK7NóÜ*·Î8Ø 1ó2¹.â&%Èj,1ZÇÈºnb ÌöîÒïW6îØ.ÙZ®*é]²4}A_>Ö³ |ù!jb~ëŽÍÆÞ+²ëÂÝÿ${\¹ÞT'V2C!._o Kò`Àhm[n:\-õkRåæs<N(ä3$Å=f ÄV;ù€eÜc[±ä±ÚÊÖSÅmø7BÁåP¢ÔÔ×S 2²šv'`)$SšuÄðs&Aªé9óÇäÅ¥â@ŸjŒž¶¢TaÀ*2"»ýÆöÉÇJò¬²«Xsæak©°|×œôµ«Î@òsžøÐIŽRJÁQŸëH·fm /ž>}RGäQHÓôØÌº6Æèüäo°0LèpXgŸEc'}ý}:©æÂŽäØ\ô¬ÓîMÙžÅN>©/\àÿÏÉÆ»×VLUTvÏ9vdWå x§®Ö'8ÓEe¹`\ËqVµ·È8@ÏWðãbò3GçoD9à|ª×ŸOÝµ¬zÞ±ÙyüÓøyé§»öû×ioç<vîUL²_iC_/ÃÛãÄûº.?ëùß©Y_ÇO°ýÍÛõ_¹ÿrÿõØÿXù;÷œ|³ÕEñýkÙýœú\n·ÆÖ¿ÙZ¹×nøœößclÝß³~íŸïã^w&1#êÔÃ!Ìä²évžÝñŽqšæÿ"~¬äÍlÀ<Ò ÷W%EN0&dXÇ¿F3*äFÌl¡ÔÜ.(ÍW|9R0ZC®ISa©_gk7.¹/;ÑšGZÏµÙã`fPF6 -Ñ'û_O¥oBè°. ³F2Æi94(Âc À÷ëÎyrñH#é{\16ÔÃXþÊéÜŸ+ñÛ ºêP°VpÚÌ:@&új)jÕ{N+ëYN·ñÞï°QÉ4¡âµGcæØºXŒ×wYäÕw4Rh3Â£Ó"uyÙÕA¡ìHg&>#ezþ è-È±µ#p=|)2ªø,cÆ¶ Î«Û³;l®Jn$šÒ(K7ÓÇ^òªµŠìò+8€ÙðØv%àkÖ`Ç5Ý®W7ÌþÉX?ÊÈÚ ,íQJÅÈZE!i 'R¯üŒÙX92CW 3«Oe¯b@Sn€kã¹Þ>ÎjXV^fp6Âdp³naœ±ÚB€jd³-eìî®ßºåO'×ÞnÛŒÊÚ7wzËÉmCN®NÆØ¹<v©`IzDêhÞ¥ Ä]Îcï_1&Ã¶«1éšíXùI×KU+Çfó*Ï-vñ¢+#Ô\k0)(*·ÜEjÃGéËr¶ÜZ6£DNuŽÎäé?ºTN·³2Ëg¬,WØÊóeË^sÙû=;,c3,mqýÐäâÌtÿhZú>Šv^Dàï¡ídHÔÜ÷~cI§vœµ,o¶§È6B¿M©)ŠÞk|uª6ßÇ(Ï®ÏðÐ{[äSê"ÄåSÜñÑ?(n0CJ¡åš0FH:ç @å$ã8³ñÖãÅN£Æºäðli,$'!oÈŸ×±Rz:;T,ÀSKøÿ¶#|qvðõ®7ÜïJ^Ù;§R±56drêÌïXôYŸLž¹ §[»NöÀb°"tXØ"I<F&Ø{ÈýîHÊE5Õ_],À©:\Ž¥À=*ñMÄqÒd@%ÌÅ+$ù|ÌÑ<rš¹(YLÊmb¶Ý®êbÚeOjxE Â1ëÉeqãIÎÃégWëRžÀ ^þ¥úÊ]`·Ó€p!ÀñäÃ\H8d"3O@Ø+ï,{XòÄ[°¥7· IcV%ÆöxD+Ü\ÝÓsµ¯±cV¬NàåDª»Ë+jòvŒ3U°šèòh©:r$ÒI=Ï?²§íñãP3Fk62Ä^=ñç¥ZD Ì2³áµBÿX$jL§ÛXÑnâò4£áaè®FÉŒ¶[aŽ~ÎK§w%+r²ÆvFŠkYôŸØ3qè5ÃIQ¢FèùäNWàz€IP€ŒÁupE w *XÍu ¶7ÎLÙÓñ¹^Þ5RE1vÛäac¢6ÖÆàõ&=Žµ¢Ç"ÂæŒDë×ÕðÝwº)µ¶úcd¯Yõ§Zf?fY`ñ ê|µdÞ çV×ôÎdL-4ó$F·gRãzl "^;m*îXFHš>É=;[º®WªÚœ£¢:(£¢:(£¢:(£¢:(£¢:(£¢:(£¢ÿÙ

1 0

[Dovecot] Why does it appear that dovecot is deleting messages after migration?
by Bill Eccles 28 Apr '14

28 Apr '14

Hi, y'all, long-time Mac OS X Server user Bill here with a thorny question for the mailing list since nobody at discussions.apple.com can quite put their finger on the answer. While well-aquainted with other aspects of Server, Dovecot is a bit of a mystery still to me. So here it goes: Background I'm struggling to migrate from MacOS X 10.6 to 10.9. I tried twice using the "live server in target disk mode" method, but after things went horribly awry (meaning I was left with no working services on the new server), I gave up on that and have been working to slowly bring services over, one at a time. I've got both Dovecot and PostFix accepting connections from my test machine, and I am able to connect with IMAP to the new server. What I Do... First, I turn both mail servers off. Then I tar up the /var/spool/imap/dovecot/mail directory on the old server, move it to the new server, untar it in /Library/Server/Mail/Data/ (where it belongs), and change ownership to _dovecot:mail, all per many other suggestions found in the Apple forums. (All files appear to be in maildir format, that I can tell.) I then turn the mail service back on on the new server. What Dovecot Does... (or appears to do) If I quickly connect to the new server with my IMAP client (MacOS X Mail.app) and create a "fresh user" in Mail.app, message folders appear correctly. But it's only a matter of time before Dovecot, or something, runs "doveadm index -u (usernames) (mailboxes)" on all of the mailboxes. As it does, it deletes thousands of messages, leaving, for example, the same 17 in INBOX and 3695 in "Deleted Items Archive". And 0 in others, and other seemingly-random numbers of messages in still yet others. I can watch it marching through the mailboxes, one at a time, if I "ps -ax" enough times. What I've Done to Counteract This... Nothing I've done so far has been able to do anything about it. Re-untar the archive, and it just does it all again. Try using dsync, and it just deletes the messages from the un-tar'd archive. In other words, there are thousands of messages in the archive which don't seem to meet Dovecot's requirement for being in that particular folder, so it deletes them. The "cur" directory in a mailbox directory may start out with >21000 messages in it, but when it's done, it'll have deleted the same messages from "cur" every time, leaving me with a fraction of what I started out with. I even used the 65-migrate_mailboxes.pl script (supplied as part of OS X 10.9 Server), and the same thing happens. (The migrate script does a lot more than just what I've noted above, but most of what it does is responsible for settings and configuration migration. Very little of the script is responsible for moving the data, and that part of the script ends up being a bunch of "cp" followed by a "chown"--essentially what I'm doing.) The Questions What is going on? Failing a fix, am I trying to migrate the wrong way? Is there a better way? Random Thoughts and Observations I've changed hostnames. The old one was shr-xs.mydomain.net, and the new one is shr-mini.mydomain.net. Is it unhappy with that for some reason? In one of the directories where messages are deleted, there were a zillion files named like this: 1396718896.M324523P43630.shr-xs.mydomain.net,S=1209,W=1238:2,Sac There were also a bunch of files named like this: 1211416234.cyrus.457,S=893:2,Sac When it's all said and done, and Dovecot has done its thing, care to guess which ones are left? Only these: 1211416234.cyrus.457,S=893:2,Sac Just to see if I could influence which files get deleted, I deleted all of the dovecot* files in the mailbox directory. And Dovecot recreated them faithfully, but still deleted all but the ones which said "cyrus" in the filenames. I changed the hostname to match shr-xs.mydomain.net, and that doesn't seem to have affected things a bit, though I don't have enough data to support that I really succeeded in changing the hostname for all services (specifically for Dovecot). Is Dovecot really filtering out messages that just don't seem to "belong" in the folder? Thanks, y'all. I've puzzled on this one for about eight hours and it now hurts my brain. I hope somebody else has an answer sans brain hurts.

3 3

[Dovecot] dovecot temporary suspension all of pop3 login about 5 minutes
by Jason 28 Apr '14

28 Apr '14

Dear All， When the user login P0P3 more than 10 times in 1 minute that the dovecot temporary suspension all of pop3 login about 5 minutes. How to disable the setting for dovecot. Mail Log: Apr 24 16:11:14 mww dovecot: pop3-login: Login: user=<scan>, method=PLAIN, rip=192.168.16.84, lip=192.168.16.159, mpid=8767, session=<5USPZMX3/QDAqBBU> Apr 24 16:11:14 mww dovecot: pop3(scan): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Apr 24 16:11:15 mww dovecot: auth-worker: Error: no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory Apr 24 16:11:15 mww dovecot: pop3-login: Login: user=<scan>, method=PLAIN, rip=192.168.16.84, lip=192.168.16.159, mpid=8769, session=<GzyeZMX3/wDAqBBU> Apr 24 16:11:15 mww dovecot: pop3(scan): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Apr 24 16:11:16 mww dovecot: auth-worker: Error: no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory Apr 24 16:11:16 mww dovecot: pop3-login: Login: user=<scan>, method=PLAIN, rip=192.168.16.84, lip=192.168.16.159, mpid=8771, session=<bGSsZMX3AQDAqBBU> Apr 24 16:11:16 mww dovecot: pop3(scan): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Apr 24 16:11:17 mww dovecot: auth-worker: Error: no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory Apr 24 16:11:17 mww dovecot: pop3-login: Login: user=<scan>, method=PLAIN, rip=192.168.16.84, lip=192.168.16.159, mpid=8773, session=<ASq6ZMX3AwDAqBBU> Apr 24 16:11:17 mww dovecot: pop3(scan): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Apr 24 16:11:18 mww dovecot: auth-worker: Error: no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory Apr 24 16:11:18 mww dovecot: pop3-login: Login: user=<scan>, method=PLAIN, rip=192.168.16.84, lip=192.168.16.159, mpid=8775, session=<Ux3JZMX3BQDAqBBU> Apr 24 16:11:18 mww dovecot: pop3(scan): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Apr 24 16:11:23 mww dovecot: pop3-login: Disconnected (auth failed, 1 attempts in 4 secs): user=<scan>, method=PLAIN, rip=192.168.16.84, lip=192.168.16.159, session=<kP3WZMX3BwDAqBBU> Apr 24 16:12:04 mww dovecot: pop3-login: Disconnected (auth failed, 1 attempts in 4 secs): user=<jason>, method=PLAIN, rip=192.168.16.59, lip=192.168.16.159, session=<WX9NZ8X3pwDAqBA7> Dovecot v2.2.9 # 2.2.9: /etc/dovecot/dovecot.conf doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:99: ssl_disable has been renamed to ssl # OS: Linux 3.13.0-24-generic x86_64 Ubuntu 14.04 LTS disable_plaintext_auth = no mail_location = mbox:~/mail:INBOX=/var/mail/%u namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = " imap pop3" ssl = no ssl_cert = </etc/dovecot/dovecot.pem ssl_key = </etc/dovecot/private/dovecot.pem userdb { driver = passwd } protocol imap { mail_max_userip_connections = 100 } protocol pop3 { mail_max_userip_connections = 100 } Best regards, Jason

2 3

Re: [Dovecot] Fwd: Dovecot cannot connect to PostgreSQL server
by Chris Vaas 28 Apr '14

28 Apr '14

On Mon, Apr 28, 2014 at 9:30 AM, Steffen Kaiser < skdovecot(a)smail.inf.fh-brs.de> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Mon, 28 Apr 2014, Chris Vaas wrote: > > I just looked into my SELinux audit log and found the following denial. >> >> type=AVC msg=audit(1398609990.493:280): avc: denied { name_connect } for >> pid=5964 comm="auth" dest=5432 >> scontext=unconfined_u:system_r:dovecot_auth_t:s0 >> tcontext=system_u:object_r:postgresql_port_t:s0 tclass=tcp_socket >> >> There seems to be a good chance, that this is my problem, doesn't it? But >> how can I allow the connection? >> > > I don't run SELinux, checkout a SELinux HowTo, e.g. > http://wiki.centos.org/HowTos/SELinux, audit2allow looks promising. > > - -- Steffen Kaiser > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > > iQEVAwUBU14Dj3z1H7kL/d9rAQKtdwf/d4mIe45sOFRkOc+BGfhD/PSYOKK9Akk9 > xRofzDZszgj/I9w1T5AWrND3Xn3RfXmCA3MuvEG4L3JAIznuPJWAATkV1XMw56v5 > pe4Z6SRB9aH6QZFvmDBfO5pEVrsGoXYeDCY78rZhSERXXgutCDuWHhQUK6pnnXTY > m2lumWt6w1mHpvLZZ5gxd2MjZiDZqYJYhhDbMGxb6lcVN42WJgfD5Lm1J000F6Pq > pbwCR+2lz2W9tBTCChJqTwIMebUhxesUQxcmFrh9/0/tR7b5hKkEY2o9OtDxRGt6 > A6qE/9H82peC64AtV7Cn6rbEJ76HVSCWMP9lLOhmiflpP3cwF+d7VA== > =aI5S > -----END PGP SIGNATURE----- > Bam. Works! Thank you very much, everyone! Cheers Chris

1 0

Re: [Dovecot] Fwd: Dovecot cannot connect to PostgreSQL server
by Chris Vaas 28 Apr '14

28 Apr '14

On Mon, Apr 28, 2014 at 9:11 AM, Steffen Kaiser < skdovecot(a)smail.inf.fh-brs.de> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Mon, 28 Apr 2014, Chris Vaas wrote: > > On Mon, Apr 28, 2014 at 8:43 AM, Steffen Kaiser < >> skdovecot(a)smail.inf.fh-brs.de> wrote: >> >> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> On Sun, 27 Apr 2014, Chris Vaas wrote: >>> >>> [fixed ugly top posting] >>> >>> On Sat, Apr 26, 2014 at 11:39 PM, Steffen < >>> skdovecot(a)smail.inf.fh-brs.de >>> >>>> wrote: >>>>> >>>> >>>> -----BEGIN PGP SIGNED MESSAGE----- >>>> >>>>> Hash: SHA1 >>>>> >>>>> Chris Vaas wrote: >>>>> >>>>> I am currently facing the following log output: >>>>>> >>>>>> Apr 26 16:40:28 h2290750 dovecot: auth: Error: pgsql(localhost): >>>>>> Connect failed to database mail: could not connect to server: >>>>>> Permission denied Apr 26 16:40:28 h2290750 dovecot: auth: Error: >>>>>> #011Is the server running on host "localhost" (::1) and accepting >>>>>> Apr 26 16:40:28 h2290750 dovecot: auth: Error: #011TCP/IP >>>>>> connections on port 5432? >>>>>> >>>>>> I have double checked the database. It is listening correctly and I >>>>>> can connect to it via >>>>>> >>>>>> psql -U mailreader mail >>>>>> >>>>>> I provided all necessary information to dovecot via this >>>>>> configuration snippet: >>>>>> >>>>>> driver = pgsql connect = host=localhost dbname=mail user=mailreader >>>>>> password=secret default_pass_scheme = SHA512 >>>>>> >>>>>> >>>>> does Postgres allow connections on "host ::1" for user mailreader ? >>>>> Actually I wonder, because I thought the Postgres lib defaults to >>>>> "local" (socket) by default on localhost -> does Postgres allow >>>>> connections on "local" for mailreader? Permissions are configured in >>>>> pg_hba.conf, but -> Does Postgres logs something? It should if PG >>>>> denies the connection. >>>>> >>>>> >>>> I set the host to 127.0.0.1 now. And my pg_hba.conf looks like that: >>> >>>> >>>> # TYPE DATABASE USER ADDRESS METHOD >>>> # Mail stuff >>>> host mail mailreader 127.0.0.1/32 md5 >>>> host mail mailreader ::1/128 md5 >>>> local all all md5 >>>> host all all 127.0.0.1/32 ident >>>> host all all ::1/128 ident >>>> >>>> >>> What about the "Does Postgres logs something?" >>> >>> >> The log under /var/logs/pgsql is completely empty. >> > > In addition to Aleksandar's question: Does Postgres runs at all? > > >>> Do you have SELinux or something like that running? >>> What about this question? >>> >> >> I do have a SELinux up and running, yeah. >> > > Did you've checked its logs, e.g. (pretty old): > http://linux.derkeiler.com/Mailing-Lists/Fedora/2006-03/msg05342.html > - -- Steffen Kaiser > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > > iQEVAwUBU13/FXz1H7kL/d9rAQLjbQf+IQV/jSAj+fvxCaIgxgzktUuJenONp5Za > LrxYEQ79YelD5ljH1Ms1cYyegp5+8ecHsp0Fc850ZBeEYsplfZjfvAoPP4lO+cdH > GOPt3+zniEdeEVMVFfOokyTGjSPWbRrlb5r/wWYj6pU35pkw1pK3M6hPxF2Y6grm > poLMdHvaktwIr9STtqu1JTOxRffLgW5qh1AcQwJ+BoNs+h0MKs7ddqgnfeV9bKZx > rmyOuAU36QnNcv+LJQJSiJMFw1pejS+OBvI23xYsj/04dAAiTzNHGe3doz/sF1PX > P2zroewTEEb+lkvjUkOmukLuTlLnCAVgdHyWZF37c5vML9HD7Xyqrg== > =e13N > -----END PGP SIGNATURE----- > It is running, yes. I can connect from my local machine to the server without a flaw. About SELinux: I just looked into my SELinux audit log and found the following denial. type=AVC msg=audit(1398609990.493:280): avc: denied { name_connect } for pid=5964 comm="auth" dest=5432 scontext=unconfined_u:system_r:dovecot_auth_t:s0 tcontext=system_u:object_r:postgresql_port_t:s0 tclass=tcp_socket There seems to be a good chance, that this is my problem, doesn't it? But how can I allow the connection? Cheers Chris

2 1

Re: [Dovecot] Fwd: Dovecot cannot connect to PostgreSQL server
by Chris Vaas 28 Apr '14

28 Apr '14

On Mon, Apr 28, 2014 at 8:43 AM, Steffen Kaiser < skdovecot(a)smail.inf.fh-brs.de> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Sun, 27 Apr 2014, Chris Vaas wrote: > > [fixed ugly top posting] > > On Sat, Apr 26, 2014 at 11:39 PM, Steffen <skdovecot(a)smail.inf.fh-brs.de >> >wrote: >> >> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> Chris Vaas wrote: >>> >>>> I am currently facing the following log output: >>>> >>>> Apr 26 16:40:28 h2290750 dovecot: auth: Error: pgsql(localhost): >>>> Connect failed to database mail: could not connect to server: >>>> Permission denied Apr 26 16:40:28 h2290750 dovecot: auth: Error: >>>> #011Is the server running on host "localhost" (::1) and accepting >>>> Apr 26 16:40:28 h2290750 dovecot: auth: Error: #011TCP/IP >>>> connections on port 5432? >>>> >>>> I have double checked the database. It is listening correctly and I >>>> can connect to it via >>>> >>>> psql -U mailreader mail >>>> >>>> I provided all necessary information to dovecot via this >>>> configuration snippet: >>>> >>>> driver = pgsql connect = host=localhost dbname=mail user=mailreader >>>> password=secret default_pass_scheme = SHA512 >>>> >>> >>> does Postgres allow connections on "host ::1" for user mailreader ? >>> Actually I wonder, because I thought the Postgres lib defaults to >>> "local" (socket) by default on localhost -> does Postgres allow >>> connections on "local" for mailreader? Permissions are configured in >>> pg_hba.conf, but -> Does Postgres logs something? It should if PG >>> denies the connection. >>> >> > I set the host to 127.0.0.1 now. And my pg_hba.conf looks like that: >> >> # TYPE DATABASE USER ADDRESS METHOD >> # Mail stuff >> host mail mailreader 127.0.0.1/32 md5 >> host mail mailreader ::1/128 md5 >> local all all md5 >> host all all 127.0.0.1/32 ident >> host all all ::1/128 ident >> > > What about the "Does Postgres logs something?" > The log under /var/logs/pgsql is completely empty. > > Do you have SELinux or something like that running? >>> >> > What about this question? > I do have a SELinux up and running, yeah. > > > I remember that I had a server that had wrong permissions on: >>> >>> ls -al /var/run/postgresql >>> >>> drwxrwsr-x 2 postgres postgres 4096 Feb 10 07:32 ./ >>> srwxrwxrwx 1 postgres postgres 0 Apr 26 23:15 .s.PGSQL.5432= >>> >>> the .s.PGSQL. socket is the local socket usually used for localhost >>> connections and automatically found by libpg. >>> >> > The folder /var/run/postgresql is not existing on my machine. >> > > - -- Steffen Kaiser - Chris

2 2

[Dovecot] Fwd: Dovecot cannot connect to PostgreSQL server
by Chris Vaas 28 Apr '14

28 Apr '14

I set the host to 127.0.0.1 now. And my pg_hba.conf looks like that: # TYPE DATABASE USER ADDRESS METHOD # Mail stuff host mail mailreader 127.0.0.1/32 md5 host mail mailreader ::1/128 md5 local all all md5 host all all 127.0.0.1/32 ident host all all ::1/128 ident The folder /var/run/postgresql is not existing on my machine. The problem is still present. :( On Sat, Apr 26, 2014 at 11:39 PM, Steffen <skdovecot(a)smail.inf.fh-brs.de>wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Chris Vaas wrote: > > I am currently facing the following log output: > > > > Apr 26 16:40:28 h2290750 dovecot: auth: Error: pgsql(localhost): > > Connect failed to database mail: could not connect to server: > > Permission denied Apr 26 16:40:28 h2290750 dovecot: auth: Error: > > #011Is the server running on host "localhost" (::1) and accepting > > Apr 26 16:40:28 h2290750 dovecot: auth: Error: #011TCP/IP > > connections on port 5432? > > > > I have double checked the database. It is listening correctly and I > > can connect to it via > > > > psql -U mailreader mail > > > > I provided all necessary information to dovecot via this > > configuration snippet: > > > > driver = pgsql connect = host=localhost dbname=mail user=mailreader > > password=secret default_pass_scheme = SHA512 > > does Postgres allow connections on "host ::1" for user mailreader ? > Actually I wonder, because I thought the Postgres lib defaults to > "local" (socket) by default on localhost -> does Postgres allow > connections on "local" for mailreader? Permissions are configured in > pg_hba.conf, but -> Does Postgres logs something? It should if PG > denies the connection. > > Do you have SELinux or something like that running? > > I remember that I had a server that had wrong permissions on: > > ls -al /var/run/postgresql > > drwxrwsr-x 2 postgres postgres 4096 Feb 10 07:32 ./ > srwxrwxrwx 1 postgres postgres 0 Apr 26 23:15 .s.PGSQL.5432= > > the .s.PGSQL. socket is the local socket usually used for localhost > connections and automatically found by libpg. > > - -- > Steffen > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (Darwin) > Comment: Using GnuPG with undefined - http://www.enigmail.net/ > > iQEVAwUBU1wnoXD1/YhP6VMHAQJh8gf/fyThDqYhNiMXk6YNtwgiAT8MLyCblXOR > 1/4scQAFQUTbHgOODBfoJkoTdtsmhBu0UmxNe9Y/1Y+j2pAcVU2GrJAGLEED1Is0 > OmPPptnrdGaqjsIaybIDpmuJM7vqmOYhPMvAOGVXdgXdKa5QQZU3hgo/fH1xdIrj > j45LEfLE8Cu9QedOolXz4adFLk2XuRylMJWhQWrsT3yutr38Nv6wqhRDl7Rxwo4p > 2y1b2GiBTZkVHXzUs0a2UKxOsYsgQVgCcN6wCyio0ogCTAKwHWeQ00rUpNmn9COw > xKf5nhFPR8RYlCKukk7Djb2aklIfvko6S9+QoCKZEufjNi/moA4pcg== > =1sd0 > -----END PGP SIGNATURE----- >

3 2

Re: [Dovecot] Dovecot cannot connect to PostgreSQL server
by Joseph Tam 28 Apr '14

28 Apr '14

Chris Vaas writes: >> psql -U mailreader mail >> >> I provided all necessary information to dovecot via this configuration >> snippet: >> >> driver = pgsql >> connect = host=localhost dbname=mail user=mailreader password=secret >> default_pass_scheme = SHA512 ... > I set the host to 127.0.0.1 now. And my pg_hba.conf looks like that: > > # TYPE DATABASE USER ADDRESS METHOD > # Mail stuff > host mail mailreader 127.0.0.1/32 md5 Shouldn't the last column here match your "default_pass_scheme" above? Maybe change "default_pass_scheme" to "md5-crypt" or "md5"? Joseph Tam <jtam.home(a)gmail.com>

2 1

[Dovecot] All Mail folder as in Gmail
by Dmitry Podkovyrkin 27 Apr '14

27 Apr '14

Hello How to make a folder "All Mail" so that it got a letter from the Inbox and Sent? Mail client makes a copy of emails sent to the folder Sent. -- Regards Dmitry Podkovyrkin email: dmirty(a)rutelecom.company

2 2

[Dovecot] Dovecot cannot connect to PostgreSQL server
by Chris Vaas 26 Apr '14

26 Apr '14

I am currently facing the following log output: Apr 26 16:40:28 h2290750 dovecot: auth: Error: pgsql(localhost): Connect failed to database mail: could not connect to server: Permission denied Apr 26 16:40:28 h2290750 dovecot: auth: Error: #011Is the server running on host "localhost" (::1) and accepting Apr 26 16:40:28 h2290750 dovecot: auth: Error: #011TCP/IP connections on port 5432? I have double checked the database. It is listening correctly and I can connect to it via psql -U mailreader mail I provided all necessary information to dovecot via this configuration snippet: driver = pgsql connect = host=localhost dbname=mail user=mailreader password=secret default_pass_scheme = SHA512 password_query = SELECT email as user, password, 'maildir:/home/mail'||maildir as userdb_mail FROM users WHERE email = '%u' How can I debug this situation? Cheers Chris

4 4

Re: [Dovecot] Dovecot cannot connect to PostgreSQL server
by Reindl Harald 26 Apr '14

26 Apr '14

first: don't reply off-list and don't top-post Am 26.04.2014 18:26, schrieb Christian Vaas: > How do I determine my postgresql socket location? > > On Apr 26, 2014 6:17 PM, "Reindl Harald" <h.reindl(a)thelounge.net <mailto:h.reindl@thelounge.net>> wrote: > > Am 26.04.2014 18 <tel:26.04.2014%2018>:06, schrieb Chris Vaas: > > I am currently facing the following log output: > > > > Apr 26 16:40:28 h2290750 dovecot: auth: Error: pgsql(localhost): Connect > > failed to database mail: could not connect to server: Permission denied > > Apr 26 16:40:28 h2290750 dovecot: auth: Error: #011Is the server running on > > host "localhost" (::1) and accepting > > Apr 26 16:40:28 h2290750 dovecot: auth: Error: #011TCP/IP connections on > > port 5432? > > > > I have double checked the database. It is listening correctly and I can > > connect to it via > > > > psql -U mailreader mail > > > > I provided all necessary information to dovecot via this configuration > > snippet: > > > > driver = pgsql > > connect = host=localhost dbname=mail user=mailreader password=secret > > default_pass_scheme = SHA512 > > password_query = SELECT email as user, password, > > 'maildir:/home/mail'||maildir as userdb_mail FROM users WHERE email = '%u' > > > > How can I debug this situation? > > try "host=/path/to/your/unix/socket" instead just only "localhost" > or switch to TCP with using 127.0.0.1 instead localhost > > in case of mysqld this would be "host=/var/lib/mysql/mysql.sock" why don't you know that? it's your machine and i don't use PostgreSQL at all "updatedb; locate post | grep socket" may be a good start just read the man page of your distribtion or use google google: "name-of-your-distribution postgresql unix socket" or simply try 127.0.0.1 which is as explained different to localhost localhost is typically unix-socket and 127.0.0.1 TCP/IP, in any case you have to make sure that the user is allowed in case of mysql i can set different permissions for "user1@localhost" and "user1(a)127.0.0.1", most likely PostgeSQL supports that too

1 0

[Dovecot] Incompatibility Thunderbirds Auth Mech TLS-Certificate <-> Dovecot
by Christian Felsing 25 Apr '14

25 Apr '14

Hello, it seems there there is an issue regarding "TLS-Certtificate" authentication in Thunderbird and Dovecot. Obviously client certificate is recognized by Dovecot: Apr 25 14:29:01 dovecot dovecot: imap-login: Valid certificate: /emailAddress=christian.felsing(a)example.net/CN=Christian Felsing (Test)/OU=CF Certificates/O=example.net/C=DE AFAIK Dovecot always requires IMAP login, even in "static" passdb config. Static means arbitrary password is ok, but not "no login" I hope, I am wrong, following log entry gave a hint, what Thunderbird does or more precisely - not do: Apr 25 14:29:01 dovecot dovecot: imap-login: Disconnected (no auth attempts in 5 secs): user=<>, rip=192.168.1.99, lip=192.168.42.1, TLS, session=<3+1THN33NQBtWq5D> Dovecot wants an IMAP login, but Thunderbird does not so. I am not sure if that is a bug (or feature) of Dovecot or Thunderbird. Thunderbird does several strange things on client certificates: 1st) If Dovecot is configured to request a client certificate and Thunderbird is configured to use plain text auth, Thunderbird offers a client certificate and login succeeds as configured in Dovecot. Unfortunately Thunderbird uses same certificate for all configured accounts to that host. Very bad if Dovecot reads username from certificate attributes. 2nd) If Dovecot is configured to request a client certificate and Thunderbird is configured to use TLS-Certificate, Thunderbird also offers a client certificate, but Dovecot requests login from Thunderbird. That fails, because Thunderbird assumes TLS-Certificate is enough for successful log. If it is true that Dovecot is not compatible to Thunderbirds way of TLS-Certificate Authentication, I consider to set up a proxy, which supports that way. May be Nginx would be a solution, it supports IMAP and LUA module plus some LUA code will fake the authentication. This is an ugly hack so I would like to avoid that, if anybody has a better solution. Thunderbird is a very widespread IMAP client so it should not be ignored. best regards Christian ---Dovecot config--- # /opt/dovecot/bin/doveconf -n # 2.2.12: /opt/dovecot/etc/dovecot-cert/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.4 auth_debug = yes auth_debug_passwords = yes auth_master_user_separator = * auth_ssl_require_client_cert = yes auth_ssl_username_from_cert = yes auth_username_chars = "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@#" auth_username_translation = "@#" base_dir = /var/run/dovecot-cert first_valid_uid = 124 last_valid_uid = 124 listen = 192.168.42.1 log_timestamp = %Y-%m-%d %H:%M:%S login_greeting = example.net imap4/pop3 (cert only) ready. mail_gid = 124 mail_location = maildir:~/Maildir mail_privileged_group = vmail mail_uid = 124 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 imapflags notify namespace { list = children location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u prefix = shared/%%u/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes list = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = / type = private } passdb { args = password=test driver = static } plugin { acl = vfile:/etc/dovecot/global-acls:cache_secs=300 acl_shared_dict = file:/var/lib/dovecot/shared-mailboxes autocreate = Trash autocreate2 = Drafts autosubscribe = Trash autosubscribe2 = Drafts quota = maildir:User quota quota_rule = *:storage=500M quota_rule2 = Trash:storage=+100M quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u recipient_delimiter = + sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +notify +imapflags } protocols = imap pop3 lmtp sieve service anvil { client_limit = 4000 } service auth-worker { group = vmail } service auth { client_limit = 8000 unix_listener auth-master { group = vmail mode = 0660 user = vmail } unix_listener auth-userdb { group = vmail mode = 0660 user = dovecot } user = root } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_limit = 1024 } service imap-postlogin { executable = script-login /opt/cfbin/lastlogin.sh } service imap { executable = imap imap-postlogin } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } process_limit = 1024 } service pop3-postlogin { executable = script-login /opt/cfbin/lastlogin.sh } service pop3 { executable = pop3 pop3-postlogin } service quota-warning { executable = script /opt/cfbin/quota-warning.sh user = vmail } ssl_ca = </opt/dovecot/etc/dovecot/client-ca.pem ssl_cert = </opt/dovecot/etc/dovecot/example.net.pem ssl_cipher_list = kEECDH:kEDH:AESGCM:ALL:+3DES:!RC4:!LOW:!EXP:!MD5:!aNULL:!eNULL ssl_dh_parameters_length = 4096 ssl_key = </opt/dovecot/etc/dovecot/example.net.key ssl_prefer_server_ciphers = yes ssl_verify_client_cert = yes verbose_ssl = yes protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_max_userip_connections = 20 mail_plugins = quota imap_quota acl imap_acl } protocol sieve { managesieve_logout_format = bytes ( in=%i : out=%o ) } protocol pop3 { mail_plugins = quota pop3_uidl_format = %08Xu%08Xv }

2 1