similar to: inetd config - dovecot doesn't exits

In install file we can read that: sieve_<extension>_exec_timeout = 10s set timeout for executing program. But regardless of setting this value (say sieve_pipe_exec_timeout=86000) I got: --8<---------------cut here---------------start------------->8--- 2012-12-10 20:55:33 LDA(kjonca): Debug: sieve: action pipe: running program: maildrop.sh 2012-12-10 20:55:43 LDA(kjonca): Debug:

I have simple old message: --8<---------------cut here---------------start------------->8--- X-Mozilla-Status: 0011 X-Mozilla-Status2: 00000000 Date: Wed, 26 Jan 2000 13:38:41 +0100 From: Kamil Jonca <kjonca at localhost.localdomain> To: Somebody X <xx at tiger.com.pl> Subject: Re: Opisy Message-ID: <20000126133839.B2888 at localhost.localdomain> References:

Is any posibility to pass parameters/environment variables to deliver with sieve plugin? I have some procmail rules to decide where mail should go, which can't be migrated to sieve (uses external programs). So far I write it to maildirs, but I wonder to migrate to mdbox, and procmail can't handle it. Any ideas? KJ --

I have some archive mails in gzipped mboxes. I could use them with dovecot 1.x without problems. But recently I have installed dovecot 2.0.12, and they are slow. very slow. Creating index files takes about 10 minutes for ~20M file with 560 messages for bzipped mbox, for gzipped is little better but still unusable :( Stracing dovecot process shows that every ~ 20 messages it rereads complete mbox

Hello sorry, for bothering you with this problem, but I ca't find solutions. I write small PAM module, and I've got the problem with conversation function with OpenSSH 3.5p1. When the message style is PAM_PROMPT_ECHO_ON, or PAM_PROMPT_ECHO_OFF everything is allright. But when I use PAM_TEXT_INFO, or PAM_ERROR_MSG, ssh prints nothing on the client side. Does anyone know the reason of

+llvmdev On Fri, Nov 12, 2010 at 7:57 AM, Jim Grosbach <grosbach at apple.com> wrote: > > On Nov 10, 2010, at 9:57 AM, Jason Kim wrote: > >> Refactoring the x86 dependent code from ELFObjectWriter class has >> repercussions among several (conflicting) axes of consideration, >> >> 1. namespace pollution - minimize pollution of the llvm:  namespace >> 2.

Probably, I''m not the first one who needs solve problem with p2p. Because, large part of my traffic is eaten by p2p software like KazAA, e-mule, Direct Connect etc, I''m looking for the way of detection of such traffic and marking it. However simple way with for instance 1214 port for KazAA doesn''t work because this software uses floating port technology. This traffic can