- dovecot - dovecot.org

FreeBSD / dovecot 2.2.27 / libwrap
by Jim Pazarena 30 Dec '16

30 Dec '16

I have compiled dovecot2 for FreeBSD with the tcpwrap option. A tcpwrap binary gets built and resides in the FreeBSD directory /usr/local/libexec/dovecot an examination of the compiled options (using the FreeBSD pkg install dovecot2) confirms: LIBWRAP : on yet, when I adjust dovecot.conf with: login_access_sockets = tcpwrap I get the following logged error message: 20161229 17:02:49 imap-login: Error: connect(tcpwrap) failed: No such file or directory Is there any way to turn up some super logging so that I can find just what dovecot feels is the failure ? Or, does anyone have an idea how to figure this out? What little hair I have is rapidly getting pulled out in frustration! Thank you. -- Jim Pazarena dovecot(a)paz.bz

2 1

doveadm expunge -A Error: Dictionary commit failed
by Alessio Cecchi 29 Dec '16

29 Dec '16

Hi, with the latest dovecot-ee version (dovecot-ee-2.2.26.1-10) if I run “doveadm expunge -A mailbox Spam savedbefore 30d” dovecot an error: doveadm: Error: dict-client: Commit failed: Dict server timeout: No input for 1916.209 secs (1 commands pending, oldest sent 0.000 secs ago: C1) (reply took 0.000 secs) doveadm: Error: expire: Dictionary commit failed Probably also "doveadm quota recalc -A" fail. Everything worked fine up to version 2.2.24 I hope can be fixed. Thanks -- Alessio Cecchi Postmaster AT http://www.qboxmail.it http://www.linkedin.com/in/alessice

3 6

dovecot-ldap.conf.ext for FreeIPA usage
by Matt . 29 Dec '16

29 Dec '16

Hello, I'm figuring out how to auth users against FreeIPA and I wonder if someone did this without GSAPI. My users are stored in a mysql DB where I wonder what I shall use as authname, the username or the mailaddress. As the mailaddress is always unique it could be best but if a user has multiple mailaddresses under seperate domains username might be better. Any clue here and maybe an example for dovecot-ldap.conf.ext when using FreeIPA ? Thanks! Matt

2 1

IPv4/IPv6 mismatches of doveadm: Fatal: connect(fd00:b::1:12345) failed: Connection refused
by Michael Grimm 28 Dec '16

28 Dec '16

Hi — I recently extendend my IPsec tunnel between two mail servers to deal with IPv4 addresses in addition to IPv6 ones. (No specific reason for that.) I ran into an issue worth reporting. This is Dovecot v2.2.27 (c0f36b0) at FreeBSD STABLE-11. Previously: dovecot.conf: plugin { mail_replica = tcp:remote.test } service doveadm { inet_listener { address = [::] } } | local> host remote.test: remote.test has IPv6 address fd00:b::1 working well. Currently: dovecot.conf: plugin { mail_replica = tcp:remote.test } service doveadm { inet_listener { address = * } } | local> host remote.test: remote.test has address 10.2.0.1 remote.test has IPv6 address fd00:b::1 Now, Replication stops and throws an error like: | <mail.crit> local.test dovecot: doveadm(user): Fatal: connect(fd00:b::1:12345) failed: Connection refused If I either #) remove IPv6 from my lokal DNS, #) use "mail_replica = tcp:10.2.0.1", or #) define the appropriate IPv4 address of remote.test in /etc/hosts, then replication works as usual. Hmm, shouldn't doveadm be more persistent in using every IP address of that entry of mail_replica *before* throwing a "Fatal:" error? Or do I miss something, and it's a feature, instead? Regards, Michael

1 0

Versioning Problem
by Günther J. Niederwimmer 28 Dec '16

28 Dec '16

Hello List, I have installed dovecot 2.2.25 on three Systems with two I have a problem with doveadm / dsync ? first: # 2.2.25 (7be1766): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.14 (099a97c) # OS: Linux 3.10.0-514.2.2.el7.x86_64 x86_64 CentOS Linux release 7.3.1611 (Core) second: # 2.2.25 (7be1766): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.14 (099a97c) # OS: Linux 3.10.0-514.2.2.el7.x86_64 x86_64 CentOS Linux release 7.3.1611 (Core) But I have this Error in the Logs ? Dec 27 12:00:12 mx dovecot: doveadm(2a02:xxxx:xxxx:xxxx::218): Error: doveadm client not compatible with this server (mixed old and new binaries?) Dec 27 12:01:08 mx dovecot: doveadm(2a02:xxxx:xxxx:xxxx::218): Error: doveadm client not compatible with this server (mixed old and new binaries?) can any tell me why ? -- mit freundlichen Grüssen / best regards Günther J. Niederwimmer

1 0

Identify if a message_part is an attachment ?
by Sai Kiran Gummaraj 27 Dec '16

27 Dec '16

Hello, This is my first post to this group. I have read through the instructions before posting. I hope am doing the right thing. If not my sincere apologies. I am in the process of developing a dovecot IMAP plugin (over v2.2.25). The plugin works with mdbox/sdbox which has ability to keep attachments as external references (via SiS POSIX). The plugin must enable fetching attachment from REDIS instead of local-store. To accomplish this I was following dovecot via my debugger. I wanted to understand if there was a way to determine a message_part to be of an attachment type ? Thanks. -- Regards, Sai Kiran cmd_fetch() |_ imap_fetch_more() |_ imap_fetch_more_int() |_ imap_fetch_state *state = &ctx->state; state->cur_mail is NULL. search mailbox |_ mailbox_search_next(state->search_ctx, &state->cur_mail) |_ mailbox_search_next_nonblock (via vfunc) |_ index_storage_search_next_nonblock |_ search_more_with_prefetching(ctx, mail_r) |_ mail = index_search_get_mail(ctx) |_ allocates mail (vfunc mail_alloc) and calls hook. |_ also allocates index_mails ret = search_more_with_mail(ctx, mail); |_ call handler (*h) => fetch_body_msgpart |_ imap_msgpart_open |_ imap_msgpart_find_part(mail, msgpart, &part); /* only mail comes here */ mail (uid=1739, seq=5) msgpart (section_number = 2, fetch_type = FETCH_MIME_BODY, partial_offset = 0, partial_size = 512, decode_cte_to_binary = 0) |_ mail_get_parts(mail, &parts) /* atmail send msgpart */ |_ call to p->v.get_parts(mail, parts_r) (index_mail_get_parts) /* atmail over-ride this function */ |_ get_cached_parts(mail) /* sets data->part */ |_ get_unserialized_parts(index_mail) |_ get_serialized_parts(mail, &part_buf) |_ index_mail_cache_lookup_field |_ mail_cache_lookup_field |_ imap_msgpart_open_normal() |_ .. see call stack below ..

2 1

permissions and doveadm
by dovecot 26 Dec '16

26 Dec '16

I did an upgrade from OpenSUSE 13.1 to 13.2 (finally), and now doveadm fails. I went from an self-compiled source, to 'repsitory'-version (from version 2.1.6, to 2.2.13) luuk@opensuse:~/bin> id uid=1000(luuk) gid=100(users) groups=100(users),7(lp),33(video),118(vboxusers) luuk@opensuse:~/bin> doveadm quota recalc luuk@opensuse:~/bin> doveadm quota recalc -u luuk doveadm(luuk): Error: userdb lookup: connect(/usr/local/var/run/dovecot/auth-userdb) failed: Connection refused doveadm(luuk): Fatal: User lookup failed: Internal error occurred. Refer to server log for more information. Why is it that with the '-u' option, doveadm is getting a connection refused? -- Luuk

4 4

postlogin script - still confused
by Michael Fox 25 Dec '16

25 Dec '16

> You need to use executable = script-login -- /path/post-login.sh -a -r -g > note the double-dash. it tells getopt to stop processing arguments. > > Aki OK. Thanks. So let me make sure I have this right, since there is no syntax defined on the wiki - just an example which doesn't show the above syntax. The valid possibilities are: executable = script-login [-d] /path/script1 /path/script2 ... -or- executable = script-login [-d] -- /path/script1 -a -r -g -s In other words, I can either call multiple scripts, each with no arguments, or I can call one script with arguments. But I cannot call multiple scripts, some with arguments, some without arguments. Is that correct? If not, please show all valid syntax options. Also, regarding the exec "$@" line shown at the end of the wiki examples. If I pass arguments "-a -r -g -s" to my script, as in: executable = script-login -- /path/script1 -a -r -g -s then doesn't the exec "$@" line at the end become: exec -a -r -g -s And surely that's not right. So, could you please explain in words the purpose of the exec line at the end - what it does, why it's needed, and what to do if I'm sending arguments to my postlogin script? Thanks, Michael

1 0

Domains on different IPs
by Mark Constable 23 Dec '16

23 Dec '16

I want to supply separate Letsencrypt certificates for each virtual domain and seeing that SNI does not work I need to allocate separate IPs. Could anyone give some pointers, or keywords to search for, on... a) how to make dovecot listen for different domains on different IPs? b) how to configure separate SSL certs for each of these IPs?

3 2

The left angle bracket at the beginning of the certificate path
by Илья 22 Dec '16

22 Dec '16

dovecot 2.2.27 (c0f36b0) openSUSE Tumbleweed x86_64 https://forums.opensuse.org/showthread.php/521796-Dovecot-doveconf-Fatal-ex… Faced with an unpleasant situation, when ssl_client_ca_file options are specified path to the left angle bracket, as in options ssl_key ssl_cert ssl_ca path is so. This doveconf shows no syntax error, and the arrow moves to managesieve which there generally is not involved in any side. dovecot: doveconf: Fatal: execvp(/usr/lib/dovecot/managesieve) failed: Argument list too long dovecot: config: Error: managesieve-login: dump-capability process returned 89 I consider this a bug, and that it should not be. And explain why you need left angle brackets in the options ssl_key ssl_cert ssl_ca?

1 0