Commit graph

8 commits

Author SHA1 Message Date
Baptiste Daroussin
fd61959c15 Add NO_STAGE all over the place in preparation for the staging support (cat: mail) 2013-09-20 19:59:12 +00:00
Andrej Zverev
69b6f05b28 - convert to the new perl5 framework
- convert USE_GMAKE to Uses

Approved by:	portmgr (bapt@, blanket)
2013-09-14 18:12:50 +00:00
William Grzybowski
7d321876ff mail/sieve-connect: update to 0.86
- Update to 0.86

Changes:
http://people.spodhuis.org/phil.pennock/software/sieve-connect.ChangeLog.txt

PR:		ports/180930
Submitted by:	Alexey Degtyarev <alexey renatasystems.org> (maintainer)
2013-07-29 23:12:53 +00:00
Bryan Drewery
1e02c1f16f - 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
target==. to mean "no".

* This works better with the Mozilla::PublicSuffix module installed.

* Added ability to blacklist authentication mechanisms

More info:

http://mail.globnix.net/pipermail/sieve-connect-announce/2013/000005.html

PR:		ports/177859
Submitted by:	"Alexey V. Degtyarev" <alexey@renatasystems.org> (maintainer)
Approved by:	portmgr (implicit)
Security:	a2ff483f-a5c6-11e2-9601-000d601460a4
2013-04-15 12:28:58 +00:00
Eitan Adler
b7b9ec7a12 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)
2013-03-02 03:55:25 +00:00
Wesley Shields
3692af59fa Update to 0.84.
Trim header and cosmetic fix to PLIST_FILES.

PR:		ports/173990
Submitted by:	"Alexey V. Degtyarev" <alexey@renatasystems.org> (maintainer)
Feature safe:	yes
2012-12-01 20:18:50 +00:00
Sylvio Cesar Teixeira
53159b05e7 - Update to 0.83
PR:		ports/168312
Submitted by:	Alexey V. Degtyarev <alexey@renatasystems.org> (maintainer)
2012-05-25 12:49:34 +00:00
Martin Wilke
5c4d327347 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 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.

WWW: http://people.spodhuis.org/phil.pennock/software/

PR:		ports/157077
Submitted by:	Alexey V. Degtyarev <alexey at renatasystems.org>
2011-06-26 08:12:57 +00:00