Path to this page:
./
mail/dovecot2-pigeonhole,
Support for the Sieve language and the ManageSieve protocol
Branch: pkgsrc-2020Q4,
Version: 0.5.13,
Package name: dovecot-pigeonhole-0.5.13,
Maintainer: adamThis 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
filters.
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.
Master sites:
SHA1: efd0ae2ebaa1b6ce7178adce84e3613fbec1bc43
RMD160: 65d6ea36b2470dd9b6d2a9258341106d80ff06fd
Filesize: 1864.101 KB
Version history: (Expand)
- (2021-01-04) Updated to version: dovecot-pigeonhole-0.5.13
- (2021-01-04) Package added to pkgsrc.se, version dovecot-pigeonhole-0.5.11nb2 (created)
CVS history: (Expand)
2021-01-04 18:40:06 by Benny Siegert | Files touched by this commit (2) | |
Log message:
Pullup ticket #6392 - requested by taca
mail/dovecot2-pigeonhole: dependent update
Revisions pulled up:
- mail/dovecot2-pigeonhole/Makefile 1.60
- mail/dovecot2-pigeonhole/distinfo 1.45
---
Module Name: pkgsrc
Committed By: taca
Date: Mon Jan 4 14:58:26 UTC 2021
Modified Files:
pkgsrc/mail/dovecot2-pigeonhole: Makefile distinfo
Log message:
mail/dovecot2-pigeonhole: update to 0.5.13
Update dovecot2-pigeonhole package to 0.5.13.
v0.5.13 2021-01-04 Aki Tuomi <aki.tuomi@open-xchange.com>
- duplicate: The test was handled badly in a multiscript (sieve_before,
sieve_after) scenario in which an earlier script in the sequence with
a duplicate test succeeded, while a later script caused a runtime
failure. In that case, the message is recorded for duplicate tracking,
while the message may not actually have been delivered in the end.
- editheader: Sieve interpreter entered infinite loop at startup when
the "editheader" configuration listed an invalid header name. This
problem can only be triggered by the administrator.
- relational: The Sieve relational extension can cause a segfault at
compile time. This is triggered by invalid script syntax. The segfault
happens when this match type is the last argument of the test command.
This situation is not possible in a valid script; positional arguments
are normally present after that, which would prevent the segfault.
- sieve: For some Sieve commands the provided mailbox name is not
properly checked for UTF-8 validity, which can cause assert crashes at
runtime when an invalid mailbox name is encountered. This can be
caused by the user by writing a bad Sieve script involving the
affected commands ("mailboxexists", "specialuse_exists").
This can be triggered by the remote sender only when the user has
written a Sieve script that passes message content to one of the
affected commands.
- sieve: Large sequences of 8-bit octets passed to certain Sieve
commands that create or modify message headers that allow UTF-8 text
(vacation, notify and addheader) can cause the delivery or IMAP
process (when IMAPSieve is used) to enter a memory-consuming
semi-infinite loop that ends when the process exceeds its memory
limits. Logged in users can cause these hangs only for their own
processes.
|