Re: sieve_after seems to not bring any effect to life in dovecot 2.3.13 dovecot-pigeonhole-0.5.13
# 2.3.13 (89f716dc2): /usr/local/etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.13 (cdd19fe3)
# OS: FreeBSD 12.2-RELEASE-p2 amd64
auth_mechanisms = plain login
debug_log_path = /var/log/dovecot/dovecot-debug.log
default_client_limit = 1400
disable_plaintext_auth = no
first_valid_gid = 6
imap_idle_notify_interval = 1 mins
last_valid_gid = 1000
last_valid_uid = 65532
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
log_path = /var/log/dovecot/dovecot.log
login_trusted_networks = (my ip address)
mail_fsync = never
mail_location = maildir:/usr/local/virtual/trash
mail_plugins = quota
maildir_stat_dirs = yes
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope encoded-character
vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy
include variables body enotify environment mailbox date ihave vacation-seconds
mmap_disable = yes
namespace inbox {
inbox = yes
location =
mailbox Drafts {
special_use = \Drafts
}
mailbox Junk {
auto = subscribe
special_use = \Junk
}
mailbox Sent {
auto = subscribe
special_use = \Sent
}
mailbox "Sent Messages" {
special_use = \Sent
}
mailbox Trash {
auto = subscribe
special_use = \Trash
}
prefix =
}
passdb {
args = /usr/local/etc/dovecot/dovecot-sql.conf
driver = sql
}
plugin {
quota = maildir:User quota
quota_rule = *:bytes=0
recipient_delimiter = +
sieve = file:~/sieve;active=~/.dovecot.sieve
sieve_after = /usr/local/etc/dovecot/sieve_after
sieve_extensions = +vacation-seconds
sieve_max_actions = 50
sieve_max_redirects = 50
sieve_max_script_size = 1M
sieve_redirect_envelope_from = recipient
sieve_vacation_default_period = 7d
sieve_vacation_max_period = 0
sieve_vacation_min_period = 1s
}
protocols = imap pop3 sieve
service auth {
unix_listener auth-client {
mode = 0660
user = mailnull
}
unix_listener auth-userdb {
group = mail
mode = 0660
user = mailnull
}
}
service imap-login {
process_limit = 1000
process_min_avail = 0
}
service imap {
process_limit = 8192
vsz_limit = 320 M
}
service managesieve-login {
inet_listener sieve {
port = 4190
}
process_min_avail = 0
service_count = 1
vsz_limit = 256 M
}
service pop3 {
process_limit = 8192
}
ssl_cert =
>>
>> 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
>
>
Re: sieve_after seems to not bring any effect to life in dovecot 2.3.13 dovecot-pigeonhole-0.5.13
Can you try turning on mail_debug=yes and see if it sheds any light why the
script(s) aren't executed?
Aki
> Data: 2021-02-11 12:46
> Nadawca: "Aki Tuomi"
> Adresat: "Bug Report" ; dovecot@dovecot.org;
>
> >
> >>
> >> 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
> >
> >
Monitoring Dovecot Replication
Hello, I have a cluster with two dovecot nodes with dovecot replication between them. The setup works fine and now I'm searching for a way to monitor the users so that I can get an information if the replication fails for one user for a longer time and I have to trigger the replication manually. Most of the time if I see a replication failure the self healing of dovecot replication repairs this in max. 10 min. I have tried different combinations of querying " doveadm replicator status '*' " and search for failed users and then send an alarm if one of fast sync, full sync or success sync reaches a threshold. But there is no combination that seems to be working if I only want to trigger this if I have to fix the replication manualy. Can someone tell me what I have to query to get only the user who's replication failed for a longer time (10 min +) and that I have to fix manually? Thank you. Oliver
Re: Monitoring Dovecot Replication
Hello, I wrote a little script for Check_MK (MRPE mode). If you want to try it I can send it to you. Andrea Il 12/02/21 11:47, MK ha scritto: > Hello, > > I have a cluster with two dovecot nodes with dovecot replication between > them. > The setup works fine and now I'm searching for a way to monitor the users so > that I can get an information if the replication fails for one user for a > longer time and I have to trigger the replication manually. Most of the time > if I see a replication failure the self healing of dovecot replication > repairs this in max. 10 min. > > I have tried different combinations of querying " doveadm replicator status > '*' " and search for failed users and then send an alarm if one of fast sync, > full sync or success sync reaches a threshold. But there is no combination > that seems to be working if I only want to trigger this if I have to fix the > replication manualy. > > Can someone tell me what I have to query to get only the user who's > replication failed for a longer time (10 min +) and that I have to fix > manually? > > Thank you. > > Oliver -- __ Ama e fa cio' che vuoi __ TIM San Marino S.p.A. Andrea Gabellini Engineering R&D TIM San Marino S.p.A. - https://www.telecomitalia.sm Via Ventotto Luglio, 212 - Piano -2 47893 - Borgo Maggiore - Republic of San Marino Tel: (+378) 0549 886237 Fax: (+378) 0549 886188 -- Informativa Privacy Questa email ha per destinatari dei contatti presenti negli archivi di TIM San Marino S.p.A.. Tutte le informazioni vengono trattate e tutelate nel rispetto della normativa vigente sulla protezione dei dati personali (Reg. EU 2016/679). Per richiedere informazioni e/o variazioni e/o la cancellazione dei vostri dati presenti nei nostri archivi potete inviare una email a priv...@telecomitalia.sm. Avviso di Riservatezza Il contenuto di questa e-mail e degli eventuali allegati e' strettamente confidenziale e destinato alla/e persona/e a cui e' indirizzato. Se avete ricevuto per errore questa e-mail, vi preghiamo di segnalarcelo immediatamente e di cancellarla dal vostro computer. E' fatto divieto di copiare e divulgare il contenuto di questa e-mail. Ogni utilizzo abusivo delle informazioni qui contenute da parte di persone terze o comunque non indicate nella presente e-mail potra' essere perseguito ai sensi di legge.
Re: Monitoring Dovecot Replication
Hi Andrea It would be great if oyu could post that here, as I (and possibly others) would also be interested. :) thanks, Steven -- https://steven.varco.ch/ > Am 12.02.2021 um 15:12 schrieb Andrea Gabellini > : > > Hello, > > I wrote a little script for Check_MK (MRPE mode). > > If you want to try it I can send it to you. > > Andrea > > Il 12/02/21 11:47, MK ha scritto: >> Hello, >> >> I have a cluster with two dovecot nodes with dovecot replication between >> them. >> The setup works fine and now I'm searching for a way to monitor the users so >> that I can get an information if the replication fails for one user for a >> longer time and I have to trigger the replication manually. Most of the time >> if I see a replication failure the self healing of dovecot replication >> repairs this in max. 10 min. >> >> I have tried different combinations of querying " doveadm replicator status >> '*' " and search for failed users and then send an alarm if one of fast >> sync, full sync or success sync reaches a threshold. But there is no >> combination that seems to be working if I only want to trigger this if I >> have to fix the replication manualy. >> >> Can someone tell me what I have to query to get only the user who's >> replication failed for a longer time (10 min +) and that I have to fix >> manually? >> >> Thank you. >> >> Oliver > > -- > __ > Ama e fa cio' che vuoi > __ > > TIM San Marino S.p.A. > Andrea Gabellini > Engineering R&D > TIM San Marino S.p.A. - https://www.telecomitalia.sm > Via Ventotto Luglio, 212 - Piano -2 > 47893 - Borgo Maggiore - Republic of San Marino > Tel: (+378) 0549 886237 > Fax: (+378) 0549 886188 > > > -- > Informativa Privacy > > Questa email ha per destinatari dei contatti presenti negli archivi di TIM > San Marino S.p.A.. Tutte le informazioni vengono trattate e tutelate nel > rispetto della normativa vigente sulla protezione dei dati personali (Reg. EU > 2016/679). Per richiedere informazioni e/o variazioni e/o la cancellazione > dei vostri dati presenti nei nostri archivi potete inviare una email a > priv...@telecomitalia.sm. > > Avviso di Riservatezza > > Il contenuto di questa e-mail e degli eventuali allegati e' strettamente > confidenziale e destinato alla/e persona/e a cui e' indirizzato. Se avete > ricevuto per errore questa e-mail, vi preghiamo di segnalarcelo > immediatamente e di cancellarla dal vostro computer. E' fatto divieto di > copiare e divulgare il contenuto di questa e-mail. Ogni utilizzo abusivo > delle informazioni qui contenute da parte di persone terze o comunque non > indicate nella presente e-mail potra' essere perseguito ai sensi di legge.
