Re: fts_encoder
Created a PR
https://github.com/dovecot/core/pull/155
On 2021-02-11 13:25, Joan Moreau wrote:
Hello
Checking further, and putting logs a bit every where in the dovecot
code, the core is sending FIRST the initial document (not decoded) then
SECOND the decoded version
Thisi is really weird, and the indexer then indexes a lot of binary
crap
I am struggling to find where in the code this double call is made.
Anyone knows ?
On 2021-02-10 00:05, John Fawcett wrote:
On 09/02/2021 15:33, Joan Moreau wrote:
If I place the following code in the plugin
fts_backend_xxx_update_build_more function (lucene, squat and xapian,
as solr refuses to work properly on my setup)
{
char * s = i_strdup("EMPTY");
if(data != NULL) { i_free(s); s = i_strndup(data,20); }
i_info("fts_backend_update_build_more: data like '%s'",s);
i_free(s);
}
and if I send a PDF by email, the data shown in the log is "%PDF-1.7 "
so it does mean the decoder data is not properly transmitted to the
plugin
Something is wrong in the data transmission
Joan
I too see something similar with fts_solr. I do see the raw %PDF string
and PDF binary data being passed through to
fts_backend_xxx_update_build_more function but I disagree with the
conclusion you draw from it.
After the raw data I also see the decoded data, so at least in my case
it is possible to see both the raw and decoded data in
fts_backend_xxx_update_build_more function. In the rawlog I no longer
see the binary data (but some blank lines), so something is filtering
it. I do see the decoded data in the rawlog. I do get hits on the solr
search for the decoded text.
John
Re: fts_encoder
On 11/02/2021 14:25, Joan Moreau wrote: > > Hello > > Checking further, and putting logs a bit every where in the dovecot > code, the core is sending FIRST the initial document (not decoded) > then SECOND the decoded version > > Thisi is really weird, and the indexer then indexes a lot of binary crap > > I am struggling to find where in the code this double call is made. > > Anyone knows ? > > Joan I didn't get round to working out where it happens. But your observation is in line with what I see for solr plugin. Only difference is that as far as I can see, the raw data does not make it to solr. That the rawlog does not contain the data is a good indication, but the proof is that searching for PDF string on solr does not get a hit on the messages. John
Re: doveadm expunge logging
W dniu 04.02.2021 o 17:37, Arkadiusz Miśkiewicz pisze:
> W dniu 04.02.2021 o 14:01, Aki Tuomi pisze:
>> Did you also load `mail_log` plugin?
>
> I didn't. Added
>
> protocol doveadm {
> mail_plugins = $mail_plugins mail_log notify acl
> }
>
> and now I'm getting logs on stderr. Nice!
>
>
> Can I get this logged into syslog without my own redirection?
>
> Trying
>
> doveadm -o 'log_path=syslog' -o 'syslog_facility=mail' ... expunge ...
>
> but I'm getting these on stderr only.
Improvement for doveadm:
https://github.com/dovecot/core/pull/156
that allows logging into syslog
>
>>
>> Aki
>>
>>> On 04/02/2021 14:52 Arkadiusz Miśkiewicz wrote:
>>>
>>>
>>> Hello.
>>>
>>> dovecot 2.3.13 here, using
>>>
>>> doveadm -c /etc/my.conf expunge -A mailbox SomeFolder savedbefore 31d
>>>
>>> and my.conf includes
>>>
>>> plugin {
>>> mail_log_events = delete undelete expunge copy mailbox_delete
>>> mailbox_rename save
>>> }
>>>
>>> unfortunately expunged messages are not logged anywhere.
>>>
>>> Tried -v and -D to see if these will get logged to output (so I could
>>> pipe these to syslog) but verbose/debug also don't show which messages
>>> were expunged.
>>>
>>>
>>> Is there a way to get this logged?
>>>
>>> Log like regular dovecot logs would be nice:
>>>
>>> doveadm(arekm): pid=<14783>, expunge: box=INBOX, uid=0,
>>> msgid=, size=15077
>>>
>>> --
>>> Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
>
>
--
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
Re: Quota-status service on Director
Did you solve this problem of quota status? I am in the same situation right now, i would appreciate you let me know any helpfull information Sent with Aqua Mail for Android https://www.mobisystems.com/aqua-mail
Re: fts_encoder
Hello
Checking further, and putting logs a bit every where in the dovecot
code, the core is sending FIRST the initial document (not decoded) then
SECOND the decoded version
Thisi is really weird, and the indexer then indexes a lot of binary crap
I am struggling to find where in the code this double call is made.
Anyone knows ?
On 2021-02-10 00:05, John Fawcett wrote:
On 09/02/2021 15:33, Joan Moreau wrote:
If I place the following code in the plugin
fts_backend_xxx_update_build_more function (lucene, squat and xapian,
as solr refuses to work properly on my setup)
{
char * s = i_strdup("EMPTY");
if(data != NULL) { i_free(s); s = i_strndup(data,20); }
i_info("fts_backend_update_build_more: data like '%s'",s);
i_free(s);
}
and if I send a PDF by email, the data shown in the log is "%PDF-1.7 "
so it does mean the decoder data is not properly transmitted to the
plugin
Something is wrong in the data transmission
Joan
I too see something similar with fts_solr. I do see the raw %PDF string
and PDF binary data being passed through to
fts_backend_xxx_update_build_more function but I disagree with the
conclusion you draw from it.
After the raw data I also see the decoded data, so at least in my case
it is possible to see both the raw and decoded data in
fts_backend_xxx_update_build_more function. In the rawlog I no longer
see the binary data (but some blank lines), so something is filtering
it. I do see the decoded data in the rawlog. I do get hits on the solr
search for the decoded text.
John
Re: sieve_after seems to not bring any effect to life in dovecot 2.3.13 dovecot-pigeonhole-0.5.13
> On 11/02/2021 13:30 Bug Report wrote:
>
>
> dovecot 2.3.13 (89f716dc2)
>
> dovecot-pigeonhole-0.5.13
>
> OS: FreeBSD amd64 12.2-RELEASE
>
> After following code
>
> --
>
> require ["copy"];
>
> # rule:[redirect]
>
> if true
>
> {
>
> redirect :copy "m...@mail.com";
>
> keep;
>
> }
>
> --
>
> (both with keep and without keep) is executed sieve_after seems to not
> execute at all.
>
> Same code together with sieve_after was working as supposed in earlier
> versions.
Please provide output of `doveconf -n`.
Aki
sieve_after seems to not bring any effect to life in dovecot 2.3.13 dovecot-pigeonhole-0.5.13
dovecot 2.3.13 (89f716dc2)
dovecot-pigeonhole-0.5.13
OS: FreeBSD amd64 12.2-RELEASE
After following code
--
require ["copy"];
# rule:[redirect]
if true
{
redirect :copy "m...@mail.com";
keep;
}
--
(both with keep and without keep) is executed sieve_after seems to not execute
at all.
Same code together with sieve_after was working as supposed in earlier versions.
