search for: purges

So I have the following: define nagios::service ( $nagios_template = ''service-template'', $host_name = $fqdn, $service_groups = '''', $contact_groups = $default_contact_group, $max_check_attempts = 3, $dependency = false, $dependent_host = $fqdn, $dependent_service = '''', $check_command = '''' ) {

I am using mdbox storage format. As far as I know, ?doveadm purge? does a complete purge. The time and disk activity would be proportional to the number mdbox files on the storage. The purge time could be huge. I wonder if there is some way of doing a kind of incremental purge, stopping/restarting purging, etc. Purging by file range would be nice too. Advice? Thanks Enviado desde mi iPhone

Is there a way to exec something on purge?

I have a little issue with purging. I use: file { [''/etc/shorewall/puppet'',''/etc/shorewall/puppet/rules'']: ensure => directory, mode => 0700, recurse => true, purge => true, } but purging does not work, i can do a touch

I am using stored configs to manage my nagios host and services checks and I have run into a problem that I have been unable to solve. When the stored configs are purged from puppet the nagios server correctly removes them from the services and hosts file but does not notify the nagios service and instead throws an error. So the entries are still there and nagios still reports on them until

On 24/8/20 7:12, Fabien KOCIK wrote: > First, extract user list using doveadm users '*'. > Then process this list to fit your needs (seven parts for a week and a > part processed by week day for example). > Finally, use -u option of doveadm purge into a loop. This is a good idea for installations with tons of users. Good point. I would be personally interested in incremental

Hello, I'm facing an issue where deleted emails keep re-appearing after my mailbox index gets recreated.??I'm running version 2.2.36 of dovecot, but I tested the same scenario under 2.3.10. I'm also using mdbox, autoexpunge, and using dovecot replication. I've had several instances now where some expunged emails show up again in a mailbox. I noticed this error: doveadm: Error:

I have the following define... define puppet::module_dir { if $name { include puppet file { "${puppetdir}/modules/${name}": ensure => directory, mode => 0755, purge => true, recurse => true, } } } I call it like so: puppet::module_dir { "main" } puppet::module_dir

But is that not adviced in the manual[1]? I am also in the process of setting up dovecot behind a haproxy. Still testing with this. I was wondering why one would choose haproxy and not eg dovecot proxy (with director) [1] https://wiki2.dovecot.org/HAProxy -----Original Message----- From: Zelic Bojan [mailto:bojan.zelic at kudelskisecurity.com] Sent: woensdag 26 augustus 2020 23:39 To:

I have a rather large and active mdbox (28 GB, 3M mess, 1200 deliveries/day). I usually have no problems working with those mails, and there is some batch processing going on (via doveadm). Every few weeks I try my luck running doveadm purge, and this a) crunches about 5GB (to be expected), b) takes rather long (ok), c) leads to long stretches of blocked mdbox, which is the problem. I always

Hi, I think you can achieve file range approach using a small piece of shell script. First, extract user list using doveadm users '*'. Then process this list to fit your needs (seven parts for a week and a part processed by week day for example). Finally, use -u option of doveadm purge into a loop. That is just a trivial first idea. You can notice that it will trigger a doveadm

?I managed to figure this out. Just wanted to follow up if anyone in the future encounters the same issue. I am using HAProxy along with dovecot replication. When an email comes in... it is round robin'd to each of the 2 dovecot/postfix servers. I have postfix running on each server and it uses the local dovecot LMTP service for storing the mails. We sometimes get surges of emails(hundreds

Hi, I know that a lot of work has been done regarding doveadm server, but I'm still experiencing easily reproducible segfault crashes of doveadm-server with 2.1.16 when running the following command in a 4 node director/mailbox cluster: /usr/bin/doveadm -c /etc/dovecot-director/dovecot-director.conf -D purge -A The dovecot-error.log shows the following errors (addresses anonymized): Apr

Should this work? # --- remove any cronjobs that are not managed by puppet. resources { "cron": purge => true } I get the following error. Resources[cron]: Failed to generate additional resources: You must specify a title for objects of type Puppet::Type::Cron Ben

> > On 24/08/2020 08:30 Jesus Cea <jcea at jcea.es> wrote: > > > > > > I would be personally interested in incremental purge per user. My > > personal IMAP account, for instance, has at this moment about 40GB > > of mdbox files. I keep most of my email for decades, but sure I > > could free some space doing a purge, but I am scared of trying with

Running "doveadm purge" with both -D and -v parms, and both -A and -u options, I don't see much in the way of output. doveadm -v purge -u username just returns with no output doveadm -v purge -A returns no output for most users - for my own mailbox it yields "20 / 21" -D returns the same, along with messages about skipping plugin modules. Is this normal? I'm

Hi all, Please excuse me if someone has already offered this, but I think the Apt provider should, in addition to -y and -q, also do --purge. This will remove config files and keeps /etc cleaner on the whole. Just a suggestion. Great product and keep up the good work etc. -- Gegroet, Tim (tim|mac or tim|imac on irc)

We've finally (!) started to put some users on mdbox instead of maildir, and now I'm wondering about the purge step. As we're running GPFS for the mailboxes (and dovecot director in front of every dovecot service), is it important to run the "doveadm purge -u $user" on the same host as $user is logged into to avoid index corruption ? If so, will we need to run the

# 2.1.10: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-44-server x86_64 Ubuntu 10.04.4 LTS doveadm -c /etc/dovecot-director/dovecot-director.conf -D purge -A shows the following message in the log when iterating the 49th user: Oct 17 00:47:17 10.129.3.233 dovecot: doveadm: Error: purge: invalid option -- 'e' Oct 17 00:47:17 10.129.3.233 dovecot: doveadm(someuser at example-ll.org):

Hi, I do store mail in mdbox format of 150m in size (dovecot 2.3.9). Once in a while I do experience mdbox files of smaller size, even after applying 'doveadm purge' and previous expunges by the users. like: -rw------- 1 vmail dovecot 104854595 Feb 9 2019 /var/mail/.maildirs/userX/storage/m.22 -rw------- 1 vmail dovecot 29088478 Mar 8 2019