Commit graph

2 commits

Author SHA1 Message Date
agc
ddbf6ddecd Add SHA512 digests for distfiles for mail category
Problems found locating distfiles:
	Package mutt: missing distfile patch-1.5.24.rr.compressed.gz
	Package p5-Email-Valid: missing distfile Email-Valid-1.198.tar.gz
	Package pine: missing distfile fancy.patch.gz
	Package postgrey: missing distfile targrey-0.31-postgrey-1.34.patch
	Package qmail: missing distfile badrcptto.patch
	Package qmail: missing distfile outgoingip.patch
	Package qmail: missing distfile qmail-1.03-realrcptto-2006.12.10.patch
	Package qmail: missing distfile qmail-smtpd-viruscan-1.3.patch
	Package thunderbird24: missing distfile enigmail-1.7.2.tar.gz
	Package thunderbird31: missing distfile enigmail-1.7.2.tar.gz

Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden).  All existing
SHA1 digests retained for now as an audit trail.
2015-11-03 23:27:00 +00:00
tv
0806b46b7b Add p5-IMAP-Client-0.13 (and its small dependency, p5-URI-imap).
From DESCR:

This module was created as a low-level inteface to any IMAP server.  It
was built to be a 'clear box' solution to working with an IMAP environ-
ment.  The idea is that anything an IMAP client should be able to do,
and any information available via the IMAP specs, should be available
to a client interface and user.  This way, the full strength of the
IMAP protocol and data can be utilized, ideally in the most network-
efficient mannger possible, rather than being contrained only to a sub-
set of commands or data-limited responses.  If the server says it, the
client should be able to see it.

This module also takes steps to be able to handle anticipated situa-
tions for the user rather than forcing a per-implementation behavior
for such expected events, such as referrals.  IMAP::Client will fully
support referrals, and will transparently handle them for whatever com-
mand is issued to them (so long as the referral s for anonymous or the
same user with the same password - a new user or different password
would require a new username/password to be obtained.  As of 0.01, this
is not supported, however the framework is down.

This module also tries to follow the various RFCs for IMAPrev1 communi-
cations very closely, enforcing client-side responsabilities where
appropriate.
2007-10-11 15:49:55 +00:00