> On 9 May 2024, at 19:45, dovecot-requ...@dovecot.org wrote:
>
> Francis Augusto Medeiros-Logeay via dovecot skrev den 2024-05-09 12:29:
>
>>> If you want to analyze emails, why not do it with scheduled crons
>>> after they are archived?
>
> maybe ask for skip older then one day in here
>
This may help, see the post from 9/9/2021:
https://github.com/goauthentik/authentik/issues/1234
On 5/9/2024 2:50 PM, Francis Augusto Medeiros-Logeay via dovecot wrote:
On 9 May 2024, at 19:45, Aki Tuomi wrote:
On 09/05/2024 20:15 EEST Francis Augusto Medeiros-Logeay via dovecot
mailto:d
> On 9 May 2024, at 19:45, Aki Tuomi wrote:
>
>
>> On 09/05/2024 20:15 EEST Francis Augusto Medeiros-Logeay via dovecot
>> mailto:dovecot@dovecot.org>> wrote:
>>
>>
>> Hi,
>>
>> I was wondering:
>>
>> 1 - Is it possible to configure authentication methods per user? For
>> example, o
> On 9 May 2024, at 19:45, Aki Tuomi wrote:
>
>
>> On 09/05/2024 20:15 EEST Francis Augusto Medeiros-Logeay via dovecot
>> mailto:dovecot@dovecot.org>> wrote:
>>
>>
>> Hi,
>>
>> I was wondering:
>>
>> 1 - Is it possible to configure authentication methods per user? For
>> example, o
On 09/05/2024 20:15 EEST Francis Augusto Medeiros-Logeay via dovecot
wrote:
Hi,
I was wondering:
1 - Is it possible to configure authentication methods per user? For
example, oauth2 for most users, but plain for others?
2 - I had a f
> On 9 May 2024, at 12:55, dovecot-requ...@dovecot.org wrote:
>
> Francis Augusto Medeiros-Logeay via dovecot skrev den 2024-05-09 11:28:
>
>> Actually, I don’t know here if that’s the sieve that’s slowing down the
>> process, or if it is something else.
>> I see that yeah, sa-learn takes a li
Hi,
I was wondering:
1 - Is it possible to configure authentication methods per user? For example,
oauth2 for most users, but plain for others?
2 - I had a feeling that when oauth2 authentication fails, dovecot tries to
authenticate via plain with the received token. Doesn’t seem logical, but I
Francis Augusto Medeiros-Logeay via dovecot skrev den 2024-05-09 12:29:
If you want to analyze emails, why not do it with scheduled crons
after they are archived?
maybe ask for skip older then one day in here
https://github.com/isbg/isbg/tree/master
while roundcube just set the needed flag
Hi,
I was running dovecot 2.3.7.2 with ubuntu 20.04
Lastweek, I upgrade to Ubuntu 22.04 and dovecot 2.3.16
My configuration was migrated and all is fine expected the sieve
duplicate. It does notwork and i don't understand why.
% doveconf -n
# 2.3.16 (7e2e900c1a): /etc/dovecot/dovecot.conf
# Pig
Hi,
I was running dovecot 2.3.7.2 with ubuntu 20.04
Lastweek, I upgrade to Ubuntu 22.04 and dovecot 2.3.16
My configuration was migrated and all is fine expected the sieve
duplicate. It does notwork and i don't understand why.
% doveconf -n
# 2.3.16 (7e2e900c1a): /etc/dovecot/dovecot.conf
# Pig
> On 2024-05-09 12:03, Marc wrote:
> > I see report-ham, instead of archiving? I am not entirely sure if this
> > is an efficient approach to archiving. My users can only set a flag for
> > 'auto archiving' via sieve and then 3 months after every year messages
> > are being moved by cron jobs, and
=
On 2024-05-09 12:03, Marc wrote:
I see report-ham, instead of archiving? I am not entirely sure if this
is an efficient approach to archiving. My users can only set a flag for
'auto archiving' via sieve and then 3 months after every year messages
are being moved by cron jobs, and modifica
Francis Augusto Medeiros-Logeay via dovecot skrev den 2024-05-09 11:28:
Actually, I don’t know here if that’s the sieve that’s slowing down the
process, or if it is something else.
I see that yeah, sa-learn takes a little while to execute. But maybe
the issue is that Dovecot doesn’t seem to
rel
I see report-ham, instead of archiving? I am not entirely sure if this is an
efficient approach to archiving. My users can only set a flag for 'auto
archiving' via sieve and then 3 months after every year messages are being
moved by cron jobs, and modification logs are put into their accounts. T
> I noticed that my sieve rules are taking a very long time when archiving
> messages. I can see on my logs that every message takes about two-three
> seconds to be evaluated.
>
> I also noticed this happens for a few accounts. Do you know what could be
> causing this?
>
> Best,
> Francis
>
---
Francis Augusto Medeiros-Logeay
Oslo, Norway
On 2024-05-09 10:11, Aki Tuomi wrote:
On 09/05/2024 10:46 EEST Francis Augusto Medeiros-Logeay via dovecot
wrote:
Hi,
I have a Dovecot server on Ubuntu 22.04, which works fine with Oauth2.
I am building a new container based on Ubuntu 24.
> On 09/05/2024 10:46 EEST Francis Augusto Medeiros-Logeay via dovecot
> wrote:
>
>
> Hi,
>
> I have a Dovecot server on Ubuntu 22.04, which works fine with Oauth2. I am
> building a new container based on Ubuntu 24.04. IMAP seems to work fine with
> plain authentication, but oauth2 fails
Hi,
I have a Dovecot server on Ubuntu 22.04, which works fine with Oauth2. I am
building a new container based on Ubuntu 24.04. IMAP seems to work fine with
plain authentication, but oauth2 fails (Dovecot v2.3.21). Same configuration as
before.
However, I got this message:
May 09 09:41:57 aut
I noticed that my sieve rules are taking a very long time when archiving
messages. I can see on my logs that every message takes about two-three seconds
to be evaluated.
My sieve for the Archive is this:
cat /var/mail/vmail/mail/sieve/global/report-ham.sieve
require ["vnd.dovecot.pipe", "copy"
19 matches
Mail list logo
