./mail/dovecot2-pigeonhole, Support for the Sieve language and the ManageSieve protocol

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]

Branch: CURRENT, Version: 0.5.19, Package name: dovecot-pigeonhole-0.5.19, Maintainer: adam

This package is part of the Pigeonhole project (http://pigeonhole.dovecot.org).
It adds support for the Sieve language (RFC 5228) and the ManageSieve protocol
(RFC 5804) to the Dovecot Secure IMAP Server.

The Sieve language is used to specify how e-mail needs to be processed. By
writing Sieve scripts, users can customize how messages are delivered, e.g.
whether they are forwarded or stored in special folders. Unwanted messages can
be discarded or rejected, and, when the user is not available, the Sieve
interpreter can send an automated reply. Above all, the Sieve language is meant
to be simple, extensible and system independent. And, unlike most other mail
filtering script languages, it does not allow users to execute arbitrary
programs. This is particularly useful to prevent virtual users from having full
access to the mail store. The intention of the language is to make it impossible
for users to do anything more complex (and dangerous) than write simple mail

Using the ManageSieve protocol, users can upload their Sieve scripts remotely,
without needing direct filesystem access through FTP or SCP. Additionally,
aManageSieve server always makes sure that uploaded scripts are valid,
preventing compile failures at mail delivery.

This package provides Sieve support as a plugin to Dovecot's Local Delivery
Agent (LDA) and Dovecot's LMTP service. The ManageSieve protocol is provided is
an additional service, next to Dovecot's own POP3 and IMAP services.

Required to run:

Required to build:

Master sites:

Filesize: 1908.348 KB

Version history: (Expand)

CVS history: (Expand)

   2022-05-11 11:28:07 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
dovecot2-pigeonhole: updated to 0.5.19

This release is done to maintain parity with dovecot 2.3.19 release, so it does \ 
not contain any news-worthy changes.
   2022-02-03 22:02:53 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
dovecot2-pigeonhole: updated to 0.5.18


	- duplicate: Users without a home directory can crash with Sieve when
	  using duplicate database. v2.3.17 regression.
	- imapsieve: When mail was expunged when processing imapsieve events, a
	  crash could occur. Fixes Panic: file mail-index-map.c:
	  line 558 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0)
	- managesieve-login: Proxy didn't support forwarding the forward_* passdb fields.
	- redirect: Sieve would crash if redirect after keep-equivalent action failed.
	- sieve: Interpreter crashes when the Sieve index extension is used with
	  index zero.
	- vnd.dovecot.filter: Envelope sender string may become corrupted when
	  Sieve scripts are using vnd.dovecot.filter. This could end up
	  corrupting mbox's From line and return wrong envelope sender string in
	  Sieve tests.
   2021-12-07 17:58:04 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
dovecot2-pigeonhole: updated to
- managesieve: Dovecot failed to start if ssl_ca was too large.
- lib-sieve-tool: Binaries failed to run if ssl_ca was too large.
   2021-11-02 13:04:39 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
dovecot2-pigeonhole: updated to 0.5.17

- duplicate: The Sieve duplicate test is prone to false negatives when
  the user receives many e-mails concurrently, meaning that duplicate
  deliveries can still occur.
- fileinto: v2.3.16 regression: Sieve delivery crashes if mail is
  delivered to non-existing and existing folder.
- imap-filter-sieve: v2.3.15 regression: The CPU limits on Sieve
  execution are too easily exceeded in IMAP context (the IMAPSieve and
  FILTER=SIEVE capabilities). Changed the default to unlimited CPU time
  for IMAP context, since similar excessive resource usage can be caused
  by other means as well. The CPU limits on Sieve scripts executed at
  LDA/LMTP delivery are still enforced by default.
- redirect:  The Sieve redirect action has protections against users
  triggering mail loops. Unfortunately, the detection of a redirect mail
  loop sometimes causes the message to get lost if no other Sieve action
  is applied that delivers the message somewhere else.
- redirect: v2.3.16 regression: With certain Sieve scripts if redirect
  fails due to temporary failure, the lmtp process may crash after the
  delivery. Fixes:
  Panic: file mail-user.c: line 229 (mail_user_deinit):
  assertion failed: ((*user)->refcount == 1).
   2021-10-26 12:54:34 by Nia Alarie | Files touched by this commit (356)
Log message:
mail: Replace RMD160 checksums with BLAKE2s checksums

All checksums have been double-checked against existing RMD160 and
SHA512 hashes

The following distfiles were unfetchable (possibly fetched

./mail/qmail/distinfo netqmail-1.05-TAI-leapsecs.patch
   2021-10-07 16:25:52 by Nia Alarie | Files touched by this commit (357)
Log message:
mail: Remove SHA1 hashes for distfiles
   2021-08-08 17:51:18 by Amitai Schleier | Files touched by this commit (2)
Log message:
Update to 0.5.16. From the changelog:

* .dovecot.sieve.log file now includes year in the header.
* Change Sieve script result execution to delay definitive action
  execution to the end of a successful Sieve script execution session.
  This is part of an effort to solve problems with the Sieve duplicate
  test. As a side-effect, some rare temporary-error cases yield
  different results, in which partial failure is more likely.
   2021-06-21 17:34:59 by Takahiro Kambe | Files touched by this commit (2) | Package updated
Log message:
mail/dovecot2-pigeonhole: update to 0.5.15

Security release.

v0.5.15 2021-06-21  Aki Tuomi <aki.tuomi@open-xchange.com>

* CVE-2020-28200: Sieve interpreter is not protected against abusive
  scripts that claim excessive resource usage. Fixed by limiting the
  user CPU time per single script execution and cumulatively over
  several script runs within a configurable timeout period. Sufficiently
  large CPU time usage is summed in the Sieve script binary and execution
  is blocked when the sum exceeds the limit within that time. The block
  is lifted when the script is updated after the resource usage times out.
* Disconnection log messages are now more standardized across services.
  They also always now start with "Disconnected" prefix.
- managesieve: Commands pipelined together with and just after the
  authenticate command cause these commands to be executed twice.