similar to: index.html keeps getting regenerated

Quick question: How does dovecot keep the message headers index file updated? Eg: if my MDA delivers an extra 10 messages while I'm logged in. How does the message index get updated? At what points is it regenerated? Thanks, Paul

This is a patch for the regenerated configure related files. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20091013/eb1ed755/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: haiku.patch Type: text/x-patch Size: 11388 bytes Desc: not available URL:

Hi, We've been using dovecot in the lab now for quite a while and really like the results we're seeing. Underlying dovecot we're using maildir mailboxes. We have the need to manually remove maildir files from time to time. That is, by hand (we'll, actually by script) but not via imap or pop. Dues to dovecot's index caching (which I might add, we love most of the time)

On Sat, May 16, 2015 at 04:53:33PM +0100, Etienne Dechamps wrote: > I believe there is a design flaw in the way SPTPS key regeneration > works, because upon reception of the KEX message the other nodes will > send both KEX and SIG messages at the same time. However, the node > expects SIG to arrive after KEX. Therefore, there is an implicit > assumption that messages won't

Hello, after switching from version 2.2.7 to 2.2.7 I miss the loglines which say: ssl-params: Generating SSL parameters ssl-params: SSL parameters regeneration completed The configuration has not been changed and reads: | # 2.2.7: /usr/local/dovecot/etc/dovecot/dovecot.conf | # OS: Linux 2.6.35.14-106.fc14.i686.PAE i686 Fedora release 14 (Laughlin) ext3 | auth_mechanisms = plain login |

Hi, I'm currently trying to troubleshoot what appears to be a very subtle bug (most likely a race condition) in SPTPS that causes state to become corrupted during SPTPS key regeneration. The tinc version currently deployed to my production nodes is git 7ac5263, which is somewhat old (2014-09-06), but I think this is still relevant because the affected code paths haven't really changed

Hello everyone, I'm having problems with DTMF regeneration on my incoming PRI. I see that when the calling party transmits a DTMF digit, it gets generated at my end at a slower rate. Normally this would not be a problem, but several of these calling party are alarm control panels that send DTMF digits at a pretty fast clip and require that the DTMF timing be left intact. I noticed that

I sent you a pull request that addresses the general issue, at least for the short term: https://github.com/gsliepen/tinc/pull/83 On 16 May 2015 at 19:36, Guus Sliepen <guus at tinc-vpn.org> wrote: > On Sat, May 16, 2015 at 04:53:33PM +0100, Etienne Dechamps wrote: > >> I believe there is a design flaw in the way SPTPS key regeneration >> works, because upon reception of

Hi there, My name is Angelica and I was just checking out your page at http://us1.samba.org/samba/docs/SambaIntro.html and noticed that the the link to the Dilbert site on http://www.unitedmedia.com/comics/dilbert/ isn't working. I'm a Dilbert fan myself :) so I thought I'd mention a page I have bookmarked: http://www.answerconnect.com/articles/dilbert-fans It has a bunch of

I went from a nightly of about 20051117 or so (about alpha4 generation) to 1.0beta1 yesterday, and dovecot is now spinning the CPU furiously apparently every ~10 minutes per: Jan 18 13:04:36 server dovecot: SSL parameters regeneration completed Jan 18 13:14:14 server dovecot: SSL parameters regeneration completed Jan 18 13:24:00 server dovecot: SSL parameters regeneration completed Jan 18

This is causing me to --clean the first key, and --sign again after the second run of puppetd --test First Run: [root@asmc1n2 ~]# puppetd --test warning: peer certificate won''t be verified in this SSL session. info: Creating a new certificate request for asmc1n2.dev.gridapp.com info: Creating a new SSL key at /var/lib/puppet/ssl/private_keys/asmc1n2.dev.gridapp.com.pem ... Second

I goofed adding some machines to my domain so now I have to do it all over. I removed the secrets.tdb and MACHINE.SID files, but when I join the domain again, the MACHINE.SID is not regenerated. How do I force them to be correctly regenerated on 2.2.4? Here's what I'm doing: 1. kill smb and winbind 2. delete secrets.tdb and MACHINE.SID 3. remove from NT4 PDC 4. add machine to NT4 PDC 5.

qemu-wrapper isn't regenerated if QEMUDIR is changed, so just delete it and force regeneration. Additionally we can drop the silent binary check, since check-with-upstream-qemu-1 already does a similar test with --version that will actually report an error to the user. --- Makefile.am | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/Makefile.am b/Makefile.am index

Greetings, I'm trying to track down and eliminate the sources of excessive disk activity in an idle system that is resulting in premature hard disk failure. Access time updates to inodes turned out to be the worst culprit, triggering writes every 35 seconds or so. Mounting filesystems with the noatime option fixed that problem. But not too far behind inode updates is the frequent

Hello! I've been trying for several hours to upload a few bits of data (not a file) from an html form to a server, and none of my variants have worked thus far. I've done some web searching, too. Anyway, here's the form: <form method="POST" action="mmsrequest"> <pre> UserID: <input type="text" NAME="userid"> Date :

On Sun, May 17, 2015 at 07:46:45PM +0100, Etienne Dechamps wrote: > I sent you a pull request that addresses the general issue, at least > for the short term: https://github.com/gsliepen/tinc/pull/83 Merged. > > You are right. The main issue with the SPTPS datagram protocol is that > > it actually doesn't handle any packet loss or reordering during > > authentication

Based on the recent found weaknesses in DH key exchange, http://weakdh.org/ I increased ssl_dh_parameters_length to 2048 bits, and found waited for 5+ minutes for dovecot to come back online after a restart. Unless you got a fast machine, the initialization of DH parameters can exceed your patience. Regeneration may not be a problem (if ssl_parameters_regenerate=0 or if Dovecot uses old

Is it possible to regenerate the index files, on other conditions than the mbox file being read? For instance, it would be nice if I could regenerate the index for a specific mbox whenever procmail delivers mail to it. If theres no existing solution, would it be possible to make a small script with something like "nc" that could send an imap command to dovecot, so that dovecot would

Dear all, I''ve the following problem with routing + NAT: If I''ve two ISP and I''m using two nexthop in default route with MASQUERADE on both ISP links, I see routing cache regenerated, but sometimes packets sent to a new link (after cache regeneration) uses wrong source address for masquerading. Here is the config. I''ve two links to outside via two

On Tue, Feb 12, 2019 at 11:05 AM Jonas Devlieghere via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Tue, Feb 12, 2019 at 10:54 AM Kostya Serebryany <kcc at google.com> wrote: > >> >> >> On Tue, Feb 12, 2019 at 10:45 AM Jonas Devlieghere <jonas at devlieghere.com> >> wrote: >> >>> Hi Kostya, >>> >>> I remember