similar to: Dovecot consulting companies

I forked the wiki to http://wiki1.dovecot.org/ is the old docs for v1.x http://wiki2.dovecot.org/ is the new docs for v2.0 For now wiki.dovecot.org points to wiki1, but once v2.0 is released I'll change it to point to wiki2. I symlinked the user directory, so users should stay synced between the wikis. The main reason for wiki2 is to be able to describe Dovecot v2.0's actual behavior

On 15 May 2018, at 12.06, Timo Sirainen <tss at iki.fi> wrote: > > If you look at .176's error log, do you see an error about "director_consistent_hashing settings differ between directors"? Have you set director_consistent_hashing=yes in the old directors? That is needed now, because the old non-consistent-hashing method is obsoleted. Unfortunately there's no easy

> On 03 Dec 2015, at 16:09, Thomas Leuxner <tlx at leuxner.net> wrote: > > * Timo Sirainen <tss at iki.fi> 2015.12.03 14:51: > >> + Added mailbox { autoexpunge=<time> } setting. See >> http://wiki2.dovecot.org/MailboxSettings for details. > > namespace inbox { > mailbox Trash { > autoexpunge = 5 days > special_use = \Trash >

Hello Everyone, In preparation for an upcoming talk, I would like to assemble a list of companies that provide consulting, services, products, or training for R. I am already aware of a number of such companies including (in alphabetical order): BlueReference <http://inference.us> Insightful <http://www.insightful.com> Metrum Institute <http://www.metruminstitute.org>

On 27 Oct 2016, at 15:29, Tanstaafl <tanstaafl at libertytrek.org> wrote: > > On 10/26/2016 2:38 AM, Gandalf Corvotempesta > <gandalf.corvotempesta at gmail.com> wrote: >> This is much easier than dovecot replication as i can start immedialy with >> no need to upgrade the old server >> >> my only question is: how to manage the email received on the

Thanks for the replies Joe. Yes, it does seem that Gluster is a very in-demand expertise. And it's hard to justify the cost of Red Hat's commercial offering without first putting a POC in place to confirm viability. Thanks again, HB On Mon, Dec 18, 2017 at 12:08 PM, Joe Julian <joe at julianfamily.org> wrote: > Yeah, unfortunately that's all that have come forward as

http://dovecot.org/releases/2.2/dovecot-2.2.7.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.7.tar.gz.sig * Some usage of passdb checkpassword could have been exploitable by local users. You may need to modify your setup to keep it working. See http://wiki2.dovecot.org/AuthDatabase/CheckPassword#Security + auth: Added ability to truncate values logged by auth_verbose_passwords

http://dovecot.org/releases/2.2/dovecot-2.2.7.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.7.tar.gz.sig * Some usage of passdb checkpassword could have been exploitable by local users. You may need to modify your setup to keep it working. See http://wiki2.dovecot.org/AuthDatabase/CheckPassword#Security + auth: Added ability to truncate values logged by auth_verbose_passwords

Hi, Sorry, I just saw the post <http://lists.gluster.org/pipermail/gluster-users/2017-December/033053.html> from last week I have seen this page <https://www.gluster.org/support/> before, however other than Red Hat (who I've spoken with and we're not ready to pay for their enterprise gluster offering) these companies appear to all be located in Europe. Ideally, it would be

> From: Timo Sirainen <tss at iki.fi> > Subject: Re: [Dovecot] general advice sought > Message-ID: <1315830847.7326.48.camel at hurina> > Content-Type: text/plain; charset="ISO-8859-15" > > On Mon, 2011-09-12 at 13:11 +0100, Alan Brown wrote: >> I'd like to hear the thoughts of list members on which type of storage >> method seems

* Timo Sirainen <tss at iki.fi> 2015.12.03 14:51: > + Added mailbox { autoexpunge=<time> } setting. See > http://wiki2.dovecot.org/MailboxSettings for details. namespace inbox { mailbox Trash { autoexpunge = 5 days special_use = \Trash } } I'm using autoexpunge on the Trash mailbox. Looking at the wiki text I'm unclear on how to limit it to a specific

Hi, Is it possible to have a static user database along with an LDAP password database and *not* be forced to set "allow_all_users=yes" for the userdb? The wiki page on static user database says "Normally static userdb handles this by doing a passdb lookup instead." How should the passdb behave in order for this to work? In my tests (on a test server) I am using

Yeah, unfortunately that's all that have come forward as available. I think the demand for gluster expertise is just so high and the pool of experts so low that there's nobody left to do consulting work. On 12/18/2017 12:04 PM, Herb Burnswell wrote: > Hi, > > Sorry, I just saw the post > <http://lists.gluster.org/pipermail/gluster-users/2017-December/033053.html>

I'm trying to get the snarf plugin working with dovecot 2.0.7. Specifically, I want to use the UW-IMAP style optional snarfing. I'm looking at the wiki2 documentation. The first question is whether the UW-IMAP optional snarfing will require any changes to the mail_location. The first section suggests (but doesn't specifically state, which I'd propose be clarified) that

We've been collecting some stats to see what kind of benefits UP/SquirrelMail's IMAP Proxy in for our SOGo webmail users. Dovecot is running in High-performance mode http://wiki2.dovecot.org/LoginProcess with authentication caching http://wiki2.dovecot.org/Authentication/Caching During the weekend two servers (webmail3 and webmail4) has been running with local imapproxy and two servers

Hi, Can anyone suggest any companies or other that do Gluster consulting? I'm looking for guidance on on configuration, best practices, trouble shooting, etc. Any guidance is greatly appreciated. HB -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20171218/d788d4ac/attachment.html>

http://dovecot.org/releases/2.2/dovecot-2.2.10.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.10.tar.gz.sig I've been really busy the last few months, as I guess people in Dovecot mailing list have seen since I haven't been very responsive. There are at least some dsync bugs I haven't had time to look into yet. The busyness probably continues for a while more, but the next year is

http://dovecot.org/releases/2.2/dovecot-2.2.10.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.10.tar.gz.sig I've been really busy the last few months, as I guess people in Dovecot mailing list have seen since I haven't been very responsive. There are at least some dsync bugs I haven't had time to look into yet. The busyness probably continues for a while more, but the next year is

http://dovecot.org/releases/2.2/dovecot-2.2.11.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.11.tar.gz.sig I haven't had time to read through the Dovecot mailing list yet, so there are likely some reported bugs that haven't been fixed yet. I'll try to get to them next week in San Francisco. (Probably can't get much done this week in Tokyo.) In the mean time here's v2.2.11

http://dovecot.org/releases/2.2/dovecot-2.2.11.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.11.tar.gz.sig I haven't had time to read through the Dovecot mailing list yet, so there are likely some reported bugs that haven't been fixed yet. I'll try to get to them next week in San Francisco. (Probably can't get much done this week in Tokyo.) In the mean time here's v2.2.11