Hello;
Some issue with virtual storage and fts-lucene:
Sep 24 08:12:16 imap(jbv00@x xx): Panic: file
virtual-storage.c: line 370 (virtual_backend_box_close): assertion failed:
(mbox->backends_open_count > 0)
Sep 24 08:12:16 imap(jbv00@x xx): Error: Raw
backtrace: /usr/local/lib/dovecot/libdovecot
On Thu, Sep 24, 2015 at 6:27 PM, Timo Sirainen wrote:
> On 09/24/2015 07:08 PM, Timo Sirainen wrote:
> > On 09/24/2015 09:23 AM, Jean-Baptiste Vignaud wrote:
> >> Hello;
> >>
> >> Some issue with virtual storage and fts-lucene:
> >>
> >> Sep
>
>
>
> Thanks for the report. Bug found. My bad. A patch is working its way
> through the internal process, and will be in the public tree soon.
>
> Cheers,
> Phil
>
Hello;
Does this patch will need to reindex lucene ?
Thanks
Hello all;
Is anyone knows if it's possible to have a dual certificate setup on
dovecot like in postfix or apache ?
i tried to add several crts in local name section :
local_name imap.server.tdl {
ssl_cert =
On Wed, Mar 2, 2016 at 3:44 PM, Timo Sirainen wrote:
>
>
> Would it work if you had a single .pem file containing both certs and a
> single file containing both keys?
>
OK, just tried this configuration but only the first certificate is
working.
I used this order : rsa cert, ecdsa cert, interme
hello all;
one colleague found a strange behavior, that can be annoying :
-bash-3.1$ telnet 0 143
Trying 0.0.0.0...
Connected to 0 (0.0.0.0).
Escape character is '^]'.
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE
AUTH=PLAIN AUTH=CRAM-MD5] Dovecot ready.
l login login pass
On Thu, Mar 11, 2010 at 10:54 AM, Timo Sirainen wrote:
>> one colleague found a strange behavior, that can be annoying :
> ..
>> and more annoying:
>>
>> l uid store 100:* +flags (\Seen \Deleted)
>> * 281 FETCH (UID 362 FLAGS (\Deleted \Seen))
>> l OK Store completed.
>
> and exactly as requi
Hello;
I was reading the message "how to config dovecot for multiple domains,
multiple SSL certs, and conditional IP access -- with passwd-file
passdb?", and i was wondering if Dovecot could support the SNI
extention of TLS ?
SNI is Server Name Indication where during the TLS negotiation, the
cli
> Oh, I didn't know this was already in OpenSSL. I'll see about adding
> support for it to v2.0. I'm not entirely sure how to make it
> configurable though. Perhaps instead of having:
>
> local_ip 1.2.3.4 {
> ssl_cert = }
> remote_ip 4.3.2.1 {
> }
>
> I could replace those with:
>
> local host.do
