|Commit History - (may be incomplete: see SVNWeb link above for full details)
|20 Sep 2013 19:59:14
Add NO_STAGE all over the place in preparation for the staging support (cat:
|14 Sep 2013 18:12:50
- convert to the new perl5 framework
- convert USE_GMAKE to Uses
Approved by: portmgr (bapt@, blanket)
|29 Jul 2013 23:12:53
mail/sieve-connect: update to 0.86
- Update to 0.86
Submitted by: Alexey Degtyarev <alexey renatasystems.org> (maintainer)
|15 Apr 2013 12:28:58
- Update to 0.85
- Convert to new options framework
sieve-connect was not actually verifying TLS certificate identities matched
the expected hostname. Changes with new version:
Fix TLS verification; find server by own hostname & SRV.
* TLS hostname verification was not actually happening.
* IO::Socket::SSL requirement bumped to 1.14 (was 0.97).
* By default, if no server specified, before falling back to localhost try to
use the current hostname and SRV records in DNS to figure out if Sieve is
available. Checks for sieve, imaps & imap protocol SRV records and honours(Only the first 15 lines of the commit message are shown above )
|02 Mar 2013 03:55:26
Variable that start with _ are considered private to the defining
makefile and may not be used by ports makefiles.
In addition, avoid problems should the defaults ever change.
Approved by: portmgr (tabthorpe)
|01 Dec 2012 20:18:50
Update to 0.84.
Trim header and cosmetic fix to PLIST_FILES.
Submitted by: "Alexey V. Degtyarev" <email@example.com> (maintainer)
Feature safe: yes
|25 May 2012 12:49:34
- Update to 0.83
Submitted by: Alexey V. Degtyarev <firstname.lastname@example.org> (maintainer)
|26 Jun 2011 08:12:57
This is sieve-connect. A client for the ManageSieve protocol, as specifed in
RFC 5804. Historically, this was MANAGESIEVE as implemented by timsieved in
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
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.
Submitted by: Alexey V. Degtyarev <alexey at renatasystems.org>