similar to: Released Pigeonhole Sieve v0.1.16 for Dovecot v1.2.11

Hello Dovecot users, It's been a while since the last Pigeonhole Sieve and ManageSieve releases. That is why this release includes quite a few changes. Most interestingly, the include extension is updated to match the most recent specification, the Sieve interpreter now includes plugin support and ManageSieve now has support for enforcing quota on the size of scripts, the number of

Hello Dovecot users, It's been a while since the last Pigeonhole Sieve and ManageSieve releases. That is why this release includes quite a few changes. Most interestingly, the include extension is updated to match the most recent specification, the Sieve interpreter now includes plugin support and ManageSieve now has support for enforcing quota on the size of scripts, the number of

Hello Dovecot users, Now that Dovecot v2.2.13 is released, I can release a new Pigeonhole. Due to changes in Dovecot, this Pigeonhole release will not compile cleanly against older Dovecot releases. This release is mainly about bugfixes. One notable addition is that I have updated the "vnd.dovecot.duplicate" extension to the new IETF draft "duplicate" extension. Changelog

Hello Dovecot users, Now that Dovecot v2.2.13 is released, I can release a new Pigeonhole. Due to changes in Dovecot, this Pigeonhole release will not compile cleanly against older Dovecot releases. This release is mainly about bugfixes. One notable addition is that I have updated the "vnd.dovecot.duplicate" extension to the new IETF draft "duplicate" extension. Changelog

Hi! I've got a segfault in managesieve while using: sieve_extensions = -vacation -reject -spamtest -virustest -enotify -redirect The problem seems to lie in "-redirect". Reason for excluding "redirect" from sieve is my users should not use sieve to forward or redirect mails but use an external method (web-script to set LDAP attribute) which checks several things like

Hello Dovecot users, I've been busy recently with some wholly unrelated Dovecot IMAP patches, so Sieve development moved a bit into the background. This release therefore consists mostly of small bugfixes. The most important change is the fix of a bug in ManageSieve's CHECKSCRIPT command that causes a segfault. Quite a few people have encountered this problem recently, so it is about

Hello Dovecot users, I've been busy recently with some wholly unrelated Dovecot IMAP patches, so Sieve development moved a bit into the background. This release therefore consists mostly of small bugfixes. The most important change is the fix of a bug in ManageSieve's CHECKSCRIPT command that causes a segfault. Quite a few people have encountered this problem recently, so it is about

hello, on the wiki, https://wiki2.dovecot.org/MailboxFormat/dbox, it says that one can use either doveadm fetch or doveadm import, however I can find no correct syntax with fetch that'll actually work. Is the idea to simply override the mail_location with -o ? That seems to work for doveadm mailbox but not for doveadm fetch or search # doveadm -f table mailbox status -u johan all dovecot

Hi, I am trying to use dovecot replication for a two-way sync. And whatever I do, sieve-scripts won?t replicate. Mails replicate near instantaneous. When I disable the sieve-script in roundcube, the other server will create in the home of the user on the other side a folder sieve/tmp but enabling won?t create the roundcube.sieve and the symlink .dovecot.sieve -> sieve/roundcube.sieve The

Hi, I have a machine running dovecot 2.0 rc4 and I can't seem to get the imap_quota plugin working, every time I try to read the quotas, I get the following in my log: > Aug 7 11:58:43 talyn dovecot: imap(chutz): Error: quotactl(Q_GETQUOTA, rootfs) failed: No such file or directory > Aug 7 11:59:53 talyn dovecot: imap(chutz): Error: quotactl(Q_GETQUOTA, rootfs) failed: No such file

I'm attempting to build Pigeonhole 0.2.3 for use with my Dovecot 2.0.12 installation on Slackware. I've downloaded the sources and unzipped into a folder which sits alongside the folder in which I built Dovecot. When I ./configure, the configuration appears to complete without error. However, when I make, the compiler throws lots of errors all stemming, I believe from its failure

Hello, Before I get in to my question is ssl on 993 or starttls on 143 better from a security perspective? I've noticed that I've got a dovecot listener on port 993, below is my doveconf -n output I don't have an imaps listener uncommented should I do so and set it's port to 0? Will that disable the 993 listener? Thanks. Dave. # 2.3.10 (0da0eff44):

Hello, I'm trying to set up a public folder called TestFolder. I'm getting this error: #doveadm acl get -A "Public/TestFolder" doveadm(username at example.com): Error: Can't open mailbox Public/TestFolder: Mailbox doesn't exist: Public/TestFolder Username ID Global Rights # ls -ld /var/vmail/public drwx------ 4 vmail vmail 512 Apr 15 23:17 public/ # ls -ld

Hello, I'm running dovecot 2.2 and trying to do last login tracking. I am using a MySQL database. When a user logs in I get this in the log: 2018-04-07 16:55:14 imap(user at example.com)<54415><BmevY0hpMN5/AAAB>: Error: last_login_dict: Failed to write value for user user at example.com: dict-server returned failure: sql dict: commit failed: Field 'name' doesn't have

Hello, I'm running Dovecot on a FreeBSD system with Postfix in a virtual user setup, with Mysql. I am trying to understand the quota configuration. I've got a Mysql database with an accounts table with a quota field. I've also got two other tables one quota (currently has nothing in it an empty set), and quota2 messages and bytes which has one entry. My goal is to have different

Hello Dovecot users, The recent release of Dovecot v1.2.15 is a good opportunity to release new versions of Sieve and ManageSieve for Dovecot v1.2. These releases consist entirely of bugfixes and introduce no new features. Changelog Sieve v0.1.18: - Imap4flags: fixed segfault bug occuring in multiscript context. Occured in specific situations when a script using imap4flags was

Hello Dovecot users, The recent release of Dovecot v1.2.15 is a good opportunity to release new versions of Sieve and ManageSieve for Dovecot v1.2. These releases consist entirely of bugfixes and introduce no new features. Changelog Sieve v0.1.18: - Imap4flags: fixed segfault bug occuring in multiscript context. Occured in specific situations when a script using imap4flags was

Hello, I've got a few misc issues that I'm trying to get a handle on. I'm having what is probably a simple error with last logins. It's not working, unable to write values to the database. Here's the log lines: 2018-04-10 10:43:34 imap-login: Info: Login: user=<user at domain.com>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=75934, TLS,

Hello Dovecot users, I have finally finished the first release of Pigeonhole for Dovecot v2.0. The most notable change from previous Dovecot v1.2 Sieve/ManageSieve releases is that all is now integrated in a single package and there is no need to patch Dovecot anymore to gain ManageSieve support. Changelog v0.2.0: * Merged Sieve and ManageSieve packages into a single Pigeonhole

Hello Dovecot users, I have finally finished the first release of Pigeonhole for Dovecot v2.0. The most notable change from previous Dovecot v1.2 Sieve/ManageSieve releases is that all is now integrated in a single package and there is no need to patch Dovecot anymore to gain ManageSieve support. Changelog v0.2.0: * Merged Sieve and ManageSieve packages into a single Pigeonhole