Le 2019-04-04 03:28, André a écrit :
I have it working, only with the user part of the email address.
It works well, as long as the whole chain of software is correctly
configured.
I have not tested with a whole domain in UTF8 yet.
More details and working examples here:
On 4/4/2019 6:42 PM, M. Balridge via dovecot wrote:
What is a general rule of thumb for RAM and SSD disk requirements as a
fraction of indexed document hive size to keep query performance at 200ms or
less? How do people deal with the JAVA GC world-stoppages, other than simply
doubling or
> I'm a denizen of the solr-u...@lucene.apache.org mailing list.
> [...]
> Here's a wiki page that I wrote about that topic. This wiki is going
> away next month, but for now you can still access it:
>
> https://wiki.apache.org/solr/SolrPerformanceProblems
That's a great resource, Shawn.
I
On 4/4/19 6:47 PM, dovecot-requ...@dovecot.org wrote:
> For a typical Solr index, 60 seconds is an eternity. Most people aim
> for query times of 100 milliseconds or less, and they often achieve
> that goal.
I'm pretty sure I get these while indexing, not querying.
Apr 04 16:44:50 host
On 4/4/2019 2:21 AM, Peter Mogensen via dovecot wrote:
What's the recommended way to handling timeouts on large mailboxes given
the hardwired request timeout of 60s in solr-connection.c:
http_set.request_timeout_msecs = 60*1000;
I'm a denizen of the solr-u...@lucene.apache.org mailing
Hi Shawn
Am 04.04.19 um 16:12 schrieb Shawn Heisey via dovecot:
> On 4/4/2019 2:21 AM, Peter Mogensen via dovecot wrote:
> Here's a wiki page that I wrote about that topic. This wiki is going
> away next month, but for now you can still access it:
>
>
On 4/4/2019 2:21 AM, Peter Mogensen via dovecot wrote:
What's the recommended way to handling timeouts on large mailboxes given
the hardwired request timeout of 60s in solr-connection.c:
http_set.request_timeout_msecs = 60*1000;
I'm a denizen of the solr-u...@lucene.apache.org mailing
> On 4 Apr 2019, at 11.03, Michael Goth via dovecot wrote:
>
> That too includes the byte in its output. But I've found that only a
> couple of mailboxes are affected, so i just renamed the folders.
>
> Thanks for your help!
The legacy server is then not RFC 3501 compliant. 8-bit folder
# in the public namespace
namespace {
...
mailbox name {
auto=subscribe
}
}
?
Aki
On 4.4.2019 12.45, Рустам via dovecot wrote:
> Hello everyone! I am trying to migrate from Dovecot 1.2 to Dovecot 2.2
> and I can`t find information how to subscribe all users to public
> folder.
Hello everyone! I am trying to migrate from Dovecot 1.2 to Dovecot 2.2 and
I can`t find information how to subscribe all users to public folder. In
Dovecot 1.2 I have a few strings kind of "autosubscribeX =
Public.Documents" and every users get subscribed to this Public folders and
can`t
On 4/3/19 2:23 PM, Sami Ketola via dovecot wrote:
On 3 Apr 2019, at 13.40, Michael Goth via dovecot wrote:
Hi!
I'm trying to migrate a mailbox from an old IMAP server (not Dovecot) to a new
Dovecot server with 'doveadm backup'. The command fails because of an
unexpected character in a
Hi,
What's the recommended way to handling timeouts on large mailboxes given
the hardwired request timeout of 60s in solr-connection.c:
http_set.request_timeout_msecs = 60*1000;
/Peter
I have it working, only with the user part of the email address.
It works well, as long as the whole chain of software is correctly configured.
I have not tested with a whole domain in UTF8 yet.
More details and working examples here:
https://github.com/progmaticltd/homebox
Good luck.
On 4
Le 2019-04-04 01:36, Michael Slusarz a écrit :
On April 3, 2019 at 10:12 PM sylvhem--- via dovecot
wrote:
I'm currently trying to set up SMTPUTF8 on my mail stack, but I can't
find any information on Dovecot's RFC 6531 support. Has it been
implemented yet?
No.
michael
Thank you for the
14 matches
Mail list logo
