- dovecot - dovecot.org

dovecot only partially indexing ... fts
by Infoomatic 14 Jun '15

14 Jun '15

hi, I have a setup using solr as fts, however it seems that when I move messages it does not automatically index the stuff. Also, when using sieve scripts to store messages in different folders I get: dovecot: indexer-worker(user): Indexed 0 messages in testfolder If I get a mail to normal INBOX I get dovecot: indexer-worker(user): Indexed 1 messages in INBOX doveadm index -u user '*' does the trick, however, I have set "fts_autoindex = yes" ... the relevant part of doveconf -n: mail_plugins = fts fts_solr zlib acl quota zlib fts fts_solr acl plugin { fts = solr fts_autoindex = yes fts_solr = url=http://localhost:8983/solr/ break-imap-search sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +notify +imapflags } protocol lda { mail_plugins = fts fts_solr zlib sieve acl } protocol imap { mail_plugins = fts fts_solr zlib acl quota imap_acl imap_quota } is this normal behaviour or did I screw something up? TIA, infoomatic

1 0

fts_solr Bad Request / BUG: Unknown internal error
by Nick Rosier 14 Jun '15

14 Jun '15

Hi, yesterday I created a new mailbox; ever since (and only for the new mailbox) I am getting these errors: 2015-06-12T00:00:29.808526+02:00 mail dovecot: indexer-worker(xxx(a)example.com): Error: fts_solr: Lookup failed: Bad Request 2015-06-12T00:00:29.808560+02:00 mail dovecot: indexer-worker(xxx(a)example.com): Error: Mailbox INBOX: Status lookup failed: BUG: Unknown internal error Is this a known issue? Rgds, N.

2 2

RE: Testin new installation
by edgar 13 Jun '15

13 Jun '15

Look at /etc/hosts ::1 is the ipv6 version of localhost. Sent from Samsung tablet -------- Original message -------- From Steve Matzura <number6(a)noisynotes.com> Date: 06/13/2015 6:00 AM (GMT-06:00) To dovecot <dovecot(a)dovecot.org> Subject Testin new installation The first place I went to for test advice and planning recommendations was http://wiki2.dovecot.org/TestInstallation - The very first test failed. Doc says: Next check that Dovecot is listening for connections: # telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN] Dovecot ready. If you got "connection refused", make sure that Dovecot is configured to serve the imap protocol and listening on the expected interfaces/addresses. The simplest way to do that would be using doveconf(1): # doveconf protocols listen protocols = imap pop3 lmtp sieve listen = *, :: If the protocols setting shouldn't contain imap so add it. Also make sure, that relevant !include or !try_include configuration lines are not commented. *** End doc extract *** All of the above specified settings are correct. Yet, when I telnet localhost 143, I get: Trying ::1... # this is certainly suspect Escape character is '^['. Connection closed by foreign host.

3 3

postfix/dovecot on debian jessie (url config at OVH)
by klrumpf 13 Jun '15

13 Jun '15

Hi list, could use some help with a pasword issue or ovh dns zone problem, dovecot newbie I have gone thru setting up a mailserver using the below http://www.binarytides.com/install-postfix-dovecot-debian/ when I try to set up an account from my laptop (iceweasel/t-bird) I get password problems. mail.log says Jun 13 18:36:04 www postfix/smtpd[701]: connect from unknown[xx.xx.214.75] Jun 13 18:36:04 www postfix/smtpd[688]: disconnect from unknown[xx.xx.214.75] Jun 13 18:36:04 www postfix/submission/smtpd[687]: disconnect from unknown[xx.xx.214.75] Jun 13 18:36:04 www postfix/submission/smtpd[694]: disconnect from unknown[xx.xx.214.75] Jun 13 18:36:04 www postfix/smtpd[693]: disconnect from unknown[xx.xx.214.75] Jun 13 18:36:04 www postfix/submission/smtpd[698]: disconnect from unknown[.... nstat also looks ok BWE1# netstat -lntp Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.1:12301 0.0.0.0:* LISTEN 492/opendkim tcp 0 0 0.0.0.0:110 0.0.0.0:* LISTEN 504/dovecot tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN 504/dovecot tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 486/nginx -g daemon tcp 0 0 0.0.0.0:465 0.0.0.0:* LISTEN 617/master tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 449/sshd tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 617/master tcp 0 0 127.0.0.1:4000 0.0.0.0:* LISTEN 653/ssh tcp 0 0 0.0.0.0:993 0.0.0.0:* LISTEN 504/dovecot tcp 0 0 0.0.0.0:995 0.0.0.0:* LISTEN 504/dovecot tcp 0 0 0.0.0.0:587 0.0.0.0:* LISTEN 617/master tcp 0 0 127.0.0.1:6379 0.0.0.0:* LISTEN 455/redis-server 12 tcp6 0 0 :::110 :::* LISTEN 504/dovecot tcp6 0 0 :::143 :::* LISTEN 504/dovecot tcp6 0 0 :::80 :::* LISTEN 486/nginx -g daemon tcp6 0 0 :::465 :::* LISTEN 617/master tcp6 0 0 :::21 :::* LISTEN 485/vsftpd tcp6 0 0 :::22 :::* LISTEN 449/sshd tcp6 0 0 :::25 :::* LISTEN 617/master tcp6 0 0 ::1:4000 :::* LISTEN 653/ssh tcp6 0 0 :::993 :::* LISTEN 504/dovecot tcp6 0 0 :::995 :::* LISTEN 504/dovecot tcp6 0 0 :::587 :::* LISTEN 617/master maybe someone has done it before, thanks <http://de.linkedin.com/in/klrumpf>

1 0

LDA versus LMTP
by Steve Matzura 13 Jun '15

13 Jun '15

My system has a great big four users. The Dovecot wiki says LMTP is more efficient, and someone on IRC told me I'd need it if I were ever to use sieve, which at this time I have no intention of doing. Should I stick with LDA, or just implement LMTP so I'm ready if ever I need it in the future? The bottom line is, it's unclear from the wiki how to explicitly specify use of one or the other, so that's my question.

5 7

Non-Existent Log File
by Steve Matzura 13 Jun '15

13 Jun '15

My /var/log/maillog was getting pretty big because of lots of testing and re-configuring I've been doing lately with both Dovecot and Postfix. I figured just remove /var/log/maillog and it would be re-created. It wasn't--not by Dovecot, not by Postfix. I had to manually create a new one, put one character in it, save it, properly secure it with chmod, and then Dovecot (and postfix) messages got written to it. This can't possibly be the proper procedure to clear maillog messages ... can it?

3 3

Error when starting Dovecot
by Steve Matzura 13 Jun '15

13 Jun '15

After applying some changes to 10-master.conf as detailed at http://wiki2.dovecot.org/HowTo/PostfixDovecotLMTP I receive the following when trying to start: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-master.conf line 49: Expecting '{' I'm trying to enable LMTP. The instructions say: Socket configuration The actual socket is configured in /etc/dovecot/conf.d/10-master.conf. The LMTP service can be bound to both INET or Unix sockets. In this example a Unix socket is placed inside the Postfix spool with appropriate permissions set: service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } I copied this block and placed it in my copy of 10-master.conf. Line 49 is the first line of this block, and there's clearly a left-brace there. The braces match, too. Thoughts?

2 3

Orphaned email boxes...
by SH Development 13 Jun '15

13 Jun '15

What is the correct way to delete mailboxes that no longer have a database entry? Jeff

2 3

Imap Notify
by Tony Morehen 12 Jun '15

12 Jun '15

I'm trying to enable Imap Notify in Dovecot 2.2.13. I know that's a bit out of date, but that's what's provided with openSuSe 13.2. The first thing I did was add mailbox_list_index=yes to /etc/dovecot/dovecot.conf. Both doveadm -n and dovecot -n show the change. I then used doveadm reload to force dovecot to reread its config file. Despite this, NOTIFY did not show up it Dovecot's capabilities: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN] Dovecot ready. I then did a systemctl restart dovecot.service and still no luck: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN] Dovecot ready. I also have noticed that the Maildirs of my various accounts include a dovecot.list.index file with a current timestamp, but no dovecot.list.index. So, where do I go for here? The output of doveadm -n: # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.7-21-desktop x86_64 openSUSE 13.2 (x86_64) disable_plaintext_auth = no log_path = /var/log/dovecot/dovecot.log mail_location = maildir:~/Maildir mail_max_userip_connections = 50 mailbox_list_index = yes 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 passdb { args = /etc/dovecot/passwd.dovecot driver = passwd-file } postmaster_address = Tony@localhost protocols = imap lmtp service auth { unix_listener auth-master { group = mailgrp mode = 0660 user = mailuser } } service lmtp { executable = lmtp -L inet_listener lmtp { address = 127.0.0.1 port = 2525 } user = mailuser } ssl = no userdb { args = /etc/dovecot/passwd.dovecot driver = passwd-file } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep } protocol pop3 { mail_plugin_dir = /usr/lib/dovecot/modules/pop3 } protocol lda { log_path = /var/log/dovecot/deliver.log mail_plugin_dir = /usr/lib64/dovecot/modules mail_plugins = sieve } protocol lmtp { log_path = /var/log/dovecot/deliver.log mail_plugin_dir = /usr/lib64/dovecot/modules mail_plugins = sieve }

2 2

1.0.15 gone, can't start version 2
by Steve Matzura 12 Jun '15

12 Jun '15

On advice/recommendation received on this list, I removed version 1.0.15 with: rm -rf /usr/local/dovecot However, now that I have version 2 properly installed, configured, and ready to start testing with Postfix, it appears the old version is still in /usr/local/sbin, /usr/local/include, /usr/local/libexec, /usr/local/lib and /usr/local/shared/doc. Thinking that anything in /usr/local is something that was installed s a result of having built it from source (which 1.0.15 definitely was), should these also be removed?

3 7