Re: SQL-AUTH driver replace for VPOPMAIL-AUTH

[Remo Mattei]

Hi Pablo, 
Roberto has it without PLAIN text, you could check that out

https://notes.sagredo.eu/en/qmail-notes-185/installing-and-configuring-vpopmail-81.html
 


I recall I used Roberto in the past, and the pass is encrypted. 

Remo

> On Feb 9, 2021, at 19:04, Pablo Murillo  wrote:
> 
> Hi
> 
> I'm made a lot of test trying to get SLQ auth driver work with vpopmail/mysql 
> configured with many domains (one table for each domain)
> Finally I made it work, but ... only with PLAIN password
> Is there a way to make SQL auth work with vpopmail/mysql tables with 
> encrypted password (CRAM-MD5 / MD5-CRYPT) ?
> 
> Thanks
> Pablo Murillo
> 
> 
> 
> -- 
> This email has been checked for viruses by AVG.
> https://www.avg.com
> 

Re: SQL-AUTH driver replace for VPOPMAIL-AUTH

[Aki Tuomi]

Return the password with {CRAM-MD5} or {MD5-CRYPT} prefix, then dovecot will 
know the password scheme.

Aki

> On 10/02/2021 05:04 Pablo Murillo  wrote:
> 
>  
> Hi
> 
> I'm made a lot of test trying to get SLQ auth driver work with 
> vpopmail/mysql configured with many domains (one table for each domain)
> Finally I made it work, but ... only with PLAIN password
> Is there a way to make SQL auth work with vpopmail/mysql tables with 
> encrypted password (CRAM-MD5 / MD5-CRYPT) ?
> 
> Thanks
> Pablo Murillo
> 
> 
> 
> -- 
> This email has been checked for viruses by AVG.
> https://www.avg.com

Re: SQL-AUTH driver replace for VPOPMAIL-AUTH

[Pablo Murillo]

Hi Remo

I check Roberto page, but I'm using a complete different configuration
I use one table per domain, he use only one table for everything

Pablo

On 2/10/2021 1:13 AM, Remo Mattei wrote:

Hi Pablo,
Roberto has it without PLAIN text, you could check that out

https://notes.sagredo.eu/en/qmail-notes-185/installing-and-configuring-vpopmail-81.html 



I recall I used Roberto in the past, and the pass is encrypted.

Remo

On Feb 9, 2021, at 19:04, Pablo Murillo > wrote:


Hi

I'm made a lot of test trying to get SLQ auth driver work with 
vpopmail/mysql configured with many domains (one table for each domain)

Finally I made it work, but ... only with PLAIN password
Is there a way to make SQL auth work with vpopmail/mysql tables with 
encrypted password (CRAM-MD5 / MD5-CRYPT) ?


Thanks
Pablo Murillo



--
This email has been checked for viruses by AVG.
https://www.avg.com 

SQL-AUTH driver replace for VPOPMAIL-AUTH

[Pablo Murillo]

Hi

I'm made a lot of test trying to get SLQ auth driver work with 
vpopmail/mysql configured with many domains (one table for each domain)

Finally I made it work, but ... only with PLAIN password
Is there a way to make SQL auth work with vpopmail/mysql tables with 
encrypted password (CRAM-MD5 / MD5-CRYPT) ?


Thanks
Pablo Murillo



--
This email has been checked for viruses by AVG.
https://www.avg.com

Re: Getting panic in http-client-request.c: line 1240 during indexing on Ubuntu 20.04

[Scott Q.]

Is this the same bug that John created a patch for but then
Dovecot fixed differently in the latest version ? 

The one with the assertion ? If so, I thought it was fixed, no ?



On Tuesday, 09/02/2021 at 17:32 Arjen Heidinga wrote:


On 08-02-2021 18:40, deano-dove...@areyes.com wrote:
>
> Do we have when (or even if) that patch will make it into the main
? 
> I would really rather prefer pulling from repo ...
>
Please! I struggle with this for at least two years now!

Arjen

Re: fts_encoder

[John Fawcett]

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: Getting panic in http-client-request.c: line 1240 during indexing on Ubuntu 20.04

[Arjen Heidinga]

On 08-02-2021 18:40, deano-dove...@areyes.com wrote:
>
> Do we have when (or even if) that patch will make it into the main ? 
> I would really rather prefer pulling from repo ...
>
Please! I struggle with this for at least two years now!

Arjen

Re: Problem enabling the mail_log plugin

[@lbutlr]

On 09 Feb 2021, at 11:34, Mike Quigley  wrote:
> So it looks like when Roundcube copies them to Trash and expunges the 
> original, it doesn't set the Trash flag on the message.

Checking on my server none of the messages in the Trash maildir have a T flag, 
they all end in things like :2,hk or :2,Sab or :2,d (and probably other things 
as well).

-- 
Doctor inherits a castle
(Young Frankenstein)

Re: Problem enabling the mail_log plugin

[Mike Quigley]

The default Debian 8 or 9 install of Dovecot duplicates Dovecot logging 
in both /var/log/mail.info & /var/log/syslog.  This server was 
originally setup with v8 and later upgraded to v9.

--

On 2021-02-09 3:46 am, Yassine Chaouche wrote:


Le 2/8/21 à 5:03 AM, Mike Quigley a écrit :
I see so difference in /var/log/mail.info & /var/log/syslog


Did you configure it to use syslog ? my config puts dovecot logs in 
/var/log/dovecot


Yassine.

Re: Problem enabling the mail_log plugin

[Mike Quigley]

I looked at the Trash messages on the Server (which is using Maildir) 
and they are flagged as :2,S (Seen) but not T (Trash). So it looks like 
when Roundcube copies them to Trash and expunges the original, it 
doesn't set the Trash flag on the message.  If I manually delete the 
message from the Trash folder, then RC does set the Trash flag and that 
action will be logged to my Dovecot logs. I did not set the expunge & 
copy options in mail_log_events because I didn't want to fill up the 
logs with all that additional logging, thinking that delete would get me 
what I was looking for.  Thanks for pointing me in the right direction.

--

On 2021-02-09 3:44 am, Yassine Chaouche wrote:


Le 2/9/21 à 11:41 AM, Yassine Chaouche a écrit :


I have expunge in mail_log_events

mail_log_events = delete undelete expunge copy mailbox_delete 
mailbox_rename


Yassine

Oh yes and copy, because when you delete mail in roundcube it actually
copies it to the trash then expunge it from where it was, so you
should look after these two

Yassine.

Re: fts_encoder

[Joan Moreau]

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

On 2021-02-09 11:58, John Fawcett wrote:

On 08/02/2021 23:05, Stuart Henderson wrote: On 2021/02/08 21:33, Joan 
Moreau wrote: Yes , once again : output of the decoder is fine, I also 
put log inide the dovecot core to
check whether data is properly transmitted, and result is that it is 
(i.e. dovecot core

receives the proper output of pdftotext via the decoder

Now, that data is the /not/ the one sent from dovecot core to the fts 
plugin (and this is the
same issue for solr and all other plugins) Seems that something is 
different with your setup than John's and mine

then, as fts_solr rawlog (which is just the http request split into
.in and .out files) has the decoded file for us.

Did you try with the actual fts_solr plugin so it's a direct comparison
with what we see? There is no need for a real solr server, just point 
it

at any http server (or I guess netcat listening on a port will also do)
with

mail_plugins = fts fts_solr

plugin {
fts_autoindex = yes
fts = solr
fts_solr = url=http://127.0.0.1:80/ rawlog_dir=/tmp/solr
}

If that is not showing decoded for you then I suppose there's some
problem on the way into/through fts. And if it does show as decoded
then perhaps fts_solr is doing something slightly different than the
places you're examining in fts and your plugin, and that might give
a point to work backwards from.
 I'd also recommend Joan to look into some of the potential 
configuration

issues I mentioned in my first reply and if the problem persists, post
some clear evidence.

John

Re: fts_encoder

[John Fawcett]

On 08/02/2021 23:05, Stuart Henderson wrote:
> On 2021/02/08 21:33, Joan Moreau wrote:
>> Yes , once again : output of the decoder is fine, I also put log inide the 
>> dovecot core to
>> check whether data is properly transmitted, and result is that it is (i.e. 
>> dovecot core
>> receives the proper output of pdftotext via the decoder
>>
>> Now, that data is the /not/ the one sent from dovecot core to the fts plugin 
>> (and this is the
>> same issue for solr and all other plugins)
> Seems that something is different with your setup than John's and mine
> then, as fts_solr rawlog (which is just the http request split into
> .in and .out files) has the decoded file for us.
>
> Did you try with the actual fts_solr plugin so it's a direct comparison
> with what we see? There is no need for a real solr server, just point it
> at any http server (or I guess netcat listening on a port will also do)
> with
>
> mail_plugins = fts fts_solr
>
> plugin {
>   fts_autoindex = yes
>   fts = solr
>   fts_solr = url=http://127.0.0.1:80/ rawlog_dir=/tmp/solr
> }
>
> If that is not showing decoded for you then I suppose there's some
> problem on the way into/through fts. And if it does show as decoded
> then perhaps fts_solr is doing something slightly different than the
> places you're examining in fts and your plugin, and that might give
> a point to work backwards from.
>
I'd also recommend Joan to look into some of the potential configuration
issues I mentioned in my first reply and if the problem persists, post
some clear evidence.

John

Re: Problem enabling the mail_log plugin

[Yassine Chaouche]

Le 2/8/21 à 5:03 AM, Mike Quigley a écrit :


 I see so difference in /var/log/mail.info & /var/log/syslog


Did you configure it to use syslog ? my config puts dovecot logs in 
/var/log/dovecot


Yassine.

Re: Problem enabling the mail_log plugin

[Yassine Chaouche]

Le 2/9/21 à 11:41 AM, Yassine Chaouche a écrit :

I have expunge in mail_log_events

  mail_log_events = delete undelete expunge copy mailbox_delete 
mailbox_rename



Yassine

Oh yes and copy, because when you delete mail in roundcube it actually
copies it to the trash then expunge it from where it was, so you
should look after these two

Yassine.

Re: Problem enabling the mail_log plugin

[Yassine Chaouche]

I have expunge in mail_log_events

  mail_log_events = delete undelete expunge copy mailbox_delete 
mailbox_rename



Yassine

Le 2/8/21 à 5:03 AM, Mike Quigley a écrit :


I need to track some issues with deleted messages so I have been 
trying to set up the mail_log plugin.  I have Dovecot v2..27 running 
on Debian 9.  I have configured /etc/dovecot/conf.d/10-logging.conf, 
20-imap.conf, and 20-lmtp.conf and restarted dovecot, but I see so 
difference in /var/log/mail.info & /var/log/syslog when I delete a 
message from my Inbox in Roundcube.  Here is the abbreviated output 
from doveconf -n:


# 2.2.27 (): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.16 ()
# OS: Linux 4.9.0-14-amd64 x86_64 Debian 9.13 ext4

plugin {
mail_log_events = delete undelete mailbox_delete mailbox_rename
mail_log_fields = uid box msgid size
sieve = ~/.dovecot.sieve
sieve_after = /etc/dovecot/sieve-after
sieve_dir = ~/sieve
}

protocols = " imap lmtp sieve pop3"

protocol lmtp {
mail_plugins = " sieve notify mail_log"
}

protocol imap {
mail_max_userip_connections = 50
mail_plugins = " notify mail_log"
}

What am I missing?

Re: Getting panic in http-client-request.c: line 1240 during indexing on Ubuntu 20.04

[@lbutlr]

On 07 Feb 2021, at 17:32, John Fawcett  wrote:
> On 07/02/2021 20:15, @lbutlr wrote:
>> On 07 Feb 2021, at 02:07, @lbutlr  wrote:
>>> On 06 Feb 2021, at 11:06, John Fawcett  wrote:
 19.08.20 
>>> Is that a malformed ISO date 2019-08-20 or a truncated europeans style 
>>> 19-08-2020?
>> Either way, I cannot find the message in my dovecot folder.
>> 
>> Closest I can find is Message-ID: 
>> <20200820141341.ga1...@meili.valhalla.31bits.net> from the 2020-08-20 at 
>> 16:13:52 but there is no patch in that mail.
>> 
> here's the post in the list archives
> 
> https://dovecot.org/pipermail/dovecot/2020-August/119703.html

Thanks, wonder why I am missing it, but glad to have read it now.

Seems like an extremely simple (and obvious) fix?

-- 
"Why do you wear that stupid bunny suit?" "Why are you wearing that
stupid man suit?"