summaryrefslogtreecommitdiff
path: root/mail/p5-Mail-SRS
AgeCommit message (Collapse)AuthorFilesLines
2021-10-26mail: Replace RMD160 checksums with BLAKE2s checksumsnia1-2/+2
All checksums have been double-checked against existing RMD160 and SHA512 hashes The following distfiles were unfetchable (possibly fetched conditionally?): ./mail/qmail/distinfo netqmail-1.05-TAI-leapsecs.patch
2021-10-07mail: Remove SHA1 hashes for distfilesnia1-2/+1
2021-05-24*: recursive bump for perl 5.34wiz1-2/+2
2020-08-31*: bump PKGREVISION for perl-5.32.wiz1-2/+2
2019-11-02mail: align variable assignmentsrillig1-5/+5
pkglint -Wall -F --only aligned -r No manual corrections.
2019-08-11Bump PKGREVISIONs for perl 5.30.0wiz1-2/+2
2018-08-22Recursive bump for perl5-5.28.0wiz1-2/+2
2017-08-16Follow some http redirects.wiz1-2/+2
2017-06-05Recursive revbump from lang/perl5 5.26.0ryoon1-2/+2
2017-03-30CONFLICTS with libsrs2, to be added shortly.schmonz1-1/+3
2016-06-08Bump PKGREVISION for perl-5.24.wiz1-2/+2
2015-11-03Add SHA512 digests for distfiles for mail categoryagc1-1/+2
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-07-12Comment out dependencies of the stylewiz1-3/+3
{perl>=5.16.6,p5-ExtUtils-ParseXS>=3.15}:../../devel/p5-ExtUtils-ParseXS since pkgsrc enforces the newest perl version anyway, so they should always pick perl, but sometimes (pkg_add) don't due to the design of the {,} syntax. No effective change for the above reason. Ok joerg
2015-06-12Recursive PKGREVISION bump for all packages mentioning 'perl',wiz1-2/+2
having a PKGNAME of p5-*, or depending such a package, for perl-5.22.0.
2014-05-29Bump for perl-5.20.0.wiz1-2/+2
Do it for all packages that * mention perl, or * have a directory name starting with p5-*, or * depend on a package starting with p5- like last time, for 5.18, where this didn't lead to complaints. Let me know if you have any this time.
2013-12-09Fix/Update DEPENDS paterns for perl CORE modules, with some trivial fixes.obache1-4/+4
Bump PKGREVISION for runtime dependency pattern changed packages.
2013-11-24Comment out p5-Storable dependency; included in perl since 5.7.3.wiz1-3/+3
2013-05-31Bump all packages for perl-5.18, thatwiz1-2/+2
a) refer 'perl' in their Makefile, or b) have a directory name of p5-*, or c) have any dependency on any p5-* package Like last time, where this caused no complaints.
2012-10-08Drop PKG_DESTDIR_SUPPORT setting, "user-destdir" is default these days.asau1-3/+1
2012-10-03Bump all packages that use perl, or depend on a p5-* package, orwiz1-2/+2
are called p5-*. I hope that's all of them.
2011-08-14Revision bump after updating perl5 to 5.14.1.obache1-2/+2
2010-08-21Bump the PKGREVISION for all packages which depend directly on perl,seb1-2/+2
to trigger/signal a rebuild for the transition 5.10.1 -> 5.12.1. The list of packages is computed by finding all packages which end up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl, or PERL5_PACKLIST defined in their make setup (tested via "make show-vars VARNAMES=..."), minus the packages updated after the perl package update. sno@ was right after all, obache@ kindly asked and he@ led the way. Thanks!
2008-10-19Bump the PKGREVISION for all packages which depend directly on perl,he1-2/+2
to trigger/signal a rebuild for the transition 5.8.8 -> 5.10.0. The list of packages is computed by finding all packages which end up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl, or PERL5_PACKLIST defined in their make setup (tested via "make show-vars VARNAMES=...").
2008-06-12Add DESTDIR support.joerg1-1/+3
2007-10-25Remove empty PLISTs from pkgsrc since revision 1.33 of plist/plist.mkjlam1-1/+0
can handle packages having no PLIST files.
2007-03-19give away to pkgsrc-userstv1-2/+2
2006-03-22Use "tv@NetBSD.org" as my MAINTAINER address; makes identifying me as atv1-2/+2
PR-responsible person (such as I am ;) a little easier.
2005-08-06Bump the PKGREVISIONs of all (638) packages that hardcode the locationsjlam1-3/+2
of Perl files to deal with the perl-5.8.7 update that moved all pkgsrc-installed Perl files into the "vendor" directories.
2005-07-13Turn PERL5_PACKLIST into a relative path instead of an absolute path.jlam1-2/+2
These paths are now relative to PERL5_PACKLIST_DIR, which currently defaults to ${PERL5_SITEARCH}. There is no change to the binary packages.
2005-04-11Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.tv1-2/+1
2005-02-24Add RMD160 digests.agc1-1/+2
2004-12-20since perl is now built with threads on most platforms, the perl archlibgrant1-1/+2
module directory has changed (eg. "darwin-2level" vs. "darwin-thread-multi-2level"). binary packages of perl modules need to be distinguishable between being built against threaded perl and unthreaded perl, so bump the PKGREVISION of all perl module packages and introduce BUILDLINK_RECOMMENDED for perl as perl>=5.8.5nb5 so the correct dependencies are registered and the binary packages are distinct. addresses PR pkg/28619 from H. Todd Fujinaka.
2004-11-29Update to 0.31. Fix HOMEPAGE (moved).tv3-15/+10
Notable changes (no changelog to speak of): - added srsc command line client to srsd - fixed upper/lower case comparisons in domain matching
2004-03-29Moved from pkgsrc-wip (http://pkgsrc-wip.sourceforge.net/):tv5-0/+70
The Sender Rewriting Scheme preserves .forward functionality in an SPF-compliant world. SPF requires the SMTP client IP to match the envelope sender (return-path). When a message is forwarded through an intermediate server, that intermediate server may need to rewrite the return-path to remain SPF compliant. If the message bounces, that intermediate server needs to validate the bounce and forward the bounce to the original sender. SRS provides a convention for return-path rewriting which allows multiple forwarding servers to compact the return-path. SRS also provides an authentication mechanism to ensure that purported bounces are not arbitrarily forwarded.