January 2019 - dovecot

SELinux policy to allow Dovecot to connect to Mysql
by Robert Moskowitz 05 Feb '19

05 Feb '19

As I have noted in previous messages, I been getting the following on my new mailserver: Apr 7 10:17:27 z9m9z dovecot: dict: Error: mysql(localhost): Connect failed to database (postfix): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (13) - waiting for 25 seconds before retry They go away when I setenforce 0. It is not a timing issue as I earlier thought. So I googled dovecot mysql selinux and the only worthwhile hit was: http://zszsit.blogspot.com/2012/12/dovecot-mysql-selinux-issue-on-centos6.h… that provides a /etc/selinux/dovecot2mysql.te and other selinux stuff. Is there a simpler way like a setsbool option? With all the howtos on dovecot with mysql, it is interesting that none of them seem to have this problem. Maybe because they connect to mysql through TCP port 3306 which has ITS set of problems (like MariaDB defaults to not listening on TCP). thanks!

1 3

Error: User bob@aaa.bbb doesn't have home dir set, disabling duplicate database
by subscription1 02 Feb '19

02 Feb '19

I made a mistake when I moved dovecot to a new server and only specified mail_location instead of mail_home All I have in 10-mail.conf is --------- mail_location = maildir:/home/vmail/mailboxes/%d/%n ------------ All emails for the few accounts I have are in these mailboxes and I can get/see them via my mail client I do, however, get the following error -------------------- imap(bob(a)aaa.bbb): Error: User bob(a)aaa.bbb doesn't have home dir set, disabling duplicate database ------------------- After looking at https://wiki2.dovecot.org/VirtualUsers/Home I tried the following -------------------------------- mail_home = /home/vmail/mailboxes/%d/%n mail_location = maildir:~/mail ------------------------------ Problem with this is that I now can't see any of my emails in the client. Appreciate any help on how to fix this. Thanks

4 8

auth: Error - Request timed out
by Hajo Locke 01 Feb '19

01 Feb '19

Hello List, i use dovecot 2.2.22 and have the same problem described here: https://dovecot.org/pipermail/dovecot/2017-November/110020.html I can confirm that sometimes there is a problem with connection to mysql-db, but sometimes not. Reasons for failing are still under investigation by my mates. My current main problem is, that this fail seems to be a one way ticket for dovecot. Even if mysql is verifyable working again and waiting for connection dovecot stucks furthermore with errors like this: May 29 07:00:49 hostname dovecot: auth: Error: plain(mail(a)example.com,xxx.xxx.xx.xxx,<HGI4FVFt2Oy80j3P>): Request 999.7 timed out after 150 secs, state=1 When restarting dovecot all is immediately working again. Is there a way to tell dovecot to restart auth services or reinitialize mysql-connection after these hard fails? I could insert "idle_kill = 1 mins" into service auth and service auth-worker, but i dont know if this would work. Unfortunately i am not able to reproduce this error and there are always a couple of days between errors. Thanks, Hajo

4 6

Dovecot and FTS experiment
by Tomasz Nowak 30 Jan '19

30 Jan '19

Hello, I'm trying to experiment with Dovecot and Solr server. I have >30k email addresses that I want to index to speed up searching and save IOPS on mail servers. For now - I'm doing some experiments and I'm testing how it is working. I'm thinking about adding one additional server with Solr and configure all mail servers to use that server. I have some questions. 1. I have 15 mail servers. It will be good If I add new server with Solr and use it on all Dovecot servers? Or maybe I should install Solr on all mail servers? 2. I notice - I have mail account with 3GB of mail. Index files in mail dir has 5MB. After indexing mailbox in Solr - index files has 15MB. What changes in those files? FTS indexing adds something to that files - but what? 3. If I need to disconnect Dovecot from Solr server - simply Can I remove plugin configuration from dovecot.conf and everything would be working? Or maybe - I need to remove index files and recreate it? It is important for me because if some day I would decide to disconnect FTS server - I would have to recreate indexes for >30k mailboxes.. 4. What if some day I want to change Solr server to new server with empty Solr database? I can simply reindex mailboxes? Or I need to do something more? Thanks!

3 4

Re: "unknown user - trying the next userdb" Info in log
by Aki Tuomi 30 Jan '19

30 Jan '19

3 3

v2.3.4 released
by Timo Sirainen 30 Jan '19

30 Jan '19

https://dovecot.org/releases/2.3/dovecot-2.3.4.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.4.tar.gz.sig Binary packages in https://repo.dovecot.org/ * The default postmaster_address is now "postmaster@<user domain or server hostname>". If username contains the @domain part, that's used. If not, then the server's hostname is used. * "doveadm stats dump" now returns two decimals for the "avg" field. + Added push notification driver that uses a Lua script + Added new SQL, DNS and connection events. See https://wiki2.dovecot.org/Events + Added "doveadm mailbox cache purge" command. + Added events API support for Lua scripts + doveadm force-resync -f parameter performs "index fsck" while opening the index. This may be useful to fix some types of broken index files. This may become the default behavior in a later version. - director: Kicking a user crashes if login process is very slow - pop3_no_flag_updates=no: Don't expunge DELEted and RETRed messages unless QUIT is sent. - auth: Fix crypt() segfault with glibc-2.28+ - imap: Running UID FILTER script with errors assert-crashes - dsync, pop3-migration: POP3 UIDLs weren't added to dovecot.index.cache while mails were saved. - dict clients may have been using 100% CPU while waiting for dict server to finish commands. - doveadm user: Fixed user listing via HTTP API - All levels of Cassandra log messages were logged as Dovecot errors. - http/smtp client may have crashed after SSL handshake - Lua auth converted strings that looked like numbers into numbers.

18 145

"unknown user - trying the next userdb" Info in log
by James Brown 30 Jan '19

30 Jan '19

I’ve set up a new mail server. Auth-worker is giving me this error all the time: auth-worker(11160): Info: passwd(sales(a)bordo.com.au <mailto:sales@bordo.com.au>,10.0.0.54,<YSFoAYHAGoLAqAEo>): unknown user - trying the next userdb Next line is from imap-login with successful login. Using MySQL as user database. Auth-sql.comf.ext is: passdb { driver = sql # Path for SQL configuration file, see example-config/dovecot-sql.conf.ext args = /usr/local/etc/dovecot/dovecot-sql.conf.ext } # "prefetch" user database means that the passdb already provided the # needed information and there's no need to do a separate userdb lookup. # <doc/wiki/UserDatabase.Prefetch.txt> userdb { driver = prefetch } userdb { driver = sql args = /usr/local/etc/dovecot/dovecot-sql.conf.ext } # If you don't have any user-specific settings, you can avoid the user_query # by using userdb static instead of userdb sql, for example: # <doc/wiki/UserDatabase.Static.txt> #userdb { #driver = static #args = uid=vmail gid=vmail home=/var/vmail/%u #} Any ideas why it is gives me this error before logging in? Where should I look? Thanks, James.

3 5

send and receive error message
by Chandran Manikandan 29 Jan '19

29 Jan '19

Hi Folks, I am running qmailtoaster on COS6 32 bit. Send and receive error message coming frequently and inbox emails are not downloading in outlook 2016 of office 365 email client. But if i restart the dovecot service then start downloading the emails in inbox then send and receive error message gone. Outlook 2010 doesn't have the same issue. Is this server issue? or email client version issues? or if i need to use standalone outlook product instead office 365? I do the dovecot service restart every one hour for this issue . if possible to do the cron job for dovecot service restart for every one hour daily or any other solution there. Kindly Any one help me. -- *Thanks,* *Manikandan.C* *System Administrator*

1 0

Re: Rsync to backup dbox with SIS (Daniel Miller)
by ash-dovecot＠comtek.co.uk 28 Jan '19

28 Jan '19

> Probably not the answer you want - but I would strongly suggest using > Dovecot replication.? Dovecot replication Just Works - so don't reinvent > the wheel when Timo provided such a polished tool already.? Okay, thanks, I'll look at replication for the warm spare. Although we do use shared folders, which your link below says don't work properly. > And based on > my previous SIS experience - while dbox is nice I would suggest avoiding > SIS until there are reports of more development.? Sdbox will be solid - > which is what you want for an archive - though maildir would be the > safest.? Archives don't need to be rapid-access - they need to be > dependable.? SIS is wonderful for space saving - but until there's more > safety checks built-in I'd suggest avoiding it for production backups.? > Drives are cheap - lost data, lost time, lost hair, lost sanity...is not. Our main motivation for dbox is SIS. We don't have a very high volume of mail, so maildir speed is unlikely to be an issue. What we do have is a lot of users who like to mail around large files. Drives are cheap, but there are advantages to a smaller mailstore. That said, data security wins. We will probably abandon dbox entirely and continue with maildir, thanks. > The backups don't have to be "visible" to other machines - don't even > have to be running IMAP/POP services (I think).? And the replication > command is run - via ssh (https://wiki.dovecot.org/Replication) - so > what's the problem? Well, our backup servers are supposed to be running a minimalist set of software. If we need to restore from backup after a security issue or application bug on a production machine, then we are trying to minimise the chance that the backup machine itself could be affected. Anyway, if we aren't using SIS, then we needn't use dbox, and therefore backup machines can continue to run a minimalist OS with only rsync. Thanks, Ash --- To opt-in to receiving communications from us or to update your email preferences please go to https://lists.comtek.co.uk/prefs. To be removed from receiving all communications from the Comtek Group, please unsubscribe at https://lists.comtek.co.uk/prefs and accept our apologies for any inconvenience caused. The Comtek Group respects your privacy. Please find our privacy policy at http://www.comtek.co.uk/privacy-policy This email and any attachments are confidential. If you are not the named recipient, please notify the sender immediately. The unauthorised use, disclosure, copying or alteration of this message or its attachments is strictly prohibited. Opinions expressed in this message are those of the individual and not Comtek Network Systems (UK) Ltd unless indicated by an authorised representative independent of this message. Comtek Network Systems does not accept responsibility for any changes to this message after it has been sent. Company Details: Comtek Network Systems (UK) Ltd. Registered Office: Comtek Network Systems (UK) Ltd, Unit 108, Tenth Avenue (Zone 3), Deeside Industrial Park, Deeside, Flintshire, CH5 2UA. Comtek Network Systems (UK) Ltd is a company registered in England and Wales with company number 05929974.

1 0

all of a sudden, slow resync
by Victor Sudakov 27 Jan '19

27 Jan '19

Dear Colleagues, All of a sudden, I've begun receiving this output when reindexing my mail boxes: # /usr/local/bin/doveadm force-resync -u vas "*" doveadm(vas): Warning: Transaction log file /home/vas/Mail/sibptus/.imap/sent/dovecot.index.log was locked for 55 seconds (Mailbox was synchronized) doveadm(vas): Warning: Transaction log file /home/vas/Mail/sibptus/.imap/dss-30-06-2010/dovecot.index.log was locked for 56 seconds (Mailbox was synchronized) doveadm(vas): Warning: Transaction log file /home/vas/Mail/sibptus/.imap/dss-2014/dovecot.index.log was locked for 95 seconds (Mailbox was synchronized) doveadm(vas): Warning: Transaction log file /home/vas/Mail/sibptus/.imap/dss-20-06-2012/dovecot.index.log was locked for 72 seconds (Mailbox was synchronized) doveadm(vas): Warning: Transaction log file /home/vas/Mail/sibptus/.imap/dss-18-05-2009/dovecot.index.log was locked for 31 seconds (Mailbox was synchronized) doveadm(vas): Warning: Transaction log file /home/vas/Mail/sibptus/.imap/dss-07-12-2008/dovecot.index.log was locked for 56 seconds (Mailbox was synchronized) doveadm(vas): Warning: Transaction log file /home/vas/Mail/sibptus/.imap/dns-operations/dovecot.index.log was locked for 95 seconds (Mailbox was synchronized) And it really takes forever to finish. What could cause this? FreeBSD 11.2-RELEASE-p8, dovecot-2.3.3_4 -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/

1 0