1 <?xml version="1.0" encoding="UTF-8"?>
2 <!DOCTYPE pkgmetadata SYSTEM "https://www.gentoo.org/dtd/metadata.dtd">
5 <email>maintainer-needed@gentoo.org</email>
7 <longdescription lang="en">
8 This is sieve-connect. A client for the ManageSieve protocol,
9 as specifed in RFC 5804. Historically, this was MANAGESIEVE as
10 implemented by timsieved in Cyrus IMAP. This software is licensed
11 and the terms are provided in the file "LICENSE" as supplied
12 with this software (BSD license without the advertising clause).
14 SIEVE is an RFC-specified language for mail filtering, which at
15 time of writing is specified in a list of RFCs at the end of this
16 document, plus various drafts, both IETF and individual submissions.
17 It's designed to be regular enough for machines to be able to
18 manipulate, whilst still being editable by humans. Alas, not many
19 clients actually implement this instead of embedding their own
20 internal codes in sieve comments, defeating the goal of being able
21 to edit with a client of your choice.
23 This is not yet fully compatible with RFC 5804, but is moving
24 towards that from the timsieved baseline; some issues to be
25 worked on are documented in the "TODO" file.
27 sieve-connect speaks ManageSieve and supports TLS for connection
28 privacy and also authentication if using client certificates.
29 sieve-connect will use SASL authentication; SASL integrity layers
30 are not supported, use TLS instead. GSSAPI-based authentication
31 should generally work, provided that client and server can use a
32 common underlaying protocol. If it doesn't work for you, please
35 sieve-connect is designed to be both a tool which can be invoked
36 from scripts and also a decent interactive client. It should also
37 be a drop-in replacement for "sieveshell", as supplied with Cyrus
41 <bugs-to>https://github.com/syscomet/sieve-connect/issues</bugs-to>
42 <remote-id type="github">syscomet/sieve-connect</remote-id>