similar to: Error: Internal quota calculation error

I'm trying to get the pipe backend to work with the new dovecot-antispam (I was very pleased to see the new version, thanks Johannes!) Before I would run the following over the maildir: spamc -d 10.0.1.109 -L ham < $file 2>&1 > /dev/null now, i'm using dovecot-antispam and mdbox and have the following configured: antispam_backend = pipe antispam_signature = X-Spam-Flag

Hi, TL;DR: I am having a hard time synthesizing the information I need out of the website/wiki documentation, and google isn't turning up what I need, so I'm looking for advice on what I should read next to understand the way aliases, dovecot's lmtp, and pigeonhole work together. Details below. I've been using dovecot happily for some years, but in a recent migration of my mail

Am 08.03.2015 um 09:08 schrieb E.B.: > Also, of course I have entered this in 90-plugins.conf > > plugin { > seive_plugins = sieve_extdata sieve_extprograms > maybe you have a typo... seive != sieve

Hi, I just want some clarification on how Dovecot's IMAP assigns UIDs when it picks files from the "new" directory of a Maildir. What I am observing is that only ctime has a role to play in it. For example if there are two files in "new", a.msg & z.msg. Even when a.msg has lower mtime than z.msg and "a" comes before "z" alphabetically, dovecot

> > I have some global scripts that were running nicely. > > > > Then I opened one in an editor and (probably, but not 100% sure) > > mindlessly saved the file, even though I hadn't made any changes. > > > > Shortly after, Sieve errors started showing in the log: > > > > Error: 4k5JA74R/1TlIwABG/SpMA: sieve: binary save: failed to create

Hello, I am currently trying to setup dovecot with a director instance and have managed to configure to invocations of dovecot on my server but my dovecot log keeps giving me errors about authentication. ?A little background on my config I am running dovecot with postfix and using an LDAP directory. Here are the errors I am seeing in my logs. dovecot.log Jun 02 10:42:59 auth: Fatal: LDAP:

http://dovecot.org/releases/2.1/dovecot-2.1.9.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.9.tar.gz.sig I've again mostly finished reading and answering most of the mails in Dovecot mailing list. There are a couple annoyingly difficult / time consuming bugreport mails that I haven't replied to yet, but if anyone thinks I should have replied to something already feel free to resend

http://dovecot.org/releases/2.1/dovecot-2.1.9.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.9.tar.gz.sig I've again mostly finished reading and answering most of the mails in Dovecot mailing list. There are a couple annoyingly difficult / time consuming bugreport mails that I haven't replied to yet, but if anyone thinks I should have replied to something already feel free to resend

Hi, As the "new Sieve implementation" is using a "gratefully stolen copy of deliver.c from dovecot" (i.e. a dirty code in mail-raw.c), would it be possible for the Sieve piece 1 - to be using files from dovecot directly rather than copying&changing it (which is very bad for maintenance) 2 - to be incorporated in the hg/mercurial tree of dovecot ? Thanks a lot

> > > > I have some global scripts that were running nicely. > > > > > > > > Then I opened one in an editor and (probably, but not 100% sure) > > > > mindlessly saved the file, even though I hadn't made any changes. > > > > > > > > Shortly after, Sieve errors started showing in the log: > > > > > > >

why does dovecot touch any ever used fuse-mountpoint and scream at the next start that is no longer mounted? "If this is intentional, remove it with doveadm mount" why if i never called "doveadm" on any setup at all? Jul 10 09:10:56 rh dovecot: master: Dovecot v2.1.8 starting up (core dumps disabled) Jul 10 09:10:56 rh dovecot: master: Warning: /sys/fs/cgroup/cpu is no longer

I have installed dovecot and sieve using the FreeBSD ports. Authentication is against a MySql Database. Dovecot is running using deliver as the LDA. But when I try to Sieve I get the following error in /var/log/dovecot.log deliver(mike at systemrt.com): Apr 19 14:07:19 Info: Loading modules from directory: /usr/local/libexec/dovecot deliver(mike at systemrt.com): Apr 19 14:07:19 Fatal: Plugin

Hello, I have a dovecot 2.2.6 on a Linux platform. I have configured manageseive extension. I have opened the manageseive port (4190) to entire world. (since I need my thunderbird and other clients to create seive scripts). I just wanted to know if it is ok to open that port to everyone, and get some feedback on some security measures specific to manageseive. -Thanks in advance Vijay PS: I

On 17 Oct 2015, at 10:24, Akash <akbwiz+dovecot at gmail.com> wrote: > > Hi, > > I just want some clarification on how Dovecot's IMAP assigns UIDs when it picks files from the "new" directory of a Maildir. What I am observing is that only ctime has a role to play in it. For example if there are two files in "new", a.msg & z.msg. Even when a.msg has

> > > I have some global scripts that were running nicely. > > > > > > Then I opened one in an editor and (probably, but not 100% sure) > > > mindlessly saved the file, even though I hadn't made any changes. > > > > > > Shortly after, Sieve errors started showing in the log: > > > > > > Error: 4k5JA74R/1TlIwABG/SpMA:

Hello All, I have built up my email server with exim + dovecot + clamv/spamassasin. I am using exim as LDA(local delivery agent). I was reading about using dovecot as LDA but I couldn't find why should I use it? Now, I am looking expert advice on "Why should I use dovecot LDA" ? Is there any benefit in terms of functionality or performance ? Any advice/suggestion/feedbacks

Hi, On a new install-from-source with Dovecot 2.2.16rc1, Piegeonhole 0.4.6 and a grab of the newest Extdata code, I confirmed basic Sieve functionality is working (made a simple sieve script with a test on message subject resulting in a fileinto action). But I cannot get Sieve to see Extdata or Extprograms. sievec reports "Warning: sieve: ignored unknown extension

Hello, What is the best way to hide sieve folders from IMAP clients? old config mail_home = /var/vmail/%d/%n plugin { sieve_dir = /var/vmail/%d/%n/.sieve/ sieve = /var/vmail/%d/%n/.dovecot.sieve } new config (hide sieve folder) mail_home = /var/vmail/%d/%n maildir_stat_dirs = yes plugin { sieve_dir = /var/vmail/%d/%n/sieve/ sieve = /var/vmail/%d/%n/.dovecot.sieve } Is there a better way

From the digest: On Aug 14, 2007, at 1:04 PM, dovecot-request at dovecot.org wrote: other messages cut out? > > > Message: 9 > Date: Tue, 14 Aug 2007 19:03:58 +0200 > From: martin f krafft <madduck at madduck.net> > Subject: Re: [Dovecot] use of deliver from procmail advisable? > To: dovecot at dovecot.org > Message-ID: <20070814170358.GA17390 at

I have some global scripts that were running nicely. Then I opened one in an editor and (probably, but not 100% sure) mindlessly saved the file, even though I hadn't made any changes. Shortly after, Sieve errors started showing in the log: Error: 4k5JA74R/1TlIwABG/SpMA: sieve: binary save: failed to create temporary file: open(/usr/local/var/dovecot/sieve/script2.svbin.example.com.4139.)