diff --git a/mail-filter/sieve-connect/Manifest b/mail-filter/sieve-connect/Manifest
new file mode 100644
index 0000000..a925aba
--- /dev/null
+++ b/mail-filter/sieve-connect/Manifest
@@ -0,0 +1 @@
+DIST sieve-connect-0.90.tar.bz2 46481 BLAKE2B d6bc466caffa3344537b1777b00a66f34697139d474763862c5296367f1e69174078a5e864225c1e967fbc5677c97d3ef71a4b75b677952d7b4993a5b8a08108 SHA512 3b4d4a6a7eb7d48f8b2dbc4c302c3de1a2a193282c7b2d25581e1131d6c7598cc2a47edabf8b108e94e0fd1a9cc50e48a103c133dba233f180f12d36c0da0718
diff --git a/mail-filter/sieve-connect/metadata.xml b/mail-filter/sieve-connect/metadata.xml
new file mode 100644
index 0000000..39c19c0
--- /dev/null
+++ b/mail-filter/sieve-connect/metadata.xml
@@ -0,0 +1,42 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+	<!-- maintainer-needed -->
+	<longdescription lang="en">
+		This is sieve-connect. A client for the ManageSieve protocol,
+		as specifed in RFC 5804. Historically, this was MANAGESIEVE as
+		implemented by timsieved in Cyrus IMAP. This software is licensed
+		and the terms are provided in the file "LICENSE" as supplied
+		with this software (BSD license without the advertising clause).
+
+		SIEVE is an RFC-specified language for mail filtering, which at
+		time of writing is specified in a list of RFCs at the end of this
+		document, plus various drafts, both IETF and individual submissions.
+		It's designed to be regular enough for machines to be able to
+		manipulate, whilst still being editable by humans. Alas, not many
+		clients actually implement this instead of embedding their own
+		internal codes in sieve comments, defeating the goal of being able
+		to edit with a client of your choice.
+
+		This is not yet fully compatible with RFC 5804, but is moving
+		towards that from the timsieved baseline; some issues to be
+		worked on are documented in the "TODO" file.
+
+		sieve-connect speaks ManageSieve and supports TLS for connection
+		privacy and also authentication if using client certificates.
+		sieve-connect will use SASL authentication; SASL integrity layers
+		are not supported, use TLS instead. GSSAPI-based authentication
+		should generally work, provided that client and server can use a
+		common underlaying protocol. If it doesn't work for you, please
+		report the issue.
+
+		sieve-connect is designed to be both a tool which can be invoked
+		from scripts and also a decent interactive client. It should also
+		be a drop-in replacement for "sieveshell", as supplied with Cyrus
+		IMAP.
+	</longdescription>
+	<upstream>
+		<bugs-to>https://github.com/syscomet/sieve-connect/issues</bugs-to>
+		<remote-id type="github">syscomet/sieve-connect</remote-id>
+	</upstream>
+</pkgmetadata>
diff --git a/mail-filter/sieve-connect/sieve-connect-0.90.ebuild b/mail-filter/sieve-connect/sieve-connect-0.90.ebuild
new file mode 100644
index 0000000..cee4de6
--- /dev/null
+++ b/mail-filter/sieve-connect/sieve-connect-0.90.ebuild
@@ -0,0 +1,32 @@
+# Copyright 1999-2020 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+
+DESCRIPTION="Sieve Command Line Interface"
+HOMEPAGE="https://people.spodhuis.org/phil.pennock/software/"
+SRC_URI="https://github.com/syscomet/sieve-connect/releases/download/v${PV}/${P}.tar.bz2"
+
+LICENSE="BSD"
+SLOT="0"
+KEYWORDS="~amd64 ~x86"
+
+DEPEND=">=dev-lang/perl-5"
+RDEPEND="${DEPEND}
+	>=dev-perl/Authen-SASL-2.11
+	dev-perl/IO-Socket-INET6
+	>=dev-perl/IO-Socket-SSL-0.97
+	dev-perl/Net-DNS
+	dev-perl/Net-SSLeay
+	dev-perl/TermReadKey
+	dev-perl/Term-ReadLine-Gnu"
+
+src_compile() {
+	emake all sieve-connect.1
+}
+
+src_install() {
+	dobin sieve-connect
+	doman sieve-connect.1
+	dodoc README*
+}