December 2019 - dovecot

some error about dovecot when compile
by Magiczero 04 Dec '19

04 Dec '19

when i build dovecot in my computer, something has occured like below: root@2030c8624e88:/dovecot-2.3.9# ./autogen.sh --2019-12-04 10:49:53-- https://www.dovecot.org/tmp/wiki2-export.tar.gz Resolving www.dovecot.org (www.dovecot.org) 94.237.12.234, 2a04:3545:1000:720:acc1:5bff:fe5e:4e9 Connecting to www.dovecot.org (www.dovecot.org)|94.237.12.234|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 446263 (436K) [application/x-gzip] Saving to: 'wiki2-export.tar.gz' wiki2-export.tar.gz 100%[===============================>] 435.80K 152KB/s in 2.9s 2019-12-04 10:49:59 (152 KB/s) - 'wiki2-export.tar.gz' saved [446263/446263] configure.ac:298: warning: macro 'AM_ICONV' not found in library libtoolize: putting auxiliary files in '.'. libtoolize: copying file './ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'. libtoolize: copying file 'm4/libtool.m4' libtoolize: copying file 'm4/ltoptions.m4' libtoolize: copying file 'm4/ltsugar.m4' libtoolize: copying file 'm4/ltversion.m4' libtoolize: copying file 'm4/lt~obsolete.m4' configure.ac:298: warning: macro 'AM_ICONV' not found in library configure.ac:22: error: possibly undefined macro: AC_DEFINE If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:127: error: possibly undefined macro: dnl configure.ac:298: error: possibly undefined macro: AM_ICONV configure.ac:429: error: possibly undefined macro: AC_CHECK_HEADER configure:24018: error: possibly undefined macro: AC_CHECK_LIB configure:25593: error: possibly undefined macro: AC_CHECK_FUNC autoreconf: /usr/bin/autoconf failed with exit status: 1 from the information, i think the problem is macro 'AM_ICONV', there are any problem in the setup script? i want you help me to solve this issue. Thank you. Best MagicZero Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 2

Pigeonhole v0.5.9 released
by Aki Tuomi 04 Dec '19

04 Dec '19

Hi all! We are pleased to release v0.5.9 of Pigeonhole. Please find it from locations below --- Aki Tuomi Open-Xchange oy https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.9.ta… https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.9.ta… Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot --- + Added events for Sieve and ManageSieve, see https://doc.dovecot.org/admin_manual/list_of_events/#pigeonhole + Pigeonhole: Implement the Sieve "special-use" extension described in RFC 8579. - duplicate: Test only compared the handles which would cause different values to be cached as the same duplicate test. Fix to also compare the actual hashes. - imap_sieve_filter: IMAP FILTER Command had various bugs in error handling. Errors may have been duplicated for each email, errors may have been missing entirely, command tag and ERRORS/WARNINGS parameters were swapped.

1 0

Fast searching from android device with Dovecot/Maildir
by John Gateley 03 Dec '19

03 Dec '19

Hello, I am using dovecot as an imap server, mail is stored in mail directories. Configuration is below. One mail directory has about 14 Gb of mail in the inbox and .Sent directories. Searching from an Android phone with gmail is slow or doesn't work (it times out). Is there a configuration for Dovecot that can improve this? A better e-mail client for Android? Thanks, John root@giraffe:~# dovecot --version 2.2.27 (c0f36b0) root@giraffe:~# doveconf -an # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.9.0-11-amd64 x86_64 Debian 9.11 ... mail_location = maildir:~/Maildir 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 = } ... protocols = " imap" ...

3 3

fts_solr and # char
by Marcio Merlone 03 Dec '19

03 Dec '19

Hi, Dovecot wiki says the solr url is something like 'solr/dovecot/' but this gives a 404, if I install solr as per the docs I have a 'solr/#/dovecot/' url: https://wiki.dovecot.org/Plugins/FTS/Solr I have installed dovecot 2.3 from https://repo.dovecot.org/ and solr 8.3 as per the wiki on a Ubuntu 18.04. The problem and the guess work I did: fts_solr = url=http://localhost:8983/solr/#/dovecot/ doveconf: Warning: Configuration file /etc/dovecot/conf.d/90-plugin.conf line 13: Ambiguous '#' character in line, treating it as comment. Add a space before it to remove this warning. fts_solr = url="http://localhost:8983/solr/#/dovecot/" Error: fts: Failed to initialize backend 'solr': fts_solr: Failed to parse HTTP url: Path component contains invalid character fts_solr = url='http://localhost:8983/solr/#/dovecot/' Error: fts: Failed to initialize backend 'solr': fts_solr: Failed to parse HTTP url: Relative HTTP URL not allowed fts_solr = url=http://localhost:8983/solr/%23/dovecot/ Error: Failed to expand plugin setting fts_solr = 'url=http://localhost:8983/solr/%23/dovecot/': Unknown variable '%/' fts_solr = 'url=http://localhost:8983/solr/#/dovecot/' fts_solr: Failed to parse HTTP url: URL fragment not allowed for HTTP URL in this context Thanks for any help. -- *Marcio Merlone=*

2 1

running dovecot under different user
by Marc Roos 02 Dec '19

02 Dec '19

Did anyone ever managed to run dovecot as a non-root user?

2 2

Running dovecot proxy as different user
by Marc Roos 02 Dec '19

02 Dec '19

I thought, I read somewhere I could prevent chroot with[1] but I am still getting chroot errors[2]. drwxrwxr-x 2 10053 101 6 Dec 2 16:54 empty drwxr-x--- 2 10053 101 73 Dec 2 17:00 login drwxr-x--- 2 10053 101 44 Dec 2 17:00 token-login [1] service anvil { chroot = } [2] Dec 2 17:07:07 c04 dovecot: stats: Fatal: chroot(/var/dovecot/empty) failed: Operation not permitted Dec 2 17:07:07 c04 dovecot: master: Error: service(stats): command startup failed, throttling for 16 secs Dec 2 17:07:07 c04 dovecot: pop3-login: Fatal: setgid(101(dovenull)) failed with euid=10053(dovecot), gid=10053(dovecot), egid=10053(dovecot): Operation not permitted (This binary should probably be called with process group set to 101(dovenull) instead of 10053(dovecot)) Dec 2 17:07:07 c04 dovecot: master: Error: service(pop3-login): command startup failed, throttling for 16 secs

1 0

Mail-crypt won't encrypt emails
by Serveria Support 02 Dec '19

02 Dec '19

Hi, (Reposting as my previous post got zero replies.) We're running Dovecot 2.2.36 and we need to set up the mail-crypt plugin to encrypt all incoming and outgoing emails. Outgoing emails seem to get encrypted fine but the incoming ones don't. We tried everything including this config: mail_attribute_dict = file:%h/Maildir/dovecot-attributes mail_plugins = $mail_plugins mail_crypt plugin { mail_crypt_global_private_key = <ecprivkey.pem mail_crypt_global_public_key = <ecpubkey.pem mail_crypt_save_version = 2 } also this one: plugin { mail_crypt_curve = prime256v1 mail_crypt_save_version = 2 } but to no avail. There are no visible errors, Dovecot restarts fine and outgoing emails get encrypted. Any ideas? -- Kind Regards, Support Team SERVERIA.COM Riga, LV-1063, Latvia US: +1 (213) 224-7938 LV: + (371) 22330032 Skype: bighostlv support(a)serveria.com www.serveria.com

3 2

Cert for ip range?
by Marc Roos 01 Dec '19

01 Dec '19

Is it possible to configure a network for a cert instead of an ip? Something like this: local 192.0.2.0 { ssl_cert = </etc/ssl/dovecot/imap-02.example.com.cert.pem ssl_key = </etc/ssl/dovecot/imap-02.example.com.key.pem } Or local 192.0.2.0/24 { ssl_cert = </etc/ssl/dovecot/imap-02.example.com.cert.pem ssl_key = </etc/ssl/dovecot/imap-02.example.com.key.pem } https://wiki.dovecot.org/SSL/DovecotConfiguration

3 5

Error: proxy: Remote returned invalid banner: 220
by Marc Roos 01 Dec '19

01 Dec '19

I had a working proxy setup added sieve to it, and out of the blue I get this Error: proxy: Remote returned invalid banner: 220 No idea what to do, nothing even in the mail list archive

2 3

dovecot: auth: Error: DNS lookup for xxx failed: Name does not resolve
by Marc Roos 01 Dec '19

01 Dec '19

I had a working container with dovecot configured as proxy. And all of a sudden I am getting these messages 'dovecot: auth: Error: DNS lookup for roosit03 failed: Name does not resolve' Pinging/nslookup these hostnames is ok

2 3