Do we really need Solr commit as cronjob?

I am testing Solr FTS on dovecot. Read online that some suggested to run cronjob commit every minute, and optimize once a day. I am using Solr 7.1.0 and I see some configurations: In /etc/default/solr.in.sh: #SOLR_OPTS="$SOLR_OPTS -Dsolr.autoSoftCommit.maxTime=3000" #SOLR_OPTS="$SOLR_OPTS

Re: iPhone/iPad IMAP connection bursts causes user+IP exceeded

Update: I have modified mail_max_userip_connections to 400 which made no difference. The end user customer actually had Apple remote into their device and they were impressed that the end user knew their IMAP settings. They tested it and during this connection time, it worked as expected with

Re: My Solr FTS problem

Thanks a lot for the help. You are right about the JSON as the default in solr v7.1.0. I now switched it back to XML and now it works. # doveadm -v index -u fail2...@mydomain.com Inbox doveadm(fail2...@mydomain.com): Info: INBOX: Caching mails seq=1..388 388/388 Gao On 2017-11-30 02:00 PM,

My Solr FTS problem

I am testing the solr FTS following the guide here: http://things.m31.ch/?p=379 Now I am having problem when I try to test: # doveadm -v  index -u fail2...@mydomain.com Inbox doveadm(fail2...@mydomain.com): Error: fts_solr: Invalid XML input at 1:0: not well-formed (invalid token) (near: {  

Re: Unable to build sieve plugin

Am 30. November 2017 18:20:58 MEZ schrieb Mark Foley : >I'm wanting to experiment with sieve processing for the first time. >Having some trouble getting >started. I googled to page, https://wiki2.dovecot.org/Pigeonhole/Sieve, >went to the "Download >and Installation" link, then

Unable to build sieve plugin

I'm wanting to experiment with sieve processing for the first time. Having some trouble getting started. I googled to page, https://wiki2.dovecot.org/Pigeonhole/Sieve, went to the "Download and Installation" link, then the "Pigeonhole download page" link and downloaded

Re: Sieve can't move messages in a public namespace

Hello all, finally I upgraded to dovecot 2.2.10 (that comes with CentOS 7.4). But the problem is still there! Why sieve can't move a message in a public namespace complaining about "Mailbox does not exists"? None of you ever try? Some of you have a working setup? I attach "dovecot -n" output.

Re: Username character disallowed by auth_username_chars: 0x13

Hi, On Wed, Nov 29, 2017 at 12:18 AM, Aki Tuomi wrote: > >> On November 29, 2017 at 5:58 AM Alex wrote: >> >> >> Hi, I'm receiving the following messages in my mail logs that I >> haven't seen before: >> >> Nov 28 22:45:31 bwipropemail dovecot:

Re: Detect port number of SASL AUTH request?

Op 16-11-2017 om 2:07 schreef MRob: Hi, this is partly Postfix related, but I want to know if there could be way to distinguish port of the SASL AUTH request to segregate user services. Currently I use unix listener for dovecot sasl auth, but could change to inet_listener. Only way I can

Re: Plugin 'sieve_imapsieve' not found

Thank you very much, the solution was so simple. Am 30.11.2017 um 14:32 schrieb Felix Zielcke: Am Donnerstag, den 30.11.2017, 13:47 +0100 schrieb Christopher Satchell: Hello, when Dovecot launches (and pretty much at any action afterwards) it always throws following error: managesieve:

Re: Dovecot lmtp doesn't log

Op 25-11-2017 om 13:00 schreef Tomislav Perisic: Does anyone have any idea regarding this? On 17 Nov 2017 11:36, "Tomislav Perisic" wrote: Hi, We have 2 servers, server A and server B. Server A has: Postfix dovecot-2.2.33.2-1.el6.x86_64 Server B has:

Re: Plugin 'sieve_imapsieve' not found

Am Donnerstag, den 30.11.2017, 13:47 +0100 schrieb Christopher Satchell: > Hello, > > when Dovecot launches (and pretty much at any action afterwards) it > always throws following error: > > > managesieve: Fatal: Plugin 'sieve_imapsieve' not found from > > directory > >

Re: Plugin 'sieve_imapsieve' not found

Op 30-11-2017 om 13:47 schreef Christopher Satchell: Hello, when Dovecot launches (and pretty much at any action afterwards) it always throws following error: | managesieve: Fatal: Plugin 'sieve_imapsieve' not found from directory /usr/lib/dovecot/modules/sieve | config: Error:

Re: Autoreplies are not sent

El 30 nov. 2017 4:02 a.m., "Steffen Kaiser" escribió: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 29 Nov 2017, Sergio Belkin wrote: Now, I'd want to every mail was sent to support-...@example.com it triggers > an autoreply vacation style. > > So, I've wrote

Re: dovecot - 2 Faktor Auth

On 30.11.2017 12:33, Hajo Locke wrote: > Hallo Liste, > > hat sich schon mal jemand mit 2 Faktor Auth für dovecot beschäftigt? > Es geht dabei nicht nur um die Absicherung einer Weboberfläche sondern > direkt die Absicherung der Standard pop/imap Verbindungen des Clients. > Wir machen das auth

dovecot - 2 Faktor Auth

Hallo Liste, hat sich schon mal jemand mit 2 Faktor Auth für dovecot beschäftigt? Es geht dabei nicht nur um die Absicherung einer Weboberfläche sondern direkt die Absicherung der Standard pop/imap Verbindungen des Clients. Wir machen das auth bisher über MySQL.  Rein technisch würde das

Re: ManageSieve: authenticate "EXTERNAL" not behaving correctly

Stephan Bosch wrote: Op 28-10-2017 om 17:18 schreef Stephan Bosch: Op 10/26/2017 om 1:32 PM schreef Marc Weustink: ... Will get back on this later. This was actually a Dovecot problem. Merged yesterday: https://github.com/dovecot/core/commit/451698c60d7b3a763742c8e99503ab30596036f0