Hi,
Thank you for your reply.
I hope this bug to be fixed soon. :)
Thank you.
Tachibana
- Original Message -
> On Mon, Jul 20, 2020 at 09:43:12 -0400, Josef 'Jeff' Sipek wrote:
> > On Mon, Jul 20, 2020 at 20:24:13 +0900, TACHIBANA Masashi wrote:
> ...
> > Thanks for the report. I repro
On 7/17/2020 3:23 AM, Maciej Milaszewski wrote:
I try schema.xml and solrconfig.xml from working solr-6.6.5 (dovecot)
"dovecot:
org.apache.solr.common.SolrException:org.apache.solr.common.SolrException:
Error initializing QueryElevationComponent"
That looks like a Solr error. This list is not
On 7/20/20 4:42 AM, Siavash Tavakoli wrote:
>
> On 19/07/2020 18:18, PGNet Dev wrote:
>>
>> What in my dovecot submission config^^ do I need to change/add to get it to
>> 'present' a client cert to the postfix relay for client cert verification?
>>
>
> Submission uses the global outgoing
On Mon, Jul 20, 2020 at 09:43:12 -0400, Josef 'Jeff' Sipek wrote:
> On Mon, Jul 20, 2020 at 20:24:13 +0900, TACHIBANA Masashi wrote:
...
> Thanks for the report. I reproduced it locally, but I'm not sure what is
> causing it yet.
Alright, it is actually a parsing bug. The problem seems to be whe
On Mon, Jul 20, 2020 at 20:24:13 +0900, TACHIBANA Masashi wrote:
> Hi,
>
> I'm Tachibana.
> Additionally, I found below:
>
> dovecot/src/plugins/fts/fts-build-mail.c:
>
> 187 i_debug("@ befor address
> parse:%s",hdr->full_value);
> 188
> 189 addr
On 19/07/2020 18:18, PGNet Dev wrote:
What in my dovecot submission config^^ do I need to change/add to get it to
'present' a client cert to the postfix relay for client cert verification?
Submission uses the global outgoing ssl settings:
https://doc.dovecot.org/settings/core/#ssl-client-
Set mail to only display mail within 30 or 60 days, Here are two
examples.
1. normal
E.g:
A654 FETCH 2:4 (FLAGS BODY[HEADER.FIELDS (DATE FROM)])
* 2 FETCH (FLAGS (\Seen) BODY[HEADER.FIELDS (DATE FROM)] {73}
Date: Tue, 07 May 2020 12:26:55 +0800
From:
)
* 3 FETCH (FLAGS (\Seen) BODY[HEADER.F
Hi,
I'm Tachibana.
Additionally, I found below:
dovecot/src/plugins/fts/fts-build-mail.c:
187 i_debug("@ befor address parse:%s",hdr->full_value);
188
189 addr = message_address_parse(pool_datastack_create(),
190
On 20/07/2020 10:37 lty wrote:
We found that there are historically corrupted mails in the tmp/
directory,
For example, Maildir/tmp/ or Maildir/.Drafts/tmp/ exists.
We suspect that it may be caused by network transmission, or the user
interrupted the network link.
Can the dovecot team possibly f
> On 20/07/2020 10:37 lty wrote:
>
>
> We found that there are historically corrupted mails in the tmp/
> directory,
> For example, Maildir/tmp/ or Maildir/.Drafts/tmp/ exists.
> We suspect that it may be caused by network transmission, or the user
> interrupted the network link.
> Can the
We found that there are historically corrupted mails in the tmp/
directory,
For example, Maildir/tmp/ or Maildir/.Drafts/tmp/ exists.
We suspect that it may be caused by network transmission, or the user
interrupted the network link.
Can the dovecot team possibly fix this problem?
dovecot --ver
Hi everyone,
after some hours when I sent my last e-mail to the ML the problem
reoccurred, again problem with some mailboxes reading some e-mails and
many errors into dovecot.log like these:
/Jul 14 15:07:50 imap(XXX): Error:
open(/mnt/mail-storage/XXX/Maildir/cur/1594641298.M607225P10899.XX
12 matches
Mail list logo
