Re: Migrating maildirs - Courier to Dovecot

[Stroller]

> On 22 Sep 2017, at 00:15, Adi Pircalabu  wrote:
> 
> Using rsync should be fine, I've done it myself recently several times. What 
> you need to consider:
> 1. The downtime required during the final incremental transfer.
> 2. If you're using the same uid/gid on the destination server make sure you 
> preserve them when transferring the data across.
> 3. To avoid duplicate messages in the destination you *must* use --delete 
> rsync switch for the incremental transfers.
> 
> Important: I'm assuming you're using virtual mailboxes under the same uid/gid.
> 
> Suggested mandatory steps, ymmv:
> 1. Configure Dovecot in the destination to use Maildir and test everything: 
> logging, SSL, authentication, mail delivery and so on. If you have 
> Courier-IMAP specific configuration, e.g. folders that are being 
> automatically created/subscribed upon the first login, replicate it and test 
> it on the Dovecot server as well.
> 2. Do the initial data transfer using "-avz --numeric-ids" and see if you're 
> happy with the result in the destination.
> 3. Run several incrementals adding "--delete" switch, followed by 
> courier-dovecot-migrate.pl *executed as the mail user* to get a ballpark 
> figure for the estimated outage window.
> 4. Test few mailboxes post-migration and compare the results with the source 
> server.
> 5. On Day D, stop Courier-IMAP and Dovecot services on both servers to 
> prevent any mailbox changes and run the last incremental, sanity checks, IP 
> reconfiguration if Dovecot is the drop-in replacement, start Dovecot, another 
> round of sanity checks, check the logs and so on. Here you're already at the 
> point of no return :)

This is all more or less as I hoped or planned it, although you have mentioned 
some details that I will now be sure not to overlook.

Many thanks.

Stroller.

Re: Migrating maildirs - Courier to Dovecot

[Adi Pircalabu]

On 22-09-2017 4:34, Stroller wrote:
[...]


I think my main question is whether there's any reason I shouldn't
just rsync the maildirs across from the old mail server to the new
one?

There aren't many clients using this server, so I don't care if
clients have to redownload all their messages (in fact, I expect
they'll probably end up doing so anyway).

I'd like to preserve read/unread status of each message, but can't
think of anything else important.

[...]

Using rsync should be fine, I've done it myself recently several times. 
What you need to consider:

1. The downtime required during the final incremental transfer.
2. If you're using the same uid/gid on the destination server make sure 
you preserve them when transferring the data across.
3. To avoid duplicate messages in the destination you *must* use 
--delete rsync switch for the incremental transfers.


Important: I'm assuming you're using virtual mailboxes under the same 
uid/gid.


Suggested mandatory steps, ymmv:
1. Configure Dovecot in the destination to use Maildir and test 
everything: logging, SSL, authentication, mail delivery and so on. If 
you have Courier-IMAP specific configuration, e.g. folders that are 
being automatically created/subscribed upon the first login, replicate 
it and test it on the Dovecot server as well.
2. Do the initial data transfer using "-avz --numeric-ids" and see if 
you're happy with the result in the destination.
3. Run several incrementals adding "--delete" switch, followed by 
courier-dovecot-migrate.pl *executed as the mail user* to get a ballpark 
figure for the estimated outage window.
4. Test few mailboxes post-migration and compare the results with the 
source server.
5. On Day D, stop Courier-IMAP and Dovecot services on both servers to 
prevent any mailbox changes and run the last incremental, sanity checks, 
IP reconfiguration if Dovecot is the drop-in replacement, start Dovecot, 
another round of sanity checks, check the logs and so on. Here you're 
already at the point of no return :)


---
Adi Pircalabu

Re: Migrating maildirs - Courier to Dovecot

[Ervin Hegedüs]

Hi,

On Thu, Sep 21, 2017 at 07:34:47PM +0100, Stroller wrote:
> I apologise, because I'm sure this subject has been done to death, but I want 
> to migrate from Courier to Dovecot.

currently, I'm working on the same project here,

> I think my main question is whether there's any reason I shouldn't just rsync 
> the maildirs across from the old mail server to the new one? 

probably that's not enough, to make a complete and clean
migration, you'll be happy with the courier-dovecot-migrate.pl
script:

http://www.dovecot.org/tools/courier-dovecot-migrate.pl

That converts all structure in-place from Courier to Dovecot.
 
> There aren't many clients using this server, so I don't care if clients have 
> to redownload all their messages (in fact, I expect they'll probably end up 
> doing so anyway).

without that the POP3 clients downloaded again all messages, but
with that script, most clients was able to switch as
transparently. (Except the MS Office Outlook - but that's not a
"client" in my opinion... :))

> I'd like to preserve read/unread status of each message, but can't think of 
> anything else important.

the read/unread status had been kept in case of IMAP, but the MS
Office downloaded again through POP3, when I skipped the script
above.
 
> It doesn't matter if there's a few hours of downtime, but I thought to use 
> rsync because I figured I copy the maildirs a day or two ahead of time, and 
> then a sync immediately before going live will be quicker.
> 
> Using imapsync [1] looks pretty good, and I'm happy to use that if it'll be 
> "cleaner" or help Dovecot to create its hierarchy more neatly.

I didn't checked it, just doveadm ... imapc: command. The result
was fine, but the POP3 redownload was annoying.
 
> It looks like Courier creates a courierimapuiddb, courierimapkeywords and 
> courierimapacl in each folder - can I not just delete these, and hand Dovecot 
> a bunch of maildir directories and files to reindex for itself?

I kept them...
 


a.

-- 
I � UTF-8

Re: Migrating maildirs - Courier to Dovecot

[Robert Schetterer]

Am 21.09.2017 um 20:34 schrieb Stroller:
> I apologise, because I'm sure this subject has been done to death, but I want 
> to migrate from Courier to Dovecot.
> 
> I think my main question is whether there's any reason I shouldn't just rsync 
> the maildirs across from the old mail server to the new one? 

I think
it will work, but if maildir is the best solution for you ,study dovecot
wiki, be sure  configure dovecot right using maildir

> 
> There aren't many clients using this server, so I don't care if clients have 
> to redownload all their messages (in fact, I expect they'll probably end up 
> doing so anyway).
> 
> I'd like to preserve read/unread status of each message, but can't think of 
> anything else important.
> 
> It doesn't matter if there's a few hours of downtime, but I thought to use 
> rsync because I figured I copy the maildirs a day or two ahead of time, and 
> then a sync immediately before going live will be quicker.
> 
> Using imapsync [1] looks pretty good, and I'm happy to use that if it'll be 
> "cleaner" or help Dovecot to create its hierarchy more neatly.
> 
> It looks like Courier creates a courierimapuiddb, courierimapkeywords and 
> courierimapacl in each folder - can I not just delete these, and hand Dovecot 
> a bunch of maildir directories and files to reindex for itself?

dovecot will index and acl by itself

> 
> There are probably only a few hundred thousand messages on the server, a few 
> GB worth, although some of them are many years old.
> 
> Some of the messages on the old server have the wrong "received" date on 
> them, having the wrong file creation / modification date on the server's 
> filesystem, having been copied there previously (years ago) without using 
> cp's --archive flag. I've always thought I should one day write a script to 
> fix this, perhaps using mboxgrep.
> 
> Thanks in advance for any of your thoughts,
> 
> Stroller.
> 
> 

i did maildir rsync migration from dovecot to dovecot many times, no
problem, never tested from Courier, but its easy to test before
production ,so simply try out, if something dont work go imapsync way
which is easy too



> 
> 
> 
> [1] https://wiki2.dovecot.org/Migration#IMAP_.3C-.3E_IMAP_copying
> 



Best Regards
MfG Robert Schetterer

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64
Schleißheimer Straße 26/MG, 80333 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein

Migrating maildirs - Courier to Dovecot

[Stroller]

I apologise, because I'm sure this subject has been done to death, but I want 
to migrate from Courier to Dovecot.

I think my main question is whether there's any reason I shouldn't just rsync 
the maildirs across from the old mail server to the new one? 

There aren't many clients using this server, so I don't care if clients have to 
redownload all their messages (in fact, I expect they'll probably end up doing 
so anyway).

I'd like to preserve read/unread status of each message, but can't think of 
anything else important.

It doesn't matter if there's a few hours of downtime, but I thought to use 
rsync because I figured I copy the maildirs a day or two ahead of time, and 
then a sync immediately before going live will be quicker.

Using imapsync [1] looks pretty good, and I'm happy to use that if it'll be 
"cleaner" or help Dovecot to create its hierarchy more neatly.

It looks like Courier creates a courierimapuiddb, courierimapkeywords and 
courierimapacl in each folder - can I not just delete these, and hand Dovecot a 
bunch of maildir directories and files to reindex for itself?

There are probably only a few hundred thousand messages on the server, a few GB 
worth, although some of them are many years old.

Some of the messages on the old server have the wrong "received" date on them, 
having the wrong file creation / modification date on the server's filesystem, 
having been copied there previously (years ago) without using cp's --archive 
flag. I've always thought I should one day write a script to fix this, perhaps 
using mboxgrep.

Thanks in advance for any of your thoughts,

Stroller.





[1] https://wiki2.dovecot.org/Migration#IMAP_.3C-.3E_IMAP_copying

Re: JMAP support in Dovecot

[Aki Tuomi]

answer is not yet. we are going to implement it when we get free resources to 
do it.


---Aki TuomiDovecot oy
 Original message From: Steinar Bang  Date: 
21/09/2017  17:28  (GMT+02:00) To: dovecot@dovecot.org Subject: Re: JMAP 
support in Dovecot 
> Aki Tuomi :

> We are working on including JMAP support to Dovecot. At this moment I
> cannot give any promise for exact version, but hopefully it will be
> part of v2.3

Any updates on jmap support in dovecot?

I tried searching the git repo for "jmap" yesterday, so I'm guessing the
answer is "no" or "not yet"...?

Re: JMAP support in Dovecot

[Steinar Bang]

> Aki Tuomi :

> We are working on including JMAP support to Dovecot. At this moment I
> cannot give any promise for exact version, but hopefully it will be
> part of v2.3

Any updates on jmap support in dovecot?

I tried searching the git repo for "jmap" yesterday, so I'm guessing the
answer is "no" or "not yet"...?

Re: Bug#876364: dovecot-sieve: Just discovered imap_sieve/sieve_imapsieve is not set up to work with virtual mailboxes.

[Apollon Oikonomopoulos]

Control: tags -1 + moreinfo upstream

[Forwarding this to the Dovecot mailing list, just in case someone can help]

Hi,

Thanks for the report! See my comments inline.

On 11:56 Thu 21 Sep , Thurgood Angelou wrote:
> Package: dovecot-core
> Version: 1:2.2.32-2
>
> I've just discovered a bug where the sieve plugin (especially IMAP) 
> will not work with a virtual mailbox. I recently found this out when 
> testing a virtual mailbox setup and I use imap_sieve for SPAM 
> filtering so to lose that would be painful.
> 
> This is what is reported in dovecot's debug log...
> 
> Sep 21 10:53:01 imap(perso...@othersider92.com): Panic: file 
> mail-index-map.c: line 549 (mail_index_map_lookup_seq_range): assertion 
> failed: (first_uid > 0)
> Sep 21 10:53:01 imap(perso...@othersider92.com): Error: Raw backtrace: 
> /usr/lib/dovecot/libdovecot.so.0(+0x9f0a2) [0x7f4226fd50a2] -> 
> /usr/lib/dovecot/libdovecot.so.0(+0x9f19a) [0x7f4226fd519a] -> 
> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f4226f65cf8] -> 
> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_map_lookup_seq_range+0x120)
>  [0x7f422733dae0] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xe8d1d) 
> [0x7f422734cd1d] -> 
> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_lookup_seq+0xf) 
> [0x7f4227350e9f] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(+0x82aa) 
> [0x7f422678a2aa] -> 
> /usr/lib/dovecot/modules/lib95_imap_sieve_plugin.so(+0x708c) [0x7f422657d08c] 
> -> 
> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_transaction_commit_get_changes+0x52)
>  [0x7f42272adca2] -> dovecot/imap(+0x10084) [0x556502adb084] -> 
> dovecot/imap(command_exec+0x5c) [0x556502ae7d9c] -> dovecot/imap(+0x1b322) 
> [0x556502ae6322] -> dovecot/imap(+0x1b3bc) [0x556502ae63bc] -> 
> dovecot/imap(client_handle_input
>  +0x18d) [0x556502ae677d] -> dovecot/imap(client_input+0xac) [0x556502ae6ccc] 
> -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7f4226fea742] -> 
> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x12e) 
> [0x7f4226febd8e] -> 
> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x36) [0x7f4226fea7d6] 
> -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f4226fea988] -> 
> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f4226f70353] -> 
> dovecot/imap(main+0x329) [0x556502ad9139] -> 
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7f4226bb92e1] -> 
> dovecot/imap(_start+0x2a) [0x556502ad92ca]

After mixing in the debug symbols, this backtrace becomes:

/usr/lib/dovecot/libdovecot.so.0(+0x9f0a2) [0x7f4226fd50a2]
default_fatal_finish at ./src/lib/failures.c:195
/usr/lib/dovecot/libdovecot.so.0(+0x9f19a) [0x7f4226fd519a]
?? at ./src/lib/failures.c:670
/usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f4226f65cf8]
i_fatal at ./src/lib/failures.c:280
/usr/lib/dovecot/libdovecot-storage.so.0(mail_index_map_lookup_seq_range+0x120) 
[0x7f422733dae0]
mail_index_map_lookup_seq_range at ./src/lib-index/mail-index-map.c:550
/usr/lib/dovecot/libdovecot-storage.so.0(+0xe8d1d) [0x7f422734cd1d]
tview_lookup_seq_range at ./src/lib-index/mail-index-transaction-view.c:178
/usr/lib/dovecot/libdovecot-storage.so.0(mail_index_lookup_seq+0xf) 
[0x7f4227350e9f]
mail_index_lookup_seq at ./src/lib-index/mail-index-view.c:522
/usr/lib/dovecot/modules/lib20_virtual_plugin.so(+0x82aa) [0x7f422678a2aa]
virtual_mail_set_uid at ./src/plugins/virtual/virtual-mail.c:213
  
/usr/lib/dovecot/modules/lib95_imap_sieve_plugin.so(+0x708c) [0x7f422657d08c]
imap_sieve_mailbox_transaction_run at 
./pigeonhole/src/plugins/imapsieve/imap-sieve-storage.c:752 (inlined by: 
imap_sieve_mailbox_transaction_commit at 
./pigeonhole/src/plugins/imapsieve/imap-sieve-storage.c:807)
/usr/lib/dovecot/libdovecot-storage.so.0(mailbox_transaction_commit_get_changes+0x52)
 [0x7f42272adca2]
mailbox_transaction_commit_get_changes at 
./src/lib-storage/mail-storage.c:2083
dovecot/imap(+0x10084) [0x556502adb084]
cmd_copy_full at ./src/imap/cmd-copy.c:146
dovecot/imap(command_exec+0x5c) [0x556502ae7d9c]
command_exec at ./src/imap/imap-commands.c:200
dovecot/imap(+0x1b322) [0x556502ae6322]
client_command_input at ./src/imap/imap-client.c:1088
dovecot/imap(+0x1b3bc) [0x556502ae63bc]
client_command_input at ./src/imap/imap-client.c:1150
dovecot/imap(client_handle_input+0x18d) [0x556502ae677d]
client_handle_input at ./src/imap/imap-client.c:1203
dovecot/imap(client_input+0xac) [0x556502ae6ccc]
client_input at ./src/imap/imap-client.c:1249
/usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7f4226fea742]
io_loop_call_io at ./src/lib/ioloop.c:600
/usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x12e) 
[0x7f4226febd8e]
io_loop_handler_run_internal at ./src/lib/ioloop-epoll.c:223
/usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x36) [0x7f4226fea7d6]
io_loop_handler_run at ./src/lib/ioloop.c:648

Re: Dovecot 2.1.17 and Solr 6.6.1

[Aki Tuomi]

https://wiki.dovecot.org/Upgrading/2.2

Aki

On 21.09.2017 14:30, Siarhei Chystsiakou wrote:
> This patch is not valid for dovecot 2.1.17 :(
> Will my config (dovecot 2.1.17) be suitable for the dovecot => 2.2.19  ?
> Thanks
>
> 2017-09-21 12:05 GMT+02:00 Aki Tuomi :
>
>> Probably, it's a small change. =)
>>
>> Aki
>>
>>
>> On 21.09.2017 13:01, Siarhei Chystsiakou wrote:
>>> Can I used the patch on dovecot 2.1.17 ?
>>>
>>> 2017-09-21 11:17 GMT+02:00 Aki Tuomi :
>>>
 On 20.09.2017 12:51, Siarhei Chystsiakou wrote:
> Hello.
> I'm trying to set fts plugin for working with Apache Solr 6.6.1, but
 after
> the setting I get the following error 
>
> o.a.s.h.RequestHandlerBase org.apache.solr.common.SolrException: Bad
> contentType for search handler :text/xml
> request={q=from:"test"=uid,score=uid+asc=%2Bbox:
 a8012d2edac165591d3c43730d65+%2Buser:"
> u...@example.com"=5543}
>
> I've set everything according to the guide on the site as well as
>> taking
> into consideration such conversation in maillist in February 2017 (
> https://dovecot.org/list/dovecot/2017-February/107255.html).
>
> The current dovecot configuration:...
>
> #cat /etc/dovecot/conf.d/90-fts.conf
> plugin {
> fts = solr
> fts_solr = debug break-imap-search url=
> http://127.0.0.1:8983/solr/dovecot/
> }
>
> full config the dovecot: https://hastebin.com/awuwohanoz.makefile
>
> I also enclose the screen from wireshark https://itmag.es/6mWng
>
> Thanks!
 This is a bug fixed in dovecot 2.2.19 with
 https://github.com/dovecot/core/commit/43da9b96171251e7e88f3a0523f9dc
 51d528580b.patch

 Aki

>>

Re: Dovecot 2.1.17 and Solr 6.6.1

[Siarhei Chystsiakou]

This patch is not valid for dovecot 2.1.17 :(
Will my config (dovecot 2.1.17) be suitable for the dovecot => 2.2.19  ?
Thanks

2017-09-21 12:05 GMT+02:00 Aki Tuomi :

> Probably, it's a small change. =)
>
> Aki
>
>
> On 21.09.2017 13:01, Siarhei Chystsiakou wrote:
> > Can I used the patch on dovecot 2.1.17 ?
> >
> > 2017-09-21 11:17 GMT+02:00 Aki Tuomi :
> >
> >>
> >> On 20.09.2017 12:51, Siarhei Chystsiakou wrote:
> >>> Hello.
> >>> I'm trying to set fts plugin for working with Apache Solr 6.6.1, but
> >> after
> >>> the setting I get the following error 
> >>>
> >>> o.a.s.h.RequestHandlerBase org.apache.solr.common.SolrException: Bad
> >>> contentType for search handler :text/xml
> >>> request={q=from:"test"=uid,score=uid+asc=%2Bbox:
> >> a8012d2edac165591d3c43730d65+%2Buser:"
> >>> u...@example.com"=5543}
> >>>
> >>> I've set everything according to the guide on the site as well as
> taking
> >>> into consideration such conversation in maillist in February 2017 (
> >>> https://dovecot.org/list/dovecot/2017-February/107255.html).
> >>>
> >>> The current dovecot configuration:...
> >>>
> >>> #cat /etc/dovecot/conf.d/90-fts.conf
> >>> plugin {
> >>> fts = solr
> >>> fts_solr = debug break-imap-search url=
> >>> http://127.0.0.1:8983/solr/dovecot/
> >>> }
> >>>
> >>> full config the dovecot: https://hastebin.com/awuwohanoz.makefile
> >>>
> >>> I also enclose the screen from wireshark https://itmag.es/6mWng
> >>>
> >>> Thanks!
> >> This is a bug fixed in dovecot 2.2.19 with
> >> https://github.com/dovecot/core/commit/43da9b96171251e7e88f3a0523f9dc
> >> 51d528580b.patch
> >>
> >> Aki
> >>
>
>

Re: Dovecot 2.1.17 and Solr 6.6.1

[Aki Tuomi]

Probably, it's a small change. =)

Aki


On 21.09.2017 13:01, Siarhei Chystsiakou wrote:
> Can I used the patch on dovecot 2.1.17 ?
>
> 2017-09-21 11:17 GMT+02:00 Aki Tuomi :
>
>>
>> On 20.09.2017 12:51, Siarhei Chystsiakou wrote:
>>> Hello.
>>> I'm trying to set fts plugin for working with Apache Solr 6.6.1, but
>> after
>>> the setting I get the following error 
>>>
>>> o.a.s.h.RequestHandlerBase org.apache.solr.common.SolrException: Bad
>>> contentType for search handler :text/xml
>>> request={q=from:"test"=uid,score=uid+asc=%2Bbox:
>> a8012d2edac165591d3c43730d65+%2Buser:"
>>> u...@example.com"=5543}
>>>
>>> I've set everything according to the guide on the site as well as taking
>>> into consideration such conversation in maillist in February 2017 (
>>> https://dovecot.org/list/dovecot/2017-February/107255.html).
>>>
>>> The current dovecot configuration:...
>>>
>>> #cat /etc/dovecot/conf.d/90-fts.conf
>>> plugin {
>>> fts = solr
>>> fts_solr = debug break-imap-search url=
>>> http://127.0.0.1:8983/solr/dovecot/
>>> }
>>>
>>> full config the dovecot: https://hastebin.com/awuwohanoz.makefile
>>>
>>> I also enclose the screen from wireshark https://itmag.es/6mWng
>>>
>>> Thanks!
>> This is a bug fixed in dovecot 2.2.19 with
>> https://github.com/dovecot/core/commit/43da9b96171251e7e88f3a0523f9dc
>> 51d528580b.patch
>>
>> Aki
>>

Re: Dovecot 2.1.17 and Solr 6.6.1

[Siarhei Chystsiakou]

Can I used the patch on dovecot 2.1.17 ?

2017-09-21 11:17 GMT+02:00 Aki Tuomi :

>
>
> On 20.09.2017 12:51, Siarhei Chystsiakou wrote:
> > Hello.
> > I'm trying to set fts plugin for working with Apache Solr 6.6.1, but
> after
> > the setting I get the following error 
> >
> > o.a.s.h.RequestHandlerBase org.apache.solr.common.SolrException: Bad
> > contentType for search handler :text/xml
> > request={q=from:"test"=uid,score=uid+asc=%2Bbox:
> a8012d2edac165591d3c43730d65+%2Buser:"
> > u...@example.com"=5543}
> >
> > I've set everything according to the guide on the site as well as taking
> > into consideration such conversation in maillist in February 2017 (
> > https://dovecot.org/list/dovecot/2017-February/107255.html).
> >
> > The current dovecot configuration:...
> >
> > #cat /etc/dovecot/conf.d/90-fts.conf
> > plugin {
> > fts = solr
> > fts_solr = debug break-imap-search url=
> > http://127.0.0.1:8983/solr/dovecot/
> > }
> >
> > full config the dovecot: https://hastebin.com/awuwohanoz.makefile
> >
> > I also enclose the screen from wireshark https://itmag.es/6mWng
> >
> > Thanks!
> This is a bug fixed in dovecot 2.2.19 with
> https://github.com/dovecot/core/commit/43da9b96171251e7e88f3a0523f9dc
> 51d528580b.patch
>
> Aki
>

Re: Dovecot 2.1.17 and Solr 6.6.1

[Aki Tuomi]

On 20.09.2017 12:51, Siarhei Chystsiakou wrote:
> Hello.
> I'm trying to set fts plugin for working with Apache Solr 6.6.1, but after
> the setting I get the following error 
>
> o.a.s.h.RequestHandlerBase org.apache.solr.common.SolrException: Bad
> contentType for search handler :text/xml
> request={q=from:"test"=uid,score=uid+asc=%2Bbox:a8012d2edac165591d3c43730d65+%2Buser:"
> u...@example.com"=5543}
>
> I've set everything according to the guide on the site as well as taking
> into consideration such conversation in maillist in February 2017 (
> https://dovecot.org/list/dovecot/2017-February/107255.html).
>
> The current dovecot configuration:...
>
> #cat /etc/dovecot/conf.d/90-fts.conf
> plugin {
> fts = solr
> fts_solr = debug break-imap-search url=
> http://127.0.0.1:8983/solr/dovecot/
> }
>
> full config the dovecot: https://hastebin.com/awuwohanoz.makefile
>
> I also enclose the screen from wireshark https://itmag.es/6mWng
>
> Thanks!
This is a bug fixed in dovecot 2.2.19 with
https://github.com/dovecot/core/commit/43da9b96171251e7e88f3a0523f9dc51d528580b.patch

Aki

Re: Very high load

[Aki Tuomi]

On 21.09.2017 00:56, absolutely_f...@libero.it wrote:
> Hi,
>
> I am using dovecot 2.0.9 (official CentOS rpm), I am experiencing very high 
> load issue.
>
> I think it is something related to my storage (/var/spool is about 3 TB and 
> it is almost full).
>
> I noticed those kind of messages in /var/log/maillog:
>
>
> Warning: Maildir: Scanning 
> /var/spool/pop/domains/domain.it/username/Maildir/cur took 100 seconds (14281 
> readdir()s, 0 rename()s to cur/)
Maybe you have just too much load on your server. Also you seem to be
triggering maildir scans which are expensive.

Also the version you are running is from 2011, so it's ... rather dated.
You should probably update your system to centos7 which at least has
2.2.10, which is still rather old, but less so.
>
> Warning: Maildir /var/spool/pop/domains/domain.it/username/Maildir: 
> Synchronization took 103 seconds (0 new msgs, 0 flag change attempts, 0 
> expunge attempts)
>
> I wondering if there is something to try, at configuration level, to 
> "mitigate" this..
>
> I use Maildir format, MTA is postfix, I have many users (> 1) with 
> pop3/imap/webmail access. Physical server with 8 GB RAM and two CPU (Intel(R) 
> Pentium(R) D CPU 3.00GHz)
>
>
> This is my dovecot's conf:
>
>
please use doveconf -n

Aki