similar to: Batching quota clone updates

Hello, I'm using 2.1.7 with seive and mysql quotas. We had an outage the other day where the database server where quotas are stored was not available for a short period of time. In dovecot land, the following types of errors occured in that scenario: Oct 26 22:19:01 grosbeak dovecot: lda(example at riseup.net): Error: Internal quota calculation error Oct 26 22:19:01 grosbeak dovecot:

> ---------- Original Message ---------- > From: Aki Tuomi <aki.tuomi at dovecot.fi> > To: micah anderson <micah at riseup.net> > Date: December 16, 2016 at 11:25 PM > Subject: Re: making a plugin encrypt index data > > When we released our encryption plugin, mail-crypt, it's capabilities include fs-crypt. This can be used to encrypt things like FTS indexes

Hello, If one passes the -p option for a non-standard port to ssh-keyscan when using the -f option to pull hosts from a file, it results in a known_hosts entry that is incorrect: micah at muck$ cat /tmp/try 199.254.238.47 micah.riseup.net,199.254.238.47 ssh-keyscan -t rsa -p 4422 -f /tmp/try > /tmp/known micah at muck$ cat /tmp/known [micah.riseup.net,199.254.238.47]:4422 ssh-rsa

Hello, I'm encrypting mail on disk using a plugin[0], but the index files are not encrypted (specifically the dovecot.index.cache can be read). I want to do is encrypt index on disk, so I'm looking for how a plugin can achieve that by hooking into the right locations. Is that easily possible in a plugin? I can turn off those indexes by passing INDEX=MEMORY, but that isn't possible

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I''ve been trying out some configurations and been frustrated because they weren''t working how I would expect. After trying practically everything I could think of, I tried removing everything except the most basic elements to see what was going on. It turns out that my client is thinking that there is no configuration change, when

I have been working on converting people from courier maildir -> dovecot mdbox and during some of the dsync runs I'm seeing the quota_exceeded_message be printed as an Error: dsync(<user>): Error: Can't save message to mailbox INBOX: You are over quota. To avoid losing mail, immediately empty your Trash and Sent folders and \ delete emails with large attachments.

On 02 Apr 2015, at 03:59, micah anderson <micah at riseup.net> wrote: > > > Hello, > > I'm using 2.2.13 on Debian stable, and I perform regular dsync > backups. Typically if there is an error, dsync can recover from it the > next time it is run, but I've been encountering a new error that doesn't > seem to self-heal: > > # /usr/bin/dsync -u gae

The load on our machines has gotten too high, so I started to see log messages that directed me to look at this page for config changes: https://pad.riseup.net/redirect#http%3A//wiki2.dovecot.org/SocketUnavailable One of the things I wanted to do on that page was to set the: service imap { service_count = 100 } but when I added that to the service imap block, and restarted dovecot, I see this

https://bugzilla.mindrot.org/show_bug.cgi?id=2479 Bug ID: 2479 Summary: ssh-keyscan non-standard port broken Product: Portable OpenSSH Version: 6.9p1 Hardware: amd64 OS: Linux Status: NEW Severity: normal Priority: P5 Component: ssh-keyscan Assignee: unassigned-bugs at

Hello, I'm using 2.2.13 on Debian stable, and I perform regular dsync backups. Typically if there is an error, dsync can recover from it the next time it is run, but I've been encountering a new error that doesn't seem to self-heal: # /usr/bin/dsync -u gae backup ssh -i /root/.ssh/id_rsa backmaildir at internal.example /usr/bin/dsync -u micah dsync-remote(micah): Error:

Restoring a user's mailbox yesterday resulted in 'doveadm import' panic'ing with an assertion failure and giving a backtrace: /usr/bin/doveadm import -u <user> mdbox:/maildir/riseup.net/a/<user>/.daily.1/mdbox restored_from_backups/daily1 all doveadm(<user>): Error: Transaction log

-- Previously Posted to FreeBSD-questions Update: I've changed the RAM in the machine. That seemed to fix the problem for a little bit, but the problem has started occuring again. Also, I'm not subscribed to the list, so please reply to this message directly. Thanks for all your help. -- Hello, Recently, I've been having kernel panics on 4.8RC. This made me upgrade to

I got tired of restarting my puppetmaster when it stopped responding and finally switched to mongrel last night. When running under mongrel, what sort of concurrent connection rates are people able to get? I dont know how many individual puppetmaster processes I should spawn, or how to tell when I should span more. Perhaps I need more than two, because this morning I had a look at how

Package: logcheck Version: 1.2.41 Severity: minor man (8) logcheck says: For hints on how to maintain rules, see README.logcheck-database.gz, but this file is not included in /usr/share/doc/logcheck. micah -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel:

I really like the feature where you can define quota rules with percents which trigger off of the default values[0] (so you can set the Trash to allow for 10% more of the user's quota for example). What I would really love in dovecot would be for the ability to configure a quota rule for dovecot-lda. I would like to configure things so we don't bounce emails for users until they are well

I've noticed that http://wiki2.dovecot.org/Quota/Configuration is out of date, it says: plugin { quota = maildir:User quota quota_rule = *:storage=1GB # 10% of 1GB = 100MB quota_rule2 = Trash:storage=10%% # 20% of 1GB = 200MB quota_rule3 = Spam:storage=20%% } but if you use the '10%%' notation, dovecot complains, and *also* incorrectly: dovecot: imap(test at

It took me forever to figure out why I couldn't tftp boot into memtest86+, I had the file "memtest86+.bin" installed into my tftproot, and it was being loaded when I selected that menu item, but it would result in a series of repeating numbers on the left hand side of the screen. Eventually, after trying a million different things, and then asking someone I know who has fought

Due to the incompatibilities with the dsync protocol version between 2.1 and 2.2, I am unable to use dsync to move users to a new machine where we have 2.2.5 setup. This wouldn't normally be a problem, as I could just rsync the user's mdbox and dovecot would happily do the right thing. However, on the new system I've placed the indexes into a faster storage medium, where on the older

I updated my Solaris 8 machines from openssh-2.3.0p1 to 2.5.1p1 yesterday and it fixed the cron/audit issue but now root logins are no longer permitted. I updated it to 2.5.1p2 this morning and that is still the case: golfer:/[207]# ssh -v tsunami OpenSSH_2.5.1p2, SSH protocols 1.5/2.0, OpenSSL 0x0090600f debug: Reading configuration data /var/ssh/ssh_config debug: Applying options for *

Hello, I'm trying to find out what the different 'doveadm mailbox create' error codes are. I've been looking through the source, but I can't seem to find them. I did determine that '65' happens when "Error: Can't create mailbox x: Mailbox already exists", but I've also received error 67, and the more mysterious error code 16640. Thanks for any