CVS log for pkgsrc/mail/p5-Mail-Sender-Easy/distinfo

Up to [cvs.NetBSD.org] / pkgsrc / mail / p5-Mail-Sender-Easy

Request diff between arbitrary revisions

Keyword substitution: kv
Default branch: MAIN

mail: Replace RMD160 checksums with BLAKE2s checksums

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

mail: Remove SHA1 hashes for distfiles

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.

Import mail/p5-Mail-Sender-Easy-0.0.5 into pkgsrc

Mail::Sender's one problem is its a bit cumbersome to use, with so
many options and things to open, close, the whole thing, parts,
multiparts etc etc., and several ways to check for successs. Its
hard to remember what needs done at what point with what data to
do what you want and then which way you check what data based on
what was done to see if it worked or not.

This module's aim is to make all of that ``Easy''

It does so by providing a single function (and method) to send mail
based on an (IMHO) easier to work with hashref and returns true or
false on success or failer and sets $@ to any errors.

The EXAMPLE section shows an ``email or die'' that will send an
email using SMTP Auth on port 26 with text and html parts, the html
part has a smiley gif embedded inline and a PDF attached and a high
priority flag and read and delivery receipt requests. It will take
you seconds to customize it to send that to yourself (and its
``Easy'' to understand what its going on without having to understand
the intracacies of SMTP and MIME messages.

Initial revision