similar to: config file includes

On Sun, Jan 13, 2013 at 10:26 AM, Tim Northover <t.p.northover at gmail.com> wrote: >> Good points David, I don't feel qualified to evaluate the differences >> between those versions though... Perhaps Richard or Doug could comment here? > > Unless I'm misreading the buildbots, we don't actually have anything > trying to build with MSVC. Have we considered how

On Sun, Jan 13, 2013 at 7:39 PM, David Blaikie <dblaikie at gmail.com> wrote: > On Sun, Jan 13, 2013 at 10:26 AM, Tim Northover <t.p.northover at gmail.com> > wrote: > >> Good points David, I don't feel qualified to evaluate the differences > >> between those versions though... Perhaps Richard or Doug could comment > here? > > > > Unless

Hi all, ok, I am running version v2.0.beta6 and the latest pigeonhole build to run managesieve and the sieve delivery filters... I am getting the following response from the managesieve port when connecting : Escape character is '^]'. "IMPLEMENTATION" "Dovecot" "SIEVE" "" "SASL" "PLAIN" "STARTTLS" "VERSION"

I have been trying to find information and possible issues with running a cluster of dovecot server with different versions without any luck. We have an existing cluster with dovecot v1.1.10 and tried migrating to a new cluster with dovecot v2.0.12. We ran into some issues when we moved traffic to the new cluster and have been unable to reproduce it in our own testing. We may need to put real

Hi, ok, I've compiled it a few times, and made sure all of my settings are correct, but the QUOTA is not appearing in the opening CAPA that comes with the greeting. I have it configured in the dovecot.conf like so: protocol imap { mail_plugins = quota imap_quota } and I can see when turning debugging on that the following is spit out when starting : Starting DovecotILoading modules

Hi all, We have put together a firmware for a range of inexpensive routers. It has been configured to provide optimum VoIP performance. We have internally tested it for number of months and it looks very good. You should be able to run it easily with 20+ phones on local network ( we still did not hit the upper limit ) assuming that you have bandwidth. Your VoIP will get prioritized over other

On Sat, March 17, 2007 10:51 pm, Timo Sirainen <tss at iki.fi> said: > Oh, and as for when the rewrite is in CVS, I'm not really sure. I'm > still wondering if I should put it there soon and make the release after > v1.0 be v2.0, or if I should first stabilize the current new CVS HEAD > features (which shouldn't take too long), do a v1.2 release and only > then

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

My understanding of the man page description of --exclude vs. --include is that the list of these is kept in order, and file names are searched against these parameters in that order for the first that matches and that one makes the decision. It doesn't seem to be working exactly as expected. But there is a factor involved that's making it unclear, which is whether or not *'s should

v1.1 has now: # Maximum number of connections allowed for a user. The limits are enforced # separately for IMAP and POP3 connections, so you can move this setting # inside protocol {} to have separate settings for them. NOTE: The user names # are compared case-sensitively, so make sure your userdb returns usernames # always using the same casing so users can't bypass this limit!

On Sun, Jan 13, 2013 at 5:18 AM, Matthieu M. <matthieu.monrocq at gmail.com> wrote: > Hello all, > > Using the Apache Wiki [1] I summed up what can be used simultaneously by gcc, > MSVC and clang. > > I mostly considered only the latest versions of the proposals where there were > several, where not there is a link to a note at the bottom. Furthermore I did > not

If anyone's interested, I updated my master/config rewrite to latest Dovecot v1.1 tree and added it to hg: http://hg.dovecot.org/dovecot-master-rewrite/ It probably doesn't work, but with the exception of plugins it compiles anyway. :) I'm thinking that maybe after v1.1.0 I could continue with the rewrite and create v2.0 after all instead of v1.2. Just look at how much cleaner

In v1.0 .. v1.1 deliver was writing incoming >128k mail to /tmp file (to avoid reading it all into memory). In v1.2 I moved it to user's home directory. This slowed deliveries for NFS users. Also people with filesystem quota had trouble since now user required twice as much available quota to save a message. The FS quota problem was "solved" by having quota-fs plugin change the

Hi Timo, ok, I have a large 2.07 NFS setup, and I have been monitoring error messages to make sure I catch things, and I've come across a lot of messages that come in pairs and look like this : Dec 01 17:48:35 lda(paul at xxxxxx.com): Error: write(/home/mailboxes/data/301/paul at xxxxxx.com/Maildir/tmp/1291254514.M620308P83269.mta2.scaledsystems.com) failed: Permission denied Dec 01

On Sun, Jan 13, 2013 at 9:57 AM, David Blaikie <dblaikie at gmail.com> wrote: > On Sun, Jan 13, 2013 at 5:18 AM, Matthieu M. <matthieu.monrocq at gmail.com> wrote: >> Hello all, >> >> Using the Apache Wiki [1] I summed up what can be used simultaneously by gcc, >> MSVC and clang. >> >> I mostly considered only the latest versions of the proposals

v1.1.0 is finally getting closer, so it's time to start planning what happens after it. Below is a list of some of the larger features I'm planning on implementing. I'm not yet sure in which order, so I think it's time to ask again what features companies would be willing to pay for? Sponsoring Dovecot development gets you: - listed in Credits in www.dovecot.org - listed in

I think I won't do any actual releases until it's mostly feature complete. Then maybe v1.1.alpha1 or v1.1.beta1. So if you want to test it before then, use CVS or the nightly snapshots. I'm planning on keeping v1.1 almost completely compatible with v1.0. There could be some minor configuration file changes, but for most people v1.0's dovecot.conf should work with v1.1. I want to

Hi Timo, ok, in my dovecot setup, I have a setting to ignore messages in the Spam folder (I will put my dovecot -n at the end of the message), and a strange thing appears to be happening. If I do a quota recalc on an account, It creates the maildirsize file correctly, without the contents of the Spam folder calculated into the total used. But, it looks like when a new spam email is delivered,

Hello! Let me smuggle 2 questions in 1 email: 1) I upgraded from 1.1.7 to 2.0.1, but couldn't get it to work, because the 'dovecot + postfix sasl howto' doesn't seem to be updated and the old sasl settings are incompatible with new version. How do I set up sasl with dovecot2 ? Is there any updated howto available? 2) In dovecot 1.1.7: my expire_plugin seems to work fine, new

I merged all the new features and latest v1.1 changes under one tree: http://hg.dovecot.org/dovecot-1.2/ The changeset order is kind of weird though. The timestamps jump all around. Wonder if there's a way to reorder them so that it looks more sane.. The status of the new features: 1. CONDSTORE extension is probably the largest change. It adds new "modification sequences" for