- dovecot - dovecot.org

Solr: URI Too Long
by azurit＠pobox.sk 29 Nov '18

29 Nov '18

Hi, i'm quite often getting this error: Error: fts_solr: Lookup failed: 414 URI Too Long Most web servers are limiting URI length to 8192 characters. Why not to use POST instead of GET when communicating with Solr? Solr is able to handle this ok, also see: https://dzone.com/articles/solr-select-query-get-vs-post azur

1 0

determine why mail clients download mails 2nd time
by Poliman - Serwis 29 Nov '18

29 Nov '18

I have strange problem. In last Friday I had a problem with dovecot. It didn't see directories with mailboxes in /var/vmail. Somehow it crashed because probably two things (a lot of this type of lines in mail.err file): *Nov 23 07:05:02 s1 dovecot: lda(poli(a)poli.li <poli(a)poli.li>): Error: User initialization failed: Initializing mail storage from mail_location setting failed: mkdir(/var/vmail/poli.li/poli/Maildir <http://poli.li/poli/Maildir>) failed: Permission denied (euid=5000(vmail) egid=5000(vmail) missing +w perm: /var/vmail, dir owned by 0:0 mode=0755)* and maybe *Nov 12 09:27:59 s1 dovecot: imap(artur(a)firmastanaszek.pl <artur(a)firmastanaszek.pl>): Error: Corrupted index cache file /var/vmail/firmastanaszek.pl/artur/Maildir/dovecot.index.cache <http://firmastanaszek.pl/artur/Maildir/dovecot.index.cache>: Broken MIME parts for mail UID 559 in mailbox INBOX: Cached MIME parts don't match message during parsing: Cached header size mismatch (parts=)Nov 12 09:27:59 s1 dovecot: imap(artur(a)firmastanaszek.pl <artur(a)firmastanaszek.pl>): Error: unlink(/var/vmail/firmastanaszek.pl/artur/Maildir/dovecot.index.cache <http://firmastanaszek.pl/artur/Maildir/dovecot.index.cache>) failed: No such file or directory (in mail-cache.c:28)* and after this event probably all mailboxes download again all emails from 1.11 to 22.11. They were duplicated in mail clients. -- *Pozdrawiam / Best Regards* *Piotr Bracha*

2 3

Bug in logging in debug mode
by Xavier 29 Nov '18

29 Nov '18

Hello, This is dovecot 2.3.4 (0ecbaf23d) If you set "mail_debug = yes" in 10.logging.conf, there's a bug in logging, which breaks log parsers : > 2018-11-29 00Debug: :41:57 lda(xavier): Effective uid=501, gid=20, home=/home/xavier ^^^^ Regards, Xavier -- Xavier Humbert - sysadmin & network engineer

1 0

(no subject)
by Root Kev 27 Nov '18

27 Nov '18

Dovecot Version: 2.3.2.1 Hello Mailing List, We are having a random issue in a couple of our production servers, where one of the child processes randomly dies with an out of memory error (see below): Nov 26 11:58:17 config: Fatal: pool_system_malloc(8192): Out of memory Nov 26 11:58:17 pop3-login: Fatal: Error reading configuration: read(/var/run/dovecot/config) failed: EOF Nov 26 11:58:17 config: Fatal: master: service(config): child 29696 returned error 83 (Out of memory (service config { vsz_limit=2048 MB }, you may need to increase it) - set CORE_OUTOFMEM=1 environment to get core dump) We only use dovecot for internal application POP3 mail access from a mailbox, and there is under 10 connecting applications. Have have gradually increased the vsz_limit from the default of 256mb up to 2GB now. Is there anything else that should/could be changed instead of continuing to through memory at it? # dovecot -n # 2.3.2.1 (0719df592): /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-862.11.6.el7.x86_64 x86_64 CentOS Linux release 7.5.1804 (Core) # Hostname: <Internal host name here, removed> doveconf: Warning: please set ssl_dh=</etc/dovecot/dh.pem doveconf: Warning: You can generate it with: dd if=/var/lib/dovecot/ssl-parameters.dat bs=1 skip=88 | openssl dhparam -inform der > /etc/dovecot/dh.pem auth_cache_size = 10 M auth_verbose = yes base_dir = /var/run/dovecot/ default_vsz_limit = 2 G instance_name = EMX Pop Mailstore listen = <Internal ethernet Name Here, removed> log_path = /var/log/dovecot-echo.log login_greeting = Pop3 MailServer Ready. login_trusted_networks = <IP Addresses Here, removed> 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 = } passdb { args = cache_key=%u driver = pam } protocols = pop3 ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = passwd } verbose_ssl = yes Thanks, Kevin

1 0

Ubuntu 18.04 (Bionic) packages now available
by Aki Tuomi 26 Nov '18

26 Nov '18

Hi! We are excited to announce that we are now providing packages for Ubuntu 18.04 (Bionic). Please find instructions on how to use them at https://repo.dovecot.org/ Aki Tuomi Open-Xchange Oy

6 6

Limit IMAP/IMAPS listening IPs
by Dudi Goldenberg 26 Nov '18

26 Nov '18

Hello list. I am running dovecot v2.2.13 on debian 8.8; I tried to add a "address =" statement for only localhost and one private IP, but then I got a complaint from system: dovecot[20515]: Error: systemd listens on port 143, but it's not configured in Dovecot. Closing. What is the proper way to resolve this? TIA & Regards, Dudi

9 23

LDAP login fails after LDAP server restart
by Dag Nygren 25 Nov '18

25 Nov '18

Hi! Just udated my Fedora dovecot to version 2.2.36 and found that after the update dovecot will fail all LDAP logins after slapd has been restarted during the logrotate. Restarting dovecot fixes the problem. Is there a bug preventing dovecot to reopen the LDAP session when it fails? Best Dag

2 2

Installing on Mojave, with Homebrew and mysql
by James Brown 25 Nov '18

25 Nov '18

I’m using Homebrew to install Dovecot on Mojave, but have to modify the formula to add ‘--with-mysql’. Unfortunately compiling always fails with: checking for mysql_config... NO checking for mysql_init in -lmysqlclient... no configure: error: Can't build with MySQL support: libmysqlclient not found I added: ENV['LD']="-L/usr/local/opt/mysql(a)5.7/lib" to the ‘def install’ section of the formula, but it still fails. config.log shows: … KRB5_LIBS='' LD='-L/usr/local/opt/mysql(a)5.7/lib/' LDAP_LIBS=‘' … And mysqlclient is here: $ locate mysqlclient /usr/local/Cellar/mysql(a)5.7/5.7.24/lib/libmysqlclient.20.dylib /usr/local/Cellar/mysql(a)5.7/5.7.24/lib/libmysqlclient.a /usr/local/Cellar/mysql(a)5.7/5.7.24/lib/libmysqlclient.dylib /usr/local/Cellar/mysql(a)5.7/5.7.24/lib/pkgconfig/mysqlclient.pc I changed the formula to: ENV['LD']="-L/usr/local/Cellar/mysql(a)5.7/5.7.xn--24/lib/-236c And still get the same thing. Any suggestions? Thanks, James.

1 0

Mac Mojave Server
by David Morsberger 24 Nov '18

24 Nov '18

Is there any information on using dovecot on Mojave? I have been using Mac OS Server for a few years and looking for the preferred way to move to Mojave since dovecot and postfix admin support has been dropped by Apple.

2 1

Testing validity of Dovecot config in a script
by Ralph Seichter 24 Nov '18

24 Nov '18

While trying to determine a given configuration is valid from within a script, I found that the following works with Dovecot version 2.3.2.1: #!/usr/bin/env bash doveconf -n >/dev/null || echo "Config is invalid" However, the return code is not documented in the doveconf manual page, and I wonder if the observed behaviour can be relied on? Is this the recommended method to test configuration validity? Personally, I'd like to have a dedicated call available. Something like # Proposal: "-t" for "test config" doveconf -t [-c config-file] with documented return codes would be ideal. -Ralph

2 2